Has this been considered?
If made sufficiently general, older clients could support any
extension of the rules.
Various hard parameters within the protocol are defined in main.h of
the official client.
In BIP-34, there is a suggested way to make changes, based on consensus.
In my fidelity bond protocol (1) I'm proposing the use of two possible
new features:
The first is the use of OP_RETURN at the end of a scriptPubKey to
designate that the txout can be immediately pruned as it is obviously
unspendable. My use-case is the publish part of the two-step
On Tue, Feb 12, 2013 at 5:49 AM, Raph Frank raph...@gmail.com wrote:
Has this been considered?
If made sufficiently general, older clients could support any
extension of the rules.
Various hard parameters within the protocol are defined in main.h of
the official client.
In BIP-34, there
On Tue, Feb 12, 2013 at 10:11 AM, Peter Todd p...@petertodd.org wrote:
Again, thoughts?
First: I really like the fidelity bond concept, and want to see it happen.
RE: OP_RETURN : I've got a knee-jerk opposition to the OP_RETURN opcode,
because it was the cause of the nastiest bug ever
On Tue, Feb 12, 2013 at 12:42:37PM -0500, Gavin Andresen wrote:
On Tue, Feb 12, 2013 at 10:11 AM, Peter Todd p...@petertodd.org wrote:
Again, thoughts?
First: I really like the fidelity bond concept, and want to see it happen.
RE: OP_RETURN : I've got a knee-jerk opposition to
5 matches
Mail list logo