Extend verify() example with parameterized case #1580

Open
opened 2025-12-28 17:16:54 +00:00 by sami · 0 comments
Owner

Originally created by @roman-khimov on GitHub (Nov 19, 2025).

I'm always frustrated when people ask me of things that we don't have any example for. We do have examples for NEP-30 verify() (btw, NEP-30 should be mentioned everywhere appropriate), but it's parameter-less. The only case where we have some parameters is the Notary contract (nspcc-dev/neo-go@8b0692e3ae/pkg/core/native/notary.go (L370)), but it's native, so not really representative.

Describe the solution you'd like

Add an example with parameterized verify(), accept some signature there and check it against the key stored in a contract, describe how to sign a transaction for it.

Originally created by @roman-khimov on GitHub (Nov 19, 2025). ## Is your feature request related to a problem? Please describe. I'm always frustrated when people ask me of things that we don't have any example for. We do have examples for NEP-30 `verify()` (btw, NEP-30 should be mentioned everywhere appropriate), but it's parameter-less. The only case where we have some parameters is the Notary contract (https://github.com/nspcc-dev/neo-go/blob/8b0692e3aeb1288b2e1aa50eb1530b66b6f7c3a1/pkg/core/native/notary.go#L370), but it's native, so not really representative. ## Describe the solution you'd like Add an example with parameterized `verify()`, accept some signature there and check it against the key stored in a contract, describe how to sign a transaction for it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neo-go#1580
No description provided.