We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am adding NNS to the neo-cli node. I need to know these contract hashes for
neo-cli
894710606
91414437
91466898
Maybe you guys know or know someone? @shargon @superboyiii
The text was updated successfully, but these errors were encountered:
NeoFS networks always have NNS deployed as the first contract, so whatever is ID 1 there is NNS. But this NNS is not the same as the one in this repository, rather it's https://github.com/nspcc-dev/neofs-contract/tree/9dcf82fc4045b959181e1bb509a8dff31725e5a0/contracts/nns and it's not 100% compatible with the C# version (see #25, #26, #27, #29 at least).
Sorry, something went wrong.
@roman-khimov on neofs can TDL be any name? Or is just .neofs?
neofs
TDL
.neofs
Can be anything if committee registers it. In fact, there is .container as well.
.container
No branches or pull requests
I am adding NNS to the
neo-cli
node. I need to know these contract hashes for894710606
(seed1t5.neo.org)91414437
(morph1.fs.neo.org)91466898
(morph01.testnet.fs.neo.org)Maybe you guys know or know someone? @shargon @superboyiii
The text was updated successfully, but these errors were encountered: