RUNEPONS

Abstract

RunePons is a permissionless inscription launchpad built natively on the Robinhood Chain. It introduces a new primitive: a token launched on a plain ETH curve that is a real Uniswap V4 pool from block one, whose entire raise, when filled, market-buys a graduated community rune and becomes locked liquidity paired with it. RunePons turns every launch into a permanent, on-chain commitment — a rune carved into stone, with no exit, no admin, and no way to unwind the terms once they are set. This document describes the protocol, the inscription standard, the mechanism, the three rites, the trust architecture, tokenomics, governance, roadmap, and risks.

1. Introduction

The launchpad is one of the most heavily used pieces of infrastructure in crypto, and one of the least trusted. Over the last several cycles, launchpads have converged on a common pattern: a synthetic bonding curve that is not actually a market, an admin key that can pause or rug, and a liquidity event that is announced but never guaranteed. RunePons was designed as the opposite of that pattern. It is not a bonding-curve widget bolted on top of a token. It is a token whose bonding curve is a live Uniswap pool, whose raise is a real market buy, and whose liquidity is locked in a contract with no exit.

RunePons is native to the Robinhood Chain, an EVM chain purpose-built for tokenized assets and stock tokens. By pairing every launch with a graduated community rune, RunePons gives every new token a reason to exist beyond speculation: its volume becomes a persistent, mechanical benefit to the community it bonds into. This is the core idea of RunePons — Runes are the liquidity, and liquidity is a gift that keeps giving.

2. The Problem

Existing launchpads suffer from a consistent set of failures that RunePons is designed to eliminate. Understanding these failures is essential to understanding why the architecture is the way it is.

• Synthetic curves are not markets. A bonding curve that lives inside a launchpad contract is not a price — it is a schedule. No external bot, no aggregator, no wallet can trade it without integrating the launchpad's specific interface. RunePons uses a real Uniswap V4 pool, quoted in ETH, so that any wallet that can swap Uniswap can trade the token from its first block.
• Liquidity is announced, not enforced. Most launchpads promise to seed liquidity after the raise and then rely on a multisig to keep that promise. RunePons enforces it in code: at 4.2 ETH the curve closes, the entire raise market-buys the quote rune in one public swap, and the position is minted directly into a locker contract with no withdraw function.
• Admins can change the rules. Fees, thresholds, and cashback terms are routinely mutable in existing platforms. In RunePons, they are snapshotted into the contract at creation and can never be changed — not by the carver, not by the protocol, not by anyone.
• Volume benefits no one but the creator. In most launchpads, trading fees flow to the deployer or the protocol and nowhere else. RunePons lets the creator choose a rite — burn, reward, or keep — that determines where the volume's value goes, permanently.

3. RunePons Overview

RunePons is composed of four interlocking pieces: the inscription protocol (how runes are created and transferred), the mechanism (how a launch works), the rites (how a launch's fees behave), and the trust architecture (why none of this can be changed after the fact). Together they form a system where launching a token is a one-way act — you carve the stone, choose the rite, and then it leaves your hands forever.

The name reflects the philosophy. A rune is an inscription — a mark written to the chain that cannot be unwritten. A Pons is the bridge that every launch crosses: the graduated community rune that the raise bonds into. RunePons is the place where those two ideas meet.

4. The Inscription Protocol

RunePons uses a calldata inscription standard in the spirit of ethscriptions and BRC-20. An inscription is a JSON document written into the data field of a zero-value transaction. There are three operations: deploy, mint, and transfer.

4.1 Deploy

Deploy inscribes a new rune. It names a ticker, sets a maximum supply, and optionally sets a per-mint limit.

{"p":"runepons","op":"deploy","tick":"RUNE","max":"21000000","lim":"1000"}

4.2 Mint

Mint claims a share of an existing rune, within the per-mint limit and the remaining supply. First come, first carved.

{"p":"runepons","op":"mint","tick":"RUNE","amt":"1000"}

4.3 Transfer

Transfer moves runes between addresses. Ownership is written in the stone and follows the transfer inscriptions.

{"p":"runepons","op":"transfer","tick":"RUNE","amt":"1000"}

4.4 Validity Rules

• Tickers are 1–12 uppercase alphanumeric characters and are unique across the ledger.
• A deploy is valid only if the ticker has not already been deployed.
• A mint is valid only if the amount respects the per-mint limit and does not exceed the remaining supply.
• All three operations are indexable by any party that scans the chain's calldata, making the protocol fully transparent and permissionless to verify.

5. The Mechanism

The mechanism is three movements, then the launch leaves the creator's hands. There is no stage after the bond where anyone can intervene.

5.1 Carve the Stone

One transaction creates the token and a live Uniswap V4 pool quoted in ETH. The bonding curve is that pool. From its first block, any wallet or bot that can swap Uniswap can trade the token, with nothing launchpad-specific to integrate. There is no separate curve contract to trust.

5.2 Choose the Rite

Before anyone buys, the creator chooses which graduated rune the raise will bond into, and which rite will govern fees. Buyers spend plain ETH; the quote rune is what the launch becomes bound to, what the pool pairs with, and what the creator's fees arrive in after the bond.

5.3 Seal the Tomb

At 4.2 ETH, the curve closes. The entire raise is market-bought into the chosen quote rune in one public swap. A new pool seeds at the curve's final price, and the resulting liquidity position is minted straight into a locker contract with no withdraw function, no transfer, and no arbitrary call. There is no exit in the code at all.

5.4 The 4.2 ETH Curve

4.2 ETH is the fixed fill threshold. It is chosen to keep launches small enough to fill quickly and large enough to seed meaningful liquidity. The threshold is not a parameter that can be changed; it is part of the mechanism itself. When the raise reaches 4.2 ETH, the bond executes automatically and unconditionally.

5.5 A Real Pool From Block One

Because the curve is a real Uniswap V4 pool, price discovery is genuine from the first block. There is no fake depth, no seeded order book, and no hidden price schedule. The market is the mechanism, and the mechanism is the market.

6. The Three Rites

A rite is a permanent, code-enforced decision about where a launch's fee volume goes. The rite is chosen at inscription, disclosed on the token page before anyone trades, and can never be changed after. There are three rites.

6.1 The Cinder Rite — Burn

Part of every fee is sent to the dead address. The launch's volume permanently shrinks the supply of the rune it bonds into. The community whose token the raise bought receives deflation in exchange — every trade burns a little of their supply forever.

6.2 The Harvest Rite — Reward

Part of every fee flows to everyone holding the launch's token, pro-rata and continuously, before and after the bond. There is nothing to stake, no snapshot to be present for, and no operator who could stop paying. Holders are rewarded simply for holding.

6.3 The Silent Rite — Keep

The creator keeps the whole take. Zero is the default, and the silent rite is the absence of a decision — a launch that does not give back, but also does not pretend to. Whatever is chosen is carved at creation and never touched again.

7. Trust Architecture

RunePons is built so that you do not have to trust it. Four properties hold, and each can be verified on-chain.

7.1 Liquidity Sealed, Not Time-Locked

The locker contract has no withdraw function, no transfer function, and no arbitrary call. This is not a long delay with a key that eventually unlocks — there is no exit in the code at all. The liquidity position is sealed the moment the bond executes.

7.2 Fee Terms Frozen at Launch

Nobody can change a live launch's fees, threshold, or rite afterwards. Not the creator, not the protocol, not the owner. The terms are snapshotted into the contract at creation, and the snapshot is immutable.

7.3 No Admin Over Your Revenue

There is no override anywhere that can redirect a creator's fees. The reference implementation that most launchpads ship with contains such an override; RunePons removed it. The glyph you leave is the glyph that stands.

7.4 Rules, Not Gatekeepers

Quote runes qualify by on-chain proof and a liquidity floor. Anyone can list one. Nobody — including the protocol itself — can delist one. Access is governed by code, not by a permission list.

8. Tokenomics

RunePons adopts the token economics of Pons on Pons, the canonical launchpad of the Robinhood Chain. The economics are deliberately minimal, and every parameter is fixed at inscription and immutable thereafter — nobody, including the protocol, can change a live launch's fees, threshold, or cashback.

8.1 Fee Structure

• Flat launch fee in ETH — paid once, to carve a rune into the chain.
• 1% base fee on trades — charged on every trade of an inscribed rune, the source of the rite cashback and the buyback-and-burn.

8.2 The Curve

Every rune launches on a plain ETH curve that is a real Uniswap V4 pool from block one. At 4.2 ETH the curve closes. The entire raise market-buys the chosen quote rune in one public swap, and the resulting position is minted into a locker with no exit. 4.2 ETH is the fixed fill threshold — small enough to fill quickly, large enough to seed meaningful locked liquidity.

8.3 Cashback — The Three Rites

The 1% trade fee is distributed according to the rite chosen at inscription. Cashback is optional, and zero is the default. Whatever is chosen is disclosed before anyone trades and can never be changed after.

• Quote burn — part of every fee is sent to the dead address, permanently shrinking the supply of the rune the launch bonds into.
• Holder rewards — part of every fee flows pro-rata and continuously to everyone holding the launch's token, before and after the bond.
• None — the creator keeps the whole take. This is the default.

8.4 $RP Buyback and Burn

The platform's defining rule: a portion of creator fees is used to buy $RP back on the open market, and the bought-back $RP is immediately burned — sent to a dead address where it can never return. This mirrors the canonical Pons burn, in which creator fees bought POP on the open market and burned it forever. The mechanism is continuous, automatic, and cannot be paused. The more the platform is used, the more $RP is bought, and the scarcer $RP becomes.

9. Governance

RunePons has minimal governance by design. The parts of the system that matter — fees, thresholds, rites, liquidity — are immutable at the contract level. What remains is operational: which quote runes qualify, and what the liquidity floor is. These are set by on-chain proof and documented in the protocol, not by a discretionary committee. If a parameter must change, it changes for future launches only, never for a launch that has already been carved.

10. Roadmap

• Phase 1 — Genesis. The inscription standard and the deploy/mint flow go live. The first runes are carved.
• Phase 2 — The Bond. Graduated community runes are whitelisted as quote assets, and the 4.2 ETH bond mechanism activates.
• Phase 3 — The Ledger. A public, open indexer exposes every inscription, bond, and rite for anyone to verify.
• Phase 4 — The Pantheon. A governance layer for the operational parameters that are not immutable, always forward-looking, never retroactive.

11. Risks

Nothing on a chain is without risk, and RunePons is no exception. The following risks are disclosed plainly.

• Market risk. Tokens launched on RunePons are subject to the same price volatility as any crypto asset, and most launches will not be successful. There is no guarantee of any return.
• Smart contract risk. The contracts, while designed to be immutable and adminless, may contain bugs. Users should only risk what they can afford to lose.
• Community rune risk. A launch bonds into a graduated community rune. If that rune's community dissolves or its value declines, the locked liquidity is affected accordingly.
• Chain risk. RunePons runs on the Robinhood Chain. Availability, finality, and security are inherited from that chain.
• Regulatory risk. The treatment of inscriptions and launchpads varies by jurisdiction. Users are responsible for their own compliance.

12. Disclaimer

Conclusion

RunePons is a small idea executed with conviction: a launchpad where every launch is a real market from block one, where the raise becomes locked liquidity in a contract with no exit, and where a token's volume can permanently benefit the community it bonds into. It is not the biggest launchpad, and it is not the loudest. It is the one where what you carve is what you get — and what you get, you cannot take back. That is the whole point. That is RunePons.