Skip to content

docs: add NEVM Registry section to sentry node setup guide#27

Open
guilhermefleury wants to merge 1 commit into
syscoin:masterfrom
guilhermefleury:docs/sentrynode-nevm-registry
Open

docs: add NEVM Registry section to sentry node setup guide#27
guilhermefleury wants to merge 1 commit into
syscoin:masterfrom
guilhermefleury:docs/sentrynode-nevm-registry

Conversation

@guilhermefleury
Copy link
Copy Markdown

Adds a new section to docs/guides/sentrynode_setup.mdx explaining the
NEVM Registry — a Syscoin Core 5.0 (Nexus) feature that requires
every Sentry Node operator to register a NEVM address via
protx_update_service.

The release notes ([5.0.0 §6][1]) describe the requirement, but the
sentry node setup guide currently doesn't mention it at all. Operators
following the guide today end up with a Sentry Node that's missing from
the registry precompile lookup and from registry-aware tooling
(decentralized sequencing, AVS-style registrations, etc.).

Syscoin Core 5.0 (Nexus) introduced the NEVM Registry — an on-chain directory mapping each Sentry Node to a NEVM address, exposed via precompile 0x62. Every Sentry Node operator must register a NEVM address via protx_update_service. Section explains the requirement, the nevmAddress argument, hosting-provider option, and gives an example call.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant