--Serena--
Member
Offline
Activity: 224
Merit: 11
|
|
March 03, 2018, 11:41:00 PM |
|
Im a newbie...cant send private messages to you...
I've adjusted my account so that I'm able to receive PMs from newbies and have sent you a message.
|
|
|
|
thongeth
Newbie
Offline
Activity: 4
Merit: 0
|
|
March 04, 2018, 12:17:22 AM |
|
Thanks u, but i am using this patch.
|
|
|
|
Speedie
|
|
March 04, 2018, 12:33:23 AM Last edit: March 04, 2018, 01:01:48 AM by Speedie |
|
Anybody using these 6 nodes in their config should remove them ASAP please. I was not made aware of the fix, nor the recommendation to use other nodes exclusively, until I read it in the forum post just now. For the sake of stability they have been permanently removed. ****** IMPORTANT ******
I have been working with support and DeroBoy this morning to try and help with the network problems that we've been seeing. To that end, I have created a network of 6 geo-diverse nodes dedicated purely to running Dero daemons. The nodes have each other as priority nodes, and it is requested that all pools add them as priority nodes too. End users may also add them as priority nodes to your local daemon which will help everything to stay in sync.
They are located in: New Jersey US, Los Angeles US, Dallas US, London UK, Amsterdam NL, and Singapore.
IP addresses:
45.63.6.91 108.61.220.229 207.148.5.250 45.77.89.64 45.76.42.165 45.77.242.137
To add them to your pool's derod startup command line:
--add-priority-node 45.63.6.91:18090 --add-priority-node 108.61.220.229:18090 --add-priority-node 207.148.5.250:18090 --add-priority-node 45.77.89.64:18090 --add-priority-node 45.76.42.165:18090 --add-priority-node 45.77.242.137:18090
I will be watching them carefully to ensure that they stay in sync and running fast. So far no problems noted, and they're under very low load. Any problems please let me know.
|
|
|
|
--Serena--
Member
Offline
Activity: 224
Merit: 11
|
|
March 04, 2018, 12:43:44 AM |
|
Thanks u, but i am using this patch. Okay, just to confirm, you've deleted the p2pstate.bin and the imbd folder? After that, please restart your computer and do a completely fresh resync using --add-exclusive-node 89.38.97.110:18090 --add-priority-node 89.38.97.110:18090 in the command line and please remove any other priority nodes you may be using even though the exclusive should override them. This is the only node we recommend people use for the next several hours.
|
|
|
|
|
|
Rei do Bitcao
Jr. Member
Offline
Activity: 47
Merit: 1
|
|
March 04, 2018, 02:04:34 AM |
|
hello there I went to the forum and download the last dero wallet and daemon.
i don't understand where i use this addnodes commands derod.exe --add-exclusive-node 89.38.97.11018090 --add-priority-node 89.38.97.11018090
how I do this? thanks!
|
|
|
|
CaptDero (OP)
Member
Offline
Activity: 308
Merit: 33
|
|
March 04, 2018, 02:37:56 AM |
|
hello there I went to the forum and download the last dero wallet and daemon.
i don't understand where i use this addnodes commands derod.exe --add-exclusive-node 89.38.97.11018090 --add-priority-node 89.38.97.11018090
how I do this? thanks!
Pls use this option with derod/derod.exe daemon. As there was fork and to sync the network its required. If you run daemon pls ignore. Also Stop daemon first, download chain data from http://seeds.dero.io/data.mdb and restart daemon with derod --add-exclusive-node 89.38.97.110:18090 Replace data.mdb in .dero/lmdb/ folder Or corresponding folder in windows user.For full details see https://forum.dero.io/t/dero-blockchain-sync-problem/21
|
|
|
|
CaptDero (OP)
Member
Offline
Activity: 308
Merit: 33
|
|
March 04, 2018, 03:35:00 AM |
|
Hello, There has been unintentional fork on DERO blockchain. To solve see following steps: 1] pls update your derod daemon with latest from github. https://github.com/deroproject/dero2] Replace data.mdb from http://seeds.dero.io/data.mdb , For full details see https://forum.dero.io/t/dero-blockchain-sync-problem/213] start derod with option: derod --add-exclusive-node 89.38.97.110:18090 Download linux pre-compiled binary from latest releases and windows binary will be updated in next few hrs. Don't use exchange for next few days/update. Only mine on official pool till forking issue is solved. Pool web is lagging but mining/payment is perfect.We are working heavily to optimized and avoid forking issues in new Golang code. P2P code is getting too much priority to avoid this in future. As we are very near to finish cryponote in Golang, so there is no good reason to fix existing C code. Hopefully we will shift our pools etc. in less than 1 month to Golang daemon. Thanks for your patience and continuous support. Pls follow twitter for any updates, will be updating everything there: https://twitter.com/DeroProjectRegards. Capt. D
|
|
|
|
ramcrypto
Member
Offline
Activity: 117
Merit: 10
|
|
March 04, 2018, 06:02:28 AM |
|
Dev why don't u start a discord channel and telegram channel..
|
|
|
|
|
cpmcgrat
Member
Offline
Activity: 223
Merit: 21
DCAB
|
|
March 04, 2018, 07:46:27 AM |
|
Hello, There has been unintentional fork on DERO blockchain. To solve see following steps: 1] pls update your derod daemon with latest from github. https://github.com/deroproject/dero2] Replace data.mdb from http://seeds.dero.io/data.mdb , For full details see https://forum.dero.io/t/dero-blockchain-sync-problem/213] start derod with option: derod --add-exclusive-node 89.38.97.110:18090 Download linux pre-compiled binary from latest releases and windows binary will be updated in next few hrs. Don't use exchange for next few days/update. Only mine on official pool till forking issue is solved. Pool web is lagging but mining/payment is perfect.We are working heavily to optimized and avoid forking issues in new Golang code. P2P code is getting too much priority to avoid this in future. As we are very near to finish cryponote in Golang, so there is no good reason to fix existing C code. Hopefully we will shift our pools etc. in less than 1 month to Golang daemon. Thanks for your patience and continuous support. Pls follow twitter for any updates, will be updating everything there: https://twitter.com/DeroProjectRegards. Capt. D Can we please get a technical explanation as to why the forks were happening in the first place and how you’re remediating it? It’s great it’s being worked on, but I doubt that Monero has broken c code. I’d assume it’s more likely an issue where some individual miner unintentionally 51% attacks (statistically more likely to be 70%+) for long enough to cause forking issues. Which is a size and redundancy issue, not an issue with the code.
|
Member, Dero Community Advisory Board (DCAB)
|
|
|
drigler
Newbie
Offline
Activity: 39
Merit: 0
|
|
March 04, 2018, 08:25:06 AM |
|
For people using the GUI wallet, please stop using version 0.0.2 because it contains hardcoded priority nodes from Speedie. These nodes are not available anymore. If you want to use GUI, you need to revert back to version 0.0.1 or build version 0.0.3 by yourself. Source is on my git www.github.com/driglerI will make a ziped release once devs release patched windows binaries v5. Tnx
|
|
|
|
Luci0gabsan
Member
Offline
Activity: 133
Merit: 10
|
|
March 04, 2018, 08:49:56 AM |
|
What a mess ... I tried to install the software but it does not work and now I'm reading problems on the blockchain.
Che casino ... ho provato ad installare il software ma non funziona e adesso leggo dei problemi sulla blockchain.
|
|
|
|
dingdongtobias
Newbie
Offline
Activity: 156
Merit: 0
|
|
March 04, 2018, 08:50:37 AM |
|
this is bad, very bad. Stocks exchange is then probably on the wrong chain, or ?
|
|
|
|
CaptDero (OP)
Member
Offline
Activity: 308
Merit: 33
|
|
March 04, 2018, 09:00:15 AM |
|
Hello,
There has been unintentional fork on DERO blockchain. To solve see following steps: snip.... ....... ...
Can we please get a technical explanation as to why the forks were happening in the first place and how you’re remediating it? It’s great it’s being worked on, but I doubt that Monero has broken c code. I’d assume it’s more likely an issue where some individual miner unintentionally 51% attacks (statistically more likely to be 70%+) for long enough to cause forking issues. Which is a size and redundancy issue, not an issue with the code. There are several reasons for forks. Like small network with low NW hash rate. Like if any pool finds blocks announces it but not able to provide block data due to lagging networks or Using NH on weak/overloaded pools. Pools closing port 18090 to share block etc. P2P code and chain splits etc. are being modified and re-designed in new Golang code. Hope to see no forks after that on DERO blockchain. ATM use only official pool for mining and derod daemon with options: derod --add-exclusive-node 89.38.97.110:18090 --add-exclusive-node 89.38.96.169:18090
|
|
|
|
korm
Member
Offline
Activity: 280
Merit: 10
|
|
March 04, 2018, 09:20:11 AM |
|
ATM use only official pool for mining and derod daemon with options: derod --add-exclusive-node 89.38.97.110:18090 --add-exclusive-node 89.38.96.169:18090
Ie the official pool is guaranteed not to be in another fork?
|
|
|
|
--Serena--
Member
Offline
Activity: 224
Merit: 11
|
|
March 04, 2018, 10:00:00 AM |
|
ATM use only official pool for mining and derod daemon with options: derod --add-exclusive-node 89.38.97.110:18090 --add-exclusive-node 89.38.96.169:18090
Ie the official pool is guaranteed not to be in another fork? Yes, steps have been temporarily taken to ensure that the pool is constantly on the valid chain. You will still see the odd orphaned block but I'm mining there myself.
|
|
|
|
Kenrich
|
|
March 04, 2018, 10:04:15 AM |
|
Hello,
There has been unintentional fork on DERO blockchain. To solve see following steps: snip.... ....... ...
Can we please get a technical explanation as to why the forks were happening in the first place and how you’re remediating it? It’s great it’s being worked on, but I doubt that Monero has broken c code. I’d assume it’s more likely an issue where some individual miner unintentionally 51% attacks (statistically more likely to be 70%+) for long enough to cause forking issues. Which is a size and redundancy issue, not an issue with the code. There are several reasons for forks. Like small network with low NW hash rate. Like if any pool finds blocks announces it but not able to provide block data due to lagging networks or Using NH on weak/overloaded pools. Pools closing port 18090 to share block etc. P2P code and chain splits etc. are being modified and re-designed in new Golang code. Hope to see no forks after that on DERO blockchain. ATM use only official pool for mining and derod daemon with options: derod --add-exclusive-node 89.38.97.110:18090 --add-exclusive-node 89.38.96.169:18090thanks ,i am in wrong fork chain ,but add this two exclusive-node ,look like it's normal right now ,waste a little time and energy
|
|
|
|
korm
Member
Offline
Activity: 280
Merit: 10
|
|
March 04, 2018, 10:25:03 AM |
|
use only official pool
can you set Minimum Denomination 0.000001? I usually use another pool dero.cryptopool.space. I would not like to scatter the remnants of different pools. Thank you
|
|
|
|
|