Explorer Submission
Submitting a project to the Reown Cloud Explorer is recommended but optional. You can still use Reown services without submitting your project. However, doing so ensures that your project is listed under WalletGuide and Cloud Explorer API.
Creating a New Project
-
Head over to cloud.reown.com and create a new project by clicking the “New Project” button in top right corner of the dashboard.
-
Give a suitable name to your project, select whether its an App or Wallet and click the “Create” button. (You can change this later)
Project Details
-
Go to the “WalletGuide” tab and fill in the details of your wallet.
| Field | Description | Required |
|---|---|---|
| Name | The name to display in the explorer | yes |
| Description | A short description explaining your project (dapp/wallet) | yes |
| Type | Whether your project is a dapp or a wallet | yes |
| Category | Appropriate category for your project. This field is dependent on the type of your project | yes |
| Homepage | The URL of your project | yes |
| Web App | The URL of your web app. This field is only applicable for dapps | yes |
| Chains | Chains supported by your project | yes |
| Logo | The logo of your project. Further requirements are provided in the explorer submission form | yes |
| Testing Instructions | Instructions on how to test your Reown Integration | yes |
| Download Links | Links to download your project (if applicable) | no |
| Mobile Linking | Required for mobile wallets targeting AppKit. Deep Link is recommended over Universal Link | no |
| Desktop Linking | Required for desktop wallets targeting AppKit. | no |
| Injected Wallet Identifiers | Required for injected wallets targeting AppKit. RDNS (from EIP-6963 metadata) is recommended over Provider Flags(Legacy) | no |
| Metadata | User-facing UI metadata for your project. Only Short Name is required. | no |
Project Submission
-
Once you’ve filled the applicable fields, click the “Submit” button to submit your project for review. Alternatively, you can save your changes and submit later. Additional information will be visible in the modal that appears after clicking the “Submit” button.
How do we test wallets?
In order to offer a great user experience in our APIs and SDKs every Cloud submission goes through a QA process to make sure that the integration of the WalletConnect protocol is working correctly.
The following list details our QA flow and how to reproduce it:
| Test Case | Steps | Expected Results |
|---|---|---|
| Set Up | 1. Download the wallet 2. Install the wallet app 3. Sign up for an account 4. Create one or more accounts | 1. N/A 2. The app is installed 3. I have an account 4. I have one or more accounts |
| Connect to dapp via web browser | 1. Open the Reown connection page appkit-lab.reown.com from a PC 2. Press “Connect Wallet” and select Reown. 3. Open the wallet app and scan QR code. 4. Accept the connection request. | 1. The app is set up correctly 2. A modal with wallet options appears 3. A QR code is shown and scanned 4. Connection established, wallet data displayed on site |
| Connect to dapp via mobile browser (Deep-link) | 1. Open appkit-lab.reown.com on mobile. 2. Select a default option (e.g., Wagmi for EVM chains), click “Custom Wallet,” enter wallet name and deep link, then add it. Press “Connect Wallet” and select the new wallet. 3. Accept connection request in the wallet app. | 1. N/A 2. A form appears to enter wallet data, new wallet option is visible. 3. User is redirected to the wallet app, sees a connection request, and successfully connects. On Android, user is redirected back to the website. |
| Switch chains - dapp side | 1. After connecting, click the modal button (top right of website). 2. Click the first button in the modal to switch chains. 3. Select a chain, close the modal, and press “Send Transaction.” | 1. Modal with account info appears. 2. A new view with supported chains appears. 3. The transaction request in the wallet shows the correct chain. |
| Switch Chains - wallet side (if supported) | 1. Check if wallet supports chain switching. If so, switch to a different chain. | 1. The chain change is reflected on the website. The first card displays the current chain ID. |
| Accounts Switching - wallet side | 1. Switch accounts in the wallet app. | 1. The account switch is reflected in the modal’s account view on the website. |
| Disconnect a wallet | 1. Press “Disconnect” in the Wallet App (if available). 2. Alternatively, press “Disconnect” from the dApp. | 1. The session disappears from both the dApp and Wallet App. 2. The session disappears from both the dApp and Wallet App. |
| Verify API | 1. Open malicious-app-verify-simulation.vercel.app. 2. Select a wallet-supported chain, press “Connect.” 3. Scan the QR code with the wallet. | 1. N/A 2. A QR code modal appears. 3. The wallet flags the site as malicious. |
Chain Specific
The following test cases only apply for wallets supporting a particular set of chains.
| Test Case | Steps | Expected Results |
|---|---|---|
| Supporting personal_sign | 1. Connect the wallet. 2. Press the “Sign Message” button. 3. Accept the signature request on the wallet. | 1. N/A 2. A modal should popup on the wallet app requesting a signature. 3. Once accepted and signed, the hash should show up on the website. |
| Supporting eth_signTypedData_v4 | 1. Connect the wallet. 2. Press the “Sign Typed Data” button. 3. Accept the signature request on the wallet. | 1. N/A 2. A modal should popup on the wallet app requesting a signature. 3. Once accepted and signed, the hash should show up on the website. |
| Supporting eth_sendTransaction | 1. Connect the wallet. 2. Press the “Send Transaction” button. | 1. N/A 2. A modal should popup on the wallet app requesting a signature. |
| Test Case | Steps | Expected Results |
|---|---|---|
| Supporting personal_sign | 1. Connect the wallet. 2. Press the “Sign Message” button. 3. Accept the signature request on the wallet. | 1. N/A 2. A modal should popup on the wallet app requesting a signature. 3. Once accepted and signed, the hash should show up on the website. |
| Supporting eth_signTypedData_v4 | 1. Connect the wallet. 2. Press the “Sign Typed Data” button. 3. Accept the signature request on the wallet. | 1. N/A 2. A modal should popup on the wallet app requesting a signature. 3. Once accepted and signed, the hash should show up on the website. |
| Supporting eth_sendTransaction | 1. Connect the wallet. 2. Press the “Send Transaction” button. | 1. N/A 2. A modal should popup on the wallet app requesting a signature. |
| Test Case | Steps | Expected Results |
|---|---|---|
| Supporting solana_signMessage | 1. Connect the wallet to appkit-lab.reown.com/library/solana. 2. Press the “Sign Message” button. 3. Accept the signature request on the wallet. | 1. N/A. 2. A modal should pop up on the wallet app requesting a signature. 3. Once accepted and signed, the hash should show up on the website. |
| Supporting solana_signTransaction | 1. Connect the wallet to appkit-lab.reown.com/library/solana. 2. Press the “Sign Transaction” button. 3. Accept the signature request on the wallet. | 1. N/A. 2. A modal should pop up on the wallet app requesting a signature. 3. Once accepted and signed, the hash should show up on the website. |
| Supporting v0 Transactions | 1. Connect the wallet to appkit-lab.reown.com/library/solana. 2. Press the “Sign Versioned Transaction” button. 3. Accept the signature request on the wallet. | 1. N/A. 2. A modal should pop up on the wallet app requesting a signature. 3. Once accepted and signed, the hash should show up on the website. |
What’s Next?
Now depending on whether or not your submission met all parameters, you will receive an email from the Reown team with the status of your submission. This change will also be reflected with more directions in the “Explorer” tab of your project. If your submission was not accepted, you can make the necessary changes and resubmit your project for review. The reason for rejection will be mentioned in the email and in the “Explorer” tab of your project.
In case of any questions, feel free to ask on Github Discussions
Was this page helpful?