-
Notifications
You must be signed in to change notification settings - Fork 116
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
2776 smart rollup origination with whitelist #2781
2776 smart rollup origination with whitelist #2781
Conversation
…itelist in localForger re #2776
New packages have been deployed to the preview repository at https://npm.preview.tezostaquito.io/. Published packages:
|
…76-smartRollupOrigination-with-whitelist
@@ -63,6 +64,7 @@ export const decoders: { [key: string]: Decoder } = { | |||
[CODEC.ZARITH]: zarithDecoder, | |||
[CODEC.PUBLIC_KEY]: publicKeyDecoder, | |||
[CODEC.PKH]: pkhDecoder, | |||
[CODEC.PKH_ARR]: pkhsDecoder, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would you consider updating this to PKH_ARRAY or PKH_LIST instead for clarity?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At the time, trying to be consistent with existing PROPOSAL_ARR
but I like your suggestions better
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if the decoder going with pkhArrayDecoder will update this as PKH_ARRAY.
@@ -57,6 +57,18 @@ export const pkhDecoder = (val: Uint8ArrayConsumer) => { | |||
} | |||
}; | |||
|
|||
export const pkhsDecoder = (val: Uint8ArrayConsumer) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what would the s
be in this case in pkhs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as the other comment inherit the naming consistency from proposalsDecoder
, I think s
means plural
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think for proposals it's because the operation itself is called Proposals
instead of proposal
.
I think we can remove the S
in this case, but that's just personal preference.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are proposalDecoder
and proposalsDecoder
. There is already pkhDecoder
will we consider pkhArrayDecoder
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah let's do pkhArrayDecoder then, seems more informative than just using s
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good work
* 2762 oxford2 branch configuration (#2764) * ci: initial configuration of oxford2 branch re #2762 * docs: replaced mumbai ref with oxford2 of rpc_nodes and wallet_api on webstie * docs: add oxfordnet to wallet_api in next version of website * ci: update ci script origiante-known-contracts command * remove tx rollups references in taquito (#2770) * remove tx rollups references in taquito * updated unit test * removed remaining tx rollup references * 2596 oxford2 update rpc types (#2772) * feat: updated rpc endpoint changes for oxford2 re #2596 * fix: fix auto-merge mistake by removing tx ref * test: fix integration test of pendingOperations * test: removed unnecessory import * refactor: imporved ux of rpc endpoint of blockOption version * 2597 remove proof (#2774) * removed references to originationProof * trigger checks * trigger checks * test commit * adjusted more tests * removed remaining origination proof artifacts * updated smart rollup docs * adjusted estimates * 2776 smart rollup origination with whitelist (#2781) * removed references to originationProof * trigger checks * trigger checks * test commit * adjusted more tests * removed remaining origination proof artifacts * updated smart rollup docs * adjusted estimates * feat: supported smartRollupOriginate with new pvmKind and property whitelist in localForger re #2776 * refactor: addressed comments of naming for clarity * test: updated contract-estimation-tests-spec.ts assertions --------- Co-authored-by: Davis Sawali <[email protected]> * 2599 oxford2 supports attestation (#2775) * feat: supports attesation along side endorsement re #2599 * feat: the rest of files of supports attesation along side endorsement * test: fix protocol logic in integration-tests/rpc-nodes.spec.ts * test: addressed pr comments of naming * test: updated contract-estimation-tests.spec.ts assertions * 2653 oxford2 reintroduce timelock (#2780) * test: added local-forging timelock test case with chest, chest_key and OPEN_CHEST re #2653 * test: added integration test originating with chest&chest_key in storage (chest_key unfinished) * test: updated chestKeyValue in integration-tests re #2653 * test: removed unneeded comment * test: address comment to reduce timeout risk * Oxford2 cleanup (#2791) * docs: updated to oxford references whereever fits * feat: updated rpc types and doc changes * ci: removed nairobi and replace mondaynet with weeklynet * fix: replaced modanynet as weeklynet * ci: comment out oxfordbox tests until oxford2 flextesa image releases * docs: address typedoc comments * removed newline * chore(releng) bump version to 19.0.0-beta-RC.0 * chore: satisfy lerna * chore(releng) bump version to 19.0.0 --------- Co-authored-by: Davis Sawali <[email protected]>
supporting whitelist property and new PVMkind riscv of smartRollupOrigination in localForging
closes #2776
Thank you for your contribution to Taquito.
Before submitting this PR, please make sure:
In this PR, please also make sure:
closes #TICKETNUMBER
in the description box (when applicable)Release Note Draft Snippet
If relevant, please write a summary of your change that will be suitable for
inclusion in the Release Notes for the next Taquito release.