https://github.com/litecoin-project/bitcoinomg/commits/0.8.5-OMG6
http://download1.rpmfusion.org/~warren/bitcoin-0.8.5-OMG6/
I've been backporting patches from master and Litecoin to make a Bitcoin
0.8 client with more features. It works quite well on Linux and Win32.
Lately I was pondering how to make floating fees and SPV wallets work well
together.
I propose the following plan:
1) 0.9 ships with something dead simple, like a command to query what a
node estimates and then clients just take the average, or cross-check a
centralised estimate against the P2P
Both can be combined into adapting the current generic messages (This
payment should become spendable shortly for incoming and This payment
has not been transmitted yet for outgoing transactions).
What would the new messages say?
We need to get away from the notion of senders attaching fees
On 12/01/2013 06:19 PM, Mike Hearn wrote:
Both can be combined into adapting the current generic messages (This
payment should become spendable shortly for incoming and This payment
has not been transmitted yet for outgoing transactions).
What would the new messages say?
Well, for starters
This payment did not become spendable since xxx minutes. Check with the
sender if s/he paid the Bitcoin network fee. Check if your internet
connection is working properly. (incoming)
That seems reasonable.
The other message should be implementable today, I think? If numBroadcastPeers
0
On Sun, Dec 01, 2013 at 06:19:14PM +0100, Mike Hearn wrote:
Both can be combined into adapting the current generic messages (This
payment should become spendable shortly for incoming and This payment
has not been transmitted yet for outgoing transactions).
What would the new messages
Bitcoin is and always will be limited in capacity - transactions may not
confirm in a reasonable about of time because of high-demand and/or DoS
attacks.
I agree in the general case, but I was talking about the mobile wallet case
specifically (i.e. people who are sending money between
On Sun, Dec 01, 2013 at 07:18:07PM +0100, Mike Hearn wrote:
Bitcoin is and always will be limited in capacity - transactions may not
confirm in a reasonable about of time because of high-demand and/or DoS
attacks.
I agree in the general case, but I was talking about the mobile wallet case
8 matches
Mail list logo