Historic Cryptogenic Bullion thread - CLOSED - page 144.

mercSuey

sr. member

Activity: 364

Merit: 250

Quote from: 110110101 on October 07, 2013, 02:26:33 PM

Quote from: elambert on October 07, 2013, 07:34:58 AM

Looks like BCT is back after taking a brief vacation. Couple quick updates for the CB commuinity:

CGB subsidy halved again about 24 hours ago so the current PoW reward is 1.25 CGB per block
Blog section added to CB website: http://cryptogenicbullion.org/blog.html

Hey elambert,
Is it possible to see what the PoW is from the wallet by some RPC command?
I was trying to figure this out by looking at the current block number, but I couldn't really get the hang of it.

For instance, with getblockcount I currently get the number: 146849
It was my impression that the PoW was halved every 50.000 blocks. So for the reward to be 1.25, wouldn't the block count have to be 150 000?

KBlock Reward
   0 10
   50 5
  100 2.5
  150 1.25

getmininginfo has the info you need, I think.

First block halving happened at 55K, next half at 95K....I joined the dev team right around that time.

All consequent halving happens at 50K intervals after block count 95K.

Killiz

hero member

Activity: 750

Merit: 503

Quote from: 110110101 on October 07, 2013, 02:26:33 PM

Quote from: elambert on October 07, 2013, 07:34:58 AM

Looks like BCT is back after taking a brief vacation. Couple quick updates for the CB commuinity:

CGB subsidy halved again about 24 hours ago so the current PoW reward is 1.25 CGB per block
Blog section added to CB website: http://cryptogenicbullion.org/blog.html

Hey elambert,
Is it possible to see what the PoW is from the wallet by some RPC command?
I was trying to figure this out by looking at the current block number, but I couldn't really get the hang of it.

For instance, with getblockcount I currently get the number: 146849
It was my impression that the PoW was halved every 50.000 blocks. So for the reward to be 1.25, wouldn't the block count have to be 150 000?

KBlock Reward
0 10
50 5
100 2.5
150 1.25

The first halving didn't go according to plan Grin

read from here https://bitcointalksearch.org/topic/m.2842262

It was quickly addressed and subsequently each halving afterward was and is staggered back by 5000 blocks to compensate for this.

110110101

legendary

Activity: 1382

Merit: 1002

Quote from: elambert on October 07, 2013, 07:34:58 AM

Looks like BCT is back after taking a brief vacation. Couple quick updates for the CB commuinity:

CGB subsidy halved again about 24 hours ago so the current PoW reward is 1.25 CGB per block
Blog section added to CB website: http://cryptogenicbullion.org/blog.html

Hey elambert,
Is it possible to see what the PoW is from the wallet by some RPC command?
I was trying to figure this out by looking at the current block number, but I couldn't really get the hang of it.

For instance, with getblockcount I currently get the number: 146849
It was my impression that the PoW was halved every 50.000 blocks. So for the reward to be 1.25, wouldn't the block count have to be 150 000?

KBlock Reward
0 10
50 5
100 2.5
150 1.25

mercSuey

sr. member

Activity: 364

Merit: 250

We'll have Swedish and German translations of the CB website very soon.

Also, stay in touch with development plans via our blog page: http://CryptogenicBullion.org/blog.html

aa

hero member

Activity: 544

Merit: 500

Litecoin is right coin

I'm hosting the Windows and Mac binaries here: http://www.lurkmore.com/wiki/Cryptocurrency_information_and_wallet_client_downloads

pmconrad

full member

Activity: 149

Merit: 102

I have created packages for openSUSE and debian:
https://build.opensuse.org/package/show/home:p_conrad:coins/cryptogenicbullion

Have fun,
Peter

elambert

legendary

Activity: 1696

Merit: 1008

Looks like BCT is back after taking a brief vacation. Couple quick updates for the CB commuinity:

CGB subsidy halved again about 24 hours ago so the current PoW reward is 1.25 CGB per block
Blog section added to CB website: http://cryptogenicbullion.org/blog.html

hypersire

hero member

Activity: 596

Merit: 500

Quote from: mercSuey on October 01, 2013, 05:07:24 PM

https://bitcointalksearch.org/topic/6-days-in-the-cgb-blockchain-ccn-305958

Wow, this is big news indeed! I fully support CB going POS only. Once that happens, I think a good course of action would be to kick the advertising campaign into the next gear and focus on the improvements that CB has over Bitcoin. For example, "CryptogenicBullion - Like Bitcoin, only with interest and no mining!"

