Author

Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1299. (Read 3058812 times)

full member
Activity: 146
Merit: 100
Nice update Smiley
Has anyone successfully mined out a block and received payout using anything but scrypt? I know that Scyntech said he was mining using SHA256...
That's not part of the program, right? Tongue

As far as I can tell SHA256 is being used. That was one of the algo's during testing period.


Are the blocks being confirmed though?  What are the block numbers of the ones you are finding?
sr. member
Activity: 349
Merit: 250
“Blockchain Just Entered The Real World”
Nice update Smiley
Has anyone successfully mined out a block and received payout using anything but scrypt? I know that Scyntech said he was mining using SHA256...
That's not part of the program, right? Tongue

As far as I can tell SHA256 is being used. That was one of the algo's during testing period.
sr. member
Activity: 285
Merit: 250
Nice update Smiley
Has anyone successfully mined out a block and received payout using anything but scrypt? I know that Scyntech said he was mining using SHA256...
That's not part of the program, right? Tongue
sr. member
Activity: 349
Merit: 250
“Blockchain Just Entered The Real World”
Taking quite a while to deposit to Cryptsy.
full member
Activity: 146
Merit: 100
Everything looks good from my testing of the wallet, great job DigiByte team!
sr. member
Activity: 335
Merit: 250
Hey all,
P2-pool Server has been updated to the new version. Have a try, server was up without interruption since 90 days Smiley.

Have a good mining.
sr. member
Activity: 349
Merit: 250
“Blockchain Just Entered The Real World”

Introducing DigiByte v3.0.0 MultiAlgo

Before we release the OSX & Linux version as well as publicly announce the release we would appreciate a few beta testers on here to run the wallet through a couple send, receive, sync & solo mining tests. (Scrypt mining will be the only algo to mine until the others kick in at block 145,000)


If the other algos don't kick in until block 145,000, how are people mining sha256???



{
"version" : 3000000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 1850509.37647499,
"blocks" : 141694,
"timeoffset" : -6,
"connections" : 11,
"proxy" : "",
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 1270.96790193,
"difficulty_sha256d" : 1270.96790193,
"difficulty_scrypt" : 340.49683390,
"difficulty_groestl" : 0.00024414,
"difficulty_skein" : 0.00024414,
"difficulty_qubit" : 0.00024414,
"testnet" : false,
"keypoololdest" : 1389569262,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}


I started solo mining/bfgminer @ 38Gh/s SHA256 with no issues. It immediately recognized the algo. Finding new blocks left and right! I'm not sure if that was part of the goal.
full member
Activity: 215
Merit: 100
I tried to get a p2pool node up and running with the new wallet.
Seems we need some change in the p2pool code too...

http://ca.p2pool.sk:9022

not sending work to the workers.


Yeah, something isn't right. I've been throwing 80+ MH at P2Pool since about 08:00 GMT and although 2 blocks (141635 & 141636) have been discovered, there are no payouts...

RJF
hero member
Activity: 616
Merit: 500
Online since '89...
Just started to mine again DGB on http://www.coinium.org/help/gettingStarted/DGB
Feels good man Smiley
Welcome back! Smiley

We will release more detailed info on everything tomorrow + the OSX wallet. Good night everyone!


Quick, stupid, question: I have been mining throughout the update period. Aside from long confirmation times, I've been getting more or less steady, if somewhat lite, returns. Will there be any problem with these coins?
sr. member
Activity: 442
Merit: 250
Now I can confirm my Linux wallet can send and receive coins.

Mining has been tested partially. I don't have enough powerful hardware to confirm it is able to find a block.
hero member
Activity: 924
Merit: 1000
Jared,
 Thank you for the hard work! Is the executable something we can just run and it will overwrite the existing version or do we need to go ahead and delete anything? Sorry for the newbie question. Smiley

YC

Introducing DigiByte v3.0.0 MultiAlgo

Before we release the OSX & Linux version as well as publicly announce the release we would appreciate a few beta testers on here to run the wallet through a couple send, receive, sync & solo mining tests. (Scrypt mining will be the only algo to mine until the others kick in at block 145,000)

