Good morning Greg and John,
I am not as sanguine here; SegWit activation was already delayed relative to
commonly-broadcast expectations, yet many services *still* do not support
sending to SegWit v0 addresses even now.
On the other hand, the major benefit of taproot is the better privacy and
Good morning Tamas,
Thank you for taking the time to implement my idea.
I filed an issue proposing a feature to add a "contact point" fixed-length
field to all advertisements.
https://github.com/defiads/defiads/issues/1
I believe this gives me the right to say: First post.
I will try to take a
I introduced you to the pattern of a side memory to bitcoin in [1] and
promised an implementation of it.
Here you are.
defiads is a side memory network to bitcoin, implemented in Rust, built
on top of rust-bitcoin, murmel, hammersbald, rust-bitcoinconsenus,
rust-wallet, all Rust open source free
On Sun, Sep 08, 2019 at 05:39:28AM +0200, Ruben Somsen via bitcoin-dev wrote:
> After looking more deeply into Tadge Dryja’s utreexo work [0], it has
> become clear to me that this opens up a way to implement PoW fraud
> proofs [1] without a soft fork.
This is a nifty idea.
> [...] you’d need to
> I'd prefer to not support P2SH-nested TR. P2SH wrapping was useful for
segwit
v0 for compatibility reasons. Most wallets/exchanges/services now support
sending
to native segwit addresses (https://en.bitcoin.it/wiki/Bech32_adoption) and
that
will be even more true if Schnorr/Taproot activate in 12
Hi,
Here are some transcripts of talks from Scaling Bitcoin 2019 Tel Aviv. Any
errors are most likely my own.
Training material
Training materials for bitcoin developers:
https://diyhpl.us/wiki/transcripts/scalingbitcoin/tel-aviv-2019/edgedevplusplus/
Foundation topics:
https://diy
