Hacki
Hackathons

Aleph Hackathon

Closed

6th edition

Sign in to participateRegister as hacker

🟧 WDK Track

Tether · you can enter 1 track from this sponsor

🎯 Overview

WDK (Wallet Development Kit) by Tether is an open-source, non-custodial toolkit for building wallets and payment flows into any app. Instead of learning a different SDK for every chain, you get one consistent interface across Bitcoin, Lightning, EVM, Solana, TON, TRON, and more, plus modules for swaps, bridging, lending, and fiat on/off-ramps, with a seamless web2 experience.

Everything is modular: install only the chains and protocols you need, keep keys on the user's device, and ship. There's an SDK (Node.js, Bare, React Native), a CLI with a bundled MCP server so AI agents can operate a wallet, and gasless modules that let your users pay fees in USD₮ instead of holding native gas tokens.

If you're new to crypto dev: you don't need to write a single smart contract to win this track. WDK handles keys, addresses, balances, and transactions; you can focus on building the product on top, for humans or agents.

🏆 Prize breakdown

Total Prize Pool: Up to $1,500 USDt in prizes, to be distributed at the judges’ discretion based on the merit, quality, originality, and impact of the submitted projects.

  • 🥇 1st place — $1,000 USDt — Best project built with the WDK CLI. For projects that use the WDK CLI (and/or its bundled MCP server) as a core building block. Agents with wallets, scripted payment flows, local wallet tooling, developer utilities… surprise us.
  • 🥈 2nd place — $500 USDt — Best gasless project: For projects that use WDK's gasless wallet modules so users can transact without holding native gas.

🧑‍💻 Track focus

Pick one prize track and go deep. Below are starting points; original ideas are more than welcome.

🥇 Track 1 — Build with the WDK CLI

The CLI is a local command-line wallet: create and unlock wallets, derive addresses, read balances and history, send native assets and tokens, manage networks and custom tokens, and generate MoonPay on/off-ramp links. It also ships wdk-mcp, an MCP server that exposes those same wallet operations to MCP-compatible clients (Claude Desktop, Claude Code, OpenClaw).

  1. Give an AI agent a wallet. Wire wdk mcp into an MCP client and build an agent that checks balances, quotes and sends USD₮ under user-defined guardrails (spending caps, allowlists, confirmation prompts). Bonus points for a thoughtful safety model.
  2. Scripted treasury and payouts. A shell-based payroll, grants or bounty-payout tool: read a CSV, preview every transfer with wdk send, batch-execute, and produce a receipt log using --json output.
  3. Merchant / invoicing tooling. A terminal POS or invoice checker that watches an address with wdk get, detects incoming USD₮ payments, and fires a webhook or prints a receipt.
  4. Developer utilities. A faucet bot, testnet ops helper, portfolio TUI, or CI job that uses the CLI as its wallet backend.
  5. Agentic payments. Combine the CLI/MCP server with x402 so an agent can pay per API call.

🥈 Track 2 — Build something gasless

Gasless modules let users transact without ever holding native gas: fees are paid by a paymaster and settled in USD₮ or USD₮0, or fully sponsored by you.

  1. Zero-to-first-payment onboarding. A user lands with an empty wallet, receives USD₮, and can immediately send it; no "go buy some SOL first" step. Show the fee quote in USD₮ before signing.
  2. EIP-7702: upgrade the EOA people already have. Keep the same address, delegate execution, and run transactions as sponsored ERC-4337 UserOperations. Great for batching (approve + swap in one operation) or "your first 10 transactions are on us" growth mechanics.
  3. Solana remittances or P2P payments. Use the gasless Solana module (Kora-compatible paymaster) for SPL/USD₮ transfers where the recipient's associated token account is created automatically.

4. Subscriptions, tipping, or in-game economies. Recurring or micro-value payments where charging the user gas would kill the UX. 5. Cross-chain gasless flows. Combine a gasless wallet with the USDT0 bridge or a swap module so the whole journey never touches native gas.

What we'll be looking at:

  • does it solve a real user problem
  • does it actually work end-to-end in the demo
  • is the WDK integration meaningful (not a wrapper around one call)
  • is the UX something a non-crypto person could use, or an agent?

🛠️ Tech requirements

Must use:

  • WDK as a core dependency of your project. @tetherto/wdk
  • Track 1:@tetherto/wdk-cli (the scoped package; the unscoped wdk-cli on npm is a different project).
  • Track 2: at least one WDK gasless wallet module (wdk-wallet-solana-gasless, wdk-wallet-evm-7702-gasless, wdk-wallet-evm-erc-4337, wdk-wallet-ton-gasless, or wdk-wallet-tron-gasfree). And gas token USD₮.

