|
pjr77
|
 |
August 02, 2014, 11:05:06 AM |
|
They have gone way out of their league now. Should have stuck with copy paste  |
|
|
|
|
|
CryptoLTD
|
|
August 02, 2014, 01:04:19 PM |
|
They have gone way out of their league now. Should have stuck with copy paste Thats the beauty of open source, im sure 'someone' will take it over if this is a case of dev's calling it quits.. I mean what better coin to do it with, no premine & hidden block noncense. |
|
|
|
|
roundmaster
Member
 Offline
Activity: 81
Merit: 10
|
|
August 02, 2014, 04:06:14 PM
Last edit: August 02, 2014, 04:21:55 PM by roundmaster |
|
I've synced again with the last repository. I see only one valid block chain. Anyway, there is an invalid block chain too, that generates the warning flag.
|
|
|
|
|
MinersPoolEU
Member
Offline
Activity: 96
Merit: 10
|
|
August 02, 2014, 04:10:56 PM |
|
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
|
|
|
|
|
roundmaster
Member
Offline
Activity: 81
Merit: 10
|
|
August 02, 2014, 04:29:37 PM |
|
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.
|
|
|
|
|
|
CryptoLTD
|
|
August 02, 2014, 04:43:02 PM |
|
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
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. |
|
|
|
|
|
CryptoLTD
|
|
August 02, 2014, 04:44:30 PM |
|
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. |
|
|
|
|
|
CryptoLTD
|
|
August 02, 2014, 04:54:00 PM |
|
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.
|
|
|
|
|
|
phzi
|
|
August 02, 2014, 07: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.
|
|
|
|
|
|
CryptoLTD
|
|
August 02, 2014, 08: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.
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. |
|
|
|
|
|
CryptoLTD
|
|
August 02, 2014, 08: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.
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. |
|
|
|
|
cyberguru
Member
Offline
Activity: 88
Merit: 10
|
|
August 03, 2014, 07: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....
|
|
|
|
|
|
execoin (OP)
|
|
August 03, 2014, 07: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.
|
|
|
|
|
cyberguru
Member
Offline
Activity: 88
Merit: 10
|
|
August 03, 2014, 08: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.
Finaly we got an answeer. Keep Working, Devs . Almoos i've lost hope.. |
|
|
|
|
llildur
Member
Offline
Activity: 118
Merit: 10
|
|
August 03, 2014, 10:33:13 AM |
|
|
|
|
|
|
|
CryptoLTD
|
|
August 03, 2014, 11:40:13 AM |
|
YAY! Dev is here..cool..will await instructions
|
|
|
|
|
cyberguru
Member
Offline
Activity: 88
Merit: 10
|
|
August 03, 2014, 02:10:53 PM |
|
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.
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... |
|
|
|
|
|
CryptoLTD
|
|
August 03, 2014, 05: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.
|
|
|
|
|
wgd
Legendary
Offline
Activity: 1815
Merit: 1005
|
|
August 04, 2014, 09:59:20 PM |
|
market moved upwards, shopping really insiders? Soon the good news In relation consistency network?
|
|
|
|
|
oni4an
|
|
August 05, 2014, 07: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 ? |
|
|
|
|
|
