Skip to content

Create class for PublicKey and Signature #989

@igormcoelho

Description

@igormcoelho

Not all of us are superhumans like Erik, so I propose to create simple classes PublicKey and Signature, for the rest of us, poor human beings 😂

Really, I still have many difficulties in understanding the usage of ECPoint, ECCurve, ECField, etc, just to handle a simple publickey. I often forget too which is the correct size of a signature for Neo secp256r1 (64 bytes, right?).
I think that, in the end, these classes are useful and necessary to represent the basic concepts of PublicKey and Signature on Neo. Signature is just a 64-bytearray today (because we are using secp256r1), but who knows tomorrow? Same for PublicKey, it's hard for me to simply handle it as a bytearray in compressed (33-bytes) or uncompressed format (which I don't know the size now...)

I think that this simplifies many things, and makes it much easier to handle this two fundamental concepts during the whole project.

Metadata

Metadata

Assignees

No one assigned

    Labels

    CosmeticType - Changes that improve user experience without affecting current functionality.DesignIssue state - Feature accepted but the solution requires a design before being implementedHousekeepingSmall enhancements that need to be done in order to keep the project organised

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions