LIVECRYPTORECEIVE ANYWHERE_

LIVECRYPTO / DOCS

From wallet signature to the alert on screen.

A practical guide to the product, the wallets it accepts, the Creator Studio, OBS and the payment path. Written for creators and operators, with the current limits stated plainly.

DEVELOPMENT PREVIEWUpdated 5 November 2026

START HERE

What LiveCrypto is, and what it is not.

LiveCrypto is a donation layer for live creators. A viewer opens your public checkout, reviews the network, amount, fee and destination, and signs a transaction in their own wallet. The money moves from the viewer to the wallet you registered. LiveCrypto does not hold a balance for you to withdraw.

The backend creates a payment intent before the wallet prompt, verifies the on-chain result against that intent, records the donation and queues an alert. The alert reaches OBS through a Browser Source. Every step is designed to be visible rather than magical.

  1. Sign in with a wallet

    An EVM, Solana or Sui wallet signs a human-readable message. Signing in proves account control; it does not move funds.

  2. Register a destination

    Save the address that should receive donations on that exact network. Sign-in and payout are separate on purpose.

  3. Share the checkout link

    The public link opens the donation page. Keep the overlay link private: it authorizes access to your alerts.

  4. Connect OBS

    Add a Browser Source, paste the private overlay URL and send a test alert before going live.

OWNER VIDEO SLOTTwo-minute product tour

Reserved for an owner-recorded walkthrough: landing, wallet sign-in, destination, checkout and OBS alert. Replace this block with the final embed; simulated footage must never be presented as a live transaction.

SCREENSHOT SLOTCreator Studio overview

Reserved for a real, current screenshot of the studio using a clearly labelled test profile.

IDENTITY

Three wallet families, one account model.

A creator account can be opened with an EVM, Solana or Sui wallet. The interface discovers wallets in the browser and asks only for a signature. There is no password, email confirmation or seed phrase.

FamilyDetected todaySign-inPayout address
EVMMetaMask, Rabby and other injected wallets announced through EIP-6963EIP-4361 (SIWE) message bound to EVM_CHAIN_ID0x followed by 40 hexadecimal characters
SolanaPhantom, Solflare and Backpack, detected independentlySigned challenge with a single-use nonceBase58 public key
SuiSlush, Sui Wallet and other Wallet Standard walletsSui personal-message signature (ed25519 or secp256k1)0x followed by 64 lowercase hexadecimal characters
  • A sign-in signature proves control of the account. It does not authorize a transfer.
  • The backend derives the Sui address from the public key and verifies the personal-message digest; the frontend sends the wallet’s exact signed text.
  • EVM sign-in is rejected when the wallet is on a different chain from EVM_CHAIN_ID, which closes a cross-chain replay gap.
  • Sign-in and payout are independent: you may authenticate with one wallet and receive on another.

THE CORE FLOW

A donation from click to alert.

A donation is not a single wallet signature. It is an intent, a transaction, a verification and an alert. Each stage has an owner and a visible state, so neither the donor nor the creator has to guess what happened.

01 / AMOUNT

The donor chooses an amount

The checkout shows the network, asset, creator destination, platform fee and network fee. Nothing is signed at this stage.

Checkout stateWhat it meansWhat resolves it
PendingA transaction was submitted but is not confirmedRequired confirmations or a verifier timeout
ConfirmedEvery intent field matched the on-chain resultThe ledger entry and the OBS alert
ExpiredThe intent window closed before settlementA new checkout and a new intent
RejectedAmount, destination, memo or chain did not matchNo ledger entry and no alert

THE WORKSPACE

Your profile, destinations and alert controls.

Creator Studio is the signed-in workspace. It is not a wallet and it does not hold funds. It stores your profile, receiving destinations, alert settings and the token used by OBS.

  1. Sign in

    Choose a wallet, connect and sign the message. Connecting alone does not open a session.

  2. Save a destination

    Pick the network and enter the receiving address. Reserved router, treasury, zero and system addresses are rejected.

  3. Configure the alert

    Choose theme, position, sound, optional media and voice. Settings are scoped to your profile.

  4. Copy the private overlay URL

    Use it only inside OBS. The public checkout link is the one you share with your community.

