Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 05 2014 21:53

    donovanhide on master

    README formatting (compare)

  • Aug 05 2014 21:49

    donovanhide on master

    Fix README (compare)

  • Aug 05 2014 21:37

    donovanhide on master

    Fix README formatting (compare)

  • Aug 05 2014 21:36

    donovanhide on master

    Improve README (compare)

  • Aug 05 2014 21:18

    donovanhide on master

    Fix Ledger Summary columns Merge branch 'master' of github… (compare)

  • Aug 05 2014 02:03
    donovanhide opened #13
  • Aug 05 2014 01:59
    donovanhide commented #12
  • Aug 05 2014 00:56

    lukecyca on master

    Add trust command Allows user … Merge pull request #12 from sin… (compare)

  • Aug 05 2014 00:56
    lukecyca closed #12
  • Aug 05 2014 00:56
    lukecyca reopened #12
  • Aug 05 2014 00:56
    lukecyca commented #12
  • Aug 05 2014 00:56
    lukecyca closed #12
  • Aug 05 2014 00:52

    lukecyca on fix-value-encoding

    (compare)

  • Aug 05 2014 00:51

    lukecyca on master

    Fix binary encoding for non-nat… (compare)

  • Aug 05 2014 00:48

    lukecyca on fix-value-encoding

    Fix binary encoding for non-nat… (compare)

  • Aug 04 2014 20:22

    donovanhide on master

    Add chat to README Merge branch 'master' of github… (compare)

  • Aug 04 2014 19:54

    donovanhide on master

    update rdb help (compare)

  • Aug 04 2014 18:49

    donovanhide on master

    Fix summary output (compare)

  • Aug 04 2014 18:46

    donovanhide on master

    Fix Ledger Summary (compare)

  • Aug 04 2014 18:26
    donovanhide commented #12
Donovan Hide
@donovanhide
Hi!
The possible plan is to have three or four tools which allow for pipelines of Ripple activities to be created.
tx produces either a JSON output or a binary output. It may be signed or unsigned. It may include or not include a Sequence and LastLedgerSequence.
Donovan Hide
@donovanhide
sign will process a JSON input of transaction(s) and add the correct Sequence, LastLedgerSequence if specified and sign the transaction with a seed.
tx and sign have common functionality
submit accepts a raw binary input of transaction(s) with their hashes and submits each one. Successful submissions result in a hash to stdout, unsuccessful submissions result in a hash to stderr
wait accepts a hash on stdin and waits for it on the transaction stream. Seen transactions are output to stdout. After a timeout or LastLedgerSequence is hit unseen transactions are output to stderr
Or something like that.
:-)
Need to decided on the format for the pipes.
Perhaps LastLedgerSequence:Hash:Raw is one possibility
Could also consider investigating AccountTxnId
Donovan Hide
@donovanhide
It does get unfortunately complicated when considering robust submission. This is perhaps one of the biggest flaws with Ripple in my eyes.
Stephen Paul Weber
@singpolyma
sign should probably (maybe?) accept binary or JSON input
Donovan Hide
@donovanhide
Is there much point to accepting binary, if the signature hasn't been generated?
Stephen Paul Weber
@singpolyma
it's a valid output format for tx, and other people's tools might prefer binary to json (depending on their implementation, etc)
Donovan Hide
@donovanhide
Ok, makes sense. A raw tx can be parsed without a Signature and PubSigningKey so there's no harm in supporting it :-)
I think the key decisions to make are which tools take which flags and how do they communicate through pipes.
The code will stem easily from those decisions
Stephen Paul Weber
@singpolyma
so, with the patches I've got on tx right now, the pipeline looks like: ./tx -b <all the data> | ./tx -submit s
Donovan Hide
@donovanhide
Perhaps all pipes should be colon separated binary. JSON makes it more complicated.
The explain tool already can take binary and make it JSON.
well, with the logging turned on it can :-)
Stephen Paul Weber
@singpolyma
is the idea with sign outputting the hash that submit can use it to make sure the blob hasn't been corrupted?
Donovan Hide
@donovanhide
No, just to pass it on to a wait command which can read the transaction stream and show when it has succeeded
sorry, been accepted into a ledger.
hence passing LastLedgerSequence as well (effectively a timeout)
Just realised that LastLedgerSequence is embedded in the transaction anyway. Doh!
Stephen Paul Weber
@singpolyma
the hash can be computed from the transaction data as well, though, yes?
Donovan Hide
@donovanhide
Yep, we just need the raw binary :-)
Stephen Paul Weber
@singpolyma
in which case it could be json or binary at some stages, though after signing should probably be binary for safety in case the order could get messed up
Donovan Hide
@donovanhide
I suppose wait is a permanently running daemon. Could be fed from a fifo pipe, but we're starting to get into esoteric unix land then...
JSON would work as well. I'm mostly just thinking out loud!
Maybe wait should be called confirm
Stephen Paul Weber
@singpolyma
yeah, confirm is a good name
but I would not use it long-running. anyone who wants that can run subscribe and look at the output
Donovan Hide
@donovanhide
True you'd want a succesful exit code of 0 from confirm when all it's input has been seen or exit code 1 if a single transaction failed.