In order for such messages to be dispatchable between apps, I suggest
prepending with an URI scheme, similar to the already existing
"bitcoin:" scheme.
Also I suggest defining a MIME type, e.g. for usage in NFC NDEF messages
or emails.
What is the relation of this BIP to BIP21 and BIP70-72? Is
Good morning,
>Or do I mistake my understanding of bech32?
Looking again at bech32 spec, yes, my understanding is wrong: the character "1"
is not allowed in the data part, so the last "1" digit in the bech32 string is
unambiguously the separator between the human-readable and data parts,
Good morning Rusty,
The fact that amount is optional, and the separator character between
human-readable and data is the character "1", may mean some trouble with
parsing of the optional amount.
Currently, the version is 0, which translates to the character "q" appearing
after "1". So 1q is
Hello,
I have spent a fair bit of time trying to nail how exactly block
filter digests[1] should be done to optimize bandwidth, space,
resource usage.
The report can be found here: http://bc-2.jp/bfd-profile.pdf
This graph shows bandwidth use of 200 wallets simulated over 5000
blocks:
On 05/29/2017 04:19 AM, Anthony Towns wrote:
> On Sat, May 27, 2017 at 01:07:58PM -0700, Eric Voskuil via bitcoin-dev wrote:
>> Anthony,
>> For the sake of argument:
>
> (That seems like the cue to move any further responses to bitcoin-discuss)
I didn't meant to imply that the point was
