Pass payloads from stdin

[edubart]

At the moment I create payload with:

cmioc encode input --binary \
    --chain-id 0 \
    --app-contract 0x0000000000000000000000000000000000000000 \
    --msg-sender 0x0000000000000000000000000000000000000001 \
    --block-number 0 \
    --block-timestamp 0 \
    --prev-randao 0 \
    --index 0 \
    --payload 0x$(echo -n "Hello advance 0!" | xxd -g0 -p) > input-0.bin

Would be nice if I could feed binary payload with --stdin-payload, so I could do something like:

echo -n "Hello advance 0!" | cmioc encode input --binary \
    --chain-id 0 \
    --app-contract 0x0000000000000000000000000000000000000000 \
    --msg-sender 0x0000000000000000000000000000000000000001 \
    --block-number 0 \
    --block-timestamp 0 \
    --prev-randao 0 \
    --index 0 \
    --stdin-payload > input-0.bin

[guidanoli]

Maybe you could even pipe encoded in binary already, because maybe not all payloads are ASCII, right?

echo -n "Hello advance 0!" | xxd -g0 -p | cmioc encode input --binary \
    --chain-id 0 \
    --app-contract 0x0000000000000000000000000000000000000000 \
    --msg-sender 0x0000000000000000000000000000000000000001 \
    --block-number 0 \
    --block-timestamp 0 \
    --prev-randao 0 \
    --index 0 \
    --stdin-payload > input-0.bin

For example:

cmioc encode input --binary \
    --chain-id 0 \
    --app-contract 0x0000000000000000000000000000000000000000 \
    --msg-sender 0x0000000000000000000000000000000000000001 \
    --block-number 0 \
    --block-timestamp 0 \
    --prev-randao 0 \
    --index 0 \
    --stdin-payload < my-binary-payload.bin > input-0.bin

[edubart]

Maybe you could even pipe encoded in binary already

Yeah, maybe two options --stdin-binary-payload and --stdin-hex-payload.

[guidanoli]

Nevermind, I got confused.
Let's stick with your original suggestion.