DO NOT DONATE TO SILLYPOTHEAD'S CANN FAUCET

The faucet is broken, not recognizing valid CANN addresses and worse, it is eating donations.

If Silly is a reader or if someone knows how to make contact please pass on the advice.

(and yes, I have PMed SillyPotHead)

first time users might want to run the client momentarily to create the target folder    

http://www.nytimes.com/2015/02/08/business/marijuana-industry-in-colorado-eager-for-its-own-bank-waits-on-the-fed.html?smid=re-share&_r=0

Sorry if it's already been discussed around here I didn't bother reading back... but I couldn't help but think of this community when I read this.

esotericism has made bootstrap.dat available with blockchain data complete to January 23, 2015.


Anyone starting a new wallet or downloading the blockchain for any reason can speed the process significantly by downloading CannabisCoin bootstrap.dat.

How to use it

Before starting your CannabisCoin wallet download bootstrap.dat and copy/move it to your CannabisCoin directory, which you can either create or simply start, then stop your wallet:

Windows: \Users\YourUserName\AppData\Roaming\CannabisCoin
Mac: ~/Library/Application\ Support/CannabisCoin
Linux ~/.Cannabiscoin

Start your wallet. It should say "Loading blocks from disk" which it will do much faster than it will download them. Once it has exhausted the bootstrap supply it will continue downloading the chain data from the 23rd onwards from the net. On completion the wallet will rename the bootstrap file bootstrap.dat.old. You can leave it where it is and reuse it if you ever need to by simply renaming it bootstrap.dat again.

Edited for clarity and sprelling :3

Above post was the latest from Dev for those who missed and Delta Nine will tweet further updates

i had a joint and read it and it felt like i smoked 10 joints after i finished reading it WOW

For miners using, or interested in using the KryptoChaos mining pool, pcmerc reports the pool has been corrected and payouts are flowing again. Problem was apparently a SYN attack from 3 offending IPs - a tcpdump conformed this. Offending IPs were: 86.13.41.222; 88.227.33.203 and; 84.25.161.117.

Normal services have been resumed.