[ANN] ECC

[Limx Dev]

I 've send my coin. Now is all lose. Transaction does not appear.

.....

http://blockexperts.com/ecc/address/EaFFwznUKZTSr8XT7fSfdctMrd2MFNMyC7

often the explorers take time to show new balances for address
but it should show the transaction in the block before it reconciles against the address.

>> try putting the tx id into the Blockcoin Super Search field.

I 've send for a week.



{
"version" : "v2.4.3.0",
"protocolversion" : 60011,
"walletversion" : 60000,
"balance" : 0.30689700,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 687502,
"timeoffset" : -2,
"moneysupply" : 18728981298.15876770,
"connections" : 2,
"proxy" : "",
"ip" : "5.56.209.255",
"difficulty" : {
"proof-of-work" : 37.53923539,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1431177149,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"errors" : ""
}

if your block height does not match the BE, then delete your blockchain and resync from the bootstrap in the original post. try adding addnode=129.21.141.135 to your conf file. i host 5 nodes and that is one of them.  this might help. once you are resynced open your debug console and type repairwallet
this should fix the balance and get you on the right chain if you arent on it

I'll add this node. I recommend a new protcolversion!!

i had been wondering lately if i should have done that.

I 've send my last 0,3 ECC @ EXzt3cDJGdR5jHaAqphQo6GhAWwmGxBd2h (Griffith)

Code:

18:00:45

getpeerinfo


18:00:45

[
{
"addr" : "188.165.82.227:19118",
"services" : "00000001",
"lastsend" : 1431964785,
"lastrecv" : 1431964785,
"conntime" : 1431964664,
"version" : 60011,
"subver" : "/ECCoin:2.4.3/",
"inbound" : false,
"startingheight" : 687502,
"banscore" : 0
}
]

CommitTransaction:
CTransaction(hash=bf1f6850a1, nTime=1431964772, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(7e1e7b502e, 0), scriptSig=304402206cfa238cfc410dd0)
    CTxOut(nValue=0.00006897, scriptPubKey=OP_DUP OP_HASH160 37b0a046eddf3f70315e13137dd8487bd57270a7 OP_EQUALVERIFY OP_CHECKSIG)
    CTxOut(nValue=0.003, scriptPubKey=OP_DUP OP_HASH160 a2d4ef3a387655797453b7c8c53d3c14b2f62dc4 OP_EQUALVERIFY OP_CHECKSIG)
AddToWallet bf1f6850a1  new
WalletUpdateSpent found spent coin 0.00306897 SUM 7e1e7b502e88c94aa95be41958a16002f31e15208c6336e37b385cd50f9d46c5
NotifyTransactionChanged bf1f6850a1a66ee94a1b3d0fbd4b3182b44b4ea05cc253f082cfe74e6c6632a2 status=0
NotifyTransactionChanged 7e1e7b502e88c94aa95be41958a16002f31e15208c6336e37b385cd50f9d46c5 status=1
CTxMemPool::accept() : accepted bf1f6850a1 (poolsz 2)
Relaying wtx bf1f6850a1
NotifyAddressBookChanged EXzt3cDJGdR5jHaAqphQo6GhAWwmGxBd2h  isMine=0 status=0

[Griffith]

I 've send my coin. Now is all lose. Transaction does not appear.

.....

http://blockexperts.com/ecc/address/EaFFwznUKZTSr8XT7fSfdctMrd2MFNMyC7

often the explorers take time to show new balances for address
but it should show the transaction in the block before it reconciles against the address.

>> try putting the tx id into the Blockcoin Super Search field.

I 've send for a week.



{
"version" : "v2.4.3.0",
"protocolversion" : 60011,
"walletversion" : 60000,
"balance" : 0.30689700,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 687502,
"timeoffset" : -2,
"moneysupply" : 18728981298.15876770,
"connections" : 2,
"proxy" : "",
"ip" : "5.56.209.255",
"difficulty" : {
"proof-of-work" : 37.53923539,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1431177149,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"errors" : ""
}

if your block height does not match the BE, then delete your blockchain and resync from the bootstrap in the original post. try adding addnode=129.21.141.135 to your conf file. i host 5 nodes and that is one of them.  this might help. once you are resynced open your debug console and type repairwallet
this should fix the balance and get you on the right chain if you arent on it

I'll add this node. I recommend a new protcolversion!!

i had been wondering lately if i should have done that.

I 've send my last 0,3 ECC @ EXzt3cDJGdR5jHaAqphQo6GhAWwmGxBd2h (Griffith)

Code:

18:00:45

getpeerinfo


18:00:45

[
{
"addr" : "188.165.82.227:19118",
"services" : "00000001",
"lastsend" : 1431964785,
"lastrecv" : 1431964785,
"conntime" : 1431964664,
"version" : 60011,
"subver" : "/ECCoin:2.4.3/",
"inbound" : false,
"startingheight" : 687502,
"banscore" : 0
}
]

CommitTransaction:
CTransaction(hash=bf1f6850a1, nTime=1431964772, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(7e1e7b502e, 0), scriptSig=304402206cfa238cfc410dd0)
    CTxOut(nValue=0.00006897, scriptPubKey=OP_DUP OP_HASH160 37b0a046eddf3f70315e13137dd8487bd57270a7 OP_EQUALVERIFY OP_CHECKSIG)
    CTxOut(nValue=0.003, scriptPubKey=OP_DUP OP_HASH160 a2d4ef3a387655797453b7c8c53d3c14b2f62dc4 OP_EQUALVERIFY OP_CHECKSIG)
AddToWallet bf1f6850a1  new
WalletUpdateSpent found spent coin 0.00306897 SUM 7e1e7b502e88c94aa95be41958a16002f31e15208c6336e37b385cd50f9d46c5
NotifyTransactionChanged bf1f6850a1a66ee94a1b3d0fbd4b3182b44b4ea05cc253f082cfe74e6c6632a2 status=0
NotifyTransactionChanged 7e1e7b502e88c94aa95be41958a16002f31e15208c6336e37b385cd50f9d46c5 status=1
CTxMemPool::accept() : accepted bf1f6850a1 (poolsz 2)
Relaying wtx bf1f6850a1
NotifyAddressBookChanged EXzt3cDJGdR5jHaAqphQo6GhAWwmGxBd2h  isMine=0 status=0

you are on a fork from the BE. it seems that there are still 2 forks left. (a main chain and 1 fork) and with these forks it is making it increasingly hard to test the new CryptoBank app. so i guess i will address them first. a new version of the wallet will be out shortly. it will contain an updated protocol level. and should be the final version.

[Limx Dev]

I 've send my coin. Now is all lose. Transaction does not appear.

.....

http://blockexperts.com/ecc/address/EaFFwznUKZTSr8XT7fSfdctMrd2MFNMyC7

often the explorers take time to show new balances for address
but it should show the transaction in the block before it reconciles against the address.

>> try putting the tx id into the Blockcoin Super Search field.

I 've send for a week.



{
"version" : "v2.4.3.0",
"protocolversion" : 60011,
"walletversion" : 60000,
"balance" : 0.30689700,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 687502,
"timeoffset" : -2,
"moneysupply" : 18728981298.15876770,
"connections" : 2,
"proxy" : "",
"ip" : "5.56.209.255",
"difficulty" : {
"proof-of-work" : 37.53923539,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1431177149,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"errors" : ""
}

if your block height does not match the BE, then delete your blockchain and resync from the bootstrap in the original post. try adding addnode=129.21.141.135 to your conf file. i host 5 nodes and that is one of them.  this might help. once you are resynced open your debug console and type repairwallet
this should fix the balance and get you on the right chain if you arent on it

I'll add this node. I recommend a new protcolversion!!

i had been wondering lately if i should have done that.

I 've send my last 0,3 ECC @ EXzt3cDJGdR5jHaAqphQo6GhAWwmGxBd2h (Griffith)

Code:

18:00:45

getpeerinfo


18:00:45

[
{
"addr" : "188.165.82.227:19118",
"services" : "00000001",
"lastsend" : 1431964785,
"lastrecv" : 1431964785,
"conntime" : 1431964664,
"version" : 60011,
"subver" : "/ECCoin:2.4.3/",
"inbound" : false,
"startingheight" : 687502,
"banscore" : 0
}
]

CommitTransaction:
CTransaction(hash=bf1f6850a1, nTime=1431964772, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(7e1e7b502e, 0), scriptSig=304402206cfa238cfc410dd0)
    CTxOut(nValue=0.00006897, scriptPubKey=OP_DUP OP_HASH160 37b0a046eddf3f70315e13137dd8487bd57270a7 OP_EQUALVERIFY OP_CHECKSIG)
    CTxOut(nValue=0.003, scriptPubKey=OP_DUP OP_HASH160 a2d4ef3a387655797453b7c8c53d3c14b2f62dc4 OP_EQUALVERIFY OP_CHECKSIG)
AddToWallet bf1f6850a1  new
WalletUpdateSpent found spent coin 0.00306897 SUM 7e1e7b502e88c94aa95be41958a16002f31e15208c6336e37b385cd50f9d46c5
NotifyTransactionChanged bf1f6850a1a66ee94a1b3d0fbd4b3182b44b4ea05cc253f082cfe74e6c6632a2 status=0
NotifyTransactionChanged 7e1e7b502e88c94aa95be41958a16002f31e15208c6336e37b385cd50f9d46c5 status=1
CTxMemPool::accept() : accepted bf1f6850a1 (poolsz 2)
Relaying wtx bf1f6850a1
NotifyAddressBookChanged EXzt3cDJGdR5jHaAqphQo6GhAWwmGxBd2h  isMine=0 status=0

you are on a fork from the BE. it seems that there are still 2 forks left. (a main chain and 1 fork) and with these forks it is making it increasingly hard to test the new CryptoBank app. so i guess i will address them first. a new version of the wallet will be out shortly. it will contain an updated protocol level. and should be the final version.

I have their chain loaded. I can send my private key for testing.

[Griffith]

please do not send ECC to and from exchanges (because it wont work) until we have confirmed that the exchange has updated the wallet. (we will be posting it in the OP)

[pineapples]

strangely it was syncing nicely with 7 connections, couple hundred blocks left when i thought i would start the ExclusiveCoind. ( this same thing happened twice. below is from the second time)

my debug.log will be gigs by morning at this rate. lol

ProcessBlock: ORPHAN BLOCK with hash = 97d184f6f334b9948b9d, prevHash=0a9392183b484dd32625



EDIT: pah. here... daemon appears in sync with BE

getinfo
{
    "version" : "v2.4.3.0",
    "protocolversion" : 60011,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 687330,
    "timeoffset" : -1,
    "moneysupply" : 18725324198.16433716,
    "connections" : 7,
    "proxy" : "",
    "ip" : "178.62.208.32",
    "difficulty" : {
        "proof-of-work" : 37.53923539,
        "proof-of-stake" : 0.00024414
    },
    "testnet" : false,
    "keypoololdest" : 1431490686,
    "keypoolsize" : 102,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00000000,
    "errors" : ""
}

here's a copy of the first "small" section of my debug.log

http://pastebin.com/edVHdMVx

it keeps filling rapidly up with large chunks of getblock requests. large chunks of orphan blockmessages
and small sections of connection timeouts.

you seem to not know how a daemon works?   

getblock requests when it says block X to 0000 and then stopping at Y is someone asking your wallet fro blocks so they can sync on the chain.
connection timeouts are supposed to happen as well, more than likely you are connecting to a peer that is offline atm.
as for orphan blocks. that happens whenevr you get sent a block that isnt the next block in the chain. so thats normal as well.

how do you know the blocks being accepted are "random"?

as for limux dev, where did you send coins to / is your wallet synced with the BE? if not then you arent on the right chain so it wont show up anyway

sorry i was tired and didnt really re-read my post so it was a bit scattered.

what i thought worth mentioning was >>

once i started ExclusiveCoind, then immediately it was generating lots of timeouts. not before. and this stopped after stopping ExclusiveCoind.

the other thing is that the debug.log was rapidly filling up. i will have to link it to /dev/null because it is far too big too quickly.
the getblock and processblocks entries were very fast and furious.

..
the other parts were questions really . i havent seen such a flurry of text before and i am curious ..
why why why ??

i have zero balance so i guess then that >>

received block 97839171ec906a734277
ProcessBlock: ORPHAN BLOCK with hash = 97839171ec906a734277, prevHash=82e8dab6440$
sending new getBlocks request from 02d4f1d14895027d1d240fbf947a364ee663f653ce1763$

is to do with other wallets minting ? or other chains trying to get accepted ??


similarly then the getblocks mayhave been related to multiple chains ? i guess i should try it with connecting only to seemingly synced nodes.

[rainly]

hello! where Trading ECC, why delete ECC Trading in  AllCoin.com.

[mdtspain]

hello! where Trading ECC, why delete ECC Trading in  AllCoin.com.

There is no delete of ECC Trading on Allcoin.com as far as I know

[mdtspain]

ECC-Wallet

We have changed the wallet protocol version and made some other small adjustments.
On this moment we are testing the wallet and sending the request to the exchanges to update the wallet. It is a mandatory update.

Everybody can use the blockchain link that is available for download in the OP, it is valid.

People that don't update won't be able to stake or sync their wallets.

For Linux wallets: The source code for version 2.4.4.0 is available on the github: https://github.com/Greg-Griffith/ECCoin

Mac and Windows links will be updated ASAP, just look for the 2.4.4.0 version.

[apojii]

Super coin will be half in some days

[Griffith]

Super coin will be half in some days

 supercoin will be dealt with after we get ECC and MWC finalized and processed.

[sacskate]

Are you planning on changing supercoin's pos specs? Will it stay 100% per year or will it change year to year. If it changes how long is left with the 100%? Are the super pos blocks still in play?

[pineapples]

once i started ExclusiveCoind, then immediately it was generating lots of timeouts. not before. and this stopped after stopping ExclusiveCoind.

the other thing is that the debug.log was rapidly filling up. i will have to link it to /dev/null because it is far too big too quickly.
the getblock and processblocks entries were very fast and furious.

word is that Exclusive daemon is a bit of a hog :p

will experiment without it and see how EEC syncs with new version.

[pineapples]

compiled new version as daemon


getblocks -1 to 00000000000000000000 limit 500
received block c840f08a2eb692cddc17
ERROR: GetSyncCheckpoint: block index missing for current sync-checkpoint ae2e43c35a3346fa798a0a356ca7a4bce57885ee64e4319295f7f3b7210944f1
ECC: checkpoints.cpp:190: bool Checkpoints::CheckSync(const uint256&, const CBlockIndex*): Assertion `mapBlockIndex.count(hashSyncCheckpoint)' failed.




does that mean i need to resync again
:p


edit.
i took that checkpoint out of checkpoints.h, recompiled, and seems to be syncing fine now.
..
am now running the "official" code. and all is well.

[david1365]

What happened to Super Coin, is it dead officially
Also most of the stakes are still orphaned.

[Griffith]

compiled new version as daemon


getblocks -1 to 00000000000000000000 limit 500
received block c840f08a2eb692cddc17
ERROR: GetSyncCheckpoint: block index missing for current sync-checkpoint ae2e43c35a3346fa798a0a356ca7a4bce57885ee64e4319295f7f3b7210944f1
ECC: checkpoints.cpp:190: bool Checkpoints::CheckSync(const uint256&, const CBlockIndex*): Assertion `mapBlockIndex.count(hashSyncCheckpoint)' failed.




does that mean i need to resync again
:p


edit.
i took that checkpoint out of checkpoints.h, recompiled, and seems to be syncing fine now.
..
am now running the "official" code. and all is well.

dont take that checkpoint out. your wallet will fuck itself. and will never sync

[sovie]

no supercoin is not dead,
its just not trading on bittrex anymore.
its trading on cryptsy and others.

The coin is still in our overall plans so
like all coin development its a waiting game.

the coins price is directly related to the coins community
and their trading of the coin or not.

as always keep minting mining and trading

[Griffith]

compiled new version as daemon


getblocks -1 to 00000000000000000000 limit 500
received block c840f08a2eb692cddc17
ERROR: GetSyncCheckpoint: block index missing for current sync-checkpoint ae2e43c35a3346fa798a0a356ca7a4bce57885ee64e4319295f7f3b7210944f1
ECC: checkpoints.cpp:190: bool Checkpoints::CheckSync(const uint256&, const CBlockIndex*): Assertion `mapBlockIndex.count(hashSyncCheckpoint)' failed.




does that mean i need to resync again
:p


edit.
i took that checkpoint out of checkpoints.h, recompiled, and seems to be syncing fine now.
..
am now running the "official" code. and all is well.

so put the checkpoint back in and resync from the chain on the op. if you dont put that checkpoint back in the other wallets will read yours as toxic and ban your ip from the connection list since they do that ysing the checkpoints

[pineapples]

compiled new version as daemon


getblocks -1 to 00000000000000000000 limit 500
received block c840f08a2eb692cddc17
ERROR: GetSyncCheckpoint: block index missing for current sync-checkpoint ae2e43c35a3346fa798a0a356ca7a4bce57885ee64e4319295f7f3b7210944f1
ECC: checkpoints.cpp:190: bool Checkpoints::CheckSync(const uint256&, const CBlockIndex*): Assertion `mapBlockIndex.count(hashSyncCheckpoint)' failed.




does that mean i need to resync again
:p


edit.
i took that checkpoint out of checkpoints.h, recompiled, and seems to be syncing fine now.
..
am now running the "official" code. and all is well.

so put the checkpoint back in and resync from the chain on the op. if you dont put that checkpoint back in the other wallets will read yours as toxic and ban your ip from the connection list since they do that ysing the checkpoints

i have put it back and it is fine.
seemed i wasnt up to that block (of the checkpoint).
i took out that checkpoint. compiled.
then it synced fine on the correct chain.
i put the checkpoint back. compiled.
all is good now.

except i'm waiting for comkort to update so i can withdraw


..
i must remember to explain myself better :p

[mdtspain]

I will open an account on comkort also. Maybe we can get some trading going on their platform

[GDF]

Tiny typo on the trustedcryptos website under 'Our Coins' the 3 coins  says X 4 conf.for a transacaction instead of transactions. I still love you guys and ECC though