Historic Cryptogenic Bullion thread - CLOSED

[mercSuey]

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

[1714043258]

1714043258

[1714043258]

1714043258

[1714043258]

1714043258

[1714043258]

1714043258

[r3wt]

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

right on i understand how it is. good luck with moving

[mercSuey]

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.

[fendlestick]

Happy to let you know that you can use this coin to purchase over 3000 products from www.cryptosextoys.com

[miffman]

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

[mercSuey]

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

[zepadee]

Hey all, any timeline on a fix ?

[mercSuey]

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

[miffman]

Was block subsidy not meant to half around today or so? The current block is around ~136k and isn't it meant to half at around ~145k? Please clear this up for me

[elambert]

Was block subsidy not meant to half around today or so? The current block is around ~136k and isn't it meant to half at around ~145k? Please clear this up for me

Should halve around Sunday per my estimation.  

Your easiest method of calculating, although not 100% due to PoS blocks not being considered is take the block reduction cut off (145k) and subtract the current block (136k) = 9k. Divide this number by 24 (hours in a day) and then again by 60 (minutes in an hour) = 6.25 (estimated days till next halving).

[zepadee]

So what exactly is the reason for the all the orphans on the pools ?

[allbiznessman]

So what exactly is the reason for the all the orphans on the pools ?

PoS growing pains. Great developers on CGB, will work through it all!!! Also, every pool (I notified flound at multipool but haven't got a reply yet) should update to only the official addnodes (above) and also delete peers.dat and then restart.

[allbiznessman]

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

You must have got my post about that the other day about this option and built cryptogenicbulliond with line 86 of src/wallet.cpp set as:

Code:

bool fWalletUnlockMintOnly = true;

instead of:

Code:

bool fWalletUnlockMintOnly = false;

so your wallet is unlocked for minting only. You need to do:

Code:

cryptogenicbulliond walletpassphrase 120
cryptogenicbulliond importprivkey <key> <label>

in order to unlock your wallet fully for 120 seconds, and then import the private key.
Also, I found it is always a good idea to use a label with every address, otherwise you can lose your default address, because it will replace the default "" address.

[miffman]

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

[allbiznessman]

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.

[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.

[flound1129]

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.

[mercSuey]

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

[allbiznessman]

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.

[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.

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.