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. |
|
|
|
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?
The difficulty does not restart from 0, it will keep the existing Scrypt Difficulty. Each other algo will start at a lower diff & will quickly adjust as needed. |
|
|
|
Multi-Algo mining does not kick in until block 145,000. Until then the mining difficulties will still display in the client using "getinfo." The wallet defaults to "sha256" unless otherwise specified in the digibyte.conf file. Example: rpcallowip=*
rpcuser=usr
rpcpassword=pass
server=1
daemon=1
txindex=1
debug=1
algo=scrypt
addnode=192.168.0.11 algo=skein algo=qubit algo=groestl algo=sha256d algo=scrypt |
|
|
|
Welcome back!  We will release more detailed info on everything tomorrow + the OSX wallet. Good night everyone! |
|
|
|
Have just built new linux wallet from sources. 1. Compilation went without issues. 2. Connections found. 3. Synchronisation stuck at block 141 627.  EDIT: Now trying to rebuild the blockchain... Awesome! That is good to know! We are working on the OSX pkg as we speak. 141 627 is the most recent block, so all is good there. It has just been a few hours since the last block so it wont display "synced" yet with a check-mark. Thanks for the feedback! Can you please point me to the sources ? This is the main source: https://github.com/digibyte/DigiByteProject |
|
|
|
Awesome... I've successfully updated my Windows 32 bit wallet to this version. It's 11 hours behind, but on the correct block (141627)... Next question... where do I point my miners  Any pools updated yet? Yes that is normal and is the last block. We haven not reached out to all the mining pools etc yet. Multi-algo mining will not be in effect until block 145,000. Once we finish the Mac OSX we will start spreading the news. Please keep providing feed back, good or bad on 3.0.0. The more tester we have the better. |
|
|
|
Rebuilt the blockchain and again the same - can't pass trough the block 141 627.
EDIT: Sorry, I have just noticed your explanation.
Does it mean the blockchain is temporary stopped?
We have seen some long delays between blocks the past few weeks. It has been normal & will be changed with this update. All is well |
|
|
|
What makes this coin different? What makes you stand out?
We are all in this for the long haul & we have some exciting things in the works. Welcome to the DigiByte community! |
|
|
|
Have just built new linux wallet from sources. 1. Compilation went without issues. 2. Connections found. 3. Synchronisation stuck at block 141 627. EDIT: Now trying to rebuild the blockchain... Awesome! That is good to know! We are working on the OSX pkg as we speak. 141 627 is the most recent block, so all is good there. It has just been a few hours since the last block so it wont display "synced" yet with a check-mark. Thanks for the feedback! |
|
|
|
Why isn't this coin on bittrex? Would love to buy some over there this instant!
That is our next step once we get this update rolled out |
|
|
|
We are compiling the final Windows v 3.0 release as we speak. We have ran it through several tests over the last 20 hours. We mined on all 5 algos for 12 hours and everything worked as expected. The hard fork will occur at block 145,000. Once the software finishes compiling we will run it through a few quick sanity checks & then we will do a soft launch on here for a few hours before announcing it on social media. We can use all the testers and feedback we can get over the next few hours. Thanks again everyone for your patience! We are now ready to enter the next stage in DigiBytes life! |
|
|
|
Thank you for posting this! This looks cool, we are going to check it out more! |
|
|
|
|
Ok everyone! After two of us working almost 5 straight days we found the 1 little itty bitty line of code screwing everything up. We have all 5 algos mining away as expected on testnet and are going to run a few more tests to make sure. We feel very relieved! If all goes well we should get the update out tomorrow!
|
|
|
|
Good news! We finally have been able to compile again! We are still experiencing a couple random crashes, so we want to test some more in the morning. It syncs with the block-chain just fine & we are able to send/receive coins as well. Thanks again for your patience. This update has been very frustrating for us. Stay tuned! Edit: We just noticed we need to change the "Bitcoin" in the Picture as well as a few other places in the wallet.  |
|
|
|
Everyone, We have just received word that DigiByte has been added to a brand new exchange named LazyCoins out of the UK. We have talked with one of the developers behind the exchange and they appear to be doing things professionally. You can check their site out here: https://lazycoins.com/tradeYou can follow them on Twitter here: https://twitter.com/LazyCoinsYou can check their blog out here: http://blog.lazycoins.com/BTCTalk thread: https://bitcointalk.org/index.php?topic=704759.0Their AML-Legal Page: https://lazycoins.com/legal-amlWe understand it is the intention of the Company to register as a money service business with HM Revenue and Customs ("HMRC"). This guidance is to assist the Company’s compliance with the Money Laundering Regulations 2007 (the “Regulations"). Detailed guidance issued by HMRC and entitled ‘Anti Money Laundering Guidance for Money Service Businesses – MLR8 MSB’ can be found at http://www.hmrc.gov.uk/mlr/mlr_msb.pdf. We are currently pursuing legal requirements with HMRC and other regulatory bodies to ensure we are fully compliant before the fiat markets are open. LazyCoins Compliance Team |
|
|
|
We apologize for the delay. We updated a couple new code changes yesterday we thought would only take a few minutes. (Bitcoin core updates) It managed to break about 10 things We have worked through the night. As soon as we get it compiled we are going to release it. Thanks again for your paintence & support. Cheers for the update. I'll be expecting a Powerpoint presentation on your progress by the end of the day please Has to have at least 10 slides, multiple fade in and fade out effects, maybe some funny video and a lot of coiparts. ah, and like 10 different typesets and bright colours. lot of colours. no technicsl details whatsoever, just strong katch phrases, like low hanging fruits, quick win, restructuralization, logos of like 10 companies that everyone knows, you know the dril, right ? :-) lol! This made us smile! We know everyone is anxious to get mining again (we are ourselves) & we are about to pull our hair out trying to get the wallet to compile. We had a working test version and when when we dropped the DigiByte blockchain information + what we thought were a couple small Bitcoin Core updates we broke everything. We are very close to getting it to compile. We will continue working until we get it done. Once finished we will release the Windows wallet & hopefully the Mac OSX wallet at the same time. The Android wallet will be released a few days after but will update by itself. We have also contacted a credible IOS developer to get a DigiByte wallet on the iTunes store. Thanks again for your patience & we very much apologize for the delay but we do not want to release a broken product just to meet a deadline we set for ourselves. |
|
|
|
Seriously though... in my line of business... and in fact every single line of business I've ever had, missing deadlines gets you the sack. Why say you can do something then miss the deadline! Not the first time either.
You obviously don't work as a programmer, where one small change to the code can break 10 things. These sorts of posts don't get anyone anywhere. We apologize for the delay. We updated a couple new code changes yesterday we thought would only take a few minutes. (Bitcoin core updates) It managed to break about 10 things We have worked through the night. As soon as we get it compiled we are going to release it. Thanks again for your paintence & support. |
|
|
|
Ok so does this we can mine again today or 2 weeks from now  Multi-algo mining will kick in @ block 145,000. Which is about 3600 blocks from now. Based upon mining data from the last three months this could take 1-3 weeks to occur depending on how much hash is thrown at the network. Once we have confirmation all the exchanges, block explorers & mining pools have updated we don't mind renting an ASIC to speed things up. But we also want to make sure someone does not throw an ASIC at the network right away and cause an un smooth hard fork. Also on a side note it appears Alt Explorer is displaying the wrong block count. After checking multiple dns seed servers we are currently at DGB block 141404. |
|
|
|
|
Show Posts
