Documentation

• ✓One-click token launch (OP_20 contract, fixed supply)
• ✓Automated Risk Card (Bob AI security audit)
• ✓Live pool trading — wallet-signed swaps on OP_NET testnet
• ✓Watchtower monitoring after contract deployment
• ✓Trading Floor — live community chat, callouts, charts
• ✓Achievement badges and leaderboard gamification
• ✓OP721 shop collection — wallet-bound NFT items
• ✗Mainnet support (pending OP_NET mainnet launch)

1. 1

   Connect your wallet

   Click "Connect Wallet" in the header. Supports Unisat, OKX, and OPNet Plugin. For quick testing, enter a testnet address manually.

2. 2

   Create a token

   Click "+ Create Coin", fill in name / ticker / supply / description. Takes ~10 seconds.

3. 3

   Run Security Checks

   On the token page, click "Run Security Checks →". Bob AI will scaffold and audit your OP_20 contract. Takes 15–60s.

4. 4

   Read the Risk Card

   Once checks complete, review your Risk Card score (0 = safe, 100 = critical). All OpStreet tokens default to LOW RISK because the template has no mint / no admin / no pause.

5. 5

   Deploy & trade

   Deploy your token to OP_NET testnet, create a liquidity pool, and start trading with live pool quotes.

When you create a token, you provide:

• Name — full display name (e.g. "Orange Protocol")
• Ticker — 2–10 uppercase characters (e.g. "ORP")
• Max Supply — fixed forever, cannot be changed after launch
• Decimals — typically 18 (like ERC-20)
• Description — 10–2000 chars, shown on the token page
• Links — optional website, Twitter, GitHub

• ✓No mint() function — supply is fixed at deployment
• ✓No owner/admin key — no privileged addresses
• ✓No pause() — transfers are always enabled
• ✓No upgrade mechanism — contract is immutable
• ✓100% supply minted to deployer at deployment

When you submit the form, OpStreet creates a project record in the database. The actual OP_20 contract (AssemblyScript) is generated when you run security checks. The generated contract uses the btc-runtime OP_20 base class from OP_NET.

Bob generates your OP_20 contract in AssemblyScript using the fixed-supply template. The generated source code is hashed and stored as the buildHash. This ensures the contract is deterministic — the same inputs always produce the same hash.

Bob audits the generated contract for security issues. The audit checks for: mint functions, admin keys, pause mechanisms, upgrade patterns, reentrancy, and more. Results are stored as the riskCard JSON and a numeric riskScore.

• Run checks until the project reaches READY
• Start launch-build to prepare the deploy artifact
• Submit the deploy transaction from your wallet and wait for watcher confirmation
• Create the pool from your wallet and wait for on-chain confirmation
• Trading unlocks only after the project reaches LIVE

Once a token is live, pricing uses constant-product AMM quotes from indexed pool reserves. Candles, volume, and player stats all derive from confirmed trade fills.

• ✓Live presence — see who's on the floor right now
• ✓Avatars — pick an emoji avatar when you join
• ✓Callouts — post 280-char alpha signals with up/down reactions
• ✓Trollbox — real-time chat (3s cooldown, spam detection)
• ✓Ticker tape — top live projects ranked by indexed market activity
• ✓Chart panel — live OHLC candles from confirmed trade fills
• ✓Live trading — wallet-signed swaps against pool reserves

Connect your wallet, then visit the Floor. A modal will appear asking for your display name and avatar. Your presence is tracked for 5 minutes after your last heartbeat — if you close the tab, you leave automatically.

• Maximum 280 characters per callout
• 2-hour cooldown between callouts (prevents spam)
• Up to 50 reactions per callout (UP or DOWN)
• Posting 10+ callouts unlocks the "Caller" avatar
• Posting 50+ callouts unlocks the "OG" avatar

If you don't have a wallet extension, you can paste a testnet Bitcoin address directly. Manual mode lets you browse launch pages, but you cannot sign transactions or verify identity (no BIP-322 signing without a wallet).

After connecting, click "Sign to verify" in the wallet dropdown. Your wallet signs a message with your private key (no funds moved). The backend verifies the signature and issues a session JWT cookie. Verification is required for:

• Entering the Trading Floor
• Posting callouts and chat messages
• Running security checks (quota: 5/day per wallet)

Click the wallet address button in the header → select "Disconnect". This clears your local session and logs you out of the API. Your token and floor data are preserved in the database.

1. 1

   Get testnet BTC

   Visit faucet.opnet.org to get 0.05 tBTC every 24 hours on OP_NET testnet.

2. 2

   Enter amount

   On the token page, enter how many sats you want to spend in the Buy panel.

3. 3

   Get a live quote

   OpStreet API returns a constant-product AMM quote from the live pool reserves, including price impact and fees.

4. 4

   Sign with wallet

   Your wallet extension (Unisat/OKX/OPNet) signs the swap transaction. No private key ever leaves your device.

5. 5

   Broadcast

   The signed transaction is broadcast to the OP_NET network and executed against the pool contract.

6. 6

   Confirmation

   The watcher confirms the trade on-chain. Your fill, candle data, and stats update automatically.