feat: extend auxData to 96 bytes #652
Draft
+65
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this pull request do? Explain your changes. (required)
Allow a 64–96 byte
auxDatafield to support additional on-chain metadata. This was part of the protocol work to distinguish different job types on-chain (see this tech spec: https://www.notion.so/On-Chain-Ticket-Job-Type-Distinction-2bf660222d08814d89b1fa7221ad3291).This proposal was originally drafted as a protocol change that would not materially increase gas costs or code complexity. However, given the new requirement to also encode payment clearinghouse information on-chain, please review this approach with @mehrdadmms, @yondonfu, and @j0sh to confirm whether this is still the preferred solution.
Specific updates (required)
How did you test each of these updates (required)
Not fully tested, however made sure tests pass.
Does this pull request close any open issues?
Checklist:
yarn testpass