TrueCloudLab/neo-go
8
0
Fork 0
mirror of https://github.com/nspcc-dev/neo-go.git synced 2025-03-29 19:03:51 +00:00
Code Issues Projects Releases Packages Wiki Activity

docs: adjust DB compatibility notes

Browse source 
It's dangerous to change `Max*` ProtocolConfiguration settings:

* Changes in MaxBlockSize, MaxBlockSystemFee and MaxTransactionsPerBlock
  may lead to the fact that accepted block or transaction becomes invalid.
  I agree that these settings are not written in the DB, but at the same
  time it's not correct to compare databases that have these settings
  mismatched.
* Changes in MaxTraceableBlocks may lead to the fact that some
  transaction will be processed differently, it's a possible contract
  state mismatch.
* Changes in MaxValidUntilBlockIncrement may lead to the fact that
  `setMaxNotValidBeforeDelta` method of native Notary contract may be
  processed in a different way which is also a possible contract state
  mismatch.

Ref. 5d29a3fdab.

Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
This commit is contained in:
Anna Shaleva 2024-08-05 12:26:19 +03:00
parent d8e3e57f88
commit 7e277fa948
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/node-configuration.md
View file

@ -412,9 +412,9 @@ configurations you may want to save some resources by performing synchronization
on one node and then copying the DB over to other instances. In general, this on one node and then copying the DB over to other instances. In general, this
can be done and this is supported, but NeoGo has a lot of options that may can be done and this is supported, but NeoGo has a lot of options that may
affect this: affect this:
- any differences in `ProtocolConfiguration` section make databases - any differences in `ProtocolConfiguration` section make (or may make) databases
incompatible, except for `Max*` settings, `MemPoolSize`, incompatible, except for `MemPoolSize`, `P2PNotaryRequestPayloadPoolSize`,
`P2PNotaryRequestPayloadPoolSize`, `SeedList`, `TimePerBlock`. `SeedList`, `TimePerBlock`.
Protocol configuration is expected to be the same on all nodes of the same Protocol configuration is expected to be the same on all nodes of the same
network, so don't touch it unless you know what you're doing. network, so don't touch it unless you know what you're doing.
- DB types (Level/Bolt) must be the same - DB types (Level/Bolt) must be the same