@onyo this looks like a good change, has it been tested?
Syncing an existing wallet, a fresh new sync, importing/rescanning, and sending funds works OK.
> @onyo this looks like a good change, has it been tested?
Syncing an existing wallet, a fresh new sync, importing/rescanning, and sending funds works OK.
> @onryo did you do those tests on Hush or DragonX or both?
Yes, both.
Also tested DragonX as follows:
- Remove .hush/DRAGONX.
- Change nodes:
```
if (isdragonx) {
DRAGONX_nodes = {"node1.hush.is","node2.hush.is","node3.hush.is",
"node4.hush.is","node5.hush.is","node6.hush.is"};
}
```
dragonx.is currently has no records that point to DRGX nodes, so I changed to node.is records for a test.
Then started the node without supplying the seed node as follows:
```
./hush-arrakis-chain -ac_name=DRAGONX -ac_algo=randomx -ac_halving=3500000 -ac_reward=300000000 -ac_blocktime=36 -ac_private=1
```
I get a few peers from `DRAGONX_nodes`.
@onyo this looks like a good change, has it been tested?
Syncing an existing wallet, a fresh new sync, importing/rescanning, and sending funds works OK.
@onryo did you do those tests on Hush or DragonX or both?
Yes, both.
Also tested DragonX as follows:
dragonx.is currently has no records that point to DRGX nodes, so I changed to node.is records for a test.
Then started the node without supplying the seed node as follows:
I get a few peers from
DRAGONX_nodes
.1526a754d2
into dev 1 week ago1526a754d2
.