Does Electrum Daemon give a transaction id even when balance is too low?

Occasionally in my database I have a transaction id output from electrum for some bitcoin sent but that transaction id is invalid. If the balance is too low on electrum and I try to send an amount greater than the wallet balance will electrum still give me a bitcoin transaction id?

This wreaks havoc on my service because it appears that transactions happen when in fact those txids are invalid. This wasn’t happening before, but now it appears to happen a few times a day (with a volume of a few hundred transactions – everything works, except for those occasional invalid trx)

Recent Questions – Bitcoin Stack Exchange

Stanford University to Host Blockchain Conference

Ahead of the Blockchain Protocol Analysis and Security Engineering 2017 conference slated for January 2017, the Cyber Initiative of Stanford University has announced its call for papers from interested presenters. The conference will explore the use of formal methods, empirical analysis, and risk modeling to better understand security and systemic risk in blockchain protocols. It […]

The post Stanford University to Host Blockchain Conference appeared first on CCN: Financial Bitcoin & Cryptocurrency News.

News – CCN: Financial Bitcoin & Cryptocurrency News

Spain to Tax its Bitcoin Miners up to 47% of Profits

A recent notice from the official taxation authority in Spain sees bitcoin mining fall under the purview of an economic activity, opening cryptocurrency mining to taxation. Bitcoin and cryptocurrency miners in Spain will see taxation of their profits, a recent notice issued by the country’s National Directorate of Tax revealed. First reported Spanish industry publication […]

The post Spain to Tax its Bitcoin Miners up to 47% of Profits appeared first on CCN: Financial Bitcoin & Cryptocurrency News.

News – CCN: Financial Bitcoin & Cryptocurrency News

special block version or is my data corrupt?

I’ve recently written my own blockchain parser. It works well (yay!) up to a certain block and then fails because the data read is pure nonsense.

I’ve tracked down the error away from my code to the data on the disc and I get the same result if I parse the file only using a sheet of paper and a hex editor. Even after deleting the file and executing bitcoind -reindex I still get the same errornous results.

My question is if anybody can reproduce this or if my data is still corrupted somehow. Maybe I just need to delete all files and let bitcoind create them again?

My findings:

  • blk00622.dat causes the trouble
  • Problem still exists after deleting blk00622.dat and running bitcoind -reindex (according to diff the new file equals the old one)
  • The last ok block is block #428949 (at file address 0x7B748DF). I have no problem parsing it with my hex editor, I get the same results as shown here: https://blockchain.info/de/block-index/1144703
  • The errornous block begins at file address 0x7C68AB3
  • It starts with F9 BE B4 D9 41 0F 0F 00 F9 BE B4 D9*

F9 BE B4 D9 is the block’s magic number and 41 0F 0F 00 is the block size. The strange thing here is that the following version number again equals the magic number (which makes me thing that maybe my data is still corrupt). The remaining data of the block makes no sense, for example the time field points to 03/04/1948 ..

Thanks!

*see https://en.bitcoin.it/wiki/Block

Recent Questions – Bitcoin Stack Exchange