[ANN] DERO: DAG + Cryptonote + Bulletproofs + SSL + POW + Smart Contracts

[--Serena--]

The Dero team is pleased to announce that we're listed on SouthXchange and trading should be enabled soon!

https://www.southxchange.com/Balance/Index/DERO

[choriori86]

I sent coin but it doesn't arrive.

13  Show transaction history
Height 52188 transaction 0935872fd553925e650456e0d8818a80020ec8abdc0a66e4058aeba5e24658ed received XXX DERO PAYMENT ID:XXX

Where is it stopped?

pls can you give more details. Your TX is mined and accepted by Network.

This is also stopped.
Height 52530 transaction 96147bcf3c26972805b01bc1074404b48d4f080a1e26a896014ea7d88005ca9c received



Now the coins I sent arrived.

[MagicSmoker]

Any chance the new daemon/wallet is messing up the old blockchain? I ask because once again my wallet daemon is unable to sync, but unlike the previous forking incident, this time the "new top block candidate" keeps oscillating between blocks 53023 and 52402, which is puzzling, to say the least.

At this point we're encouraging everyone to move over to the new network. We will likely make an official announcement almost any time now to let all individual users know it's time to switch 

http://seeds.dero.io/alpha/

hmmm... I'm getting a veritable sea of "err while loading output data index..." errors on the new daemon as it tries to sync. Currently sitting around 7300 out of 53407.

Not exactly confidence inspiring, and I generally loathe alpha/beta testing software (I do enough of that for my job), hence why I didn't rush to volunteer for doing that here.

[--Serena--]

Any chance the new daemon/wallet is messing up the old blockchain? I ask because once again my wallet daemon is unable to sync, but unlike the previous forking incident, this time the "new top block candidate" keeps oscillating between blocks 53023 and 52402, which is puzzling, to say the least.

At this point we're encouraging everyone to move over to the new network. We will likely make an official announcement almost any time now to let all individual users know it's time to switch 

http://seeds.dero.io/alpha/

hmmm... I'm getting a veritable sea of "err while loading output data index..." errors on the new daemon as it tries to sync. Currently sitting around 7300 out of 53407.

Not exactly confidence inspiring, and I generally loathe alpha/beta testing software (I do enough of that for my job), hence why I didn't rush to volunteer for doing that here.

It's in debug mode so you're seeing all kinds of things from passed history in the blockchain. You will see a number of things like that but it's nothing to worry about. If you ran other blockchains with debug on you'd see similar things everywhere.

We're now listed on SouthX btw!

[--Serena--]

The Dero team is pleased to announce that we're listed on SouthXchange and trading should be enabled soon!

https://www.southxchange.com/Balance/Index/DERO





(One time double post because of excitement!)

[CaptDero]

Any chance the new daemon/wallet is messing up the old blockchain? I ask because once again my wallet daemon is unable to sync, but unlike the previous forking incident, this time the "new top block candidate" keeps oscillating between blocks 53023 and 52402, which is puzzling, to say the least.

At this point we're encouraging everyone to move over to the new network. We will likely make an official announcement almost any time now to let all individual users know it's time to switch  

http://seeds.dero.io/alpha/

hmmm... I'm getting a veritable sea of "err while loading output data index..." errors on the new daemon as it tries to sync. Currently sitting around 7300 out of 53407.

Not exactly confidence inspiring, and I generally loathe alpha/beta testing software (I do enough of that for my job), hence why I didn't rush to volunteer for doing that here.

Hi @MagicSmoker,
 So many warning scrolling are debug mode on by default for testers. Above errors are TXs that are recent but not in your blockchain-db as you are not fully synced. Will go away when fully synced.
Relax our alphas are more than just alphas. Any bugs reported are fixed on same day.
Believe me you will love and appreciate the new code for its reliability and robustness soon.

Rd.
Capt. D

[itslukebenz]

Good news on top of good news, well done! Looking forward to that special announcement you mentioned, made me curious.

[--Serena--]

