This coin is a total scam. The manifesto is a lie.
FreeTrade purposefully kept UPnP out of the client so that people wouldn't be able to mine memorycoins.
Topic: [ANN] MemoryCoin - page 18. (Read 100357 times)
I sent a bunch of coins over to bter, came back hours later to find I was apparently not synced with the blockchain anymore, restarted qt and now my transaction of over 443 coins is sitting at 0 confirmations and they are gone from my wallet. What the hell happened to my coins?
transactionID? Double click on transaction.....copy....paste here.... I've noticed that sometimes you need to wait for the first confirmation when sending.
Status: 0/unconfirmed
Date: 8/23/2013 02:24
To: MMBWC43KSr3L1HEhASimHsBdwBF1FS98qj
Debit: -443.465899 MEG
Net amount: -443.465899 MEG
Transaction ID: b408b6fedc3ca911e269ac13e0c6e66da8733289370acf99b70995f16b65e955
Checked block explorer and nothing shows up
Sounds like a rescan might be needed. Make a backup copy of wallet and read the following....This sounds like your problem. It occurs on all coins, though I have never had the issue.
http://bitcoin.stackexchange.com/questions/1249/how-exactly-does-rescan-work
Let us know if it helps.
It showed up in block 4338...http://memorycoin.21stcenturymoneytalk.org/?tx=b408b6fedc3ca911e269ac13e0c6e66da8733289370acf99b70995f16b65e955
Yes, it did finally show up. I'm done with this coin now anyway. The qt is constantly desyncing, can't keep it synced for more than a few blocks at a time.
FreeTrade, I have some question about the votes,
In the log you can see that some address are eliminated on round 2
Those address have a lots off votes (~10,000)
And on round 4 you see others address are eliminated, but they have a much lower number of votes (~1,000 or less)
How come the biggest get eliminated first ?
Is this a bug ?
In the log you can see that some address are eliminated on round 2
Those address have a lots off votes (~10,000)
And on round 4 you see others address are eliminated, but they have a much lower number of votes (~1,000 or less)
How come the biggest get eliminated first ?
Is this a bug ?
I doubt it is a bug. Without an example, it is hard to say....But for example, see block award for 4460. Are you asking why MVTEoEohmThgMYijuR2oPZSmStTdycrGzp was eliminated in round 1 (balance 7233) when in round 3 there is someone with lower balance (2457)........Appears to be that account MNNFraHV8KfeLoqib6Vwf6P31twihjRqQD was voting for MVTEoEohmThgMYijuR2oPZSmStTdycrGzp and MVTEoEoHX4XhRkJnkGVLKDYhHG4MbJDVCT. When the grant went to MVTEoEoHX4XhRkJnkGVLKDYhHG4MbJDVCT, his MVTEoEohmThgMYijuR2oPZSmStTdycrGzp was eliminated because those votes were used up by VCT....or some went to VCT and the remainder left the Gzp account below the number of votes of those that had already been eliminated.
My take on it at least.
Block 4460:
Award Round:0
Candidates Eliminated (19)
Candidate Eliminated: MVTEoEorjtwtccACwSTb53uJcjmjUnyexu(1488)
Candidate Eliminated: MVTEoEoiZ8QhdkbiFmvWqA8RcWhg5QX9JA(1488)
Candidate Eliminated: MVTEoEocT88fm2fZuyNFgrD9W5nEKVtqaH(2497)
Candidate Elected: MVTEoEomFfe7WuSEepMLsorgYzCQGBVw1z (15867)
Surplus Transfer Value: 0.131896
-------------:
Award Round:1
Candidates Eliminated (2)
Candidate Eliminated: MVTEoEohmThgMYijuR2oPZSmStTdycrGzp(7233)
Candidate Elected: MVTEoEoHX4XhRkJnkGVLKDYhHG4MbJDVCT (16835)
Surplus Transfer Value: 0.181818
-------------:
Award Round:2
Candidate Eliminated: MVTEoEo5LgYAMVh95oBBfGPj2eCDzkuJC3(10603)
Candidate Elected: MVTEoEoXmYzFydRfg5uNJRewt9tZ329fAN (19569)
Surplus Transfer Value: 0.296135
-------------:
Award Round:3
Candidates Eliminated (6)
Candidate Eliminated: MVTE2E2WrdHtk8Mj61V1H9b41zcE6W33Cv(2457)
Candidate Elected: MVTEoEoUtxKDFLVRJt8c79oqP5C2GB9oBP (13514)
Surplus Transfer Value: 0
-------------:
Award Round:4
Candidate Elected: MVTEoEoiMwtXEeHDUYfuwA9ZvbKSH8Jfqb (11172)
Surplus Transfer Value: 0
On the contrary rGzp is eliminated, then DVCT get the votes (2nd choice) who where on rGzp (1st choice).
->Balance:7233 - MNNFraHV8KfeLoqib6Vwf6P31twihjRqQD
--Preference 1 10000 MVTEoEohmThgMYijuR2oPZSmStTdycrGzp
--Preference 2 30000 MVTEoEoHX4XhRkJnkGVLKDYhHG4MbJDVCT
But I was not referring to that but : uJC3 with (10603) eliminated on round 2, then after there are even address with (46) who get eliminated on round 3
Award Round:3
Candidate Eliminated: MVTE2E2QkUKbxdkEFTPZ2UY6W5PE5G2Hse(46)
Candidate Eliminated: MVTEoEoyZywJ7gvHmZKJWK9nY1UtzzH1Aa(248)
Candidate Eliminated: MVTEoEosATGKUKV9KCsK8NxGg9tkxumfeR(248)
Candidate Eliminated: MVTEoEoppa8mvP1V8AkLNKT8W3NvPr2BMp(248)
Candidate Eliminated: MVTEoEo3asirrJiyCF11rFtaPt2XKNcsjk(430)
Candidate Eliminated: MVTEoEoHoCw1UFpcXTtQZ5inZLuJjuUVcP(649)
Candidate Eliminated: MVTE2E2WrdHtk8Mj61V1H9b41zcE6W33Cv(2457)
Candidate Elected: MVTEoEoUtxKDFLVRJt8c79oqP5C2GB9oBP (13514)
what blockheight is it now ? atm I see atleast 2 different invalid chains at heights 2479 and 2962. Looks a bit like a forked blockchain to me. Tho it could be some obsolete chains ghosting around while im at initial DL.
EDIT: from debug.log -> "receive version message: version 70001, blocks=4407" hmm....
EDIT: from debug.log -> "receive version message: version 70001, blocks=4407" hmm....
I am having an issue with block 2479 when I compile with gcc 4.2. On the same system (BSD) I get an instant
crash when I compile with gcc 4.8 or clang 3.3.
What compiler or build are you using? What OS?
As a side question, is the voting pool a manual effort? I saw you got some grants (>150 block ago) and have not seen payments.
It's semi-automatic.
I don't want to leave a daemon running for now, so I do it in batch.
The thing is, since the coin are on the same address, I have to wait 1 confirmation between each transaction, so it's a pain in the ass...
So yeah I won't send it as soon as it mature...
FreeTrade, I have some question about the votes,
In the log you can see that some address are eliminated on round 2
Those address have a lots off votes (~10,000)
And on round 4 you see others address are eliminated, but they have a much lower number of votes (~1,000 or less)
How come the biggest get eliminated first ?
Is this a bug ?
In the log you can see that some address are eliminated on round 2
Those address have a lots off votes (~10,000)
And on round 4 you see others address are eliminated, but they have a much lower number of votes (~1,000 or less)
How come the biggest get eliminated first ?
Is this a bug ?
22:59:30

