-
Notifications
You must be signed in to change notification settings - Fork 2
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
The Omnilock of ForceBridge #532
Comments
Is the issue asking the explorer team to add the outdated Omnilock to its known scripts list? |
Yes, this script is used by several dapps, and it was declared an omnilock, but in fact it's a customized one, so it would be better to be annotated. |
The PR will be merged first, the link to the code will be added after the Chinese New Year. The link to the code should point to the git commit which was deployed on the chain. |
History
The Yokai Swap launched in 2022, but at that time, the Force Bridge was using the PW-Lock, which was not supported by Yokai Swap. But at that time, the Omnilock hadn't launched in Mainnet. So we just deployed the Omnilock from the source code which had not been released. And the migration from PW-Lock was also launched for this.
And the Yokai Swap and the Force Bridge are still using this version of Omnilock now.
Dependency
Refference
https://forcebridge.com
https://github.com/homura/pw-up/blob/master/src/lib/PwUp.ts
https://www.yokaiswap.com/bridge/deposit
https://pw-up.vercel.app/
https://github.com/nervosnetwork/force-bridge/blob/main/docs/asset-migration-guide.md
The text was updated successfully, but these errors were encountered: