Gotcha, Just did a fresh install >.< lol

v3.0.0
daemon would be crashed , when I try some rpc call

Essentially a couple people were able to mine a few block on the SHA algo. However since these coins are on a separate chain the existing network is rejecting them. The few people who did download 3.0.0 can see these blocks, but we are recompiling the wallet with a fix as we speak to v 3.0.1

We are implementing a checkpoint on the old chain that will invalidate all the SHA blocks. Stay tuned, and who ever is mining the SHA blocks please note they will be rejected by the old chain and will be invalid if you try and send them anywhere.

So if i run a p2pool it would be only for one algo ? Or people would be able to mine any algo with the p2pool ?

@ Digibyte...  trying to solo mine Scrypt...  why does your digibyte.conf as listed on the first post contain an rpcport=14022 AND a port=12024? Also...  are the nodes as listed still correct?

Thanks for fast response.
Do you have a link for all the rpc port and config informations for each algos for digibyte ?

Don't try solo mining with the 3.0.0 wallet as even "scrypt" blocks will be invalidated on that chain. We are working on getting 3.0.1 out as fast as we can.

We will release all the .conf info once we get this issue resolved. Thanks again for all your patience. This is a very complicated update. All will be normal again soon!

May i also ask how did you set the block times to each algo? Won't that mean that block can be found on any algo anytime so that could cause up to 5 (or how many algos dgb has) blocks beign found at once?

Keep up the good work, no one expected everything to be silky smooth. I'm sure you have everyone's 100% support.