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
Hi team 👋 — I'm writing on behalf of the DeBox team.
What DeBox is
DeBox is a Web3 social app with a built-in DApp browser, available on iOS and Android. When a dapp is opened inside DeBox, our provider is injected as window.ethereum (flagged isDeBox) and announced over EIP-6963.
What we'd like to contribute
A deboxWallet connector following the existing trustWallet pattern — injected connector when DeBox is detected, WalletConnect + debox://wc?uri= deep link otherwise.
The branch is ready: 9 files, changeset included, pnpm lint and pnpm test both green. Happy to open the PR as soon as you give the go-ahead (per CONTRIBUTING, asking first).
While testing we hit something that seems to contradict the docs, so sharing in case it's helpful to you or to other wallet teams.
In #2461 it's stated that "EIP-6963 provider discovery on mobile will work if the user accesses your dApp inside a mobile wallet's in-app browser". On a real device we found discovery does work, but the wallet never reaches the modal:
wagmi auto-reconnects to the EIP-6963 connector, so discovery is working
The connect modal still doesn't list DeBox
Same injected script, same page — switching only the UA to desktop makes "Installed → DeBox" appear
This lines up with MobileOptions.tsx filtering on isRainbowKitConnector, which #2497 explains well. So the behaviour is intentional — it's just that #2461 reads as though the in-app-browser case is covered, which may confuse other wallet teams running into the same thing.
We're not asking you to change that filter for us — the connector above works within the current design. But if supporting EIP-6963 in the mobile modal for in-app browsers is ever on the table, we'd be glad to contribute the PR and provide test devices.
Question
Is the wallet addition welcome? Anything you'd like included beyond what's in #2652 (extra locales, a particular icon format, etc.)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi team 👋 — I'm writing on behalf of the DeBox team.
What DeBox is
DeBox is a Web3 social app with a built-in DApp browser, available on iOS and Android. When a dapp is opened inside DeBox, our provider is injected as
window.ethereum(flaggedisDeBox) and announced over EIP-6963.What we'd like to contribute
A
deboxWalletconnector following the existingtrustWalletpattern — injected connector when DeBox is detected, WalletConnect +debox://wc?uri=deep link otherwise.The branch is ready: 9 files, changeset included,
pnpm lintandpnpm testboth green. Happy to open the PR as soon as you give the go-ahead (per CONTRIBUTING, asking first).Branch:
PonyDevAI:feat/debox-walletOne data point that may be useful to you
While testing we hit something that seems to contradict the docs, so sharing in case it's helpful to you or to other wallet teams.
In #2461 it's stated that "EIP-6963 provider discovery on mobile will work if the user accesses your dApp inside a mobile wallet's in-app browser". On a real device we found discovery does work, but the wallet never reaches the modal:
rainbowkit.comEIP-6963 initialized,mountMode: immediate)This lines up with
MobileOptions.tsxfiltering onisRainbowKitConnector, which #2497 explains well. So the behaviour is intentional — it's just that #2461 reads as though the in-app-browser case is covered, which may confuse other wallet teams running into the same thing.We're not asking you to change that filter for us — the connector above works within the current design. But if supporting EIP-6963 in the mobile modal for in-app browsers is ever on the table, we'd be glad to contribute the PR and provide test devices.
Question
Is the wallet addition welcome? Anything you'd like included beyond what's in #2652 (extra locales, a particular icon format, etc.)?
All reactions