The Onboarding Problem
Let's be honest about where Hive stands on user growth.
In the early days of the chain, Hive was adding 5,000–8,000 new accounts per month. The Splinterlands wave in late 2021 showed what happens when there's a compelling reason to join — hundreds of thousands of accounts created in a matter of months. But since that spike faded, signups have been in steady decline. Through 2023 and 2024, the baseline settled around 3,000–5,000 per month. In 2026 so far, it's dropped below 2,000.
It's not that Hive lacks compelling features. 15% APR on a USD-pegged stablecoin, censorship-resistant blogging, a thriving gaming ecosystem — these are genuine differentiators. The primary problem is getting people in the door.
On most blockchains, there's no account creation step — users just generate a keypair and go. Hive's named on-chain accounts are a genuine advantage (human-readable names, key recovery, resource system), but they come with an onboarding cost that someone has to pay. That cost shows up as friction at every step:
- Account creation sites require email verification, waiting periods, or payment in crypto the user doesn't have yet
- Existing invite systems need the inviter to navigate technical UIs and the invitee to understand blockchain concepts before they even have an account
- Community-based onboarding depends on active volunteers who may take hours or days to respond
The result? A motivated new user encounters friction at the very first step. Many give up before they ever experience what Hive has to offer.
The Splinterlands spike showed the demand is there when there's sufficient motivation to overcome the friction — but that wave was powered by a single game burning significant amounts of HIVE to create accounts. That's not a repeatable model for the broader ecosystem. We need onboarding that is instant, scales without human bottlenecks, and uses the account creation tokens that are already sitting on-chain.
Introducing Hive Invite Cards
Hive Invite Cards is a new open-source system for creating and distributing Hive account invitations — inspired by gift cards, designed for mass adoption.
Here's how it works:
For the person being invited
- Receive an invite — a link, QR code, or physical card from someone you trust
- Enter a short PIN — 6 characters, printed on the card or sent alongside the link
- Pick a username — the app checks availability in real time
- Save your keys — a master password and encrypted QR backup are generated for you
- Done — your Hive account is created within seconds, with delegated HP so you can start transacting immediately
No email verification, no waiting period, no crypto required. Just a phone with a camera. The whole process takes under a minute.
For the person sending invites
Any Hive account holder with account creation tokens can become an invite provider. You generate a batch of invites using a command-line tool, and each invite becomes a self-contained, encrypted package — a QR code plus a PIN.
The system handles everything:
- Cryptographic signing — each invite is signed with your memo key, so recipients can verify it's genuinely from you
- On-chain declaration — a Merkle root of the batch is published as a
custom_json, creating a tamper-proof record - PIN encryption — the invite payload is AES-256-GCM encrypted; without the PIN, the QR code reveals nothing
- Automatic account setup — the claim service creates the account, sets keys, and delegates HP on your behalf
You can distribute invites however you like — print physical cards for events, share links in group chats, hand out QR codes at meetups, or use the automated bots.
Distribution Bots: Telegram & Discord
To make distribution effortless at scale, Hive Invite Cards ships with bots for both Telegram and Discord. An invite provider loads a batch of invites into the bot and chooses how to distribute them:
Free distribution — Operators and trusted users can gift invites directly to anyone in the chat with a simple /gift @username command. The recipient gets a DM with the QR code, PIN, and a clickable invite link.
Paid distribution — The bot supports selling invites for HBD or Bitcoin Lightning (via v4v.app). Users run /buygift, choose a payment method, and receive their invite automatically upon payment confirmation.
Shared codes — Operators can generate claim codes with /share that anyone can redeem on a first-come, first-served basis. Drop them in a community chat, tweet them out, or include them in a newsletter.
Crucially, operators can whitelist trusted users to distribute invites on their behalf. A community leader doesn't have to be online 24/7 — they can authorize moderators or active members to gift cards from the shared inventory. The whitelisted users never see private keys or batch secrets; they just run /gift and the bot handles the rest.
The bots handle inventory management, payment verification, and delivery — the operator just needs to generate batches and load them.
4.9 Million Invites Waiting to Happen
Right now, over 2,000 Hive accounts hold a combined 4.9 million unused account creation tokens. These tokens were claimed using Resource Credits — they cost nothing but RC — and they're sitting on-chain, waiting to be converted into new user accounts. Many large stakeholders have been accumulating them for years.
And these aren't dead accounts. 530 of those token holders have posted or voted in the last 90 days, and they hold 4.4 million of the tokens — over 90% of the total. These are active community members who could start issuing invites tomorrow.
Every single one of those tokens could become an instant Hive invite. To put that in perspective: 4.4 million tokens in active hands is enough to double Hive's entire user base several times over. The capacity for massive growth already exists on-chain. What's been missing is a frictionless way to convert those tokens into actual accounts in the hands of real people.
Hive Invite Cards bridges that gap.
(You can verify these numbers yourself on HiveSQL — query pending_claimed_accounts on the Accounts table.)
How It Works Under the Hood
For the technically curious:
- Invite generation — A provider runs a script that creates cryptographically random tokens, signs each with their memo key, encrypts payloads with per-invite PINs using AES-256-GCM (PBKDF2, 100K iterations), and publishes a Merkle root on-chain
- Distribution — QR codes and PINs are delivered via physical cards, chat bots, links, or any other channel
- Claiming — The invite app (a static HTML page) decrypts the payload client-side, generates Hive keys locally (keys never leave the user's device), and sends only public keys to the claim service
- Account creation — The claim service validates the token against the on-chain Merkle root, broadcasts
create_claimed_account, and delegates HP - Verification — Anyone can verify a token belongs to a declared batch by checking the Merkle proof against the on-chain declaration
Security highlights:
- Private keys are generated client-side and never transmitted
- PINs never leave the user's device
- The URL fragment containing encrypted data is cleared immediately after decryption
- The claim service only holds the provider's active key (scoped to account creation and delegation)
- Double-redemption is prevented by both on-chain and database checks
Open Source, Run Your Own
The entire system is open source. If you have account creation tokens and want to grow Hive, you can:
- Run your own claim service — The claim service is a single Node.js process with an embedded SQLite database — no Redis, no Postgres, no moving parts. It runs comfortably on a Raspberry Pi 4 or any cheap VPS, and can be deployed to Fly.io's free tier
- Generate your own invite batches — Use the CLI tools to create as many invites as you have tokens
- Run your own distribution bot — Set up a Telegram or Discord bot for your community
- Design your own cards — The system generates print-ready PDFs, but you can customize the design
- Brand the onboarding for your platform — Hive service providers can customize where new users land after claiming. Instead of arriving at peakd.com, a Splinterlands invite could drop the user straight into the game, a 3Speak invite into the video platform, a LeoFinance invite into the finance dashboard. Same account creation under the hood, but the onboarding experience belongs to your app. Today this means forking the invite app; customizable flows without forking are coming soon
You don't need permission from anyone. You don't need to coordinate with a central authority. If you have the tokens, you can start onboarding people today.
Make It Yours: Custom Card Designs
The default invite cards use standard Hive branding — clean, minimal, and functional. But every invite provider can customize the card design to match their own identity or community.
Imagine community leaders handing out invites at meetups with cards that match their own branding — 
The card generator produces print-ready PDFs from a TypeScript template. If you're comfortable with code, you can modify the layout, colours, fonts, and branding directly. If not, tools like Claude Code can help you customize the design by describing what you want — your community's colours, your logo, your own messaging — and generating the PDF template for you.
This matters because onboarding is a personal act. When you invite someone to Hive, you're vouching for it. The card should feel like it comes from you, not from a generic system.
Don't Want to Self-Host?
Not every invite provider will want to run their own claim service — and that's fine. A provider can delegate their active key authority to a hosted service operator, allowing that operator's instance to create accounts on their behalf. Hive's native authority system makes this possible: you add the operator's key as an authority on your account, and you can revoke it at any time through Peakd or Keychain.
The trust requirement is real — active key authority means the operator could perform other active-level operations on your account, including theft of liquid funds. You can revoke access at any time, but there's a tradeoff: revoking authority means any unredeemed cards from your batches become void, since the service can no longer create accounts on your behalf. So revocation is an emergency brake, not a casual toggle. For providers who know and trust the operator, this may be a practical path to issuing invites without touching a terminal.
The limitations here are a result of account creation tokens being non-transferable, and that Hive does not have fine grained permissions that would limit authorized keys to only specific transaction types.
A fully multi-tenant hosted service — where providers can register, manage their batches, and monitor usage through a dashboard — is on the roadmap but not yet built.
A Call to App Developers: Keyless Onboarding
Here's something I find genuinely exciting about the architecture.
The claim service exposes a simple HTTP API: send a token, a username, and four public keys — get back a Hive account. The invite web app handles QR scanning, PIN decryption, and key generation today, but there's nothing stopping a native mobile app from doing all of that itself.
Imagine Hive Keychain integrating invite card redemption directly. A user scans a card, enters the PIN, picks a username — and Keychain generates the keys internally, stores them in its own encrypted vault, and calls the claim API. The user never sees a master password. Never handles raw keys. Never needs to understand what a "posting key" is. Keychain can prompt for backup later through its own backup flow, on its own terms — not in the middle of onboarding when the user is least prepared for it.
That's a fully keyless onboarding experience — from physical card to working Hive account with keys securely managed, in under a minute.
The same applies to any Hive app with a mobile presence. Ecency could build invite redemption into its app and land new users directly in their feed. Splinterlands could hand out invite cards at gaming events and have players scanning straight into the game. 3Speak could onboard creators who've never touched a blockchain.
The crypto primitives required are standard (AES-256-GCM for PIN decryption, PBKDF2 for key derivation) and the claim API is documented and open. If you're building a Hive app and want to integrate invite card redemption, the infrastructure is ready — reach out and let's make it happen.
What's Next
Hive Invite Cards is live and working today. Here's what's on the roadmap:
- Localized invite app — The invite flow is currently English-only. Bringing the onboarding experience into all supported languages is a priority.
- More distribution channels — Telegram and Discord bots are ready. Email and Signal distribution are next.
- Customizable onboarding flows — Letting service providers configure where new users land after claiming (their app, their branding) without needing to fork the invite app
Try It / Get Involved
- GitHub: HiveAccessibleAnywhere
- Try it: Contact @demotruk for an invite, or purchase one via the Telegram bot or Discord bot
- Check your tokens: Run
SELECT pending_claimed_accounts FROM Accounts WHERE name = 'yourusername'on HiveSQL
There are over 500 active accounts that could start issuing invites right now, holding 4.4 million tokens ready to become new users. If you're one of those account holders, the tools to turn those idle tokens into real Hive users are here. Let's use them.
Hive Invite Cards is part of the Hive Accessible Anywhere project — building infrastructure to make Hive accessible to everyone, everywhere.
This post was co-authored by @demotruk and Claude (Anthropic). The Hive Invite Cards system was also built with Claude as a coding partner.
