On Tue, Oct 11, 2022 at 04:18:10PM +, Pieter Wuille via bitcoin-dev wrote:
> On Friday, October 7th, 2022 at 5:37 PM, Dario Sneidermanis via bitcoin-dev
> wrote:
> > Thanks for the fast answer! It seems I missed the link to the PR, sorry for
> > the
> > confusion. I'm referring to the
It is still true that cryptography is hard, unfortunately. Yannick Seurin, Tim
Ruffing, Elliott Jin, and I discovered an attack against the latest version of
BIP MuSig2 in the case that a signer's individual key A = a*G is tweaked before
giving it as input to key aggregation.
In more detail, a
On Friday, October 7th, 2022 at 5:37 PM, Dario Sneidermanis via bitcoin-dev
wrote:
> Hello David,
>
> Thanks for the fast answer! It seems I missed the link to the PR, sorry for
> the
> confusion. I'm referring to the opt-in flag for full-RBF from #25353
>
Hi all,
Today I am publishing "Validity Rollups on Bitcoin", a report I produced as
part of the Human Rights Foundation's ZK-Rollup Research Fellowship.
Here's the preface:
> Ever since Satoshi Nakamoto first publicly announced bitcoin, its supporters,
> critics, and skeptics alike have
Propagation of these kinds of transactions will be hampered until becomes 10%+ of the network or so, like any other policy
relaxation.
On Tue, Oct 11, 2022 at 9:08 AM KING JAMES HRMH
wrote:
> I am reading between the lines, wouldn't that mean an older client like
> v0.18 may not be able to
There are a number of issues with adding arbitrary size restrictions to
consensus(I personally think it's additional complexity for negative gain),
but most of all this may resolve in burned coins.
On Tue, Oct 11, 2022 at 6:22 AM Loki Verloren via bitcoin-dev <
Hello fellow Bitcoiners,
After looking at some fairly exotic possible transaction types, I ran into
the current policy limit requiring transactions to be 85 non-witness
serialized bytes. This was introduced as a covert fix to policy fix
for CVE-2017-12842. Later the real motivation was revealed,
The recent 998 of 999 multisig segwit transaction highlights a problem with
BIP144. As the solution applied for btcd shows, effectively a single
transaction witness can be the same as the maximum block size.
11000 bytes may not be so unreasonable but now there is a special case with a
block
Silent Payment v4 (coinjoin support added)
Changes:
. Silent payments now use all inputs to create transactions. Previously, they
only used the first input. This change increases privacy and makes silent
payments compatible with coinjoin.
. `getspaddress` RPC renamed to `getsilentaddress` for
