Finally got my wallet synched.
The problem was that the version of the wallet on the official website did not match the updated wallet from this thread and I was downloading from the official website of the coin and not from here.
Anyways, that resolved it. thanks
if that s true, it shows a lack of competence from the DEV Sorry, I love this coin, but the lack of communication and mistakes are becoming too much... Its as if the coin holders are trying harder than the DEVS for this coin to succeed i agree... from the beginning a lot of error from devs... not good for the rise of new coin... i mine in solo 142.400coins i backup wallet.dat to update wallet delete old roaming\cleanwater folder i install latest wallet shutdown wallet replace wallet.dat. restart wallet to resync: I loose 142.400coins!!!!!really good job devs!!!!
|
|
|
30 seconds !!
no wallet available...
|
|
|
F*ckin AWESOME IPO !!
Ready to launch ?!?! How's everyone feeling?...
One quick question though... where are the wallets DEVS ?!?!
i think this will be another fake launch! latest post of EmiratesCoin is on: April 30, 2014, 09:10:02 PM....I think it is not seriously not having written anything yet 5 minutes from launch Furthermore the wallet is not yet available!!!!
|
|
|
what kind of shit wallet... issue on issue!!! i lost all my cleanWater mined today!!!! in debug windows-->Information "Current number of blocks" are never the same of "estimated total block"!!!! incredible!!! How did you lose all your coins mined today? i download latest wallet. i update cleanwater.conf file.. i restart solo mining. all was ok but few minutes ago i check again wallet and all blocks mined today was gone! in wallet there are only 76 transactions.. but the wallet counter in "Overview" section show me the correct number: "number of transaction: 236" !!!!! just block with this transaction id was good and aded in wallet : 2b728aa9ff9ac1535a98a73b874f71b826af9e5e6978695e520703c812770a1c MAGIC WALLET!!! damn shit wallet!!!
|
|
|
what kind of shit wallet... issue on issue!!! i lost all my cleanWater mined today!!!! in debug windows-->Information "Current number of blocks" are never the same of "estimated total block"!!!! incredible!!!
|
|
|
UPDATE ON MINTPAL VOTING coin VOTE XXL 90040 WATER 89978
what kind of race!!!! fantastisc!! UPDATE ON MINTPAL VOTING coin VOTE XXL 90092 WATER 90029
|
|
|
UPDATE ON MINTPAL VOTING coin VOTE XXL 90040 WATER 89978
|
|
|
VOTE ON MINTPAL
XXL overtaken cleanWater again!!!
situation RANK COIN CODE COIN NAME VOTES 1 XXL XXLcoin 89931 2 WATER CleanWaterCoin 89669 3 C2 Coin2 72805
|
|
|
..oggi ho provato a minare in solo summercoin fin da subito. sto cercando di capire il log generato dal wallet nella fase di mining in solo per vedere se le monete accreditate sono corrette.. dunque... minando in solo i casi sono 2: o trovi un blocco e viene accettato o trovi un blocco e questo va in stale. Ecco come ho proceduto per cercare di "leggere" il log... ho preso "ID della transazione" di un blocco minato. Per esempio 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 e l'ho cercato nel log. ecco cosa ho trovato: "new proof-of-work block found" sembra il messaggio che logga il wallet quando viene trovato l'hash del nuovo blocco "CTxOut(nValue=1480.00" e "CTxOut(nValue=20.00" solo il valore accreditato sul mio wallet e 20 sono le monete che per ogni blocco il dev cede in beneficieza. "AddToWallet 267fa275d8 new" sembra l'istruzione che aggiorna il contatore delle monete nel wallet "ProcessBlock: ACCEPTED" questo forse è il messaggio che indica che l'operazione è andata a buon fine. [b]CheckWork() : new proof-of-work block found [/b] hash: 00000003b0bea6892320a949df37819fd67b0da289d4b506d0c248a1fceda651 target: 00000003fffc0000000000000000000000000000000000000000000000000000 CBlock(hash=00000003b0bea6892320a949df37819fd67b0da289d4b506d0c248a1fceda651, ver=6, hashPrevBlock=0000000176dd1ea7c0466de395696c442975405b5e6c9b63265e87924e7aab08, hashMerkleRoot=267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5, nTime=1398708216, nBits=1d03fffc, nNonce=526045, vtx=1, vchBlockSig=) Coinbase(hash=267fa275d8, nTime=1398708216, ver=1, vin.size=1, vout.size=2, nLockTime=0) CTxIn(COutPoint(0000000000, 4294967295), coinbase 022e010108) CTxOut[b](nValue=1480.00[/b], scriptPubKey=OP_DUP OP_HASH160 1db90e7e0f31294f0309328572b3d8dc1fbf098a OP_EQUALVERIFY OP_CHECKSIG) CTxOut([b]nValue=20.00[/b], scriptPubKey=OP_DUP OP_HASH160 9d12999dad778a2ac107abc6f76b924062858eaa OP_EQUALVERIFY OP_CHECKSIG) vMerkleTree: 267fa275d8 [b]generated 1500.00[/b] [b]AddToWallet 267fa275d8 new[/b] NotifyTransactionChanged 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 status=1 NotifyTransactionChanged 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 status=0 updateWallet 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 1 SetBestChain: new best=00000003b0bea6892320 height=302 trust=21152193924 blocktrust=1073758208 date=04/28/14 18:03:36 ProcessBlock: ACCEPTED inWallet=1 inModel=0 Index=0-0 showTransaction=1 derivedStatus=0 updateWallet 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 0 inWallet=1 inModel=1 Index=0-1 showTransaction=1 derivedStatus=0 Warning: updateWallet: Got CT_NEW, but transaction is already in model received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 IRC got join received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 accepted connection 70.176.73.232:60464 IRC got join send version message: version 60013, blocks=302, us=79.56.0.98:11110, them=70.176.73.232:60464, peer=70.176.73.232:60464 Added time data, samples 67, offset -6 (+0 minutes) nTimeOffset = -1 (+0 minutes) Moving 70.176.73.232:11110 to tried receive version message: version 60013, blocks=301, us=79.56.0.98:11110, them=70.176.73.232:11110, peer=70.176.73.232:60464 received block 0000000825a680abbfbb ProcessBlock: ACCEPTED Flushing wallet.dat Flushed wallet.dat 7ms getblocks 248 to 00000007fca9e9ab3967 limit 500 getblocks stopping at 251 00000007fca9e9ab3967 received block 000000033e451005664c SetBestChain: new best=000000033e451005664c height=303 trust=22225952132 blocktrust=1073758208 date=04/28/14 18:03:37 NotifyTransactionChanged 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 status=1 ProcessBlock: ACCEPTED updateWallet 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 1 inWallet=1 inModel=1 Index=0-1 showTransaction=1 derivedStatus=1
altro caso quando il blocco minato va in stale anche quì abbiamo il messagio "CheckWork() : new proof-of-work block found" che indica che un blocco è stato risolto. Prova ad accreditare i 1480 coins e 20 sui 2 indirizzi. ma il checkWork da errore "ERROR: CheckWork() : generated block is stale" il processo si conclude con "ProcessBlock: ACCEPTED" [b]CheckWork() : new proof-of-work block found[/b] hash: 0000014926625b19de3470ee0ff64dd533ae9a3e208cd0d778983d5369f9108e target: 00000fffff000000000000000000000000000000000000000000000000000000 CBlock(hash=0000014926625b19de3470ee0ff64dd533ae9a3e208cd0d778983d5369f9108e, ver=6, hashPrevBlock=000008d9fd3630515f6f9d6f7e8f677b2c10527313508a609bc5291b0313e0d5, hashMerkleRoot=de9634270757be3a37b40fbaa152273027be5bee0fdf286ecb9e078354bc9761, nTime=1398708030, nBits=1e0fffff, nNonce=354861, vtx=1, vchBlockSig=) Coinbase(hash=de96342707, nTime=1398708030, ver=1, vin.size=1, vout.size=2, nLockTime=0) CTxIn(COutPoint(0000000000, 4294967295), coinbase 01120101) CTxOut[b](nValue=1480.00[/b], scriptPubKey=OP_DUP OP_HASH160 1db90e7e0f31294f0309328572b3d8dc1fbf098a OP_EQUALVERIFY OP_CHECKSIG) CTxOut([b]nValue=20.00[/b], scriptPubKey=OP_DUP OP_HASH160 9d12999dad778a2ac107abc6f76b924062858eaa OP_EQUALVERIFY OP_CHECKSIG) vMerkleTree: de96342707 generated 1500.00 [b]ERROR: CheckWork() : generated block is stale[/b] getblocks 8 to 00000000000000000000 limit 500 received block 0000009594cfd72f055d SetBestChain: new best=0000009594cfd72f055d height=20 trust=22020117 blocktrust=1048577 date=04/28/14 18:00:29 [b]ProcessBlock: ACCEPTED[/b]
quindi io mi aspettavo di trovarmi N blocchi minati per quanti messaggi generated 1500.00AddToWallet 267fa275d8 newmi trovo nel log del wallet... ma così non è. Il dubbio mi è venuto perchè i pop up in basso a destra, dei blocchi trovati erano molti di più di quanti poi effettivamente me ne ritrovo nel wallet che sono solo 3. Sicuramente non c'ho capito una mazza.. e volevo una spiegazione da chi ne capisce più di me.... potrei vedere il codice c++ del wallet su github, ma purtroppo non ho competenze su c++... quindi mi affido a chi ne capisce più di me per avere una "lezione" su come si legge il log generato dal wallet... inoltre penso che sia cosa gradita per la comunità!!!! CIAO BBBBELLII!!! cavolo ma proprio nessuno è in grado di leggere il log generato dal wallet? nessuno che sappia spiegarmi come funziona?
|
|
|
EVERYONE - VOTE ON MINTPAL!!
XXLCoin has overtaken WATER in the voting, make sure you put in your 5 votes an hour!
Xxl overtaken cleanwater by 700 votes!!!!Cmon in volte on mintpal!!!!!
|
|
|
hey guys... vote on mintpal... do not let cleanwater be overtaken by XXL!!!
this is the situation!!! don't loose the chance to be on mintpal echange!!!!
RANK COIN CODE COIN NAME VOTES 1 WATER CleanWaterCoin 88778 2 XXL XXLcoin 88379 3 C2 Coin2 72411
|
|
|
Price goes up... cant believe it actually. .. people are stacking up before mintpal... having no idea whats happening in here...
what do you mean ? edit: when is the POW phase ending? Dont get me wrong bro... but the wallet is having MAJOR issues... been fixed mutiple times... problems keep popping up... Devs need to contact mintpal to put us onhold, until they fix ALL the damn problems... or else mintpal will be our dumping container.... hey guys.... some body here want to be clever!!! check new chain explorer... who mined all this block with 0 difficulty??? this situation for me is not corret...
|
|
|
sorry!!! wrong session!!! moderator, you can delete this thread!!!
|
|
|
..oggi ho provato a minare in solo summercoin fin da subito. sto cercando di capire il log generato dal wallet nella fase di mining in solo per vedere se le monete accreditate sono corrette.. dunque... minando in solo i casi sono 2: o trovi un blocco e viene accettato o trovi un blocco e questo va in stale. Ecco come ho proceduto per cercare di "leggere" il log... ho preso "ID della transazione" di un blocco minato. Per esempio 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 e l'ho cercato nel log. ecco cosa ho trovato: "new proof-of-work block found" sembra il messaggio che logga il wallet quando viene trovato l'hash del nuovo blocco "CTxOut(nValue=1480.00" e "CTxOut(nValue=20.00" solo il valore accreditato sul mio wallet e 20 sono le monete che per ogni blocco il dev cede in beneficieza. "AddToWallet 267fa275d8 new" sembra l'istruzione che aggiorna il contatore delle monete nel wallet "ProcessBlock: ACCEPTED" questo forse è il messaggio che indica che l'operazione è andata a buon fine. [b]CheckWork() : new proof-of-work block found [/b] hash: 00000003b0bea6892320a949df37819fd67b0da289d4b506d0c248a1fceda651 target: 00000003fffc0000000000000000000000000000000000000000000000000000 CBlock(hash=00000003b0bea6892320a949df37819fd67b0da289d4b506d0c248a1fceda651, ver=6, hashPrevBlock=0000000176dd1ea7c0466de395696c442975405b5e6c9b63265e87924e7aab08, hashMerkleRoot=267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5, nTime=1398708216, nBits=1d03fffc, nNonce=526045, vtx=1, vchBlockSig=) Coinbase(hash=267fa275d8, nTime=1398708216, ver=1, vin.size=1, vout.size=2, nLockTime=0) CTxIn(COutPoint(0000000000, 4294967295), coinbase 022e010108) CTxOut[b](nValue=1480.00[/b], scriptPubKey=OP_DUP OP_HASH160 1db90e7e0f31294f0309328572b3d8dc1fbf098a OP_EQUALVERIFY OP_CHECKSIG) CTxOut([b]nValue=20.00[/b], scriptPubKey=OP_DUP OP_HASH160 9d12999dad778a2ac107abc6f76b924062858eaa OP_EQUALVERIFY OP_CHECKSIG) vMerkleTree: 267fa275d8 [b]generated 1500.00[/b] [b]AddToWallet 267fa275d8 new[/b] NotifyTransactionChanged 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 status=1 NotifyTransactionChanged 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 status=0 updateWallet 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 1 SetBestChain: new best=00000003b0bea6892320 height=302 trust=21152193924 blocktrust=1073758208 date=04/28/14 18:03:36 ProcessBlock: ACCEPTED inWallet=1 inModel=0 Index=0-0 showTransaction=1 derivedStatus=0 updateWallet 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 0 inWallet=1 inModel=1 Index=0-1 showTransaction=1 derivedStatus=0 Warning: updateWallet: Got CT_NEW, but transaction is already in model received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 IRC got join received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 accepted connection 70.176.73.232:60464 IRC got join send version message: version 60013, blocks=302, us=79.56.0.98:11110, them=70.176.73.232:60464, peer=70.176.73.232:60464 Added time data, samples 67, offset -6 (+0 minutes) nTimeOffset = -1 (+0 minutes) Moving 70.176.73.232:11110 to tried receive version message: version 60013, blocks=301, us=79.56.0.98:11110, them=70.176.73.232:11110, peer=70.176.73.232:60464 received block 0000000825a680abbfbb ProcessBlock: ACCEPTED Flushing wallet.dat Flushed wallet.dat 7ms getblocks 248 to 00000007fca9e9ab3967 limit 500 getblocks stopping at 251 00000007fca9e9ab3967 received block 000000033e451005664c SetBestChain: new best=000000033e451005664c height=303 trust=22225952132 blocktrust=1073758208 date=04/28/14 18:03:37 NotifyTransactionChanged 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 status=1 ProcessBlock: ACCEPTED updateWallet 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 1 inWallet=1 inModel=1 Index=0-1 showTransaction=1 derivedStatus=1
altro caso quando il blocco minato va in stale anche quì abbiamo il messagio "CheckWork() : new proof-of-work block found" che indica che un blocco è stato risolto. Prova ad accreditare i 1480 coins e 20 sui 2 indirizzi. ma il checkWork da errore "ERROR: CheckWork() : generated block is stale" il processo si conclude con "ProcessBlock: ACCEPTED" [b]CheckWork() : new proof-of-work block found[/b] hash: 0000014926625b19de3470ee0ff64dd533ae9a3e208cd0d778983d5369f9108e target: 00000fffff000000000000000000000000000000000000000000000000000000 CBlock(hash=0000014926625b19de3470ee0ff64dd533ae9a3e208cd0d778983d5369f9108e, ver=6, hashPrevBlock=000008d9fd3630515f6f9d6f7e8f677b2c10527313508a609bc5291b0313e0d5, hashMerkleRoot=de9634270757be3a37b40fbaa152273027be5bee0fdf286ecb9e078354bc9761, nTime=1398708030, nBits=1e0fffff, nNonce=354861, vtx=1, vchBlockSig=) Coinbase(hash=de96342707, nTime=1398708030, ver=1, vin.size=1, vout.size=2, nLockTime=0) CTxIn(COutPoint(0000000000, 4294967295), coinbase 01120101) CTxOut[b](nValue=1480.00[/b], scriptPubKey=OP_DUP OP_HASH160 1db90e7e0f31294f0309328572b3d8dc1fbf098a OP_EQUALVERIFY OP_CHECKSIG) CTxOut([b]nValue=20.00[/b], scriptPubKey=OP_DUP OP_HASH160 9d12999dad778a2ac107abc6f76b924062858eaa OP_EQUALVERIFY OP_CHECKSIG) vMerkleTree: de96342707 generated 1500.00 [b]ERROR: CheckWork() : generated block is stale[/b] getblocks 8 to 00000000000000000000 limit 500 received block 0000009594cfd72f055d SetBestChain: new best=0000009594cfd72f055d height=20 trust=22020117 blocktrust=1048577 date=04/28/14 18:00:29 [b]ProcessBlock: ACCEPTED[/b]
quindi io mi aspettavo di trovarmi N blocchi minati per quanti messaggi generated 1500.00AddToWallet 267fa275d8 newmi trovo nel log del wallet... ma così non è. Il dubbio mi è venuto perchè i pop up in basso a destra, dei blocchi trovati erano molti di più di quanti poi effettivamente me ne ritrovo nel wallet che sono solo 3. Sicuramente non c'ho capito una mazza.. e volevo una spiegazione da chi ne capisce più di me.... potrei vedere il codice c++ del wallet su github, ma purtroppo non ho competenze su c++... quindi mi affido a chi ne capisce più di me per avere una "lezione" su come si legge il log generato dal wallet... inoltre penso che sia cosa gradita per la comunità!!!! CIAO BBBBELLII!!!
|
|
|
..oggi ho provato a minare in solo summercoin fin da subito. sto cercando di capire il log generato dal wallet nella fase di mining in solo per vedere se le monete accreditate sono corrette.. dunque... minando in solo i casi sono 2: o trovi un blocco e viene accettato o trovi un blocco e questo va in stale. Ecco come ho proceduto per cercare di "leggere" il log... ho preso "ID della transazione" di un blocco minato. Per esempio 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 e l'ho cercato nel log. ecco cosa ho trovato: "new proof-of-work block found" sembra il messaggio che logga il wallet quando viene trovato l'hash del nuovo blocco "CTxOut(nValue=1480.00" e "CTxOut(nValue=20.00" solo il valore accreditato sul mio wallet e 20 sono le monete che per ogni blocco il dev cede in beneficieza. "AddToWallet 267fa275d8 new" sembra l'istruzione che aggiorna il contatore delle monete nel wallet "ProcessBlock: ACCEPTED" questo forse è il messaggio che indica che l'operazione è andata a buon fine. [b]CheckWork() : new proof-of-work block found [/b] hash: 00000003b0bea6892320a949df37819fd67b0da289d4b506d0c248a1fceda651 target: 00000003fffc0000000000000000000000000000000000000000000000000000 CBlock(hash=00000003b0bea6892320a949df37819fd67b0da289d4b506d0c248a1fceda651, ver=6, hashPrevBlock=0000000176dd1ea7c0466de395696c442975405b5e6c9b63265e87924e7aab08, hashMerkleRoot=267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5, nTime=1398708216, nBits=1d03fffc, nNonce=526045, vtx=1, vchBlockSig=) Coinbase(hash=267fa275d8, nTime=1398708216, ver=1, vin.size=1, vout.size=2, nLockTime=0) CTxIn(COutPoint(0000000000, 4294967295), coinbase 022e010108) CTxOut[b](nValue=1480.00[/b], scriptPubKey=OP_DUP OP_HASH160 1db90e7e0f31294f0309328572b3d8dc1fbf098a OP_EQUALVERIFY OP_CHECKSIG) CTxOut([b]nValue=20.00[/b], scriptPubKey=OP_DUP OP_HASH160 9d12999dad778a2ac107abc6f76b924062858eaa OP_EQUALVERIFY OP_CHECKSIG) vMerkleTree: 267fa275d8 [b]generated 1500.00[/b] [b]AddToWallet 267fa275d8 new[/b] NotifyTransactionChanged 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 status=1 NotifyTransactionChanged 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 status=0 updateWallet 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 1 SetBestChain: new best=00000003b0bea6892320 height=302 trust=21152193924 blocktrust=1073758208 date=04/28/14 18:03:36 ProcessBlock: ACCEPTED inWallet=1 inModel=0 Index=0-0 showTransaction=1 derivedStatus=0 updateWallet 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 0 inWallet=1 inModel=1 Index=0-1 showTransaction=1 derivedStatus=0 Warning: updateWallet: Got CT_NEW, but transaction is already in model received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 IRC got join received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 received getdata for: block 00000003b0bea6892320 accepted connection 70.176.73.232:60464 IRC got join send version message: version 60013, blocks=302, us=79.56.0.98:11110, them=70.176.73.232:60464, peer=70.176.73.232:60464 Added time data, samples 67, offset -6 (+0 minutes) nTimeOffset = -1 (+0 minutes) Moving 70.176.73.232:11110 to tried receive version message: version 60013, blocks=301, us=79.56.0.98:11110, them=70.176.73.232:11110, peer=70.176.73.232:60464 received block 0000000825a680abbfbb ProcessBlock: ACCEPTED Flushing wallet.dat Flushed wallet.dat 7ms getblocks 248 to 00000007fca9e9ab3967 limit 500 getblocks stopping at 251 00000007fca9e9ab3967 received block 000000033e451005664c SetBestChain: new best=000000033e451005664c height=303 trust=22225952132 blocktrust=1073758208 date=04/28/14 18:03:37 NotifyTransactionChanged 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 status=1 ProcessBlock: ACCEPTED updateWallet 267fa275d80d8e7929f47e373f3d96953aada23255fbaa34cab95d22d22b04a5 1 inWallet=1 inModel=1 Index=0-1 showTransaction=1 derivedStatus=1
altro caso quando il blocco minato va in stale anche quì abbiamo il messagio "CheckWork() : new proof-of-work block found" che indica che un blocco è stato risolto. Prova ad accreditare i 1480 coins e 20 sui 2 indirizzi. ma il checkWork da errore "ERROR: CheckWork() : generated block is stale" il processo si conclude con "ProcessBlock: ACCEPTED" [b]CheckWork() : new proof-of-work block found[/b] hash: 0000014926625b19de3470ee0ff64dd533ae9a3e208cd0d778983d5369f9108e target: 00000fffff000000000000000000000000000000000000000000000000000000 CBlock(hash=0000014926625b19de3470ee0ff64dd533ae9a3e208cd0d778983d5369f9108e, ver=6, hashPrevBlock=000008d9fd3630515f6f9d6f7e8f677b2c10527313508a609bc5291b0313e0d5, hashMerkleRoot=de9634270757be3a37b40fbaa152273027be5bee0fdf286ecb9e078354bc9761, nTime=1398708030, nBits=1e0fffff, nNonce=354861, vtx=1, vchBlockSig=) Coinbase(hash=de96342707, nTime=1398708030, ver=1, vin.size=1, vout.size=2, nLockTime=0) CTxIn(COutPoint(0000000000, 4294967295), coinbase 01120101) CTxOut[b](nValue=1480.00[/b], scriptPubKey=OP_DUP OP_HASH160 1db90e7e0f31294f0309328572b3d8dc1fbf098a OP_EQUALVERIFY OP_CHECKSIG) CTxOut([b]nValue=20.00[/b], scriptPubKey=OP_DUP OP_HASH160 9d12999dad778a2ac107abc6f76b924062858eaa OP_EQUALVERIFY OP_CHECKSIG) vMerkleTree: de96342707 generated 1500.00 [b]ERROR: CheckWork() : generated block is stale[/b] getblocks 8 to 00000000000000000000 limit 500 received block 0000009594cfd72f055d SetBestChain: new best=0000009594cfd72f055d height=20 trust=22020117 blocktrust=1048577 date=04/28/14 18:00:29 [b]ProcessBlock: ACCEPTED[/b]
quindi io mi aspettavo di trovarmi N blocchi minati per quanti messaggi generated 1500.00AddToWallet 267fa275d8 newmi trovo nel log del wallet... ma così non è. Il dubbio mi è venuto perchè i pop up in basso a destra, dei blocchi trovati erano molti di più di quanti poi effettivamente me ne ritrovo nel wallet che sono solo 3. Sicuramente non c'ho capito una mazza.. e volevo una spiegazione da chi ne capisce più di me.... potrei vedere il codice c++ del wallet su github, ma purtroppo non ho competenze su c++... quindi mi affido a chi ne capisce più di me per avere una "lezione" su come si legge il log generato dal wallet... inoltre penso che sia cosa gradita per la comunità!!!! CIAO BBBBELLII!!!
|
|
|
ahahahahaa forte!!!! come giveaway hano già fatto stampare un container di magliette degli iron maiden dei tempi d'oro!!!
|
|
|
Eccoti il sito: www.cryptocoincalendar.comQuesto sito dispone di calendari che indicano l'uscita delle prossime monete e i relativi link ai siti di quest'ultime. Eccoti un altro sito: www.google.itQuesto sito dispone di un potente algoritmo che consente di trovare quasi tutto ciò che è disponibile su Internet. Impara a usarlo. Per il resto c'è il DeepWeb, dove puoi accedere tramite TOR. (Eccoti un altro sito: www.google.it) = (Si. [FaSan]) or (lol [braytz])
|
|
|
ragazzi ma di futures coin con il discorso di allungare il tempo delle conferme?
non ho letto l'op di presentazione,ma...perchè si dovrebbe prolungare artificialmente il tempo di conferma? dal thread originale: "The reasoning behind our long block maturity is simply to keep the miners in check. It is to prevent the instant "mine and dump", and give miners a vested interest in the success and stability of the coin. Not only does this give the coin more resilience in the first few weeks of usage, it also reduces risk among those that hold the coin through our futures market. Similar to "vesting" in a stock option. See http://en.wikipedia.org/wiki/Employee_stock_option#Contract_differences*IPO and bounty accounts for first 400 blocks. 2 week block maturity: 401-14000 blocks 3 week block maturity: 14001-140001 blocks 4 week block maturity: 140001- ∞ blocks" potrebbe esser einteressante anche l'algo: un mix tra Groestl (old GPU/CPU), Skein (new GPU/CPU) e SHA256 (ASIC). Futurecoin has a 1 minute block time per algo, such that each algorithm should find a block every 3 minutes. magari consuma pure poco tipo HEFTY1 se non X11... vediamo...
|
|
|
ragazzi ma di futures coin con il discorso di allungare il tempo delle conferme? cosa ne pensate? è una delle poche che introduce qualche novità...
|
|
|
|