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

Multi-Asset and Cross-Chain Bounties #6189

Draft
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

muharem
Copy link
Contributor

@muharem muharem commented Oct 23, 2024

part of #5500

Introduces the asset_kind parameter for a bounty and moves the payments processing from the Currency (only local transfers) trait to Pay (simpler alternative allowing cross-chain setups) trait.

@davidk-pt davidk-pt added the T1-FRAME This PR/Issue is related to core FRAME, the framework. label Nov 14, 2024
ensure!(
bounty.value <= max_amount,
native_amount <= max_amount,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this will needs to be wrapped into the context. check the treasury spend call for reference

)
.map_err(|_| Error::<T, I>::FundingError)?;
*payment_status = PaymentState::Attempted { id };
return Ok(Pays::No.into());
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the caller should still pay. but you sill needs DispatchResultWithPostInfo type because this call in most cases will have bigger worth case weight than actual. the payout have two payments to process, the funding and the cancelation only one. I would process all of them with the same calls, process_payment and check_payment_status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T1-FRAME This PR/Issue is related to core FRAME, the framework.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants