-
Notifications
You must be signed in to change notification settings - Fork 697
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
base: master
Are you sure you want to change the base?
Conversation
ensure!( | ||
bounty.value <= max_amount, | ||
native_amount <= max_amount, |
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.
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()); |
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.
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
.
part of #5500
Introduces the
asset_kind
parameter for a bounty and moves the payments processing from theCurrency
(only local transfers) trait toPay
(simpler alternative allowing cross-chain setups) trait.