The interest-bearing, environmentally-friendly aspects of the POS-only scheme must be at the forefront of the advertising as this is what makes CB truly unique in the sea of alt-coins.

Keep up the great work Team CB!

mercSuey

sr. member

Activity: 364

Merit: 250

https://bitcointalksearch.org/topic/6-days-in-the-cgb-blockchain-ccn-305958

mercSuey

sr. member

Activity: 364

Merit: 250

Quote from: allbiznessman on September 30, 2013, 02:31:41 PM

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.html
It contains a link within: http://maxminer.files.wordpress.com/2013/06/ftc_51attack.pdf
that 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.

allbiznessman

member

Activity: 74

Merit: 10

SudoSuRootDev... AKA... AllBiznessMan

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.html
It contains a link within: http://maxminer.files.wordpress.com/2013/06/ftc_51attack.pdf
that 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!!!

allbiznessman

member

Activity: 74

Merit: 10

SudoSuRootDev... AKA... AllBiznessMan

If I understand, from what I have gathered, the addnodes will not really do much until the checkpoint sever is online. It is just PoS growing pains. You'll notice, when there 10 PoS block in a row is usually when you see a long row of orphans, or the reverse, going from that 10 block PoS row back to PoW blocks.

nearmiss

sr. member

Activity: 448

Merit: 250

using new addnodes and a fresh peers.dat, things seemed pretty decent for awhile, but just orphan'd another 40 or so blocks in a row. Guess we are off it for now, which is maybe what your after anyways

allbiznessman

member

Activity: 74

Merit: 10

SudoSuRootDev... AKA... AllBiznessMan

Quote from: mercSuey on September 30, 2013, 11:49:31 AM

Quote from: allbiznessman on September 30, 2013, 11:03:05 AM

While looking through the code, I have come upon

Code:

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

Yeah, I was the one that brought that option up the other day, but all it really does is make it so that if someone get into your PC they have to send your coins to themselves rather than being able to dumpprivkey and import in their wallet.

allbiznessman

member

Activity: 74

Merit: 10

SudoSuRootDev... AKA... AllBiznessMan

Quote from: miffman on September 29, 2013, 04:29:38 PM

So I'm not sure if I'm doing this right, but I made my own vanity address using the normal vanity address generator but using the settings -X 11 (prefix) to gen. my own CGB address. I have the address and privkey. I tried to import the privkey with the console and cryptogenicbulliond but I keep getting the "Wallet is unlocked for minting only. (code -13)" message. How can I import it into the GUI so I can use it properly?

I got to the settings by using help from https://en.bitcoin.it/wiki/Vanitygen

I just tried vanitygen with -X 11 and 5cgb as a prefix and I was able to importprivkey but it shows a totally different address than Vanitygen gave me, with private key.

mercSuey

sr. member

Activity: 364

Merit: 250

Quote from: allbiznessman on September 30, 2013, 11:03:05 AM

While looking through the code, I have come upon

Code:

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

flound1129

hero member

Activity: 938

Merit: 1000

www.multipool.us

I did a git pull but it only updated version.h and version.cpp.

Anyway, Multipool is now running with the latest code and addnodes.

allbiznessman

member

Activity: 74

Merit: 10

SudoSuRootDev... AKA... AllBiznessMan

While looking through the code, I have come upon

Code:

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.

allbiznessman

member

Activity: 74

Merit: 10

SudoSuRootDev... AKA... AllBiznessMan

Quote from: miffman on September 30, 2013, 10:17:02 AM

my wallet is not encrypted, so walletpassphrase doesn't work. Surely I should just be able to importprivkey though?

OK, I hadn't thought about that when I responded. That was the reason when I was sharing this option for PoS coins with mercSuey the other day, that I was telling him that it would need to be added as a command. Right now, there is no way to release the wallet. Since it is built into the cryptogenicbulliond daemon, you will need a way to release it. I am going to add it to the code for you, and mercSuey and elambert can add it if they chose.

Since it is set as a constant when built, for now you would have to rebuild and launch CGB with a backup wallet, and do it without changing line 86 this time... for now. Please repost whether you have a backup or not or if you have coins in the wallet. If you have coins and no backup, I will get it worked out for you as soon as possible. If not, I can take it a bit slower.

miffman

legendary

Activity: 1904

Merit: 1005

PGP ID: 78B7B84D

my wallet is not encrypted, so walletpassphrase doesn't work. Surely I should just be able to importprivkey though?

Topic: Historic Cryptogenic Bullion thread - CLOSED - page 144. (Read 286628 times)