You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 10, 2025. It is now read-only.
Summary or problem description
As all hashes and signatures are network-dependent now all clients need to know the magic number of the network. This magic number can be configured explicitly in the client, but I think we can do a bit better than that by making it discoverable from the server.
Do you have any solution you want to propose?
I don't think it's worth another RPC call, we can just add a magic field to the getversion RPC call return value.
In general, this follows the same line as #355 (and maybe intersects a bit with intentions of neo-project/neo#1977), I'd really like the client to have exactly one thing to configure --- RPC endpoint to use, everything else it needs should be available from that.
Where in the software does this update applies to?
Summary or problem description
As all hashes and signatures are network-dependent now all clients need to know the magic number of the network. This magic number can be configured explicitly in the client, but I think we can do a bit better than that by making it discoverable from the server.
Do you have any solution you want to propose?
I don't think it's worth another RPC call, we can just add a
magicfield to thegetversionRPC call return value.In general, this follows the same line as #355 (and maybe intersects a bit with intentions of neo-project/neo#1977), I'd really like the client to have exactly one thing to configure --- RPC endpoint to use, everything else it needs should be available from that.
Where in the software does this update applies to?