I support this experiment  . If this is successful, then exchanges will be even more integral to the industry. So we support your experiment as well.  Cheers! -Merc |
|
|
|
Hey guys, I just read something which you may have already seen, but I bring it up because of the time I have dedicated to this coin and wanting it to survive. This is the forum post link: http://forum.feathercoin.com/index.php/topic,2178.0.htmlIt contains a link within: http://maxminer.files.wordpress.com/2013/06/ftc_51attack.pdfthat demonstrates how the FTC 51% attack occurred. What jumped out at me is something I have been watching and bringing up a lot about certain orphaned CGB blocks, that are accepted 10 - 15 minutes after the same block was orphaned (Thank God none have been successful). If you view page 2 of the demonstration link, you will see a note on the demonstration that says "NOTICE THE TIME WARP". The block time jumps backwards. I have noticed this with a lot of the orphans while mining on multipool which is where my miners are. So, I just wanted to put this out there for the developers who may not have seen this, in order to try and avoid this here!!! Learning from the past and other's misfortunes can help us to succeed!!! Yeah, the roll backs to a PoS block will have timestamps before the PoW orphans, because they take longer to process. At first my concern was similar to yours and I asked flound awhile ago to keep an eye on any fishy activity through multipool; flound has not noticed anything yet. But I thank you for sharing the info. It's definitely important to learn from past mistakes within the industry. |
|
|
|
While looking through the code, I have come upon no importprivkey in mint-only mode So, it makes me realize that it is probably going to be more difficult that at first thought. So, my best suggestion, rebuild with a fresh source and then mess with importprivkey. At first I was thinking all your wallet commands were locked, but it should only be locking importprivkey and dumpprivkey The option is there to keep your wallet secure in case your PC gets hacked, but still open for minting. We started to mess with those settings on the github but then changed it back because we knew it would confuse people. There was only a couple hour window to update from that commit. Sure enough it seems Cryptsy and miff updated with that commit. Cryptsy updated to the latest commit yesterday. As far as the PoW orphans, I explained it above. But our checkpoint server is not online yet because we were giving time for everyone to update to the latest client, else we would risk forking the blockchain. Once the checkpoint server goes online then the PoW orphans should be drastically improved. We're on top of it and we'll announce any new developments. -Merc |
|
|
|
Looks like there might be some problems recently, rounds 1608-1610 ?
A 22 minute CGB round with 0 blocks.
A CSC round with a time of 00:00:-1
A 2 minute MEC round with no blocks, and now we're on MEC currently for a long time.
CGB having PoS problems. All orphans. CGB isn't having PoS 'problems'...PoS overrules PoW by design. Long sequences of PoS blocks happen even for PPC, but it's about ten times more likely for CGB because of the one minute PoS blocks. But PPC isn't susceptible to multipool hash spikes that can instantly double or triple the network hash rate, many dozens of times throughout each day. Consequently there are roll backs when multipool or hashcows points their hashing at CGB right when a PoS block lands and/or in the middle of a sequence of PoS blocks. PoS isn't the most friendly kind of coin for multipooling. It's the risk you take when mining at multipools. |
|
|
|
Hey all, any timeline on a fix ?
There's nothing to fix per say, we're analyzing the situation as PoW subsidy halves and PoS block frequency increases and takes over the blockchain, as planned. Once the PoW subsidy reaches the baseline .01, it will be extremely inefficient, since PoS blocks overrule PoW blocks. But the plan from the start was to have CB PoW fully mined and running only on PoS. We have several plans ready to be implemented to assure a lower bound in the PoS block frequency so that we can guarantee the transactions will move. Other than that, these are just growing pains as we analyze the behavior, use testnet on the side to continue to experiment with development ideas, and eventually we'll have the tweaks so that the blockchain is in the sweet spot. -Merc |
|
|
|
|
There were several roll backs because of long sequences of PoS blocks. As I said before, we'll tweak the math and analyze the potential for letting PoS takeover, so these are growing pains. When the time comes, we'll modify the PoS when we have enough testnet data to justify it. In the meantime, make sure you have the new addnodes in your config file, as the old ones are useless:
addnode=70.98.114.237
addnode=72.78.100.7
addnode=192.81.209.17
addnode=192.241.222.16
addnode=88.198.184.231
addnode=109.169.220.58
addnode=80.255.6.123
addnode=66.58.170.165
addnode=37.187.9.53
Thanks.
-Merc
|
|
|
|
|
We announced new addnodes a couple days ago, FYI
addnode=72.78.100.7
addnode=70.98.114.237
addnode=192.81.209.17
addnode=192.241.222.16
addnode=88.198.184.231
addnode=109.169.220.58
addnode=80.255.6.123
addnode=66.58.170.165
addnode=37.187.9.53
addnode=216.158.85.123
addnode=119.9.15.177
|
|
|
|
Hello all,
Please note that the addnodes have been changed in the OP. Please replace the addnodes in your config file with these.
addnode=70.98.114.237
addnode=72.78.100.7
addnode=192.81.209.17
addnode=192.241.222.16
addnode=88.198.184.231
addnode=109.169.220.58
addnode=80.255.6.123
addnode=66.58.170.165
addnode=37.187.9.53
Thank you.
Repost, in case you missed it. |
|
|
|
merc, i don't mind to provide a linux binary if you need one.
Hi rewt, Thanks for the offer. I'm in the middle of moving into my new home in North Carolina and I don't have any of my Linux machines setup yet. I'm afraid I'm a bit of a mess for another day or two. lol Elambert was going to pm you, and we appreciate the offer. Cheers, -Merc |
|
|
|
I'm late to the CGB party and was wondering if is still worth mining with a CPU either solo or pool? Or you just need a few good GPUs? If you are still finding blocks solo, what is your hashrate? Thanks in advance.  Consistently in the top five most profitable scrypt coins to mine. Network hashrate is steady in the 400-500mh range. A cpu will work but if you have a good gpu then obviously that's better. Solo blocks will not be easy with anything under 1mh. Thanks for your interest! -Merc |
|
|
|
I'm sorry but they're all terrible. Just as terrible as the splash screen for the QT.
A lens flare, bevel/emboss, and drop shadow. Seriously? Looks like a 15 mins Photoshop filter hack job on some rough edge lines.
These are the main reasons I can't take this coin seriously. Let's hope it keeps evolving into something interesting.
I started to read your comment but then I saw your username, so I couldn't take it seriously. theBee2112 looks like a name a child would have chosen. And the 2112, was that a way to be clever? You could have used better fonts. I don't get it. And what's the point of capitalizing the 'B' but not the 't'? Maybe your name choosing will evolve and then I'll begin to take you seriously...  As for the logo and splash page, we had a contest to get the community involved and this was our winner. And we're proud of our winner and the participation we experienced from the community. Have a nice day. -Merc |
|
|
|
|
To be sure the new checkpoint/seed info is being used by your client, the block chain and peers data need to be downloaded anew.
If you are getting the "checkpoints too old" message, then you must definitely do this.
Close your client and go to your AppData/Roaming/CryptogenicBullion folder and delete the following files:
blk001.dat
blkindex.dat
peers.dat
Do not touch any other file, especially the wallet.dat file, or else you'll lose ALL your coins!
Restart your client and you'll see the blockchain download from start. Don't be alarmed if your coins are unconfirmed. Your wallet balance will return to the expected value once the blockchain has downloaded completely and the wallet is in sync.
-Merc
|
|
|
|
You guys also win the award for the worlds largest splash image, did you dev the coin on a 1080p monitor?  ... We'd like to thank the Academy.Yes, it was. lol. i like the splash image... Thank you, sir. |
|
|
|
You guys also win the award for the worlds largest splash image, did you dev the coin on a 1080p monitor? ... We'd like to thank the Academy.Yes, it was. |
|
|
|
Oh, and FiniteByDesign can we have window or numbers printed across the holograms on the coins showing the starting characters blockchain addresses this time if possible?
I can actually do this with the current Primecoins but opted to only provide the address on the Certificate of Authenticity as it made for a more professional and cleaner look. I believe I can accommodate this request, I just think it looks better without the window. With the CGB bars, I will most likely have the address (or at least a portion) engraved on the bar itself. The privkey would still be hidden under the tamper proof hologram sticker. This seems the best option per discussion with customers. if you can do vanity addresses engraved on, that would be incredible!! That's the plan, actually. |
|
|
|
archived files got mixed in there...my bad. Should be fixed. |
|
|
|
|
Show Posts
