search

priestc / Autotip

Decentralized Cryptocurrency Microtiping Platform
http://autotip.io
MIT License
37 stars 14 forks source link

Transaction speed issue #4

Closed priestc closed 9 years ago

priestc commented 9 years ago

Here is the problem:

say you fund your deposit address with one large transaction of $10 worth of bitcoin.

That deposit address now has one "unspent outputs".

You then make one $0.05 microtip transaction.

A transaction is made using that one $10 input. The two outputs are the deposit address (same as before), and the other output address is the microtip address.

Once that transaction is sent to the network, the deposit address is in a state where its one and only unspent output is from an unconfirmed transaction. Until that transaction gets confirmed, no more transactions can be made.

Its my huntch that if autotip was pushing its transaction directly to the bitcoind rpc, then the transaction could go through. The reason why it's failing is because blockr.io is trying to verify the transaction and kicking it out when it realized it's output is not confirmed.

The response returned from blockr.io is this:

{"status":"fail","data":"Could not push your transaction!","code":500,"message":"Did you sign your transaction?"}

(this error message is the same error that gets returned for any kind of error)

Maybe if we switch to another blockchain service that will allow unconfirmed unspent outputs?

priestc commented 9 years ago

This issue has been resolved. The issue was with the blockr.io API not returning most uo to the minute latest version of an address's "unspent outputs". The issue was fixed by switching to bitpay insight, which does not cache