RIP
?Patience little grasshopper! =)
Topic: Execoin: | First Open-Source Stealth Wallet Released! | Fast | ASIC-proof - page 25. (Read 281694 times)
August 05, 2014, 05:17:21 AM
August 05, 2014, 05:07:03 AM
RIP
August 05, 2014, 04:31:25 AM
I think, bugs in code, are the problem. Finding them, testing tak a lot of time. Making new soft take also a lot of
time. That's not only a copy & paste from vert...... It's better to stuck frozen, for a longer time.
Devs, take your time & make it better & worth "millions"
. agree
August 05, 2014, 03:20:24 AM
market moved upwards, shopping really insiders? Soon the good news In relation consistency network?
Maybe the devs giving an update make some people buy back. But the rise was really small anyway.
August 05, 2014, 03:13:24 AM
[/quote]
I think, bugs in code, are the problem. Finding them, testing tak a lot of time. Making new soft take also a lot of
time. That's not only a copy & paste from vert...... It's better to stuck frozen, for a longer time.
Devs, take your time & make it better & worth "millions"
. 
August 05, 2014, 02:09:45 AM
The problem is that afterfork code has a bug. At some arbitrary point of time a node fails to agree with the rest of the network on a reward amount:
ERROR: ConnectBlock() : coinbase pays too much
and the wallet gets stuck on the corresponding block. Darkcoin once had a similar problem with wallets getting stuck because of a bug in their dynamic reward code.
Because of a lot of transfers went to nowhere, the only solution is to fix the bug and restart the network from 307770 again.
restart what is the problem ? ERROR: ConnectBlock() : coinbase pays too much
and the wallet gets stuck on the corresponding block. Darkcoin once had a similar problem with wallets getting stuck because of a bug in their dynamic reward code.
Because of a lot of transfers went to nowhere, the only solution is to fix the bug and restart the network from 307770 again.
August 04, 2014, 04:59:20 PM
market moved upwards, shopping really insiders? Soon the good news In relation consistency network?
August 03, 2014, 12:29:16 PM
I think the key here, is to get everyone on the same page. If people node-ops dont respond in a set ammount of time, their node isnt coded in. Obviously more nodes can be added by the end usere @ any time as they become available.
Dev's, if you need any non-coding assistance & all.. please speak up, I don't want to speak for others.. but If theres is anything we can help with, even if trivial.. please let us know. I have already let one of the mods know @ Poloniex of the pending re-release @ block 307770, about to do same with cryptsy.
Dev's, if you need any non-coding assistance & all.. please speak up, I don't want to speak for others.. but If theres is anything we can help with, even if trivial.. please let us know. I have already let one of the mods know @ Poloniex of the pending re-release @ block 307770, about to do same with cryptsy.
August 03, 2014, 09:10:53 AM
The problem is that afterfork code has a bug. At some arbitrary point of time a node fails to agree with the rest of the network on a reward amount:
ERROR: ConnectBlock() : coinbase pays too much
and the wallet gets stuck on the corresponding block. Darkcoin once had a similar problem with wallets getting stuck because of a bug in their dynamic reward code.
Because of a lot of transfers went to nowhere, the only solution is to fix the bug and restart the network from 307770 again.
ERROR: ConnectBlock() : coinbase pays too much
and the wallet gets stuck on the corresponding block. Darkcoin once had a similar problem with wallets getting stuck because of a bug in their dynamic reward code.
Because of a lot of transfers went to nowhere, the only solution is to fix the bug and restart the network from 307770 again.
Sound like new wallets & other stuff, more coding, more possible errors. Devs, work & take your time, i'ts better for the coin, to stuck in 1 week of hard fork, then stuck 3 times for 3 days in row...
August 03, 2014, 06:40:13 AM
YAY! Dev is here..cool..will await instructions
August 03, 2014, 05:33:13 AM
The problem is that afterfork code has a bug. At some arbitrary point of time a node fails to agree with the rest of the network on a reward amount:
ERROR: ConnectBlock() : coinbase pays too much
and the wallet gets stuck on the corresponding block. Darkcoin once had a similar problem with wallets getting stuck because of a bug in their dynamic reward code.
Because of a lot of transfers went to nowhere, the only solution is to fix the bug and restart the network from 307770 again.
ERROR: ConnectBlock() : coinbase pays too much
and the wallet gets stuck on the corresponding block. Darkcoin once had a similar problem with wallets getting stuck because of a bug in their dynamic reward code.
Because of a lot of transfers went to nowhere, the only solution is to fix the bug and restart the network from 307770 again.
Lets do it thanks 4 the update
August 03, 2014, 03:39:33 AM
The problem is that afterfork code has a bug. At some arbitrary point of time a node fails to agree with the rest of the network on a reward amount:
ERROR: ConnectBlock() : coinbase pays too much
and the wallet gets stuck on the corresponding block. Darkcoin once had a similar problem with wallets getting stuck because of a bug in their dynamic reward code.
Because of a lot of transfers went to nowhere, the only solution is to fix the bug and restart the network from 307770 again.
ERROR: ConnectBlock() : coinbase pays too much
and the wallet gets stuck on the corresponding block. Darkcoin once had a similar problem with wallets getting stuck because of a bug in their dynamic reward code.
Because of a lot of transfers went to nowhere, the only solution is to fix the bug and restart the network from 307770 again.
Finaly we got an answeer. Keep Working, Devs . Almoos i've lost hope..
August 03, 2014, 02:37:36 AM
The problem is that afterfork code has a bug. At some arbitrary point of time a node fails to agree with the rest of the network on a reward amount:
ERROR: ConnectBlock() : coinbase pays too much
and the wallet gets stuck on the corresponding block. Darkcoin once had a similar problem with wallets getting stuck because of a bug in their dynamic reward code.
Because of a lot of transfers went to nowhere, the only solution is to fix the bug and restart the network from 307770 again.
ERROR: ConnectBlock() : coinbase pays too much
and the wallet gets stuck on the corresponding block. Darkcoin once had a similar problem with wallets getting stuck because of a bug in their dynamic reward code.
Because of a lot of transfers went to nowhere, the only solution is to fix the bug and restart the network from 307770 again.
August 03, 2014, 02:17:18 AM
Miracles doesnt exist in crypto world... Sell yours exe, for nothing... if you are lucky, and u dosn,t stuck in your wallet....
August 02, 2014, 03:36:06 PM
Yeesh, you don't need devs right now. And why the heck are you spamming this thread so frequently, CryptoLTD?
The correct fork is the longer fork that is compliant with the current daemon. That's how blockchains works - the community reaches consensus, not the developers.
The correct fork is the longer fork that is compliant with the current daemon. That's how blockchains works - the community reaches consensus, not the developers.
If you want this coin tradable anywhere, you can re-release newly coded src & wallet , put up nodes, contact the exchanges and merchants that use it, and sort it all out, providing 'The community' agrees. As it stands now.. the 'open source' code is NON functional. Feel free .. get to work.. were waiting...still waiting.
August 02, 2014, 03:32:49 PM
Yeesh, you don't need devs right now. And why the heck are you spamming this thread so frequently, CryptoLTD?
The correct fork is the longer fork that is compliant with the current daemon. That's how blockchains works - the community reaches consensus, not the developers.
The correct fork is the longer fork that is compliant with the current daemon. That's how blockchains works - the community reaches consensus, not the developers.
There is no correct chain, its forked, off on its own.. aside from the one the dev forked 'to' you're wrong. Thats how it works.. your very wrong, again. Theres no community on 'a' chain. If that was the case, the one pool thats mining 'A' chain would have OPEN registrations.. its not, its closed, because poloniex synced to THAT chain... which is the incorrect chain, whish is not available to any one, more specifically 'THE' public block chain that did exist, from the developers open source git code & wallet. FTR, poloniex has froze their wallet, as they should have.
August 02, 2014, 02:36:50 PM
Yeesh, you don't need devs right now. And why the heck are you spamming this thread so frequently, CryptoLTD?
The correct fork is the longer fork that is compliant with the current daemon. That's how blockchains works - the community reaches consensus, not the developers.
The correct fork is the longer fork that is compliant with the current daemon. That's how blockchains works - the community reaches consensus, not the developers.
August 02, 2014, 11:54:00 AM
A competent pool would do the same.. but I see, thats not in your 'agenda'. Hoping the devs come back & roll with 'your' chain. Dev's are gone.. for now.. just deal with it.
August 02, 2014, 11:44:30 AM
The 'warning' flag locked the daemon, and this flag will be still there for some time; Some are mining on the wrong chain, and not all the daemons are updated. And mining is not so easy with the current situation: the daemon goes in 'safe mode'. Anyway transferring to an exchange is not safe for the time being.
You cant.. exchganges are all locked down. And will remain so untill the developers say which one is right. With a working explorer, @ least the competent ones.
August 02, 2014, 11:43:02 AM
My wallet uses the same blockchain than Poloniex. I tried to send some coins to Poloniex and I received coins.
If you want to synchronise your wallet, here is my node execoin.miners-pool.eu
If you want to synchronise your wallet, here is my node execoin.miners-pool.eu
Not using any block chain unless the developers say which one is right. The OLY block chain, will be THEE block chain that the wallet uses in conjunction with ALL exchanges and ALL services. Untill then.. its done. Devs dissapeared. Needs to be taken over.
Jump to: