forked from TrueCloudLab/neoneo-go
49cea72e41
I've carefully checked the way how new service can be added to the Blockchain instance or to be removed from it. Current implemention of SetNotary and SetOracle methods doesn't contain dangerous code, and native contracts have atomic values everywhere where service is stored. Current implementation of Notary, Oracle and StateRoot services' reload/disabling/enabling on SIGUSR1 is safe and doesn't require any adjustment. This commit closes #2944, it's not a bug in the code, it's just stale documentation. Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru> |
||
|---|---|---|
| .. | ||
| compiler | ||
| config | ||
| consensus | ||
| core | ||
| crypto | ||
| encoding | ||
| interop | ||
| io | ||
| neorpc | ||
| neotest | ||
| network | ||
| rpcclient | ||
| services | ||
| smartcontract | ||
| util | ||
| vm | ||
| wallet | ||