moltbot
Telegram Web App for Chia wallet verification via WalletConnect and Sage. Enables cryptographic proof of wallet ownership through signature verification using MintGarden API.
bunx add-skill moltbot/skills -s chia-walletconnectLoadingβ¦
Verify Chia wallet ownership via Telegram using WalletConnect integration with Sage Wallet.
This skill provides a Telegram Mini App (Web App) that enables users to:
Use Cases:
/verify command β Web App button β WalletConnect β Sage signs β Verification
The user never leaves Telegram. The entire flow happens in-app via the Telegram Web App API.
# Install via ClawdHub
clawdhub install chia-walletconnect
# Install dependencies
cd skills/chia-walletconnect
npm install
# Make CLI executable
chmod +x cli.js
Deploy the webapp/ folder to a public HTTPS URL:
Vercel (Recommended):
cd skills/chia-walletconnect/webapp
vercel
# Copy the URL (e.g., https://chia-verify.vercel.app)
Netlify:
cd skills/chia-walletconnect/webapp
netlify deploy --prod
Your Server:
# Start Express server
npm start
# Expose via ngrok or reverse proxy
/newapp or /editappverify// Send /verify command handler
message({
action: 'send',
target: chatId,
message: 'Click below to verify your Chia wallet:',
buttons: [[{
text: 'π± Verify Wallet',
web_app: { url: 'https://your-app.vercel.app' }
}]]
});
// In your bot's web_app_data handler
bot.on('web_app_data', async (msg) => {
const data = JSON.parse(msg.web_app_data.data);
const { address, message, signature, publicKey, userId } = data;
// Verify signature
const { verifySignature } = require('./skills/chia-walletconnect/lib/verify');
const result = await verifySignature(address, message, signature, publicKey);
if (result.verified) {
// Wallet verified! Grant access, record verification, etc.
message({
action: 'send',
target: msg.chat.id,
message: `β
Wallet verified!\n\nAddress: ${address}`
});
// Store verification
// await db.saveVerification(userId, address);
} else {
message({
action: 'send',
target: msg.chat.id,
message: `β Verification failed: ${result.error}`
});
}
});
The skill includes a CLI for testing:
# Generate challenge message
node cli.js challenge xch1abc... telegram_user_123
# Verify signature manually
node cli.js verify xch1abc... "message" "signature" "pubkey"
# Validate address format
node cli.js validate xch1abc...
# Start development server
node cli.js server
Endpoint: POST https://api.mintgarden.io/address/verify_signature
{
"address": "xch1abc...",
"message": "Verify ownership of Chia wallet:...",
"signature": "hex_signature",
"pubkey": "hex_public_key"
}
Response:
{
"verified": true
}
| Method | Purpose |
|---|---|
chip0002_getPublicKeys | Fetch public keys from wallet |
chip0002_signMessage | Request message signature |
chia_getCurrentAddress | Get current receive address |
1. User sends /verify to bot
2. Bot responds with Web App button
3. User taps button β Mini App opens in Telegram
4. Mini App initializes WalletConnect
5. User connects Sage Wallet
6. Challenge message generated (includes nonce + timestamp)
7. User signs message in Sage Wallet
8. Signature sent back to bot via Telegram.WebApp.sendData()
9. Bot verifies signature with MintGarden API
10. Bot confirms verification success/failure
Time: ~5-10 seconds for full flow (user-dependent)
Create .env in skill folder:
PORT=3000
WALLETCONNECT_PROJECT_ID=your-project-id
MINTGARDEN_API_URL=https://api.mintgarden.io
webapp/app.jsDefault Project ID:
The skill includes 6d377259062295c0f6312b4f3e7a5d9b (Dracattus reference). For production, use your own.
chia-walletconnect/
βββ webapp/
β βββ index.html # Telegram Web App UI
β βββ app.js # WalletConnect logic
β βββ styles.css # Styling
βββ lib/
β βββ challenge.js # Challenge generation
β βββ verify.js # MintGarden API client
βββ server/
β βββ index.js # Express webhook server
βββ cli.js # CLI interface
βββ package.json # Dependencies
βββ SKILL.md # This file
βββ README.md # Full documentation
// Clawdbot skill handler
const { verifySignature } = require('./lib/verify');
// /verify command
if (message.text === '/verify') {
await message({
action: 'send',
target: message.chat.id,
message: 'Verify your Chia wallet:',
buttons: [[{
text: 'π± Connect Wallet',
web_app: { url: process.env.WEB_APP_URL }
}]]
});
}
// Handle web app data
bot.on('web_app_data', async (msg) => {
const { address, message: challengeMsg, signature, publicKey } =
JSON.parse(msg.web_app_data.data);
const result = await verifySignature(address, challengeMsg, signature, publicKey);
if (result.verified) {
// Grant access
await grantAccess(msg.from.id, address);
await message({
action: 'send',
target: msg.chat.id,
message: `β
Verified! Welcome, ${address.substring(0, 12)}...`
});
} else {
await message({
action: 'send',
target: msg.chat.id,
message: `β Verification failed`
});
}
});
// Check if user owns specific NFT collection
const { verifySignature } = require('./skills/chia-walletconnect/lib/verify');
const mintGarden = require('./skills/mintgarden'); // Assume mintgarden skill exists
bot.on('web_app_data', async (msg) => {
const { address, message, signature, publicKey } =
JSON.parse(msg.web_app_data.data);
// Verify signature first
const verifyResult = await verifySignature(address, message, signature, publicKey);
if (!verifyResult.verified) {
return bot.sendMessage(msg.chat.id, 'β Invalid signature');
}
// Check NFT ownership
const nfts = await mintGarden.getNFTsByAddress(address);
const hasRequiredNFT = nfts.some(nft =>
nft.collection_id === 'col1required...'
);
if (hasRequiredNFT) {
// Grant access to private group
await inviteToGroup(msg.from.id);
bot.sendMessage(msg.chat.id, 'β
Access granted! Check your invites.');
} else {
bot.sendMessage(msg.chat.id, 'β You need a Wojak NFT to join!');
}
});
| Stage | Time |
|---|---|
| WalletConnect Init | ~1-2s |
| Connection Approval | User action |
| Sign Request | ~2-5s |
| MintGarden Verify | ~0.5-1s |
| Total | ~5-10s |
@walletconnect/sign-client β WalletConnect v2@walletconnect/utils β WalletConnect helpers@walletconnect/types β TypeScript typesexpress β Web servernode-fetch β HTTP clientcors β CORS middlewaredotenv β Environment config1.0.0
MIT β Koba42 Corp
Built with π± by Koba42 Corp
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.