Add NNS support to native contracts about neo HOT 2 CLOSED

Usually SDKs know native contract hashes exactly. Like to me it's gas.Hash (https://pkg.go.dev/github.com/nspcc-dev/neo-go/pkg/interop/native/gas#pkg-constants or https://pkg.go.dev/github.com/nspcc-dev/[email protected]/pkg/rpcclient/gas#pkg-variables), whatever that is. And it's known without NNS.

from neo.

The problem is that you need to use different ways to find script hashes.
I was thinking if we could use the same solution to refer to native and user deployed contracts.

In practice, we don't need to call NNS in runtime, but use it during compilation.

In other words, I wish that finding contracts are consistent, even if they are native contracts. They should be able to "refer to" Flamingo the same way they refer the ContractMamagement native contract.

Maybe instead of multiple domains, just one using subdomains? Maybe this doesn't need any kind of intervention from the core team.

from neo.