LinkWhere it appearsWho can use it
Public checkout/pay/{creator} on your site, bio or chatAnyone you share it with
Private overlay/overlay/{token}, copied from Creator StudioOnly your OBS Browser Source; keep it secret

ON SCREEN

One Browser Source. No plugin.

OBS Studio renders LiveCrypto as a normal web page inside a Browser Source. OBS keeps the page open, the WebSocket connection delivers one alert at a time, and the overlay acknowledges each alert after playing it.

  1. Create a Browser Source

    In your scene, open Sources, click + and choose Browser.

  2. Paste the private URL

    Copy the overlay link from Creator Studio. Do not use the public checkout link here.

  3. Match the canvas

    Use 1920 × 1080, or the exact resolution of your stream canvas, so the overlay is not cropped.

  4. Send a test alert

    Trigger the test in Creator Studio and watch the scene. A queued command alone does not prove display.

BROWSER SOURCE / REFERENCE VALUES
URL      https://your-domain/{locale}/overlay/{private-token}
Width    1920
Height   1080
FPS      30
Audio    Control audio via OBS (optional)
Separate sourceAdd to the end of the URLSize
Everything togethernothing1920 × 1080
Alerts only?widget=alerts1920 × 1080
Goal bar?widget=goal1000 × 170
Supporters?widget=ranking420 × 520
Donation ticker?widget=ticker1920 × 80
Subathon timer?widget=timer520 × 220
Paid poll?widget=poll640 × 420

DELIVERY

Queued, delivered, acknowledged.

A verified donation is written to the financial ledger and to an outbox in the same database transaction. Redis publishes a wake-up signal; it does not replace the durable queue. If OBS disconnects, alerts remain queued and replay when the source reconnects.

StateWhat it meansWhat proves it
QueuedThe donation is recorded and the alert is waitingA row in the outbox
DeliveredThe OBS source received the alertThe WebSocket send completed
AcknowledgedThe overlay finished playing itAn ACK from the overlay
  • Alerts are delivered one at a time; a second alert waits instead of overlapping the first.
  • Sound, media and voice are configured per profile in Creator Studio.
  • Any past alert can be replayed from the Studio history. A replay shows again on stream but never counts twice in the goal, the ranking or the supporters.
  • A subathon timer counts down on stream and every confirmed donation adds time: a fixed number of seconds on any network, plus seconds per R$ 1 on mainnet. Test alerts and replays never add time.
  • A paid poll asks viewers a question with 2 to 5 options. While it is open, the donation page offers the options and each confirmed donation that picks one votes: R$ 1 = 1 vote on mainnet, 1 vote per donation on test networks. Results are counted from confirmed donations, so nothing counts twice.
  • After OBS starts, keep the source visible long enough for the overlay to load and connect.
  • A missing alert is diagnosed from the outbox state, not from assumptions about the scene.

MONEY PATH

Non-custodial by design, gated by evidence.

LiveCrypto is non-custodial. The checkout creates a payment intent that snapshots the creator, chain, destination, sender, amount, fee, memo and monitoring cursor. A transaction settles only when every field matches.

RailCurrent stateGate
EVMTestnet code path; router and treasury must be configuredDONATIONS_ENABLED=true, deployed router, confirmed DonationRouted event
SolanaDevnet code path; finalized native split transferDONATIONS_ENABLED=true, treasury and cluster genesis hash match
Sui identitySign-in and payout registration availableSUI_NETWORK configured; no Move router required
Sui checkoutImplemented; enabled only when configuredPublished live_crypto Move package, SUI_PACKAGE_ID and SUI_TREASURY_ADDRESS
  • The proposed platform fee is 2% (PLATFORM_FEE_BPS=200), displayed separately from the network fee.
  • The creator portion goes to the registered destination; the fee goes to the configured treasury.
  • The donor’s wallet shows the network fee before signing. LiveCrypto cannot refund an on-chain transfer.
  • The browser only receives public RPC endpoints; URLs that contain provider keys stay on the server.

MOBILE ENTRY

The QR opens the checkout, not a wallet.

