Configure NeoXDKG fork height

[AnnaShaleva]

It won't be a part of v0.3.0 since we'd like to firstly upgrade nodes to v0.3.0 and see how the things are going.

[txhsl]

The next epoch start height of T4 is 1995840, which is about 38h later (around 15:00, March 12th, UTC+0). If we want to run DKG for this epoch, then this round of DKG start should start at 1995840-2880*2=1990080, which is about 30h later.

So we can take 1990080 as the NeoXDKG fork height for T4. The second choice is 2050560, will be in 114h from now, for this we can take 1995840, the epoch start height, as the fork height.

If we take 1990080, then CNs should be reinited in at most 34h.

[vncoelho]

I think that sometimes we need a hard fork that we stop the node.

For this it would be good to create a standard for CN, here and N3, that we save mempool and then start again with it.

Basically, mempool being lost is the only problem we have.

[AnnaShaleva]

Mempool is not being lost, Geth has a cache for pending transactions AFAIK.

[txhsl]

Mempool is not being lost, Geth has a cache for pending transactions AFAIK.

Yes.

[AnnaShaleva]

If we take 1990080, then CNs should be reinited in at most 34h.

The height itself is good to me, but it's not only CNs, it's also all seed nodes should be upgraded because we enable BLS precompiles and CNs will send transactions interacting with this logic, so I think that without this upgrade seed nodes won't be able to properly process these transactions.