Hello List,
I would like to propose a BIP that specifies a way of referring to transactions
that have been successfully inserted into the blockchain.
The format makes use of the excellent Bech32 encoding, and is designed to be
short and useful for human use. A C reference implementation is
Hello list,
I would like to propose a draft BIP that takes the next available transaction
version number and defines a new transaction template. This proposal does not
have any consensus changes, and is purely for the application layer of Bitcoin.
The new transaction template defines a special
Hello List,
I have been pondering this problem for some time and have not yet come up with
an elegant solution, so I am asking here to get more perspective.
There are many usecases for proof of burn. The current working solution is to
use OP_RETURN with some application specific data.
Dear Bitcoin Development Mailing List,
I would like to present for initial comment a new draft BIP that we have been
working on.
This BIP provides a new standard template for creating revocable proof-of-burn
transactions that can be easily and cheaply verified by nodes running under SPV