As always make sure to back up your wallet.dat before upgrading! (File -> Backup Wallet -> Select location to save to)

If you see any typo's or other mistakes in the wallet please let us know! Thanks everyone!

Windows x32 bit
http://www.digibyte.co/sites/digibyte.co/files//crypto/digibyte-3.0.0-win32-setup.exe

Windows x64 bit
http://www.digibyte.co/sites/digibyte.co/files//crypto/digibyte-3.0.0-win64-setup.exe

sr. member
Activity: 393
Merit: 250
is the new multi-algo code online? where can I find the new source code?

cheers



This is the main source: https://github.com/digibyte/DigiByteProject
sr. member
Activity: 392
Merit: 250
is the new multi-algo code online? where can I find the new source code?

cheers

full member
Activity: 274
Merit: 101

Introducing DigiByte v3.0.0 MultiAlgo

Before we release the OSX & Linux version as well as publicly announce the release we would appreciate a few beta testers on here to run the wallet through a couple send, receive, sync & solo mining tests. (Scrypt mining will be the only algo to mine until the others kick in at block 145,000)


If the other algos don't kick in until block 145,000, how are people mining sha256???



{
"version" : 3000000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 1850509.37647499,
"blocks" : 141694,
"timeoffset" : -6,
"connections" : 11,
"proxy" : "",
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 1270.96790193,
"difficulty_sha256d" : 1270.96790193,
"difficulty_scrypt" : 340.49683390,
"difficulty_groestl" : 0.00024414,
"difficulty_skein" : 0.00024414,
"difficulty_qubit" : 0.00024414,
"testnet" : false,
"keypoololdest" : 1389569262,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
hero member
Activity: 756
Merit: 500
Community Liaison,How can i help you?

Introducing DigiByte v3.0.0 MultiAlgo

Before we release the OSX & Linux version as well as publicly announce the release we would appreciate a few beta testers on here to run the wallet through a couple send, receive, sync & solo mining tests. (Scrypt mining will be the only algo to mine until the others kick in at block 145,000)

As always make sure to back up your wallet.dat before upgrading! (File -> Backup Wallet -> Select location to save to)

If you see any typo's or other mistakes in the wallet please let us know! Thanks everyone!

Windows x32 bit

Windows x64 bit





install. win x64                        = √
sync                                          = √
receive DGB in wallet                 = √
send DGB                                    = √
Receive  DGB on exchange           =√          

Buy more Digibyte                          = √                        

Good job guys!
sr. member
Activity: 434
Merit: 250
Does the difficulty from now work as from the start?
Does that mean it did start from 0? That could restart the value of this coin on exchanges or nope?
sr. member
Activity: 393
Merit: 250
I tried to get a p2pool node up and running with the new wallet.
Seems we need some change in the p2pool code too...

http://ca.p2pool.sk:9022

not sending work to the workers.
legendary
Activity: 1106
Merit: 1000
The future is bright with DigiByte.
Installed and synced the windows wallet and no issues found. Great job Jared !!! Thanks Smiley
sr. member
Activity: 349
Merit: 250
“Blockchain Just Entered The Real World”
3.0 installed and solo mining and solving blocks.... woot! no issues to post
full member
Activity: 215
Merit: 100
Compiled fine, and when I try to start the daemon.
Error initializing wallet database environment /wallets/.digibyte!
db.log shows
illegal flag combination specified to DB_ENV->open

debug.log
2014-08-14 08:04:40 CDBEnv::Open : LogDir=/wallets/.digibyte/database ErrorFile=/wallets/.digibyte/db.log
2014-08-14 08:04:40 ERROR: CDBEnv::Open : Error 22 opening database environment: Invalid argument

What version of libdb do you use?
I have  libdb5.1++-dev and works all right.

Solved:
I had 4.8 library in /usr/local/lib, so even when it compiled fine with 5.1, it wanted to use the 4.8.
checked with ldd. now its working.
thanks


Do you know if ALL P2 nodes need to update for this to be effective?

Jump to: