Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define contract spec for Hash; adds instruction for XDR-gen #361

Merged
merged 2 commits into from
Apr 15, 2024

Conversation

jayz22
Copy link
Contributor

@jayz22 jayz22 commented Apr 12, 2024

What

Picks up:
stellar/stellar-xdr#182
stellar/stellar-xdr#183

Also adds the instruction for how to regenerate from XDR changes.

Why

[TODO: Why this change is being made. Include any context required to understand the why.]

Known limitations

[TODO or N/A]

@jayz22 jayz22 changed the title Define contract spec for Hash Define contract spec for Hash; adds instruction for XDR-gen Apr 15, 2024
@jayz22 jayz22 marked this pull request as ready for review April 15, 2024 21:07
@dmkozh dmkozh added this pull request to the merge queue Apr 15, 2024
Merged via the queue into stellar:main with commit d013877 Apr 15, 2024
10 checks passed
github-merge-queue bot pushed a commit to stellar/rs-soroban-env that referenced this pull request Apr 16, 2024
### What

Picks up stellar/rs-stellar-xdr#361 

### Why

[TODO: Why this change is being made. Include any context required to
understand the why.]

### Known limitations

[TODO or N/A]
github-merge-queue bot pushed a commit to stellar/rs-soroban-sdk that referenced this pull request Apr 23, 2024
### What

Add support for secp256r1 signature verification (picking up env changes
stellar/rs-soroban-env#1376).

And adapts the existing `Crypto` module by split the cryptographic
functions into two sets:
- `Crypto`: standard, recommended set of cryptographic functions. This
includes `secp256k1_recover` and `secp256r1_verify` taking the full
`message: Bytes` as input and performs hashing underneath.
- `CryptoHazmat`: hazardous material. Contains low-level, unsecure if
used incorrectly functions including `secp256k1_recover_prehash` and
`secp256r1_verify_prehash`, taking a `message_hash: BytesN<32>` as
input.

Design rationales were discussed in the env PR (started on
stellar/rs-soroban-env#1376 (comment)
and onward).

XDR changes associated with the new contract spec:
stellar/stellar-xdr#182,
stellar/stellar-xdr#183
rs-xdr: stellar/rs-stellar-xdr#361

End-to-end with secp256r1 account contract:
stellar/rs-soroban-env#1402

### Why


[TODO: Why this change is being made. Include any context required to
understand the why.]

### Known limitations

[TODO or N/A]

---------

Co-authored-by: Leigh McCulloch <351529+leighmcculloch@users.noreply.github.com>
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.

None yet

2 participants