Environment:

  • Node.js 22.18.0 or later.
  • WDK packages are currently in beta. Use a dedicated test wallet with limited funds, never a personal wallet with real money in it.**

### Paymaster setup (Track 2)

We do not hand out paymaster endpoints for the hackathon — you get your own, and it's quick. Providers like Candide and Pimlico give you an endpoint in a few minutes from their dashboards. Each gasless module's docs page lists exactly what it needs (RPC, bundler URL, paymaster URL, paymaster token, and for EIP-7702 a delegation address), and the per-chain posts on the WDK blog walk through the setup chain by chain.**

Testnet vs mainnet — read this before you plan your demo:

  • Testnet USD₮ is only available on Sepolia, via Candide and Pimlico. If you're building on Sepolia, you're covered.
  • For any other chain (Solana, TON, TRON, other EVMs), deploy your own mock USD₮ token and point the paymaster config at it. Do not substitute another stablecoin provider's faucet token — that won't be accepted.
  • Or work on mainnet with small amounts. Your call; just budget the time.**

Reusing code

  • You may reuse existing code. We will only judge what you built during the hackathon.
  • The WDK integration itself must be new, written this weekend.
  • Do not bolt WDK on in parallel. If we find a project that already has its own wallet/payment layer and simply added WDK alongside it for the prize, we will discard it. The integration has to actually do something in your product.**

AI-assisted coding

Fully allowed, and encouraged, we ship tooling specifically for it:

But review what your model writes. WDK integrations are only a few lines of code; models tend to over-engineer them, invent methods that don't exist, and hallucinate config. ObviousAI slop (hallucinated APIs, dead code, a README describing features that aren't there) gets discarded without further review. Use the Agent Skills and docs above to keep your assistant grounded, and run the thing before you submit it.

Submission must include

  • Public repo with a README explaining what you built and which WDK modules you used.
  • Permalinks to the WDK integration, direct GitHub links to the specific files/lines where WDK is used. This is what we look at first, so make it easy.
  • Recorded demo video (async, see Judges section) showing the flow actually running.
  • List of WDK packages and versions you installed.
  • Setup instructions that work from a clean clone: install steps, .env.example with the variables you need (RPC, bundler, paymaster, token addresses), and the command to run it.
  • Network and token details, which chain you demoed on, and if you deployed a mock USD₮, its contract address.

📚 Developer resources

Start here

Building with AI

Track 1 — CLI

Track 2 — Gasless

Tools & extras

Community & support

💬 Mentors

  • Raquel DevRel | Telegram:@rraigal & Twitter:@rraigal_
  • Mentorship is IRL & online: you will have your dedicated topic in the hackathon Telegram group chat, and hackers can ping mentors whenever they need them.
  • For deeper technical questions, mentors will point you to the channels where the WDK engineering team lives:
  • Discord: https://discord.gg/tetherdev
  • Keet keet://chat/gfo4d3jdeokkg3uouq4obczt1wzepyb1e5ip9694f8c4ow9opsof6nnnj4mis3aer3acu1do14hgax8anggkd4i4w8ssonwa7icctc4t1c85anm518x45mendcrqjcntn9d1zm31wi8g9xosqtuid7cf6sfhcyedtjnjgnbszntxzenp4p3jpn8pueo4yya
  • The hackathon kicks off on Saturday at 12PM (ARG time) and wraps up on Sunday at 12PM (ARG time). Mentors will be especially available on Saturday (the peak day for support and guidance).

🎓 Judge

  • Raquel DevRel | Telegram:@rraigal & Twitter:@rraigal_
  • Judging will start at 1PM (Arg time) on Sunday 23rd, for about 4hs.
  • Everything happens online.
  • The demo is async: hackers will record a demo and attach it to their project submission.

💻 Workshop

WDK Essentials: and how to vibe-code with it without shipping slop

  • Saturday 10AM (ARG time), before kickoff. Live at the hackathon venue and streamed online.
  • A hands-on session covering everything you need to build on WDK this weekend, plus the AI-coding practices that separate a winning submission from a discarded one. We'll cover the WDK essentials: installing the CLI, creating and unlocking a wallet, reading balances, sending a transfer, and setting up a gasless account so fees are paid in USD₮ instead of native gas. Then we'll get into working with AI assistants: how to use WDK's Agent Skills and MCP Toolkit to keep your model grounded in the real API, why WDK integrations should stay short, and how to spot the hallucinated methods and over-engineered wrappers that judges will notice immediately. Bring a laptop: you'll leave with a working wallet and a setup that lets your AI assistant write WDK code that actually runs.