Once the fork is completed, we will need a new ann  Actually once new release will be out a new ann will be posted. Otherwise people might still install older version. All to make sure that fork will be smooth. |
|
|
|
Ticker: DOGETH
This ticker is way too short. Use DOGECOINETHEREUM instead. |
|
|
|
Just to make sure, along with everything else, you are going to update the code to work with the current version of secp256k1, right?
Yes |
|
|
|
New code will be released on Sunday, 23 Aug (UTC).
I am still not sure about binaries. Will do my best to publish them with the new code.
|
|
|
|
No i have no idea lol, currently 8 weeks behind now. its moving just very slowly
It's because lack of checkpoints. If you are using Linux or if you are able to compile own Windows / Mac binary you will get insta speedup. No fud, but are you still on this project full-time? Shall we talk about mastertrader coin, hyper inflation, lack of volume, delisting warning, 90% of staking in devs hands, private investment options and cool charts on your website? FUCK OFF |
|
|
|
No i have no idea lol, currently 8 weeks behind now. its moving just very slowly
It's because lack of checkpoints. If you are using Linux or if you are able to compile own Windows / Mac binary you will get insta speedup. |
|
|
|
because developer is couchpotato
*hugs*  Anyone know why the chain is taking for ever to catch up, 9 weeks behind taking absolute ages, days even, 11 connections block 68108
Are you able to compile own binary? |
|
|
|
Reading things like "force myself to do it?" aint very good, what are you a couchpotato?
Nah, just busy with other, not planned things. They are almost done so I will be able to focus on 8BIT soon. |
|
|
|
First of all please make sure that your block height is >= 145000. Bittrex wallet is at height 144082, its probably not a fork as it was last checked many hours ago. So in your tickets just ask them to restart their wallet because its stuck. Please also include dynamic list of seednodes addnode=node00.8-bit.party
addnode=node01.8-bit.party
addnode=node02.8-bit.party
addnode=node03.8-bit.party
addnode=node04.8-bit.party
addnode=node05.8-bit.party
addnode=node06.8-bit.party
addnode=node07.8-bit.party
addnode=node08.8-bit.party
addnode=node09.8-bit.party
addnode=node10.8-bit.party
addnode=node11.8-bit.party
addnode=node12.8-bit.party
addnode=node13.8-bit.party
addnode=node14.8-bit.party
addnode=node15.8-bit.party
addnode=node16.8-bit.party
addnode=node17.8-bit.party
addnode=node18.8-bit.party
addnode=node19.8-bit.party
addnode=node20.8-bit.party
|
|
|
|
Any news about fork time?
Seems like I have to set deadline to force myself to finally do it. |
|
|
|
|
So would I. Besides education, video is the best advertisement.
|
|
|
|
|
With port issues client should not start at all. At least daemon version, not sure about qt wallet.
|
|
|
|
|
Without at least pubkey (your public 8BIT address) or txid I can't help.
|
|
|
|
|
This message is shown when somethings wrong with your masternode input. Check it.
|
|
|
|
|
Well I am bit frustrated with no new release yet so will do my best to publish it as soon as possible. It's like fresh air we all need.
|
|
|
|
|
Show Posts
