Make neofscrypto.Signer be compatible with crypto.Signer #284

Open
opened 2025-12-28 18:07:40 +00:00 by sami · 0 comments
Owner

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

I'm always frustrated when I can't reuse user.Signer as crypto.Signer even though it does something very similar.

Describe the solution you'd like

Make its Sign() signature be the same as of crypto.Signer. The problem is that it's more complex.

Describe alternatives you've considered

Keep things as is.

Originally created by @roman-khimov on GitHub (Nov 22, 2025). ## Is your feature request related to a problem? Please describe. I'm always frustrated when I can't reuse `user.Signer` as `crypto.Signer` even though it does something very similar. ## Describe the solution you'd like Make its `Sign()` signature be the same as of `crypto.Signer`. The problem is that it's more complex. ## Describe alternatives you've considered Keep things as is.
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/neofs-sdk-go#284
No description provided.