Summary
Production wallet UIs in liberdus.github.io should use the shared liberdus-wallet-module instead of legacy MetaMask-only or bespoke wallet code.
Already deployed here
| Folder |
Source repo |
Update script |
Status |
farm/ |
lib-lp-staking-frontend |
./update-farm.sh |
Done |
bsc-bridge/ |
liberdus-bsc-bridge-ui |
./update-bsc-bridge.sh |
Done |
token/ |
liberdus-token-ui |
./update-token-client.sh |
Done |
Still needs migration (production folders)
| Folder |
Current wallet stack |
Source repo |
Update script |
lock/ |
MetaMask-only MetaMaskConnector |
token-lock-ui |
./update-lock.sh |
otc/ |
Custom WalletManager via window.ethereum |
otc-web-client-1 |
./update-otc-client.sh |
rewards/ |
Custom EIP-6963 wallet code in js/shared/wallet.js |
liberdus-airdrop/frontend |
./update-rewards.sh |
Related follow-up (separate deploy path): farm/migration/ still uses the legacy MetaMask wallet manager and is synced via ./update-farm-migration.sh.
Blockers
This github.io work is blocked upstream for all three folders. Two already have open integration PRs that need review feedback addressed and merged before we can sync to Pages:
rewards/ — blocked on source PR
lock/ — blocked on source PR
- PR: Liberdus/token-lock-ui#9 — feat: import liberdus wallet module (open)
- Replaces MetaMask-only integration with shared wallet core
- Review feedback pending: wallet picker flow for multi-wallet installs, local disconnect / session cleanup, and related module session handling — see inline review threads on the PR
- After merge: run
./update-lock.sh to copy token-lock-ui → lock/
- Consider updating
update-lock.sh to init/check vendor/liberdus-wallet-module submodules (similar to update-token-client.sh)
otc/ — blocked on source work (no open wallet-module PR yet)
- Still uses legacy wallet code in
otc/js/config.js
- No wallet-module integration PR identified yet in the OTC source repo (
otc-web-client-1 / otc-web-client)
- Needs source-repo integration work before
./update-otc-client.sh can deploy the module to otc/
Acceptance criteria
Notes
- Test/staging counterparts (
locktest, otctest, rewards-test) can be updated separately after production paths are validated.
- Submodule bump/maintenance scripts (
scripts/bump-wallet-module.sh, docs/SUBMODULE.md) should be mirrored from the token/bridge/farm pattern where applicable.
Summary
Production wallet UIs in
liberdus.github.ioshould use the sharedliberdus-wallet-moduleinstead of legacy MetaMask-only or bespoke wallet code.Already deployed here
farm/lib-lp-staking-frontend./update-farm.shbsc-bridge/liberdus-bsc-bridge-ui./update-bsc-bridge.shtoken/liberdus-token-ui./update-token-client.shStill needs migration (production folders)
lock/MetaMaskConnectortoken-lock-ui./update-lock.shotc/WalletManagerviawindow.ethereumotc-web-client-1./update-otc-client.shrewards/js/shared/wallet.jsliberdus-airdrop/frontend./update-rewards.shRelated follow-up (separate deploy path):
farm/migration/still uses the legacy MetaMask wallet manager and is synced via./update-farm-migration.sh.Blockers
This github.io work is blocked upstream for all three folders. Two already have open integration PRs that need review feedback addressed and merged before we can sync to Pages:
rewards/— blocked on source PR./update-rewards.shto copyliberdus-airdrop/frontend→rewards/lock/— blocked on source PR./update-lock.shto copytoken-lock-ui→lock/update-lock.shto init/checkvendor/liberdus-wallet-modulesubmodules (similar toupdate-token-client.sh)otc/— blocked on source work (no open wallet-module PR yet)otc/js/config.jsotc-web-client-1/otc-web-client)./update-otc-client.shcan deploy the module tootc/Acceptance criteria
lockandrewardsotc./update-lock.sh,./update-otc-client.sh, and./update-rewards.shrun successfully against updated source reposlock/,otc/, andrewards/containvendor/liberdus-wallet-module/(or equivalent vendored copy) and usecreateWalletCore/ shared module session APIsNotes
locktest,otctest,rewards-test) can be updated separately after production paths are validated.scripts/bump-wallet-module.sh,docs/SUBMODULE.md) should be mirrored from the token/bridge/farm pattern where applicable.