Topic: [ANN] MemoryCoin - page 33. (Read 100357 times)

Do they show up as orphans when you type "listtransactions" in the debug console?

16:27:05

Welcome to the Bitcoin RPC console.
Use up and down arrows to navigate history, and Ctrl-L to clear screen.
Type help for an overview of available commands.


16:27:36

listtransactions


16:27:37

[
{
"account" : "",
"address" : "MTJRe6e7qAJeViWyxZZMNNtBmZEHs2u778",
"category" : "orphan",
"amount" : 24.00000000,
"confirmations" : 0,
"generated" : true,
"txid" : "d41dbf53dff21fff5bfc2932f3759959cc4b5410f522fb461178046155325e3a",
"time" : 1375923512,
"timereceived" : 1375923515
},
{
"account" : "",
"address" : "MTJRe6e7qAJeViWyxZZMNNtBmZEHs2u778",
"category" : "orphan",
"amount" : 24.00000000,
"confirmations" : 0,
"generated" : true,
"txid" : "9ddd78fda5fa0100d56bd9f6aa7bf76e62a47c7a7e2e38e08bb4b93c69e6d8fe",
"time" : 1375964890,
"timereceived" : 1375964893
},
{
"account" : "",
"address" : "MTJRe6e7qAJeViWyxZZMNNtBmZEHs2u778",
"category" : "orphan",
"amount" : 24.00000000,
"confirmations" : 0,
"generated" : true,
"txid" : "9a42911231de815694ce56696bc5616b3230bab47f658c07d71257008528723c",
"time" : 1375964994,
"timereceived" : 1375964998
}
]

I'm getting tired of restarting the miner on my machines all the time when it hangs on a block.

The network time is used to validate new blocks. As a precaution, nodes reject any block timestamp that is greater than 2 hours from the current network time. Block timestamps that are earlier than the median time of the past 11 blocks are also rejected. This validation puts upper and lower bounds on the acceptable range of block timestamps.

The attacker would then create a new block with a timestamp set 190 minutes ahead of the real time. (The amount of time required to generate a block would depend on the attacker's share of the network's total power, but it could be done 10 times a week on average by someone with a relatively small 1% share.)

The target node would reject this new block (because the timestamp is 260 minutes past its own slowed-down network time) and continue using the previous chain. However the miners would accept the block (because it's no more than 120 minutes past their own sped-up network time).

The target would now be isolated from the network's normal transaction processing. As network processing continues, each new block created by the miners would appear to be invalid (because it would bear a timestamp 140 minutes past the target's network time). The target would immediately drop invalid blocks (in CheckBlock()) without bothering to request and re-check the blocks' ancestors. The attack could continue indefinitely until either an unaffected node or the target itself creates a block, clocks are reset, or operators intervene.

The transaction history is kept in the block chain. Considering that these are immature coins, your local copy of the block data would have to be almost fully synchronized before they show up.

OK, good to hear you have identified the problem and are solving it.
Looking forward to the fix.