Historic Cryptogenic Bullion thread - CLOSED

[flound1129]

Multipool getting lots of orphans..  Possible fork?

[mercSuey]

Multipool getting lots of orphans..  Possible fork?

I sent you an email over an hour ago...YOUR pool is forked.

Smalltimeminer and others are fine.

[mercSuey]

A couple blocks confirmed and there's 10 confirms on 127,641.  So it looks like you're okay now.

[elambert]

Turkish version of the website is now up! CB continues it's spread across the globe! Updating OP now

http://cryptogenicbullion.org/index_turkish.html


Special thanks to OracionSeis!

[allbiznessman]

Yeah I emailed flound1129 last night and got a reply, to make sure I got the peers deleted and restarted. I was thinking it was someone trying to introduce false blocks or a false blockchain though, because the orphans were 19 minutes before the accepted block with the same number would be accepted. That just seems way to far ahead of the chain. Plus it was accepting the correct one's just solving the orphans first, so it had to be someone else with the fork.

[mercSuey]

Guys,

Make sure your passwords on Cryptsy are at least 12 characters long and a mix of letters(lower case and upper case), numbers, special chars.

The 2fa isn't going to do shit when it's known that the first three characters are alpha and the last three are numeric.  I can literally brute force it in seconds.

I'm sure there is a locking mechanism for too many failed attempts, but just in case that is bypassed then your only defense is a strong password.  So don't lose your password.

And do NOT use the same password on another site.  Make sure it's unique.


Rock on, CB community!



-Merc


Brute force attack definition:   http://en.wikipedia.org/wiki/Brute-force_attack

[mercSuey]

Yeah I emailed flound1129 last night and got a reply, to make sure I got the peers deleted and restarted. I was thinking it was someone trying to introduce false blocks or a false blockchain though, because the orphans were 19 minutes before the accepted block with the same number would be accepted. That just seems way to far ahead of the chain. Plus it was accepting the correct one's just solving the orphans first, so it had to be someone else with the fork.

We're going to try to get some nodes geographically closer to multipool.  For whatever reason, multipool is getting peers data a bit later than other pools and it'll run off on its own chain for several blocks before rolling back blocks to get in sync.  This is especially true when a sequence of PoS blocks happen.  We don't see any issues with other pools.  Perhaps this is a network topology issue, who knows?  So we will try to help out flound and get some vps nodes near him so that peers data is getting to him with lower latency.  But it's clear it's a peers data issue.

EDIT:  let me be clear that I'm a fan of multipool and I consider them an ally since the 1gh/s hashing they provide can help to counter a malicious hash spike, at least somewhat.  So the sooner we get this done the better.

[pgbit]

Guys,

Make sure your passwords on Cryptsy are at least 12 characters long and a mix of letters(lower case and upper case), numbers, special chars.

The 2fa isn't going to do shit when it's known that the first three characters are alpha and the last three are numeric.  I can literally brute force it in seconds.

I'm sure there is a locking mechanism for too many failed attempts, but just in case that is bypassed then your only defense is a strong password.  So don't lose your password.

And do NOT use the same password on another site.  Make sure it's unique.
Rock on, CB community!
-Merc
Brute force attack definition:   http://en.wikipedia.org/wiki/Brute-force_attack

? why dont they use Google authenticator.

[allbiznessman]

That is cool, I am always up for helping CGB. That is all that I mine now. I'm kind of wishing I hadn't sold most of them though, especially from the 10 coin blocks, now that the reward is about to drop to 1.25.
I was thinking about using one of my servers for a node, if needed, I can set it up real fast.

The cryptsy 2FA thing, I agree. It is just a hassle for me. I just keep a totally random password that makes it hard enough to brute force that you'd be better off mining and earning the coins than trying to steal. I would use Google Authentication because it is less of a hassle, than going into my email then back to cryptsy for a 3 letter 3 number code. 

I stay logged in on this laptop, and sleep with it also... quick and easy.

[miffman]