Typing an address on a phone is error-prone. The mobile entry is a QR code that encodes the public checkout URL for the creator. Opening it loads the same checkout as the shared link, with network, amount, fee and destination visible before anything is signed.

A QR containing only a raw wallet address would skip the payment intent, the fee disclosure and the alert attribution. LiveCrypto does not use a bare-address QR for donations; the checkout remains the source of truth.

  • Creator side: Creator Studio shows the QR of the public checkout next to the link, with PNG and SVG downloads. It is generated in the browser; no external service sees the URL.
  • Donor side: the phone camera opens the checkout; a wallet-capable browser or wallet app signs the prompted transaction.
  • Server side: the same intent and verifier run; the QR adds no trust and no shortcut.
  • Amount or memo parameters are only accepted after the checkout validates them server-side.
QR PAYLOAD / CHECKOUT URL ONLY
https://your-domain/{locale}/pay/{creator}

Never encode: private keys, seed phrases, overlay tokens,
or a bare address that skips amount, fee and destination review.

TRUST

What we protect, and what you must verify.

Security starts by keeping secrets out of the browser. Sessions are HttpOnly, SameSite=Strict cookies rather than tokens in localStorage. Nonces are single-use, auth and payment routes are rate limited, and private RPC URLs never leave the server.

  • Sign in only on the domain you expect, and read the origin in the wallet prompt.
  • Never enter a seed phrase or private key. LiveCrypto never asks for either.
  • Review the payout destination on the exact network before saving it.
  • Treat the overlay token as a password and rotate it after sharing a screenshot.
  • As a donor, read the network, destination, amount and fee before signing.
  • Confirm whether you are on the intended testnet or mainnet; chain IDs are not interchangeable.
  • Blockchain transfers are generally irreversible. There is no platform balance to reverse.

RUN IT

Two Node processes, four local services.

The repository runs an Express API and a Next.js web app. PostgreSQL and Redis are optional in preview mode and required for persistent accounts, sessions and the durable alert queue. Node.js 24 and npm are the only mandatory prerequisites.

POWERSHELL / FROM THE REPOSITORY ROOT
.\start-dev.bat          # preview: temporary data, payments off
.\start-dev.bat --full   # Docker PostgreSQL + Redis, persistent data
.\start-dev.bat --check  # localized pages, API and assets, then stop
ServiceDefault URLNotes
Web apphttp://localhost:3000Next.js; 17 static pages in the production build
APIhttp://localhost:8080Express; health, auth and payment endpoints
PostgreSQLlocalhost:5432Persistent mode only
Redislocalhost:6379Sessions and alert wake-ups
VERIFY BEFORE YOU TRUST A BUILD
cd backend ; npm test
cd frontend ; npm run test:i18n ; npm run lint:product ; npm run build
cd contracts ; npm test

EVIDENCE

What is proven, and what is still pending.

The honest status on 5 November 2026: the protocol paths are implemented and tested, the production build passes, and the browser journey has been exercised with simulated wallets. Real wallets, a real OBS scene, a real testnet donation, TLS, backups and an independent audit are still pending.

AreaStateEvidence
Sui identityVerified in code and testsed25519 and secp256k1 signatures, digest, address derivation and tamper rejection
Multi-wallet UIImplemented; simulated browser journeyWallet Standard test wallet over CDP; the Solana picker lists three brands
EVM / Solana checkoutTestnet code paths; real funds not exercisedBackend verifier tests and RPC fixtures
Sui checkoutImplemented, not yet validated on testnetMove package publication and a real-wallet testnet donation
OBS end-to-endPendingNo real OBS scene has been run in this environment
Production deploymentNot validated hereCompose stack defined; no VPS or TLS run recorded
Security auditPendingAutomated tests and internal review only
OWNER VIDEO SLOTValidation walkthrough

Reserved for a recorded end-to-end run: testnet checkout, confirmation, ledger entry and OBS acknowledgement. The recording should show the network and the testnet badge at all times.

LIVECRYPTO / DOCS

Ready to connect OBS?

Sign in with the wallet you use for the destination, copy the private overlay URL and run a test alert before your next stream.

Open Creator Studio

Development preview · payments disabled by default · no mainnet claim