chia-walletconnect_skill

This skill enables Telegram users to verify Chia wallet ownership through WalletConnect and MintGarden, delivering secure in-app authentication without leaving
  • Python

2.5k

GitHub Stars

6

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill chia-walletconnect

  • _meta.json670 B
  • cli.js4.3 KB
  • package-lock.json115.0 KB
  • package.json846 B
  • README.md14.1 KB
  • SKILL.md10.1 KB

Overview

This skill is a Telegram Web App that verifies Chia wallet ownership by integrating WalletConnect (Sage) and MintGarden signature verification. It enables users to sign a challenge inside Telegram and returns a cryptographic proof of ownership to your bot. The flow keeps users inside the Telegram Mini App and requires no private keys to leave the device.

How this skill works

The Web App initializes WalletConnect v2 and requests a message signature from the user's Sage Wallet. It generates a nonce-based challenge, collects address, signature, and optional public key, then sends that payload back to your bot via Telegram.WebApp.sendData(). The bot forwards the payload to the MintGarden verify_signature endpoint and acts on the verified response (granting access, recording verification, etc.).

When to use it

  • Gate Telegram groups or channels to NFT holders or token owners
  • Validate airdrop eligibility by proving wallet control
  • Add Web3 authentication for bot commands and services
  • Confirm DAO voting identities tied to on-chain addresses
  • Record secure proof of wallet ownership for audits

Best practices

  • Deploy the webapp over HTTPS and use your own WalletConnect Project ID
  • Expire challenges quickly (default 5 minutes) and include nonces to prevent replay
  • Link each verification to the Telegram user ID to avoid spoofing
  • Rate limit verification endpoints and log attempts for auditing
  • Store verification records in an encrypted persistent database

Example use cases

  • A bot that invites verified Chia wallet owners to an exclusive NFT group
  • Airdrop eligibility check: verify wallet ownership before distributing tokens
  • Require wallet verification before allowing proposal submissions in a DAO
  • One-click verification flow inside Telegram for onboarding collectors
  • Backend service that records verifiable proofs for KYC-lite processes

FAQ

No. The WalletConnect flow runs inside the Telegram Web App; users approve signatures in Sage without leaving Telegram.

Is any private key transmitted to the skill?

No. Only the signature, address, and optional public key are transmitted. Private keys remain in the user's wallet.

What happens if MintGarden is down?

Signature verification will fail until MintGarden responds. Implement retry logic and surface a clear error to the user while logging the attempt.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational