Meaning in
every mark.
The rune is an identity. The dossier is a trail. BN RUNES brings supply, issuance limits, source evidence and BNB launch planning into one reviewable record.
A name, with boundaries.
Each launch begins with a name, a ticker, a finite canonical supply and a purpose. The forge keeps these together as a versioned launch dossier for BNB Chain, chain ID 56.
BN RUNES is a rune-inspired BSC project. Its public Bitcoin observatory reads block and fee data from mempool.space ↗. Observing Bitcoin does not create a Bitcoin Rune, bridge an asset or establish a reserve.
| Available now | Opens after integration |
|---|---|
| Launch identity, limits and budget studies | Token issuance and live curve transactions |
| Public Bitcoin block observations | Automated ownership or reserve attestation |
| Browser-local dossiers and Agent review briefs | Public project indexing and automated reward distribution |
Genesis Folio entries are editable design studies, with no issued tokens or trading markets. Saved records belong to this browser; exported files are portable copies.
Limits are part of the identity.
- Canonical supply: the proposed total, between 100 and 1,000,000,000,000 whole units.
- Issuance lot: a proposed unit amount per issuance action, at least one unit and no greater than the wallet ceiling.
- Per-wallet ceiling: a proposed maximum holding allocation, no greater than the canonical supply.
- Network: BNB Chain, chain ID 56. A Bitcoin source reference does not change the execution network.
The launch contract must independently enforce the final limits. Saving a dossier or submitting a theme parameter event does not issue tokens, enforce a cap or reserve an allocation.
The budget is inspectable.
The forge uses a linear marginal-price study. Supply, target BNB budget and slope determine the opening price. The allocation slider calculates cumulative units and the corresponding budget from zero to that allocation.
T = net curve target in BNB
s = selected slope, from 0 to 10
p₀ = T / [Q × (1 + s / 2)]
p(q) = p₀ × (1 + s × q / Q)
R(q) = p₀ × [q + s × q² / (2Q)]
Gross budget = R(q) / 0.97
Tax budget = gross budget − R(q)
The 3% tax is an issuance proposal used for the budget study. The slippage allowance adds the selected percentage to the gross budget; it is a maximum planning allowance, not an extra tax. Gas is excluded.
This curve is a mathematical launch design. It is not a live market quote, the current FLAP pricing formula or a promise of price growth. Final launch settings and execution quotes must be checked at the time of any transaction.
A reference is the beginning.
A dossier may include a Bitcoin transaction-output reference, a Rune block-and-transaction index, a public HTTPS evidence URL and review notes. An attached link only means the link is present; it does not mean the underlying claim has been verified.
- Identify the original network, source transaction and asset.
- Verify ownership and the exact amount at a stated time.
- Document custody, redemption conditions and independent verification.
- Keep unresolved questions visible before any issuance or distribution.
Records can be saved while evidence is missing. Their Agent brief preserves the missing fields and requires independent checks. The record fingerprint uses SHA-256 when the browser supports it; it identifies the saved parameters and is not an on-chain attestation.
Funding follows a published plan.
The BNR issuance plan proposes a 3% trading tax to support holder and contributor rewards alongside token recovery. No fixed split, reward amount, price outcome or automatic distribution is promised.
| Stage | Required record |
|---|---|
| Revenue | Final token tax configuration and designated FLAP vault after issuance. |
| Budget | Published reward period, eligibility, available assets and recovery budget. |
| Execution | Project-managed distributions or token recovery, with transaction evidence. |
| Review | Compare the announced plan to actual expenditure; defer actions when funding or eligibility is unresolved. |
VAULT rules and WITHDRAW fund management
The theme vault uses a configured primary wallet and an authorized backup wallet. Either can independently call the management withdrawal methods. Funds go to the calling authorized wallet. Other addresses cannot use those methods.
These methods manage project funds; they do not automatically distribute assets to all holders. Theme operations record submitted parameters through events. They do not execute rune issuance, bridging, trading, rewards or token recovery.
Different roles.
Different addresses.
BN RUNES FLAP vault factory
The factory creates project theme vaults. Its address is not the BNR token address and cannot be used as a mint, swap or rewards endpoint.
Deployment details will be published here.Token, project vault and launch execution
The official token and project-vault addresses will be published after issuance. Live rune minting, curve trading, bridge services and automated rewards require their own execution contracts and integration.
Theme parameter operations
The factory's theme vault exposes six event-recording operations: rune identity, issuance plan, curve plan, reserve evidence, reward plan and recovery plan. Each writes the submitted parameters to an event and requires gas. Final vault access must use the issued project's vault address.
Pass context, not blind instructions.
The forge creates an English brief from the current draft or an opened sealed record. It contains the identity, exact limits, curve study, evidence references, version and record fingerprint.
The default handoff requests a read-only review. Your Agent should identify missing evidence and check the official addresses, deployed code and ABI. If launch status or an execution address is missing, it must stop before signing or sending funds.
Wallet connection, minting, bridging, approvals and trading are separate actions. A subsequent transaction requires its own verified network, recipient, value, gas preview and explicit instruction.
Prepare an Agent brief ↗