TrueCloudLab/neoneo-go
7
0
Fork 2
Code Issues Pull requests Projects Releases Packages Wiki Activity
neoneo-go/config
History
Roman Khimov 4e7cee4e12 config: replace VerifyBlocks with SkipBlockVerification 
It directly affects node security and the default here MUST BE the safe choice
which is to do the verification. Otherwise it's just dangerous, absent any
VerifyBlocks configuration we'll get an insecure node. This option is not
supposed to be frequently used and it doesn't affect the ability to process
blocks, so breaking compatibility (in a safe manner) should be OK here.
2022-12-07 17:35:56 +03:00
..
protocol.mainnet.neofs.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00
protocol.mainnet.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00
protocol.privnet.docker.four.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00
protocol.privnet.docker.one.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00
protocol.privnet.docker.single.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00
protocol.privnet.docker.three.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00
protocol.privnet.docker.two.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00
protocol.privnet.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00
protocol.testnet.neofs.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00
protocol.testnet.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00
protocol.unit_testnet.single.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00
protocol.unit_testnet.yml config: replace VerifyBlocks with SkipBlockVerification 2022-12-07 17:35:56 +03:00