I just had a successful withdrawal of 450 Dero from SouthXchange (https://www.southxchange.com/Balance/Index/DERO) and 87 on Stocks.Exchange (https://stocks.exchange/trade/DERO/BTC)

[--Serena--]

https://twitter.com/DeroProject/status/978843185551114240

[leo1in88]

so can i safety withdraw dero from stockexchane now? last time i withdrew its fail

[--Serena--]

so can i safety withdraw dero from stockexchane now? last time i withdrew its fail

I won't be able to say that with a reasonable degree of certainty until they're on the next release of the golang implementation (they're on v7 linux until then). That being said, I've had success today with one 87 Dero withdrawal

[krypt0id]

so can i safety withdraw dero from stockexchane now? last time i withdrew its fail

I would say the safest bet with stocks.exchanges is still 25 dero or less, unfortunately.

[MagicSmoker]

hmmm... I'm getting a veritable sea of "err while loading output data index..." errors on the new daemon as it tries to sync. Currently sitting around 7300 out of 53407.

Not exactly confidence inspiring, and I generally loathe alpha/beta testing software (I do enough of that for my job), hence why I didn't rush to volunteer for doing that here.

Hi @MagicSmoker,
 So many warning scrolling are debug mode on by default for testers. Above errors are TXs that are recent but not in your blockchain-db as you are not fully synced. Will go away when fully synced.
Relax our alphas are more than just alphas. Any bugs reported are fixed on same day.
Believe me you will love and appreciate the new code for its reliability and robustness soon.

Rd.
Capt. D

Well, I woke up this AM to find the daemon stuck on block 8648 with "failed tx" and "mempool stopped" as the last two messages reported. I rather expected the daemon to make a lot more progress than that so it seems whatever "mempool stopped" is, it's fatal.

EDIT - blockchain syncing did resume when I restarted the daemon, btw.

[CaptDero]

hmmm... I'm getting a veritable sea of "err while loading output data index..." errors on the new daemon as it tries to sync. Currently sitting around 7300 out of 53407.

Not exactly confidence inspiring, and I generally loathe alpha/beta testing software (I do enough of that for my job), hence why I didn't rush to volunteer for doing that here.

Hi @MagicSmoker,
 So many warning scrolling are debug mode on by default for testers. Above errors are TXs that are recent but not in your blockchain-db as you are not fully synced. Will go away when fully synced.
Relax our alphas are more than just alphas. Any bugs reported are fixed on same day.
Believe me you will love and appreciate the new code for its reliability and robustness soon.

Rd.
Capt. D

Well, I woke up this AM to find the daemon stuck on block 8648 with "failed tx" and "mempool stopped" as the last two messages reported. I rather expected the daemon to make a lot more progress than that so it seems whatever "mempool stopped" is, it's fatal.

EDIT - blockchain syncing did resume when I restarted the daemon, btw.

Fixed above connection handler bug.
Also I assume you are using  daemon from  http://seeds.dero.io/alpha/
Failed  TX and mempool bugs will go after full db sync. If they appear after full sync then pls report.
On recent systems chain sync takes 25-60 mins depending on Network bandwidth and processing.

[CaptDero]

Alpha has  been updated for minor bug, if any user show their daemon disconnected/killed. Pls update to new release.
http://seeds.dero.io/alpha/

[--Serena--]

southX markets are live

https://www.southxchange.com/Market/Book/DERO/BTC

[--Serena--]

All of the functionality on SouthXchange (SX is what I like to call it) seems to be working well!

[MagicSmoker]

Well, I woke up this AM to find the daemon stuck on block 8648 with "failed tx" and "mempool stopped" as the last two messages reported. I rather expected the daemon to make a lot more progress than that so it seems whatever "mempool stopped" is, it's fatal.

EDIT - blockchain syncing did resume when I restarted the daemon, btw.

Fixed above connection handler bug.
Also I assume you are using  daemon from  http://seeds.dero.io/alpha/
Failed  TX and mempool bugs will go after full db sync. If they appear after full sync then pls report.
On recent systems chain sync takes 25-60 mins depending on Network bandwidth and processing.

25-60 minutes to sync, you say? I was running the 386 version up until this morning, then switched over to the amd64 version (it wasn't clear which one to use, given that the laptop I run my wallets on has a Celeron CPU) and had to start the sync all over again, apparently. At any rate, 3+ hours later and I am at ~40xxx out of 53386 which is far slower than your estimate but far faster at syncing than any other wallet I've run.

However, my poor laptop is noticeably slower while running this hot little daemon; CPU load is quite heavy at around 25-30%.

Now, how to load the wallet from the old client to the new one? I presume I'll need to use the --restore-deterministic-wallet and --electrum-seed=<seed phrase> commands?

[miner.rocks]

Now, how to load the wallet from the old client to the new one? I presume I'll need to use the --restore-deterministic-wallet and --electrum-seed=<seed phrase> commands?

yep

./dero-wallet-cli --restore-deterministic-wallet --electrum-seed="yourMnemonicPhrase" --generate-new-wallet=yourWallet --password=yourWalletPassword

[--Serena--]

DERO: a new blockchain technology with CryptoNote Privacy + Smart Contracts

Dero has written a new blockchain technology based on the CryptoNote protocol with the next major step being new smart contract controls. Dero's new blockchain is coded in golang (Go) to bring together the CryptoNote protocol and smart contracts on the Dero blockchain.

Dero's new blockchain based on the CryptoNote protocol and written in golang is now complete and the development team have completed their Q1 roadmap goals early. Having written a new blockchain technology from the ground up successfully, the team is now turning their attention to smart contracts with CryptoNote privacy.

For now, the new code is backwards compatible with the previous CryptoNote protocol (Helium Hydra). If you download the previous and new clients you're able to run both sets of daemons in parallel. That being said, it adds a lot of effort to maintain compatibility and some time in the near future we will drop support for the previous CryptoNote protocol (Helium Hydra).

We will provide technical details and developer details in the future.

Bitcointalk ANN: https://bitcointalk.org/index.php?topic=2525508.0
Pre-compiled binaries: http://seeds.dero.io/alpha/
Website: https://dero.io/
Forum: https://forum.dero.io/
GitHub: https://github.com/deroproject

Please follow us on Twitter for the most up to date information as it becomes available: https://twitter.com/DeroProject

Dero has a very welcoming community and we would enjoy the opportunity to have you join us in Slack, Discord, or on Reddit!

Slack: https://join.slack.com/t/deroproject/shared_invite/enQtMzAwMDc5MDY4NDUzLTAzOWNjYWZmNDgxZTk1YjNiNWFiYjg1OWNiMmQ2MmUxOWRmNjNjOWM3ODAzMzE3M2RhNzBhZjUyZGQxYjQxY2U

Discord: https://discord.gg/aQcphjF

If you have any questions or require assistance, please don't hesitate to reach out for any reason. Slack tends to elicit the fastest response times from the community but all listed links are checked several times a day