Document how to deploy contracts using aztec.js
#1608
Assignees
Comments
This was referenced Aug 17, 2023
Closed
spalladino
added a commit
that referenced
this issue
Aug 17, 2023
Fixes #1591 **Note**: I've decided to create a [separate issue ](#1608 documenting how to deploy the contracts using `aztec.js`. I've linked it to the big docs issue. # Checklist: Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge. - [ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag. - [ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code. - [ ] Every change is related to the PR description. - [ ] I have [linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) this pull request to relevant issues (if any exist). --------- Co-authored-by: Santiago Palladino <[email protected]>
AztecBot
pushed a commit
to AztecProtocol/docs
that referenced
this issue
Aug 17, 2023
Fixes #1591 **Note**: I've decided to create a [separate issue ](AztecProtocol/aztec-packages#1608 documenting how to deploy the contracts using `aztec.js`. I've linked it to the big docs issue. # Checklist: Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge. - [ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag. - [ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code. - [ ] Every change is related to the PR description. - [ ] I have [linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) this pull request to relevant issues (if any exist). --------- Co-authored-by: Santiago Palladino <[email protected]>
|
Gonna pick this up! |
rahul-kothari
added a commit
that referenced
this issue
Aug 22, 2023
) Fix #1608 --------- Co-authored-by: Jan Beneš <[email protected]>
codygunton
pushed a commit
that referenced
this issue
Jan 23, 2024
…rmula (#1608) * Fixed bigfield bugs: 1) The basic CRT formula bug (quick and dirty fix) didn't allow for small values on division (a*b < r) 2) Limb product maximum value computation used uint256_t resulting in overflows 3) Joined range checks can't handle the maximum range values, so in those cases we need to use separate range checks 4) Lots of issues with constant bigfield elements, where we try to access non-existing context 5) assert_is_in_field borrowing logic was wrong 6) 1 miscellaneous funny bug, where evaluate_square_add always expected an even number of elements to add, and because of that did a buffer overread * Minor fixes * Fixed Guido's bigfield conditional negate bug and added limb << operator * Fixed some ASSERTs that triggered Guido's fuzzer. * Removed misguided ASSERT. * Fixing picking wrong modulus for counting carry range * Removed formula dirty fix and test * Deleted old comments * Minor typos are fixed Co-authored-by: arijitdutta67 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've already documented how to deploy contracts using aztec-cli in this PR. Document how to do the same thing using
aztec.js. Use the tab functionality of docusaurus to achieve this look:Note: Don't miss the
Syncing tab choicessection.The text was updated successfully, but these errors were encountered: