Scaffold-HBAR template

Launch a token. Give it a market. Block by block.

LaunchBlocks turns a Hedera token launch into blocks you snap together: create an HTS token, open a public HCS log, seed a SaucerSwap pool and make the first trade. Then it runs the launch on testnet and shows every transaction as it lands.

Open Launch StudioView on GitHub

Verified on testnet

One run of the full launch. Every id is also recorded on its HCS log.

Start from an example

Each opens in the Launch Studio, ready to edit, validate and run.

Token launch with a SaucerSwap market

The full launchpad: create the token, log the launch on HCS, seed its first SaucerSwap V1 pool against HBAR, make the first trade to prove the market is live, and record it.

hts.createTokenhcs.createTopichcs.submitMessagesaucerswap.createPoolsaucerswap.swaphcs.submitMessage
Open in studio →

Token launch with locked liquidity

The launch with a lock: open the SaucerSwap market, deploy a TokenLock contract, move the pool's LP tokens into it for 30 days, read the lock back, and record it on HCS.

hts.createTokenhcs.createTopichcs.submitMessagesaucerswap.createPoolcontract.deployhts.transfercontract.callcontract.callhcs.submitMessage
Open in studio →

Token launch with scheduled unlocks

Hold back part of the supply and schedule it to unlock in two tranches, at 30 and 60 days. The network mints each one on its date with nobody online.

hts.createTokenhcs.createTopichcs.submitMessagehss.scheduleMinthss.scheduleMinthcs.submitMessage
Open in studio →

HTS token launch with HCS log

Fungible token with a fractional fee, finite supply and a public HCS launch log; mints a reserve and records it.

hts.createTokenhcs.createTopichcs.submitMessagehts.minthcs.submitMessage
Open in studio →

How it works

Compose

Snap steps together. Sockets take a typed value or an output of an earlier step, dragged from the Outputs drawer.

Check

Every param and every reference is validated against the step schemas before a single HBAR is spent.

Run

Steps execute on testnet in order. Each block turns green as its transaction reaches consensus, with HashScan links.

Export

Download the flow as JSON for the CLI, or as a standalone launch.ts that calls the same functions.

Under the hood

Creating a pool and trading against it takes a few SDK calls. Getting them right took measurements on testnet: the LP recipient must be the account's EVM alias, the pool is created in two calls so the opening price comes out exact, and the documented gas is too low.

Read how the SaucerSwap integration works
Token Service
Fungible tokens with configurable keys, finite or infinite supply, fractional and HBAR custom fees, mints, transfers and HIP-904 airdrops.
Consensus Service
A public, ordered, timestamped log per launch, in text or JSON.
SaucerSwap
The token's first pool with an exact opening price, then a first trade quoted by the router itself.
Schedule Service
Vesting transfers and supply unlocks as long-term schedules, which the network runs on their date with nobody online.
Smart contracts
Deploy and call your own Hardhat contracts from blocks, such as a TokenLock that holds the pool's LP tokens for 30 days.
Mirror node
Free quotes, pool and contract reads, EVM-alias resolution, exchange rates, and reading the launch log back.

Make it your starting point

Scaffold your own copy, add a testnet operator, and launch. New step types slot into the registry and appear here with no frontend changes.

npm create scaffold-hbar@latest -- --template jmgomezl/scaffold-hbar-launchblocks
Quick start and cost of a launch

Hedera Harness

Let an agent add the next block

The template ships a Hedera Harness recipe. It asks a coding agent to add a Burn tokens step by following AGENTS.md, then grades the work itself, up to burning real supply on testnet. The checks were tried both ways: 15 findings on the template as shipped, none on a correct implementation. Any launch you build can become a recipe of its own: in the studio, choose Export, then Harness recipe.

yarn harness:run
The recipe and how it was verifiedWhat the agent is asked to build
  1. Tier 0–1

    The step, its tests and a new example sit where AGENTS.md puts them; tests, lint, strict types, a dry run of the new flow and the production build pass.

  2. Tier 2

    The app boots, and its pages and the step and gallery APIs render.

  3. Tier 3

    Burn tokens is in the studio toolbox, its example loads as valid, and export generates the call.

  4. Tier 3.5

    The new flow burns supply on testnet, signed by the harness's own funded throwaway account.

Get testnet HBAR