chromaway/ngcccbase

Incoming transaction refusing to confirm

Closed this issue · 4 comments

Updated to new refactored version (cool!) and sent myself some testnet coins (after I realized that we are running on mainnet by default - which was scary). Transactions are marked as confirmed in bitcoin-qt, but as unconfirmed by ngccc. This has been the case for over an hour.

The transactions can be viewed here, if that helps:
http://blockexplorer.com/testnet/address/miHAzgUWtaypUMtA7cbV1QUoT7rPu2XXLH

  1. Confirmations work only on mainnet, as it relies on blockchain.info. In testnet mode we have to use ABE, and ABE doesn't report information about confirmations. (But it is possible to implement it, in principle.)
  2. It is supposed to rely on "chromanode" server for some functions, and currently no public servers are available, so this kinda needs more work...

And currently I'm in process of testing and fixing things which do not work.

I'm just testing ATM, but maybe in the near future I'll be able to do some (minor) fixing as well.

Works great now! Closed.