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

docs: update documentation for ToRistrettoPoint opcode #113

Merged
merged 1 commit into from
Dec 6, 2023

Conversation

AaronFeickert
Copy link
Contributor

Description

Updates the documentation for the ToRistrettoPoint opcode.

Motivation and Context

This opcode now requires a canonical scalar parsing. Further, the existing documentation was somewhat unclear. This PR updates the documentation for clarity and correctness.

How Has This Been Tested?

It renders as expected.

SWvheerden pushed a commit to tari-project/tari that referenced this pull request Nov 21, 2023
Description
---
Updates the handling of the `ToRistrettoPoint` opcode.

Closes #5818.

Motivation and Context
---
The `ToRistrettoPoint` opcode now requires that stack input be the
canonical encoding of a Ristretto secret key. This PR updates the opcode
documentation and adds a test for proper handling of invalid encoding.
It also corrects the error returned on invalid stack input.

There is a [separate PR](tari-project/rfcs#113)
that updates the RFC documentation.

How Has This Been Tested?
---
Existing tests pass. A modified test passes.

What process can a PR reviewer use to test or verify this change?
---
Check that the updated documentation reflects the opcode handling. Check
that the modified test correctly detects invalid input. Check that the
error returned on invalid input is correct.
sdbondi pushed a commit to sdbondi/tari that referenced this pull request Nov 27, 2023
Description
---
Updates the handling of the `ToRistrettoPoint` opcode.

Closes tari-project#5818.

Motivation and Context
---
The `ToRistrettoPoint` opcode now requires that stack input be the
canonical encoding of a Ristretto secret key. This PR updates the opcode
documentation and adds a test for proper handling of invalid encoding.
It also corrects the error returned on invalid stack input.

There is a [separate PR](tari-project/rfcs#113)
that updates the RFC documentation.

How Has This Been Tested?
---
Existing tests pass. A modified test passes.

What process can a PR reviewer use to test or verify this change?
---
Check that the updated documentation reflects the opcode handling. Check
that the modified test correctly detects invalid input. Check that the
error returned on invalid input is correct.
Copy link
Contributor

@CjS77 CjS77 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a line in the change log at the bottom of the file.

@AaronFeickert
Copy link
Contributor Author

Please add a line in the change log at the bottom of the file.

Done!

@CjS77 CjS77 merged commit 845e7e5 into tari-project:main Dec 6, 2023
2 checks passed
@AaronFeickert AaronFeickert deleted the update-point-opcode branch December 6, 2023 12:58
CjS77 pushed a commit that referenced this pull request Dec 19, 2023
Description
---
Updates the documentation for the `ToRistrettoPoint` opcode.

Motivation and Context
---
This opcode now requires a canonical scalar parsing. Further, the
existing documentation was somewhat unclear. This PR updates the
documentation for clarity and correctness.

How Has This Been Tested?
---
It renders as expected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants