feat: initial draft of secp256r1-verify SIP

[brice-stacks]

No description provided.

[jcnelson]

Feel free to also change the README to link to this SIP document. Thanks!

[brice-stacks]

Feel free to also change the README to link to this SIP document. Thanks!

Sounds good. I'll do that once this is assigned a number.

[wileyj]

Looks good. before merging, i would like to see a PR or commit for the docs changes.

[Hero-Gamer]

Can we get it posted on Stacks Forum too just for visibility?
(I think every SIP proposal should have a post on Stacks Forum, if that can be the official new SIP-000 process, can discuss separately but)

[brice-stacks]

Looks good. before merging, i would like to see a PR or commit for the docs changes.

stacks-network/stacks-core#6763

[wileyj]

Looks good. before merging, i would like to see a PR or commit for the docs changes.

stacks-network/stacks-core#6763

Thanks, but I meant only for the documentation changes. That PR seems to address the unintended behaviour, but not the documentation updates proposed here.

[brice-stacks]

Thanks, but I meant only for the documentation changes. That PR seems to address the unintended behaviour, but not the documentation updates proposed here.

The docs change is in there (see clarity/src/vm/docs/mod.rs). Or did you mean a PR to the docs site?

[wileyj]

Thanks, but I meant only for the documentation changes. That PR seems to address the unintended behaviour, but not the documentation updates proposed here.

The docs change is in there (see clarity/src/vm/docs/mod.rs). Or did you mean a PR to the docs site?

ahh, i see it now - thanks!
edit - since that PR also addresses the fix as well as the docs update proposed here, i think it's fine to leave as NA

[wileyj]

Suggested change

	SIP Number:
	SIP Number: 035

@rafaelcr @314159265359879 @jiga i didn't see any other SIP using this number, so i'm pre-emptively proposing it here.