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
{{ message }}
This repository was archived by the owner on Apr 25, 2026. It is now read-only.
We want to "rescue tokens" by signature on the Substrate side which can come about using a handler or potentially not. This task should include investigate into the potential routes we can take given Substrate's capabilities.
Overview
We want to "rescue tokens" by signature on the Substrate side which can come about using a handler or potentially not. This task should include investigate into the potential routes we can take given Substrate's capabilities.
Details
There is already a
treasuryaccount inprotocol-substrateand the fees are being sent there:https://github.com/webb-tools/protocol-substrate/blob/main/pallets/token-wrapper/src/lib.rs#L105
https://github.com/webb-tools/protocol-substrate/blob/main/pallets/token-wrapper/src/lib.rs#L291
So we don't need to implement a separate treasury pallet. What we can instead do is the following:
rescue_tokensfunction to thetoken-wrapperpallet. This function signature forrescue_tokensshould look something like:execute_rescue_tokensfunction to thetoken-wrapper-handlerpallet.rescue_tokensvia thesignature-bridge.