★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit

[DigiByte]

Just got a reply from Cryptsy. I sent 1675449.00 DGB, but so far the deposit has not shown up and the address for the transaction is not listed. Going to wait for all the verifying to finish and then uninstall the wallet. Re-install fresh

It does appear that a fork has already emerged between new 3.0.0 wallets & the old chain. We pulled the 3.0.0 downloads until we get a lid on exactly what is going on.

It appears Sha256 is still active while the other algos are not * should not be mine-able until block 145,000. But since it is default backbone of the multi-algo code we are going to re-check our switch over code.

Please hold off on mining the sha256 code until we get a lid on it. We can implement a checkpoint on the old chain if need be.

[Scyntech]

Just got a reply from Cryptsy. I sent 1675449.00 DGB, but so far the deposit has not shown up and the address for the transaction is not listed. Going to wait for all the verifying to finish and then uninstall the wallet. Re-install fresh

It does appear that a fork has already emerged between new 3.0.0 wallets & the old chain. We pulled the 3.0.0 downloads until we get a lid on exactly what is going on.

It appears Sha256 is still active while the other algos are not * should not be mine-able until block 145,000. But since it is default backbone of the multi-algo code we are going to re-check our switch over code.

Please hold off on mining the sha256 code until we get a lid on it. We can implement a checkpoint on the old chain if need be.

Gotcha, Just did a fresh install >.< lol

[DigiByte]

Just got a reply from Cryptsy. I sent 1675449.00 DGB, but so far the deposit has not shown up and the address for the transaction is not listed. Going to wait for all the verifying to finish and then uninstall the wallet. Re-install fresh

It does appear that a fork has already emerged between new 3.0.0 wallets & the old chain. We pulled the 3.0.0 downloads until we get a lid on exactly what is going on.

It appears Sha256 is still active while the other algos are not * should not be mine-able until block 145,000. But since it is default backbone of the multi-algo code we are going to re-check our switch over code.

Please hold off on mining the sha256 code until we get a lid on it. We can implement a checkpoint on the old chain if need be.

Gotcha, Just did a fresh install >.< lol

Ok. Yeah we are going over the code again real quick. It does appear the normal chain is on block 141,663 while the 3.0.0 wallet is on block 141,988.

We will re-compile and release 3.0.1. Just keep your existing coins (pre-update) in your wallet and don't move them just yet.

[prdomain]

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

Code:

./digibyte-cli getinfo 
error: no response from server

or
./digibyted getinfo
error: no response from server

[gamer1coin]

Can someone clear things up for me? Are people obtaining coins from mining on SHA 256 when they're not supposed to?

[DigiByte]

Can someone clear things up for me? Are people obtaining coins from mining on SHA 256 when they're not supposed to?

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.

[thefrog]

@DigiByte

What p2pool github can we use to have a multi-algo running ?
Does https://github.com/zone117x/node-open-mining-portal is the one working ?

As I understand it, its not a p2pool in the link.
It's a centralized pool using local database to store shares mined by each miner, which get then payed out.

P2pool is a de-centralized network of p2pool nodes, which are interconnected, with peer to peer communication so miners can connect to any p2pool node, even hop between the nodes in the p2pool network, without loosing their shares. And p2pool is using PPLNS payout system.

[The_Cashier]

@DigiByte

What p2pool github can we use to have a multi-algo running ?
Does https://github.com/zone117x/node-open-mining-portal is the one working ?

As I understand it, its not a p2pool in the link.
It's a centralized pool using local database to store shares mined by each miner, which get then payed out.

P2pool is a de-centralized network of p2pool nodes, which are interconnected, with peer to peer communication so miners can connect to any p2pool node, even hop between the nodes in the p2pool network, without loosing their shares. And p2pool is using PPLNS payout system.

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]

@DigiByte

What p2pool github can we use to have a multi-algo running ?
Does https://github.com/zone117x/node-open-mining-portal is the one working ?

As I understand it, its not a p2pool in the link.
It's a centralized pool using local database to store shares mined by each miner, which get then payed out.

P2pool is a de-centralized network of p2pool nodes, which are interconnected, with peer to peer communication so miners can connect to any p2pool node, even hop between the nodes in the p2pool network, without loosing their shares. And p2pool is using PPLNS payout system.

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 ?

It is possible to mine 5 different alogs on one pool. But you will need 5 instances of the wallet running, each set to a different algo with a different rpc port to mine on. NOMP is essentially a p2p pool that can handle this out of the box. https://github.com/zone117x/node-open-mining-portal/

[tdcooper99]

@ 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?

[tdcooper99]

Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....

[The_Cashier]

@DigiByte

What p2pool github can we use to have a multi-algo running ?
Does https://github.com/zone117x/node-open-mining-portal is the one working ?

As I understand it, its not a p2pool in the link.
It's a centralized pool using local database to store shares mined by each miner, which get then payed out.

P2pool is a de-centralized network of p2pool nodes, which are interconnected, with peer to peer communication so miners can connect to any p2pool node, even hop between the nodes in the p2pool network, without loosing their shares. And p2pool is using PPLNS payout system.

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 ?

It is possible to mine 5 different alogs on one pool. But you will need 5 instances of the wallet running, each set to a different algo with a different rpc port to mine on. NOMP is essentially a p2p pool that can handle this out of the box. https://github.com/zone117x/node-open-mining-portal/

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

[DigiByte]

@ 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?

The nodes listed need to be updated. The ports are correct.

[DigiByte]

Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....

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.

[tdcooper99]

Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....

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.

Ok, good to know. But no worries...  can't friggin' get it to work anyway 

[DigiByte]

Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....

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!

[tdcooper99]

Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....

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!

Don't worry...  we're all just pumped to get on it again.... you're obviously on it so no worries!

[DubFX]

Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....

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.

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?

[ycagel]

Glad I haven't updated yet. Let's wait for more fixes.

Appreciate the constant dedication Jared!

YC

[illodin]

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!

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