neo-go/config
Anna Shaleva f7ee66ff8b config: enable hardforks for default NeoFS testnet config
Otherwise all hardforks enabled by default from genesis which leads to
errors like this if we introduce new hardfork:
```
Dec 04 02:46:46 titan1 neofs-node[157390]: warn        client/multi.go:43        could not establish connection to RPC node        {"endpoint": "wss://rpc.morph.t5.fs.neo.org/ws", "error": "WS client initialization: failed to get network magic: unexpected hardfork: Echidna"}
```

Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
2024-12-04 12:22:07 +03:00
..
config_embed.go cli: add embedded node config 2024-07-01 10:59:11 +03:00
protocol.mainnet.neofs.yml config: enable NeoFSBlockFetcher by default 2024-11-29 19:28:03 +03:00
protocol.mainnet.yml config: enable NeoFSBlockFetcher by default 2024-11-29 19:28:03 +03:00
protocol.privnet.docker.four.yml *: move NativeUpdateHistory logic under Hardforks management 2023-11-21 14:05:28 +03:00
protocol.privnet.docker.one.yml *: move NativeUpdateHistory logic under Hardforks management 2023-11-21 14:05:28 +03:00
protocol.privnet.docker.single.yml *: move NativeUpdateHistory logic under Hardforks management 2023-11-21 14:05:28 +03:00
protocol.privnet.docker.three.yml *: move NativeUpdateHistory logic under Hardforks management 2023-11-21 14:05:28 +03:00
protocol.privnet.docker.two.yml *: move NativeUpdateHistory logic under Hardforks management 2023-11-21 14:05:28 +03:00
protocol.privnet.yml *: move NativeUpdateHistory logic under Hardforks management 2023-11-21 14:05:28 +03:00
protocol.testnet.neofs.yml config: enable hardforks for default NeoFS testnet config 2024-12-04 12:22:07 +03:00
protocol.testnet.yml config: enable NeoFSBlockFetcher by default 2024-11-29 19:28:03 +03:00
protocol.unit_testnet.single.yml config: fix TestRun_WithNewVMContextAndBreakpoints path for windows 2024-02-14 13:22:07 +03:00
protocol.unit_testnet.yml config: fix TestRun_WithNewVMContextAndBreakpoints path for windows 2024-02-14 13:22:07 +03:00