Navigation Menu wallets-list Code Pull requests 0 stars 169 forks 0 watching 1 Branch 0 Tags Activity Public repository · Forked from ton-blockchain/wallets-list Red03Red03547/wallets-list This branch is up to date with ton-blockchain/wallets-list:main.

.github/workflows/comment.md

@@ -0,0 +1,63 @@
+# TON Connect Integration Review Process
+
+Thank you for contributing to the TON ecosystem\! To ensure a seamless experience for users and maintain high-quality integrations, we review all wallet submissions thoroughly. Below is an overview of our process:  
+---
+
+### **Why We Audit Integrations**
+
+We audit integrations to:
+
+* Ensure the **best possible experience** for TON ecosystem users.  
+* Confirm that TON Connect is implemented securely, reliably, and in alignment with our specifications.
+
+---
+
+### **Integration & Audit Process**
+
+Follow these steps to submit your wallet for inclusion in the TON Connect list:
+
+1. **Review Documentation**:  
+   * Study our [**TON Connect Documentation & Specifications**](https://docs.google.com/document/d/1Z2dWpn-p7net3fE1gBJlyNUeTN5nZaUC2g7lUt4t2TY/edit?usp=sharing).  
+   * Implement TON Connect in your wallet using the guidelines provided.  
+2. **Self-Test Using Checklist**:  
+   * Validate your integration against our [**Checklist of Tests**](https://www.notion.so/theopenplatform/Checklist-of-tests-1571e095988680828da8c2d57e5bf567).  
+   * Ensure all functionalities (e.g., connection, transaction signing, error handling) work as expected.  
+3. **Review Wallet Manifest Requirements**:  
+   * Familiarize yourself with the [**wallet manifest format and requirements**](https://github.com/ton-blockchain/wallets-list/?tab=readme-ov-file#entry-format).  
+   * Ensure your wallet manifest follows the specified format with all required fields.  
+4. **Submit a PR**:  
+   * Open a Pull Request (PR) to add your wallet to the TON Connect registry.  
+5. **Notify Us**:  
+   * Reach out to [**@kawaiinya**](https://t.me/kawaiinya) on Telegram to confirm your submission.  
+   * We’ll create a dedicated Telegram chat to coordinate the audit.
+
+---
+
+### **Audit Process Details**
+
+* **Initial Review**:  
+  * Our team will schedule an audit and share a report.  
+  * If no issues are found, your PR will be merged promptly.  
+* **Revisions & Re-Audits**:  
+  * If issues arise, we’ll provide feedback. Once fixes are implemented, we’ll re-audit.  
+  * This cycle continues until all requirements are met.
+
+---
+
+### **Audit Timeline**
+
+* **Typical Duration**: \~3 working days (*after the audit begins*).  
+* **Current Backlog**: Due to high demand (15+ wallets in the queue), audits may be delayed.  
+  * We appreciate your patience and will notify you once your audit is scheduled.
+
+---
+
+### **Resources**
+
+* [**TON Connect Specifications**](https://docs.google.com/document/d/1Z2dWpn-p7net3fE1gBJlyNUeTN5nZaUC2g7lUt4t2TY/edit?usp=sharing)  
+* [**Integration Checklist**](https://www.notion.so/theopenplatform/Checklist-of-tests-1571e095988680828da8c2d57e5bf567)
+
+---
+
+We’re excited to collaborate with you and welcome your wallet to the TON ecosystem\! 🚀  
+For questions, please contact [**@kawaiinya**](https://t.me/kawaiinya) on Telegram.

.github/workflows/pr-comment.yml

@@ -0,0 +1,20 @@
+name: PR Auto Comment
+
+on:
+  pull_request_target:
+    types: [opened]
+
+permissions: 
+   pull-requests: write
+
+jobs:
+  add-comment:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+
+      - name: Comment PR
+        uses: thollander/actions-comment-pull-request@v3
+        with:
+          file-path: .github/workflows/comment.md

README.md

@@ -26,7 +26,18 @@ Each entry has the following format (subject to change):
         "key": "tonkeeper"
      }
   ],
-  "platforms": ["ios", "android", "chrome", "firefox", "safari", "windows", "macos", "linux"]
+  "platforms": ["ios", "android", "chrome", "firefox", "safari", "windows", "macos", "linux"],
+  "features": [
+    {
+      "name": "SendTransaction",
+      "maxMessages": 4,
+      "extraCurrencySupported": false
+    },
+    {
+      "name": "SignData",
+      "types": ["text", "binary", "cell"]
+    }
+  ]
 }
 ```
 
@@ -41,6 +52,12 @@ Each entry has the following format (subject to change):
     - `type="sse"`: specify the `url` of your wallet's implementation of the [HTTP bridge](https://github.com/ton-connect/docs/blob/main/bridge.md#http-bridge).
     - `type="js"`: specify the `key` through which your wallet handles [JS Bridge](https://github.com/ton-connect/docs/blob/main/bridge.md#js-bridge) connection, specify the binding for your bridge object accessible through `window`. Example: the key `"tonkeeper"` means the bridge can be accessed as `window.tonkeeper`.
 - `platforms`: list of platforms on which your wallet works: mobile app "ios", "android"; desktop app "windows", "macos", "linux"; browser extension "chrome", "firefox", "safari".
+- `features`: list of supported TON Connect features and their capabilities:
+    - `SendTransaction`: Transaction sending capability
+        - `maxMessages`: maximum number of messages in one transaction (typically 4 or 255)
+        - `extraCurrencySupported`: (optional, `false` by default) whether wallet supports extra currencies
+    - `SignData`: Data signing capability  
+        - `types`: array of supported data types for signing: `"text"`, `"binary"`, `"cell"`
 
 If your wallet supports HTTP Bridge, you should specify `universal_url` and `bridge.type="sse"`.