We really need someone to apply merged mining patches to bitcoin and make just that into a github repo.
Maybe all the merged mined coins could gang up to offer a multi-currency bounty for that or something?
-MarkM-
Topic: [DEAD] Coiledcoin - yet another cryptocurrency, but with OP_EVAL! - page 3. (Read 68090 times)
May 05, 2013, 02:53:17 PM
May 05, 2013, 06:19:02 AM
I've taken my node with what I assume is the dead chain offline and am trying to redownload a new blockchain. I'll see what one I end up getting.
My redownload has now got the non-dead chain. Hopefully that one will disappear as nodes using it go offline. May 05, 2013, 05:00:15 AM
I have a vague memory-of-a-memory of something about the BDB problems that led to the recent Bitcoin fork being able to abort a branch due to a BDB error, the error being handled in such a way the block was treated as bad instead of the system realising it had no real idea whether the block was actually bad because it simply ran out of BDB locks when trying to work with the problem.
That is, a re-org attempt would run out of locks and think like "oh I guess I was fine without a re-org".
It was why the bitcoin fork was going the way it was going I think, nodes with low BDB lock count would crap out trying to take one path of the fork and assume it was a bad block instead of realising they didn't have enough locks to be able to really process the thing to find out it was not a bad block just a bad (too low) BDB locks count limit.
We need to apply the merged mining patches to a recent but good/stable bitcoin to make a "bitcoin with ONLY the merged mining patches applied" repository, then each merged mined coin can individually fork off of that to add their own unique patches that make them the particular merged mined chain that they are. They could all do with a code update/upgrade.
-MarkM-
That is, a re-org attempt would run out of locks and think like "oh I guess I was fine without a re-org".
It was why the bitcoin fork was going the way it was going I think, nodes with low BDB lock count would crap out trying to take one path of the fork and assume it was a bad block instead of realising they didn't have enough locks to be able to really process the thing to find out it was not a bad block just a bad (too low) BDB locks count limit.
We need to apply the merged mining patches to a recent but good/stable bitcoin to make a "bitcoin with ONLY the merged mining patches applied" repository, then each merged mined coin can individually fork off of that to add their own unique patches that make them the particular merged mined chain that they are. They could all do with a code update/upgrade.
-MarkM-
May 05, 2013, 04:56:46 AM
Smalll change test coin is running, I think diff is small there. Also anyone plans to releae SHA3 currency? And if I for example really wanted to mine some coin with a friend I would simply restart it again and again till its still fun lol And if Luke did not process blocks others could still process them right? From what I understood even if someone got 51% they can only double spend their blocks not others since then they would have to resolve every block back in time right?
Well, don't connect to the block chain used by the above block explorer. Its last block is dated ~15 days ago - 2013-04-20 13:06:52 May 05, 2013, 04:53:39 AM
When i try to solomine my coiledcoin client (server) crashes. It's the only coin with that problem; Does someone know what's wrong?
Mine usually crashes when I try to solo mine before the block chain is completely done downloading.Strange, my client has a bug then. It is fully synchronised but says 'last block generated %n seconds ago'
May 05, 2013, 04:50:25 AM
I think I might have been connected to that last node. My last transaction was on 4/16/2013 with a total block count of 183148. Looks like I am about to lose a lot of coins from my wallet.
I'm curious why a reorg never happened. I've taken my node with what I assume is the dead chain offline and am trying to redownload a new blockchain. I'll see what one I end up getting. May 05, 2013, 04:45:12 AM
./coiledcoind.sh getblockhash 179577
e654dad298eeccbcd74e90804a5ac1583a875a4fd08ed4e90844e44cd6806e34
./coiledcoind.sh getblockcount
195368
Thanks, that's what one of my nodes gets. The other has:e654dad298eeccbcd74e90804a5ac1583a875a4fd08ed4e90844e44cd6806e34
./coiledcoind.sh getblockcount
195368
Code:
coiledcoind getblockhash 179577
c4720651f8f96152894218250efad3266110b378689209b671f13c94285993f9
coiledcoind getblockcount
183496
It hasn't seen a block since 18th April though so whatever node that was feeding it might be gone.
I think I might have been connected to that last node. My last transaction was on 4/16/2013 with a total block count of 183148. Looks like I am about to lose a lot of coins from my wallet.
May 05, 2013, 04:43:16 AM
When i try to solomine my coiledcoin client (server) crashes. It's the only coin with that problem; Does someone know what's wrong?
Mine usually crashes when I try to solo mine before the block chain is completely done downloading. May 05, 2013, 04:39:09 AM
When i try to solomine my coiledcoin client (server) crashes. It's the only coin with that problem; Does someone know what's wrong?
May 05, 2013, 04:36:07 AM
./coiledcoind.sh getblockhash 179577
e654dad298eeccbcd74e90804a5ac1583a875a4fd08ed4e90844e44cd6806e34
./coiledcoind.sh getblockcount
195368
Thanks, that's what one of my nodes gets. The other has:e654dad298eeccbcd74e90804a5ac1583a875a4fd08ed4e90844e44cd6806e34
./coiledcoind.sh getblockcount
195368
Code:
coiledcoind getblockhash 179577
c4720651f8f96152894218250efad3266110b378689209b671f13c94285993f9
coiledcoind getblockcount
183496
It hasn't seen a block since 18th April though so whatever node that was feeding it might be gone.
May 05, 2013, 04:32:40 AM
Both of my servers dvcstable01.devcoin.org and dvcstable02.devcoin.org get the same result:
./coiledcoind.sh getblockhash 179577
e654dad298eeccbcd74e90804a5ac1583a875a4fd08ed4e90844e44cd6806e34
./coiledcoind.sh getblockcount
195368
I thought most plans to watch for too-large re-orgs were going to go into don't do anything mode and display "please intervene or something" messages for operator to see,
I guess we can manually pick the longer chain and put a checkpoint at the divisive block-number but for sure it would be nice to find out what is really going on. Phase Of Moon (POM) errors are just so ... well... sacrificing goats to keep computers running was supposed to have gone out of fashion last millenium wasn't it?
-MarkM-
./coiledcoind.sh getblockhash 179577
e654dad298eeccbcd74e90804a5ac1583a875a4fd08ed4e90844e44cd6806e34
./coiledcoind.sh getblockcount
195368
I thought most plans to watch for too-large re-orgs were going to go into don't do anything mode and display "please intervene or something" messages for operator to see,
I guess we can manually pick the longer chain and put a checkpoint at the divisive block-number but for sure it would be nice to find out what is really going on. Phase Of Moon (POM) errors are just so ... well... sacrificing goats to keep computers running was supposed to have gone out of fashion last millenium wasn't it?
-MarkM-
May 05, 2013, 04:17:15 AM
Firing up coiledcoin-qt.exe i'll let you know in 10 20 minutes. soon. It's taking quite a while to sync up.
Edit: This is going to take quite a while. Log file shows a massive reorganization going on.
Thanks, it'll be interesting to see what happened. Both nodes on different chains that I run have all the blocks from the other chain but they're orphaned. Neither are doing a block reorg to the others chain though. Did coiledcoin have a limit to stop large reorgs? Edit: This is going to take quite a while. Log file shows a massive reorganization going on.
May 05, 2013, 03:58:07 AM
Smalll change test coin is running, I think diff is small there. Also anyone plans to releae SHA3 currency? And if I for example really wanted to mine some coin with a friend I would simply restart it again and again till its still fun lol And if Luke did not process blocks others could still process them right? From what I understood even if someone got 51% they can only double spend their blocks not others since then they would have to resolve every block back in time right?
May 05, 2013, 03:03:23 AM
Firing up coiledcoin-qt.exe i'll let you know in 10 20 minutes. soon. It's taking quite a while to sync up.
Edit: This is going to take quite a while. Log file shows a massive reorganization going on.
Edit: This is going to take quite a while. Log file shows a massive reorganization going on.
May 05, 2013, 03:00:50 AM
I fired up my coiledcoin client a few weeks ago to see if it was still alive but noticed there were multiple chains. One client I connected with had a block count ahead of the blockchain explorer, with different hashes for the blocks with the same numbers as the explorer, but another client I connected with on a different machine matched the block explorer. Neither chain reorg'd when connected to each other.
I did some analysis of two diverging coiledcoin chains. They diverged at block 179577. Both chains have hash 0277f8ea8189d5e18aabe669226375492fc58ec0d30b14a9b6cc0b79c1bab8ba as block 179576. But for block 179577 one chain has c4720651f8f96152894218250efad3266110b378689209b671f13c94285993f9 and the other e654dad298eeccbcd74e90804a5ac1583a875a4fd08ed4e90844e44cd6806e34.So here's a question for the coiledcoin users (all 2 of you?). What is the output of:
Code:
coiledcoind getblockhash 179577
And what is your current block number:
Code:
coiledcoind getblockcount
I'm curious why it forked there. Some OP_EVAL transaction causing a fork maybe?
April 25, 2013, 04:14:29 PM
I fired up my coiledcoin client a few weeks ago to see if it was still alive but noticed there were multiple chains. One client I connected with had a block count ahead of the blockchain explorer, with different hashes for the blocks with the same numbers as the explorer, but another client I connected with on a different machine matched the block explorer. Neither chain reorg'd when connected to each other.
April 25, 2013, 02:10:49 PM
Is there a client for windows?? I wouldent mind throwing my labtop into this for giggles
found a working link courtesy of http://www.deadcoin.com/2012/02/first-crypto-corpse-coiledcoin.html
http://goo.gl/wAWZN
April 24, 2013, 10:42:23 PM
Is there a client for windows?? I wouldent mind throwing my labtop into this for giggles
March 28, 2013, 07:40:45 AM
This coin is a nice opportunity for small miners, as its difficulty right now is only 62.94940247 plus it can be merged mined so you don't even need to divert any hashing from other mainline coins (bitcoin and those that can be merged mined alongside bitcoin).
Heck come to think of it, chances are good that terracoin inherited from bitcoin the ability to be the main chain in a merge, so possibly it can even be merged-mined alongside terracoin for people who have diverted hashing power from the main line to terracoin...
-MarkM-
Heck come to think of it, chances are good that terracoin inherited from bitcoin the ability to be the main chain in a merge, so possibly it can even be merged-mined alongside terracoin for people who have diverted hashing power from the main line to terracoin...
-MarkM-
March 23, 2013, 07:59:38 AM
No, it's not alternative. P2SH & P2SH/CHV are alternatives to OP_EVAL, but not vice versa. 
Jump to: