How KRELOFI works.

Overview

KRELOFI is an AI creative launch studio for Web3 builders on Robinhood Chain. You describe an idea and get an editable launch kit with five sections: Brand, Visuals, Social, Website and Launch. Every field is yours to rewrite. You can work across several sessions, regenerate one section at a time, restore earlier versions, export the kit as a ZIP, and, if you want to, launch a token through the Pons V2 factory from your own wallet.

KRELOFI is non-custodial. It never asks for a private key or seed phrase and it cannot move funds. It prepares a transaction; your wallet signs it. KRELOFI is an independent product and is not affiliated with or endorsed by Robinhood or Pons.

Start a project in the studio, or write one sentence on the home page.

Brand

The idea, name, ticker, concept, positioning, description and lore. Generation suggests several name and ticker pairs; picking one fills the name and ticker. Everything else in the kit (social copy, website copy, token details) is written from the brand, so set it first.

• Names, tickers, handles and domains are suggestions only. KRELOFI does not check whether they are available or trademarked.
• The brand preview uses your project's own colors from the Website section, not KRELOFI's.
• The generation brief under the idea is what every generation is written from. Edit it to steer the results.

Visuals

Generate a profile picture and an X banner, or upload PNG, JPEG or WebP files. Uploads are identified by their actual bytes, limited in size, then decoded and re-encoded, which removes metadata and anything hidden in the file. SVG and other formats are refused.

The crop guides show how X displays each image. Drag to reposition and use Zoom. Downloads and exports use exactly the crop you see: 800 × 800 for the profile picture and 1500 × 500 for the banner, never a stretched image. Earlier images stay in the project library, which marks the one in use.

Social

An X bio (160 characters), an introduction post, a launch announcement draft and follow-up posts (280 characters each), with a live character count and a copy button for each.

• Nothing is posted for you. KRELOFI has no access to your X account.
• The launch announcement keeps the placeholder [CA] until a launch is confirmed. Generated copy that looks like a contract address or transaction hash is rejected.
• Drafts never claim users, partners, listings or prices.

Website

Three templates: Editorial brand page, Community or character, and Minimal product launch. You choose colors, images, links, text, and which sections appear in what order. Desktop and mobile previews render the saved site with the same code as the export.

Templates are fixed code. Your content is inserted as escaped text, links must be https, and no generated code is executed. The preview runs in a sandboxed frame with its own origin, so it cannot reach your KRELOFI session.

The Token section says Not launched yet until KRELOFI has verified a launch for the project. After that it shows the contract address, chain, Pons link and deployment transaction. The exported site has no wallet connection, and the one action it cannot perform is labeled Under development.

Saving and versions

Projects are private. When you start working, KRELOFI gives this browser a session, and your drafts belong to it. Signing in with a wallet attaches the drafts to that wallet so you can reach them on other devices.

Autosave

Edits are saved shortly after you stop typing. The top bar shows Saving…, All changes saved, or Save failed with a Retry button. Saves are sent one at a time and carry the version they were based on. If the project changed elsewhere, for example in another tab or because a generation finished, your unsaved fields are re-applied on top of the latest version instead of overwriting it. Exports, downloads, regenerations and launch reviews save pending edits first.

Versions

Before a generation or a restore replaces a section, KRELOFI stores the section as it was, and then stores the new state. History lists these versions per section. Restoring one first saves the current state, so a restore can itself be undone.

Your edits are kept

KRELOFI tracks which fields you changed by hand. Regenerating a section leaves those fields alone unless you tick Replace my edited fields. History shows which fields were kept.

Wallet sign-in

Connecting a wallet only tells the page an address. To sign in, you sign a one-time message that KRELOFI issued for your session. Signing costs no gas and sends no transaction. Each message has a nonce, expires after ten minutes and works once. KRELOFI never treats an address sent by the browser as proof of ownership.

On first sign-in, the drafts you made in this browser move to the wallet account. Sign out from the wallet menu at any time; your drafts stay with the wallet.

AI generation and limits

All text and image generation runs on the KRELOFI server. Provider keys never reach the browser. The text model returns structured content only, which KRELOFI validates, trims to field limits and checks before saving. It is never asked for HTML or code, and your idea is treated as material to write about, not as instructions.

• Each generation is a job that survives restarts. Clicking twice or reloading does not start a second paid job.
• A paid request is sent to the provider once per job. If it times out, fails or returns invalid output, the job is marked failed and is not resubmitted automatically, because the provider may already have charged for it. Starting again is your choice and counts toward your limit.
• Image providers that work asynchronously are polled until the image is ready, without submitting a second request.
• There are daily limits per account (higher when signed in with a wallet) and a limit on simultaneous generations. Your remaining allowance is shown next to the generation controls.
• Cost is recorded per provider call where the provider reports it or prices are configured. Unknown cost is shown as unavailable, never as zero.

When generation is not available

Generation buttons are disabled and say why. Writing, editing, uploads, versions and export still work. An operator can turn on demo fixtures, which return placeholder content labeled Demo fixture everywhere it appears, including in the pixels of fixture images.

Launch kit export

Export launch kit saves your pending edits first, then downloads a ZIP built from the saved project:

The ZIP contains only this project. It has no secrets and no data from other projects.

Launching on Pons

Launching is optional. Launches go through the Pons V2 launch factory on Robinhood Chain (chain ID 4663) at 0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e. Pons is a third-party protocol. KRELOFI adds no fee and no contract of its own. Pons's own documentation says to treat V2 as unaudited until its audit reports are published, and that public launches are closed to non-whitelisted wallets for now.

Prerequisites

• A wallet signed in to KRELOFI and connected to Robinhood Chain.
• Token name, ticker and description within the Pons limits, plus a logo (your profile picture, a link, or none).
• Enough ETH for the launch fee and gas. The review shows both before you sign.
• A wallet that Pons allows to launch. KRELOFI checks canLaunch(wallet) on the factory. While Pons public launches are closed, only whitelisted wallets can launch, and KRELOFI cannot change that.

What KRELOFI reads before it lets you launch

• That contract code exists at the factory address, and that the factory points to the hook, deployer, escrow and vault that Pons documents.
• The launch fee and who receives it, the launch configurations, the creator tax ceiling and whether public launches are open.
• Which quote assets the factory supports. Native ETH is offered when a configuration is enabled for it. Any other asset is offered only if approvedPairTokens is true for it, the factory holds economics for it, and its decimals match.
• That KRELOFI can reproduce the factory's own economics digest from the values it read. If it cannot, KRELOFI's understanding of the contract is wrong and Launch stays disabled.

If any of this cannot be read, the Launch section shows Pons integration unavailable with the reason, and the button is disabled. Everything else keeps working.

Review and signature

1. Review launch saves your edits and builds the exact launchToken call. The server simulates it from your address, then your browser simulates it again and estimates gas.
2. The review lists network, wallet, token, supply, quote asset, fees and recipients, factory, approvals, launch fee, gas and anything unresolved. No token approval is needed: launching only sends the ETH launch fee. There is no automatic initial buy.
3. If the wallet, network, launch details or Pons terms change after the review, it is discarded and you review again. The call also pins the reviewed economics, so a change on the Pons side makes the transaction revert instead of launching on different terms.
4. Sign and launch opens your wallet. KRELOFI does not send anything itself.

Transaction states

You can close the page after signing. The server keeps checking, and if the hash never reached KRELOFI it finds the launch onchain by the reference it placed in the transaction.

Explore and analytics

Explore lists only launches made through KRELOFI that reached the Confirmed state. It is not an index of every Pons launch. Each entry stores the chain ID, contract address, creator, transaction hash, block and verification state. If a block is reorganized away, the launch is removed from Explore and checked again.

Analytics shows counts from that verified data, plus bonding-curve trades of KRELOFI launches read from chain events since KRELOFI started following the chain. Pool volume after graduation, creator earnings and protocol revenue have no data source yet and are shown as Unavailable.

For operators

Server settings live in the environment file; see .env.example and the README in the source for install, update and backup steps.

• The site URL, X link, platform token address and its Pons link are runtime settings served by /api/public-config. Change them with npm run config -- set <key> <value>. No rebuild or restart is needed. Until the token address is set, the site says Not configured.
• Use a provider RPC endpoint for Robinhood Chain in production. The public endpoint is rate limited.
• AI providers, model IDs and optional prices are configured on the server. Nothing is assumed when they are empty.
• /api/health reports that the process is up. /api/readiness reports each dependency separately.

Live status

Read from this server just now.

Checking…