getmininginfo
22:59:30

{
"blocks" : 4446,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00032724,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
I'm not sure what I'm doing wrong. Downloaded the qt, added nodes, synced the blockchain, went into console and "setgenerate true -1" and on my i5-3570k at 4.4GHz I'm doing 16h/p/s and 12 hours later my wallet still shows 0. Is my test period too short, or did I miss a step and that 12 hours was wasted, or is 12 hours the usual variance in finding a block?
Should average a block about 13.47 hours at 16 h/s at diff 0.0002217....Hang in there a few more hours.
Also, make sure your current block matches the block count at http://memorycoin.21stcenturymoneytalk.org
can you please provide the formula?
oh nvm, was thinking of setup a pool, thus I would have had to write miner for it also. At the current state of the coin I didnt see any point pushing this idea forward.
added a guide on how to mine MEG using amazon ec2.
http://21stcenturymoneytalk.org/index.php/topic,60.0.html
http://21stcenturymoneytalk.org/index.php/topic,60.0.html
what blockheight is it now ? atm I see atleast 2 different invalid chains at heights 2479 and 2962. Looks a bit like a forked blockchain to me. Tho it could be some obsolete chains ghosting around while im at initial DL.
EDIT: from debug.log -> "receive version message: version 70001, blocks=4407" hmm....
EDIT: from debug.log -> "receive version message: version 70001, blocks=4407" hmm....
Your client probably just got stuck on block 2479 or 2962 while downloading the blockchain.
Start the client without mining and wait for the entire blockchain to download before starting the mining process.
you can see what block the real blockchain is at here: http://memorycoin.21stcenturymoneytalk.org/
what blockheight is it now ? atm I see atleast 2 different invalid chains at heights 2479 and 2962. Looks a bit like a forked blockchain to me. Tho it could be some obsolete chains ghosting around while im at initial DL.
EDIT: from debug.log -> "receive version message: version 70001, blocks=4407" hmm....
EDIT: from debug.log -> "receive version message: version 70001, blocks=4407" hmm....
Thanks for your testing - very helpful to know when the errors are occurring. For now it sounds like grant blocks, and maybe when the computer mines a new block is when there are problems.
It seems that now the difficulty has gone up, I get less crashes/hangs.
It does hang sometimes but not as much as before. Might be coincidence or maybe related.
Hope this info helps ironing the bugs out.
So far very happy with MEG coin, I dont seem to be having all the problems people speak of, hanging wallets etc, only the crash if you mine before its synced, love to see that fixed, or already fixed ?
Some good prices on early trade on Bter, early days yet, and with the 5% drop per week, fair to say in a few months price will increase substantially. Great work FairTrade , youve put a lot of work into it. With a simple wallet app you could have the voting down pat. Bring on the pools
Hopefully they release this at Cryptsy soon, bound to get some traction, hopefully Bter drop their 20 confirms, 10 or 5 is enough.
Some good prices on early trade on Bter, early days yet, and with the 5% drop per week, fair to say in a few months price will increase substantially. Great work FairTrade , youve put a lot of work into it. With a simple wallet app you could have the voting down pat. Bring on the pools
Hopefully they release this at Cryptsy soon, bound to get some traction, hopefully Bter drop their 20 confirms, 10 or 5 is enough.
I sent a bunch of coins over to bter, came back hours later to find I was apparently not synced with the blockchain anymore, restarted qt and now my transaction of over 443 coins is sitting at 0 confirmations and they are gone from my wallet. What the hell happened to my coins?
transactionID? Double click on transaction.....copy....paste here.... I've noticed that sometimes you need to wait for the first confirmation when sending.
Status: 0/unconfirmed
Date: 8/23/2013 02:24
To: MMBWC43KSr3L1HEhASimHsBdwBF1FS98qj
Debit: -443.465899 MEG
Net amount: -443.465899 MEG
Transaction ID: b408b6fedc3ca911e269ac13e0c6e66da8733289370acf99b70995f16b65e955
Checked block explorer and nothing shows up
I sent a bunch of coins over to bter, came back hours later to find I was apparently not synced with the blockchain anymore, restarted qt and now my transaction of over 443 coins is sitting at 0 confirmations and they are gone from my wallet. What the hell happened to my coins?
I'm not sure what I'm doing wrong. Downloaded the qt, added nodes, synced the blockchain, went into console and "setgenerate true -1" and on my i5-3570k at 4.4GHz I'm doing 16h/p/s and 12 hours later my wallet still shows 0. Is my test period too short, or did I miss a step and that 12 hours was wasted, or is 12 hours the usual variance in finding a block?
few hours
i generate about 2 hours with 12mkey/s ... still waiting )) 
few hours
approximately how much time it takes to generate grant address?
Jump to: