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

Double DEFAULT_PROOF_SIZE to support staking unbond via xcm transactor #2320

Merged
merged 1 commit into from
May 30, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions primitives/xcm/src/ethereum_xcm.rs
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,10 @@ use sp_std::vec::Vec;
// Defensively we increase this value to allow UMP fragments through xcm-transactor to prepare our
// runtime for a relay upgrade where the xcm instruction weights are not ZERO hardcoded. If that
// happens stuff will break in our side.
// Rationale behind the value: e.g. staking unbond will go above 32kb and thus
// Rationale behind the value: e.g. staking unbond will go above 64kb and thus
// required_weight_at_most must be below overall weight but still above whatever value we decide to
// set. For this reason we set here a value that makes sense for the overall weight.
pub const DEFAULT_PROOF_SIZE: u64 = 128 * 1024;
pub const DEFAULT_PROOF_SIZE: u64 = 256 * 1024;

/// Max. allowed size of 65_536 bytes.
pub const MAX_ETHEREUM_XCM_INPUT_SIZE: u32 = 2u32.pow(16);
Expand Down