Skip to content

Conversation

ironman0x7b2
Copy link

@ironman0x7b2 ironman0x7b2 commented Sep 17, 2025

The Sentinel team has created a new channel between Cosmos Hub and Sentinel for IBC ERC-20 token transfers. Relayers will be running on both channel pairs.

@JeremyParish69
Copy link
Contributor

This would be the first instance of a mainnet ibc connection registering an IBC channel with transfer on both ports. I believe some earlier assumptions were that there would only every be one trasnfer/transfer IBC channel per chain pair. Why not use the existing transfer/transfer IBC channel?

@ironman0x7b2
Copy link
Author

ironman0x7b2 commented Sep 17, 2025

@JeremyParish69 An initial version of the IBC ERC20 smart contract exists for current channels, but it has fixed metadata and doesn’t allow assigning a new contract. To address this, we deployed a new contract with customized metadata and an IMintableAndBurnable implementation. This required setting up a new channel between Sentinel and Cosmos Hub.

Ref: https://docs.skip.build/go/eureka/custom-erc20-integration

@JeremyParish69
Copy link
Contributor

@JeremyParish69 An initial version of the IBC ERC20 smart contract exists for current channels, but it has fixed metadata and doesn’t allow assigning a new contract. To address this, we deployed a new contract with customized metadata and an IMintableAndBurnable implementation. This required setting up a new channel between Sentinel and Cosmos Hub.

Ref: https://docs.skip.build/go/eureka/custom-erc20-integration

Ok thanks for explaining, I think I understand. I'm trying to double check with the Skip team, and also need to figure out how we're going to play this at the Registry since it's a first occurrence that was never supposed to be allowed.

@JeremyParish69
Copy link
Contributor

Btw, after talking with Skip, I believe this addition to be valid. This PR hasn't been forgotten--just working out the final details on how to handle it, but should be resolve soon, I believe.

@ironman0x7b2
Copy link
Author

Btw, after talking with Skip, I believe this addition to be valid. This PR hasn't been forgotten--just working out the final details on how to handle it, but should be resolve soon, I believe.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants