BIP 177 is NOT assigned. Do not self-assign BIP numbers!
Please read BIP 2:
https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki
Luke
On Sunday 24 December 2017 2:57:38 AM Damian Williamson via bitcoin-dev wrote:
> BIP 177: UTPFOTIB - Use Transaction Priority For Ordering Transac
If all transactions pay the proposed max then fee there are still going to be
an awful lot of never confirming transactions once the transaction bandwidth
limit is surpassed, as I suppose that it roughly is now:
https://bitinfocharts.com/comparison/bitcoin-transactions.html
This is what I have
BIP 177: UTPFOTIB - Use Transaction Priority For Ordering Transactions In Blocks
This BIP proposes to address the issue of transactional reliability in Bitcoin,
where valid transactions may be stuck in the mempool for extended periods.
There are two key issues to be resolved:
1. The curre
I see further arguments supporting the “bit" denomination:
huge benefit:
- amounts denominated in bits fit nicely into legacy database
structures and UIs with two decimal places for currency. This change to the
usual currrency precision is a huge benefit for integration into existing
fi
Why not use "coinbit". A bitcoin is equal to 1 million coinbits.
A bit could then be seen/used as an abbreviation of coinbit.
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-
Allowing a "no-RBF" flag serves only to fool new users into believing that
0-conf is more secure than it is. There is already too much confusion about
this point.
In Bitcoin was assume that miners are profit-maximizing agents, and so we
must assume that (flag or not) miners will replace transactio
While the usability of non-RBF transactions tends to be quite poor, there are
some legitimate risk-analysis-based reasons why people use them (eg to sell BTC
based on a incoming transaction which you will need to convert to fiat, which
has low cost if the transaction doesn't confirm), and if peo
I suppose what I intended is (2) the weak form but, what is essentially needed
is (1) the strong form. The answer may be somewhere in-between.
I do not see that an entire consensus for the mempool is needed, each node just
needs a loose understanding of the average number of non-zero fee transa
