THE FORMAT, IN PLAIN SIGHT
Made of account state.
AnyScribe combines original on-chain files with Meteora’s quote-agnostic bonding curves.
One account for the original
The System Program allocates the final account size in a top-level instruction. A 512-byte header holds the creator, mint, denominator, content type, name, description, cursor, and content commitment. The remaining bytes hold the file, unchanged.
The Solana account ceiling is 10 MiB: 10,485,760 bytes. A single AnyScribe account therefore holds up to 10,485,248 file bytes. This is separate from the Token-2022 mint; its metadata URI resolves the on-chain header.
4,096 bytes per v1 transaction
Transactions are compiled as version 1 with Solana Kit 8. Compute limits, loaded-account data limits, and the total priority fee are carried in the message configuration. Resource limits are estimated by simulation, with headroom. There are no address lookup tables or ComputeBudget instructions in the v1 path.
A small file can fit allocation, inscription, verification, pool creation, a first buy, and publication into one transaction. Everything else uploads in canonical 3,500-byte chunks. The final config + mint + pool + first buy + publication is atomic.
Resume from the chain
Each append requires the next offset and the creator’s signature. Repeating an identical confirmed chunk is idempotent; changing it or skipping ahead fails. On resume, the browser compares the RPC cursor and rolling commitment with the selected original file.
H₀ = 32 zero bytes Hᵢ₊₁ = SHA256( "anyscribe:chunk:v1" || Hᵢ || offset_u32_le || chunk )
This is a SHA-256 chain commitment, rather than the conventional SHA-256 digest of the whole file. It can be verified incrementally within Solana’s compute limits, including for a 10 MiB account.
Publication is the final step
The program verifies every byte was uploaded and the commitment matches. Publication also verifies the Meteora-owned pool and config, the creator, the base mint, and the quote mint. Published accounts have no write or close instruction. An unpublished account can be closed by its creator to reclaim its storage balance.
A curve in its own denomination
Every launch creates a fresh Meteora config. Market caps and the first buy are entered in quote-token units. Creator and partner split trading fees 50/50, the base trading fee is 1% with dynamic fees enabled, and migration goes to DAMM v2 with the LP permanently locked. Token metadata is immutable.
Your signing keys
The launch wallet signs in the browser. Its payer, storage, mint, and config keys are saved in an AES-256-GCM encrypted vault using a PBKDF2-SHA256 key with 600,000 iterations. The server only receives public addresses and signed transactions. Export the updated vault after preparing a draft to recover it on another device.
Reading the original
The content endpoint reads Solana RPC data slices and streams the original bytes, with HTTP Range support for audio and video. HTML runs in an opaque-origin sandbox. The metadata endpoint contains the storage address, byte offset, size, and commitment, so readers can reconstruct the inscription independently.
The studio also accepts base64 audio, video, images, and HTML. It decodes the input before upload, so only the original raw bytes count toward the 10 MiB account. Published audio and video can be played either from streamed account slices or from a reconstructed base64 data URI.