How Zynora works

What a seal is

1. 1SparkYou write the idea.
2. 2ShardClaude or fal.ai makes it.
3. 3SealYour wallet records its fingerprint.
4. 4CheckAnyone matches a file to the seal.

When you publish a shard, your wallet calls record(contentHash, parentHash, kind, uri) on the ZynoraSeal contract. The contract stores your address as the creator, the block time, the kind, and the fingerprint of the shard it remixes. It refuses a fingerprint that is already sealed, and a remix of something that is not.

The fingerprint is keccak256 of the shard itself: the bytes of the picture or video file, or the UTF‑8 bytes of the text or the app's HTML. Anyone can download the shard, hash it, and compare. The contract has no owner and no admin function, holds no funds and cannot be upgraded. Zynora never holds a key: the server builds the transaction, simulates it from your wallet, and hands it to your wallet to sign; you pay the gas.

Networks

Zynora runs on Robinhood Chain (chain 4663). Robinhood Chain mainnet is chain 4663 with explorer robinhoodchain.blockscout.com; the testnet is chain 46630 with explorer explorer.testnet.chain.robinhood.com. Both from the official Robinhood Chain docs.

Energy

Energy is the day's allowance of making. Each kind of spark takes a set amount:

Free energy covers chat and pictures every day. Paid energy covers every kind and never expires.

• Free energy a dayGuests 3, a signed-in wallet 5. It covers chat and images.
• Per addressAt most 60 free energy a day from one internet address, which many phones share.
• Daily free budget1.00 USD of AI across Zynora. Once it is spent, free energy stops until 00:00 UTC; paid energy goes on.
• Paying for a packIn ETH at the price read when you pick one, locked for 10 minutes. Credited once the payment is at least the quote, reaches the treasury before it expires, and is 3 blocks deep.
• RefundsA shard that fails or comes back cut off gives its energy back, unless the request itself was refused. Paid energy never expires.

• Daily plan budget0.40 USD of AI for the plan and every step, held in the database.
• How it is spentEach step gets a share of what is left. When a step uses up its share the next page is made compact; when even that runs out, the plan stops with the steps made so far.
• EnergyA plan that made something you can use keeps its 4 energy; one that made nothing gives all of it back.

Models and real costs

Each shard's seal card shows the cost computed from the provider's own usage figures for that call. Zynora's AI spend is capped in the database: each day at the free budget plus 60% of energy income not yet spent, and never more than 10 USD. When a provider refuses a key or runs out of balance, the dashboard says so plainly and the energy comes back.

The eight Studio samples in the atlas were made once, for the gallery, with FLUX 2 Max from briefs written by Claude. Shards you make use the models above.

Built apps run in a sandbox

An app is one static HTML file. It is never run on the server. It is served from a separate origin with a content security policy that allows its own inline script and nothing else: no network requests, no forms, no frames. Every page is checked before it is kept; one that fails the check is not served. In the dashboard an app is shown zoomed out until it fits its frame (never below half size), so its buttons are in view; the app itself is still served unchanged at its own address, and that file is what its fingerprint is taken from.

Agents

An agent is a task and a list of tools it may use: research, outline, draft, critique, revise, summarize, headline. Each tool is a text step with no network, no wallet and no money. Agents never trade and never give financial advice. One can run once or every day; each run takes 2 of its owner's paid energy. Your daily agents are listed in your vault, where each can be stopped or started again.

What a spark may not ask for

• Seed phrase or private keyA prompt may never ask anyone for a seed phrase, a private key, or a recovery phrase. Zynora does not ask for them and neither can anything it makes.
• A fake wallet or login screenA prompt may not imitate a wallet, a login screen, or any form that collects credentials.
• Collecting credentialsA prompt may not collect passwords, keys, or any secret from whoever opens it.
• Asking the agent for what it holdsA prompt may not ask the model to reveal its environment, keys, or tokens. Zynora gives the model none of them, and a prompt that asks for them is asking for the wrong thing.
• Instructions aimed at the model itselfA prompt may not try to override Zynora's rules for the model, or ask it to reveal its instructions. Write what you want made instead.
• Mining softwareZynora does not make mining software or anything whose point is to burn someone else's compute.
• Attacking or scanning someone elseZynora does not make anything that scans, probes, floods, or attacks a host.
• Spam, proxying, or mass scrapingZynora does not make anything that sends bulk messages, relays traffic for others, or crawls other sites at scale.
• Pretending to be another brandA prompt may not present itself as another project, exchange, or wallet.
• A promise about price or profitA prompt may not promise profit, returns, or a price. Zynora does not make those claims and neither can anything it makes.
• An airdrop or giveaway that takes a signatureA prompt may not run a claim, airdrop, or giveaway that asks anyone to sign or send anything.
• Trading or financial adviceZynora agents never trade and never give financial advice: no buy or sell calls, no price predictions, no portfolio picks.
• Sexual content involving minorsZynora never makes sexual content involving anyone under 18.

Tips and verified creators

Tips go through ZynoraTips, which passes the ETH to the creator in the same transaction; for a remix, 20% goes to the original creator. Zynora takes nothing and holds nothing. A creator can link a token they launched on Pons; the badge shows only when the Pons factory on Robinhood Chain says that wallet deployed it.

Check a file

Drop a picture or a film on Check a file. Its fingerprint (keccak256 of the file's bytes, the same function Zynora applies when a shard is made) is computed in your browser; the file is never uploaded. The fingerprint is looked up in Zynora's index of confirmed seals, and, failing that, on the chain itself: ZynoraSeal's own proofOf and its Sealed events. A match shows who sealed it, in which block, and the transaction to verify. A file changed by one byte has a different fingerprint, so a resized or re‑saved copy does not match: check the original as it was published. Every result has its own address (/check/<fingerprint>), which the Copy check link button copies.

Daily theme

One theme a day from 00:00 UTC, taken in order from a list the owner keeps.

• EnteringWhen you publish a shard, tick the box Enter today's theme. It joins that day's board with the same seal on chain.
• The boardEvery entered shard whose seal is confirmed on Robinhood Chain, ordered by the ETH tipped to it through ZynoraTips (read back from the chain), then by when it was published. Open the board.
• At 00:00 UTCThe leading shard is written to the history with its creator, its tips and their transactions.
• StreakThe run of consecutive days a creator entered, shown in the vault and on the shard's page.

Dev log

Every deploy writes an entry to the dev log: the date, what changed, and the release it points at; a contract deploy carries its transaction. Nothing there is typed in after the fact.

Token

Zynora has no token yet. Until one is launched and its address is set here, every page says coming soon and no ticker is named. Nothing about a token is a promise of anything.

Updates on X

New features and the numbers on chain are posted by Zynora's only account on X: @Zynora_Studio. Any other account using the name is not us.