You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The smart_rollup_originate operation now also takes an optional whitelist of public key hashes. This whitelist cannot be used yet (the sc_rollup.private_enable flag has to be set to true). (MR !9401)
This is from oxford2 changelog, we've added local forging support but didn't update our contractAPI. But I just checked private_enable is now true and activated on mainnet. We should also support user who wants to use smart_rollup_originate with the optional whitelist param.
The work includes updating rpc type SmartRollupOriginateParams to the entire contractAPI data flow(prepare, estimate), making sure whitelist param is carrying over to be forged, signed and injected.
Would be good to update unit/integration test and doc with the optional param, too
The text was updated successfully, but these errors were encountered:
This is from oxford2 changelog, we've added local forging support but didn't update our contractAPI. But I just checked private_enable is now true and activated on mainnet. We should also support user who wants to use smart_rollup_originate with the optional whitelist param.
The work includes updating rpc type
SmartRollupOriginateParams
to the entire contractAPI data flow(prepare, estimate), making sure whitelist param is carrying over to be forged, signed and injected.Would be good to update unit/integration test and doc with the optional param, too
The text was updated successfully, but these errors were encountered: