The field guide
How biological births, market routes, and provenance work in BIO-MARKETS.
01 / Prepare a birth
Choose an origin, paste a supported sequence or import a structured file, and confirm your rights and consent. The browser validates format and derives aggregate measurements locally. Bounded four-line FASTQ and single-record protein FASTA are supported. Compressed, wrapped FASTQ and unsupported proprietary files are rejected.
02 / Keep sensitive input private
The browser creates a cryptographically random private salt and a domain-separated SHA-256 commitment. Raw input and salt remain local. Download your private receipt if you want to independently reproduce the commitment later. Hashing biological data alone does not make it anonymous.
03 / Review and launch
The launch client constructs the protocol transaction using live mainnet state. Inspect metadata, venue, wallet, estimated network costs and protocol details. Your wallet signs. A launch becomes a registered birth only after successful chain confirmation and server verification. Metadata hosting and registration require the configured database.
04 / Trade through the correct venue
Ungraduated tokens use the native bonding curve. Supported migrated tokens use the supported liquidity pool. Other routed swaps use swap routing within shared service limits. Quotes expire; amounts and slippage are shown before signing. Protocol fees are included in estimates. No additional platform trading fee is charged by this application.
05 / Understand evidence levels
Community Submitted means a claim is self-reported. Format Validated means the local parser accepted the structure; a client claim alone does not authenticate its source. Public Dataset requires an independently accessible source. Token-bound provider/lab claims require signed attestations from explicitly trusted issuers. The separate SMART Health Card verifier checks a provider document signature; it does not establish accreditation or connect that document to a token.
06 / Deployment configuration
The Settings page reports configured integrations. DATABASE_URL, SESSION_SECRET, NEXT_PUBLIC_APP_URL, and an appropriate Solana RPC are needed for persisted launches and signed community sessions. Service configuration is managed by the application operator.
07 / Current limits
Creator tools support user-approved fee claims and permanent fee splits to reviewed recipient wallets. Wearables support private local imports and wearable account authorization using your existing application credentials. Provider documents can be verified locally. Wallet PnL reports coverage gaps and unknown costs; complete accounting depends on available history and supplied cost basis. Admin tools and closed-browser alerts are excluded. External market listings are not certified biological markets. Research listings are public scientific references, not endorsements.