Re: [bitcoin-dev] Ark: An Alternative Privacy-preserving Second Layer Solution

2023-05-24 Thread adiabat via bitcoin-dev
Hi - thanks for the Ark write up; I have a bunch of questions but here's 2: --- Q1: "Pool transactions are created by ark service providers perpetually every 5 seconds" What exactly happens every 5 seconds? From the 15.44.21-p-1080.png diagram [1], a pool transaction is a bitcoin transaction,

Re: [bitcoin-dev] BIP Proposal: Compact Client Side Filtering for Light Clients

2017-06-19 Thread adiabat via bitcoin-dev
This has been brought up several times in the past, and I agree with Jonas' comments about users being unaware of the privacy losses due to BIP37. One thing also mentioned before but not int he current thread is that the entire concept of SPV is not applicable to unconfirmed transactions. SPV

Re: [bitcoin-dev] Per-block non-interactive Schnorr signature aggregation

2017-05-10 Thread adiabat via bitcoin-dev
I messed up and only replied to Russel O'Connor; my response is copied below. And then there's a bit more. - Aha, Wagner's generalized birthday attack, the bane of all clever tricks! I didn't realize it applied in this case but looks like it in fact does. applies to this case. It would have

[bitcoin-dev] Requesting BIP assignment; Flexible Transactions.

2016-09-21 Thread adiabat via bitcoin-dev
Hi- One concern is that this doesn't seem compatible with Lightning as currently written. Most relevant is that non-cooperative channel close transactions in Lightning use OP_CHECKSEQUENCEVERIFY, which references the sequence field of the txin; if the txin doesn't have a sequence number,