Re: [bitcoin-dev] Proposed new policy for transactions that depend on other unconfirmed transactions

02:20 -0400 > From: Alex Morcos > To: Danny Thorpe > Cc: Bitcoin Dev > Subject: Re: [bitcoin-dev] Proposed new policy for transactions that > depend on other unconfirmed transactions > Message-ID: > ew-g9f5yz9edqxgzpzvs2mqj8n5wkg15ofz4cwgahq...@mail.gmail.co

Re: [bitcoin-dev] Proposed new policy for transactions that depend on other unconfirmed transactions

There is a PR up for this change at https://github.com/bitcoin/bitcoin/pull/6771, which is getting some discussion for those following along. On October 5, 2015 1:02:40 PM PDT, Alex Morcos via bitcoin-dev wrote: >Yes, total number of dependent transactions regardless of chain depth. > >A desce

Re: [bitcoin-dev] Proposed new policy for transactions that depend on other unconfirmed transactions

Yes, total number of dependent transactions regardless of chain depth. A descendant package means all the transactions that can not be included in a block before the transaction in question. An ancestor package means all the transactions that are required to be included in a block before the tran

Re: [bitcoin-dev] Proposed new policy for transactions that depend on other unconfirmed transactions

What does "package" mean here? When you say 25 txs, does that mean maximum linked chain depth, or total number of dependent transactions regardless of chain depth? Thanks, -Danny On Mon, Oct 5, 2015 at 11:45 AM, Alex Morcos via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > I'd

Re: [bitcoin-dev] Proposed new policy for transactions that depend on other unconfirmed transactions

I'd like to propose updates to the new policy limits on unconfirmed transaction chains. The existing limits in master and scheduled for release in 0.12 are: Ancestor packages = 100 txs and 900kb total size Descendant packages = 1000 txs and 2500kb total size Before 0.12 is released I would like t

Re: [bitcoin-dev] Proposed new policy for transactions that depend on other unconfirmed transactions

Thanks for everyone's review. These policy changes have been merged in to master in 6654 , which just implements these limits and no mempool limiting yet. The default ancestor package size limit is 900kb not 1MB. Yes I think these limits are generous

Re: [bitcoin-dev] Proposed new policy for transactions that depend on other unconfirmed transactions

The limits Alex proposed are generous (bordering on obscene!), but dropping that down to allowing only two levels of chained unconfirmed transactions is too tight. Use case: Brokered asset transfers may require sets of transactions with a dependency tree depth of 3 to be published together. ( N se

Re: [bitcoin-dev] Proposed new policy for transactions that depend on other unconfirmed transactions

I dont see any problem with such limits. Though, hell, if you limited entire tx dependency trees (ie transactions and all required unconfirmed transactions for them) to something like 10 txn, maximum two levels deep, I also wouldnt have a problem. Matt On 08/14/15 19:33, Alex Morcos via bitcoin-d

[bitcoin-dev] Proposed new policy for transactions that depend on other unconfirmed transactions

Hi everyone, I'd like to propose a new set of requirements as a policy on when to accept new transactions into the mempool and relay them. This policy would affect transactions which have as inputs other transactions which are not yet confirmed in the blockchain. The motivation for this policy