I would love to see txref, or something like it, as a starting point for a standard. blockchaincode+blockheight+transactionindexinblock+(optional)input/outputindexintransaction Why bech32bix encoding? Designed for smaller bytes lengths, it is both error-detecting AND error-correcting (up to about ~80/90 bytes(?)), and is designed to be read over the phone. The main thing that I see would a problem for using txref directly is that it only works for blockchains with blockheights and transaction indexes, and the current design only allows for 20+ blockchains as it uses a short prefixed "magic code" for the blockchain. -- Christopher AllenReceived on Saturday, 4 April 2020 02:10:53 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:58 UTC