[ANN] MemoryCoin

[B.T.Coin]

Yes, working on a fix for this. Seems to be to with the multithreading. I'll let you know when I have more.

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

[stas]

can't connect to the network, and I do have all "addNodes" you have provided...

Stas

[stas]

On 2 of my PC's it does not connect to the network
While on other PC it does.
All of them have the same config file with known IP addresses You provided

thank you

[stas]

OK. everything is synching now

[FreeTrade]

Okay - new download -

https://docs.google.com/file/d/0B-5Ax5kejTpMTHZnUF80cGlFU1k/edit?usp=sharing

This puts nicely formatted reports about the voting in the debug file.

It also fixes a problem where it was wasting network resources causing it to be slow to connect to the network. Thanks to 21stcenturymoney for pointing this out.

[FreeTrade]

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

Having some difficultly finding this.

Can you try deleting hashlookup.txt and the blocks and chainstate folders and restarting. It'll need to re-download and index the blockchain again, but might resolve the problem for you.

[B.T.Coin]

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

Having some difficultly finding this.

Can you try deleting hashlookup.txt and the blocks and chainstate folders and restarting. It'll need to re-download and index the blockchain again, but might resolve the problem for you.

I already tried deleting everything except for the wallet.dat file. Didn't help
The problem keeps repeating at random intervals on both my machines.

[stas]

what is your config file?

[FreeTrade]

I don't have a config file, I just start the miner from the batch file.

I don't think this is a network problem - more likely some subtle corruption of the memory state of the block caused by some with the multithreading. I'm still looking at it.

[FreeTrade]

is it normal for me to have 3 transactions saying immature for more than 24hrs ?
it just takes a while right ? (for them to be confirmed)
i got x3 at 24coins
the first one had no transaction registered but the other two did and have details about confirmations etc..
edit: after restarting all 3 of 3 have a record for the transaction now.

Some more info about unmatured blocks here -
http://21stcenturymoneytalk.org/index.php/topic,24.0.html

[FreeTrade]

edit:
update and restart and i can't sync now..
i had a feeling that would happen which is why i didn't want to restart etc
tried a ton of things so far and nothing. also the app won't close..
gotta kill it with task manager.
i was already synced and mining before i updated and restarted
and yeah i ditched my roaming folder and it acted the same way.

Try starting it without mining on - just click on the .exe rather than the .bat.

If that doesn't help, you could click on the re-index bat, it takes a few minutes, but it's painless.

[FreeTrade]

21st Century Money Talk has some new builds . . . there's a Linux GUI client now . . .

Thanks 2CMT!

http://21stcenturymoneytalk.org/index.php/topic,23.0.html

[markm]

I have been trying to find out what ports this thing uses but as far as I can tell it is unchanged bitcoin code?

It connects to the bitcoin network, on the bitcoin port, and maybe even uses the bitcoin network handshake to identify itself so it can pretend to be a bitcoin node and try to poison the bitcoin network with its hopefully incompatible blocks and in turn get all mucked up by being given bitcoin blocks by bitcoin nodes?

Or has the code been hacked in some nonstandard place to fix some of that that seems in the chain info stuff to be plain old bitcoin settings?

-MarkM-

[FreeTrade]

I have been trying to find out what ports this thing uses but as far as I can tell it is unchanged bitcoin code?

It connects to the bitcoin network, on the bitcoin port, and maybe even uses the bitcoin network handshake to identify itself so it can pretend to be a bitcoin node and try to poison the bitcoin network with its hopefully incompatible blocks and in turn get all mucked up by being given bitcoin blocks by bitcoin nodes?

Or has the code been hacked in some nonstandard place to fix some of that that seems in the chain info stuff to be plain old bitcoin settings?

-MarkM-

Hi Mark,

Port 8555 - some of the old builds had some old bitcoin stuff left in accidentally, but that should all be cleared out now. Which build or source are you using?

[torbank]

and yeah i ditched my roaming folder and it acted the same way.

I hope you saved your wallet.dat file.

[torbank]

my coins are gone and the transaction history has disappeared from my wallet.

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.

[torbank]

my coins are gone and the transaction history has disappeared from my wallet.

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.

yup my wallet.dat was not deleted and my wallet was 100 synced all night long before i updated so i dunno what happened.
how do i go from waiting for confirmations for 3 transactions to updating the wallet to no transactions and no coins ?

They might be orphans.

http://blockchain.info/orphaned-blocks

[torbank]

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

That sounds like it could be a symptom of timejacking.

https://en.bitcoin.it/wiki/Weaknesses#Forcing_clock_drift_against_a_target_node

Specifically this (the article is from 2011, so I'm not sure if bitcoin and derivatives are still susceptible):

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.

Source: http://culubas.blogspot.ca/2011/05/timejacking-bitcoin_802.html

[torbank]

well that sucks having it say i have coins getting block after block only to find out later i get nothing for my efforts

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

[jestronix]

2500 coins and not one orphan, takes about a day for them to mature.  Only thing ive noticed on this wallet is the issue of mining on startup causing it to crash, havent seen this with any other coin. i point my wallets on one local wallet and then update from that, far quicker if you have a few wallets going.