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
Relates to #1093
Add a Marker reflection endpoint so that the marker can be copied to destination chains/zones via ICA.
Problem Definition
Right now ibc denoms cannot be created as Marker.(Other than via Gov Proposals)
We can open up the regex but then it may lead to confusion where users can just create ibc denoms with less than optimal configs (A huge risk if they enable mint/burn on said ibc marker, either by accident or maliciously etc).
A more elegant solution would be to create the marker over ICA message with the user(any user) initiating the action just paying the fees, the rest being done by marker module --> relayer --> ica handler on destination chain --> ack back to source chain.
Proposal
Leverage ICA to reflect markers over to destination chain/zone
Create an endpoint to reflect the marker over the destination chain.
This msg_server/cli endpoint will take in the ibc denom, so the marker module will be able to decipher what is the destination chain, what channel/connection to use to ICA it over. (DEV TASK): Create reflect marker endpoint for ica #1180
The ^^ marker module code will make sure that the denom exists on the source chain and has not already been ICA'ed over.
The ^^ marker module code will copy the transfer permissions only in the ICA payload(A custom message called ICAReflectMarkerMsg (change name as needed).(No Minting/Burning will be allowed on the destination chain marker for obvious reasons), Supply of destination marker will not be fixed for obvious reasons. Marker Type should be copied over as is.
The assumption is here that the permissions should only be changed on source chain and then ICA'ed over.
The ^^ marker module code will make sure the base address remains same on destination chain(Derived from denom)
An assumption is to be made that a relayer will be available to relay the ICA message
Marker module will receive any Ack from the destination chain for success or failure and store it in the marker state as needed. (DEV TASK): Handle ICA responses #1190
The destination chain should be able to process the ICA packer and create the marker on that chain.
The destination chain ack back success or failure back to the source chain.
Benefits: solves #1093 needed by Figure Equity Solutions
Disadvantages: ICA messages being enabled, more complexity in the system, a reliance on relayers.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary
Relates to #1093
Add a Marker reflection endpoint so that the marker can be copied to destination chains/zones via ICA.
Problem Definition
Right now ibc denoms cannot be created as Marker.(Other than via Gov Proposals)
We can open up the regex but then it may lead to confusion where users can just create ibc denoms with less than optimal configs (A huge risk if they enable mint/burn on said ibc marker, either by accident or maliciously etc).
A more elegant solution would be to create the marker over ICA message with the user(any user) initiating the action just paying the fees, the rest being done by marker module --> relayer --> ica handler on destination chain --> ack back to source chain.
Proposal
Leverage ICA to reflect markers over to destination chain/zone
This msg_server/cli endpoint will take in the
ibc
denom, so the marker module will be able to decipher what is the destination chain, what channel/connection to use to ICA it over. (DEV TASK): Create reflect marker endpoint for ica #1180ICAReflectMarkerMsg
(change name as needed).(No Minting/Burning will be allowed on the destination chain marker for obvious reasons), Supply of destination marker will not be fixed for obvious reasons.Marker Type
should be copied over as is.The assumption is here that the permissions should only be changed on source chain and then ICA'ed over.
Benefits: solves #1093 needed by Figure Equity Solutions
Disadvantages: ICA messages being enabled, more complexity in the system, a reliance on relayers.
For Admin Use
The text was updated successfully, but these errors were encountered: