mimblewimble / grin-rfcs Goto Github PK

Reason: Signals to visitors on first look that grin project has and encourages use of the rfc paradigm, and to all parties that grin is committed to the rfc approach.

The link to "draft multisignature output specification" in https://github.com/mimblewimble/grin-rfcs/pulls/85 is broken.

why should we be so complicated?

with grin, to send some grins from the sender to the receiver, the sender needs an output specified by the receiver(feature 1 byte, a commitment 33 byte, a proof 8+675 bytes). Once the sender has that 717 bytes, a tx is constructed, the tx can and should be sent to the receiver. either the sender or the receiver could post the tx to the network.

And to receive, the payee prepares the above mentioned output(717 bytes) to the payer, the payer constructs the tx. the tx is then send to the payee. either of them can post the tx to the network.

why should it be that complicated? I feel that i don't understand slate and slatepack.
Can someone shed some light on what I missed? Thanks in advance.

Jack.

As titled RFC0019 https://github.com/mimblewimble/grin-rfcs/blob/master/text/0019-deprecate-http-tx.md does not follow the new template. Ping @j01tz,