Questions on: transactions

The Bitcoin Core -walletnotify should only run at most twice for a typical transaction: When the transaction enters the local node's mempool When a block arrives containing that transaction. I haven't tested this, but it looks like the code may also
All miners run a full node, indexing all the unspent transaction outputs (UTXO). Thus, from the computational difficulty perspective, there's no difference between verifying old and new coins that are being spent. However, there's a reasonable assump
URL character limit for get requests Here is an excerpt on URL length limitations for Internet Explorer; use it as a baseline (certain browsers such as Opera support longer URLs): "Microsoft Internet Explorer has a maximum uniform resource locator (U
The protocol doesn't include a way to reject transactions, for a variety of reasons (the protocol doesn't know which output is real and which is change; blocks can't be changed after being mined; etc) but it is possible to do something similar. Accep
I guess it depends on what you want to do with it. If for example you're using those 20 bytes as keys in a lookup table, then you should be fine as long as you remember you might get an occasional false positive so you always double check if it reall
The block chain doesn't report the IP address and the IP address isn't passes by nodes. Any entities knowledge of Bitcoin network is limited to the connections it has. If you get a transaction from a specific IP address you can't know that IP address
The Bitcoin wiki page on scalability looks at what things would be like if transaction volume was similar to that of Visa. It states: Today the Bitcoin network is restricted to a sustained rate of 7 tps by some artificial limits. These were put in pl
Bitcoin is the currency of the Internet: a distributed, worldwide, decentralized digital money. Unlike traditional currencies such as dollars, bitcoins are issued and managed without any central authority whatsoever: there is no government, company,
For a transaction to be processed it must use the very next available sequence number (as returned by account_info). If an otherwise valid signed transaction has a sequence number too small (matching a previously used sequence number), then the trans