Taking Orders Via Massive

[AusIV]

It should be possible to fill an order by piping it into massive.

[jmozah]

How are you thinking about the flow?

massive 0x csv ........ | massive 0x upload --target http://localhost:8081| massive 0x fill --target http://localhost:18545 privkey.1.asc

will the above be okay?

[AusIV]

Not quite:

I'd probably use the term "fill" instead of "match".

In 0x terminology, "match" generally implies that you have two orders and the relayer is matching them to eachother, resulting in both getting filled. I would see the massive pipeline filling orders via a particular account, not trying to match two orders.

Additionally, the "upload" stage is a sink - it consumes messages without passing them on. It wouldn't make sense for something to immediately follow that.

I had kind of envisioned the workflow for this going along with the subcommand for #5

So essentially:

massive 0x csv ........ | massive 0x upload --target http://localhost:8081

would be one command, followed by a separate:

massive 0x query --target http://localhost:8081 --maker-token=0x... --taker-token=0x... --exchange=0x... | ./proprietary-filtering-script.sh | massive 0x fill --rpc http://localhost:8545 --key mykey.priv

So the query subcommand would hit the SRA to find potential orders, the user can write their own tools to filter out which orders they think are worth filling, and then the fill subcommand would submit it to the blockchain using the account that corresponds to the specified key.

[jmozah]

@ausivi created a PR #6.

[jmozah]

#7