I'm getting a warning on my qt client, it says checkpoint is too old, wait for blockchain to download or notify developers. My client is up to date with the blockchain, but the warning still comes up. Even after a restart

[mercSuey]

I'm getting a warning on my qt client, it says checkpoint is too old, wait for blockchain to download or notify developers. My client is up to date with the blockchain, but the warning still comes up. Even after a restart

My clients don't show any warning.  PM me with any changes you may have done, if any.  I'll look into it.

[allbiznessman]

At what block does reward half again ?

145,001 is first reward at 1.25

Thank you!!

Less than 14,970 blocks till CGB reward drops from 2.5 to 1.25!!!
Those of you auto-selling right now, should think of that too!!! I'm holding everything, for now.

[mercSuey]

At what block does reward half again ?

145,001 is first reward at 1.25

Thank you!!

Less than 14,970 blocks till CGB reward drops from 2.5 to 1.25!!!
Those of you auto-selling right now, should think of that too!!! I'm holding everything, for now.

Indeed!

We'll be finishing the next client update tonight when I get home.  Updated seeder and checkpoints, among other little things...

Cheers!

-Merc

[allbiznessman]

I'm getting a warning on my qt client, it says checkpoint is too old, wait for blockchain to download or notify developers. My client is up to date with the blockchain, but the warning still comes up. Even after a restart

My clients don't show any warning.  PM me with any changes you may have done, if any.  I'll look into it.

I'm not getting the error either. There was a fork the other day and you may have got onto that forked chain, so you should stop, delete the following, then restart:

for WINDOWS delete:
%AppData/Roaming/CryptogenicBullion/blkindex.dat

for LINUX delete:
$HOME/.CryptogenicBullion/blkindex.dat

[raffern]

I'm getting the error too. It only started after i encrypted my wallet? I restarted and the message was there.

[mercSuey]

I'm getting the error too. It only started after i encrypted my wallet? I restarted and the message was there.

It's fine, we'll update checkpoints with the updated client tonight anyways. 

[Alec40Gr]

@MercSuey

Last days as I unlock wallet (windows binary), CPU usage goes to around 50% and client starts reacting very slowly. Few minutes later client is almost not responding and
walletlock command (as a way to stop PoS mining) I need to terminate process. Check it as you make an updated client...

Keep up good work guys.

[mercSuey]

@MercSuey

Last days as I unlock wallet (windows binary), CPU usage goes to around 50% and client starts reacting very slowly. Few minutes later client is almost not responding and
walletlock command (as a way to stop PoS mining) I need to terminate process. Check it as you make an updated client...

Keep up good work guys.

I'll keep an eye on it.  Please let me know if there is any change in resource usage with updated client.  But I'll start to research this now.

-Merc

[mercSuey]

@MercSuey

Last days as I unlock wallet (windows binary), CPU usage goes to around 50% and client starts reacting very slowly. Few minutes later client is almost not responding and
walletlock command (as a way to stop PoS mining) I need to terminate process. Check it as you make an updated client...

Keep up good work guys.

I sent you a pm to get more details...

or email me if you have any extra info that might be helpful:  support@CryptogenicBullion.org

[allbiznessman]

@MercSuey

Last days as I unlock wallet (windows binary), CPU usage goes to around 50% and client starts reacting very slowly. Few minutes later client is almost not responding and
walletlock command (as a way to stop PoS mining) I need to terminate process. Check it as you make an updated client...

Keep up good work guys.

The source was updated about 12 hours ago, I don't know what the issue is there, but if you download the source go to line 86 of src/wallet.cpp when you download it and you change line 86 from

Code:

bool fWalletUnlockMintOnly = false;

to

Code:

bool fWalletUnlockMintOnly = true;

your wallet will be locked for sending but it will be unlocked for minting only.

@mercsuey just a thought you could create and post a Windows Binary with that option.

I am creating PoW/PoS coin with actual changes, and additions, and not just a copy and paste clone, so I have been through the source.