Buyer's guide ยท Receipts

Trading signal marketplace source code with sealed, timestamped records

Receipts is self-hosted Node.js and TypeScript source code for a marketplace where traders publish trading signals and subscribers follow them. Every signal and every later change is a sealed event in a SHA-256 hash chain, batched into Bitcoin timestamps through OpenTimestamps. Results are computed from public market candles, so providers cannot type in their own. You run it under your own brand, with providers, subscriptions, payouts and an operator console.

What you get

  • The full source code

    The TypeScript server, the web front end, the bundled operator console, 194 automated tests in 15 files, an .env.example and the documentation.

  • Sealed signals

    Each signal and each change (stop move, close, cancel) is a new event chained to the provider's previous one. The database refuses edits and deletes, and a 128-bit nonce keeps hidden signals unguessable from their public hash.

  • Bitcoin timestamps

    New seals are batched every 10 minutes (configurable) into a Merkle root and submitted to free public OpenTimestamps calendars, then upgraded once a Bitcoin block confirms them.

  • Verification by anyone

    The hash, signature and Merkle path can be recomputed in the browser or with an offline Node script. The .ots file verifies with the reference ots client.

  • Optional provider signatures

    Providers can sign events with an Ed25519 key made in their own browser. Anything published without that key shows as unsigned or as a key change.

  • Results from market candles

    Computed from public 1-minute candles (Binance and Bybit, keyless) with a reaction window, stop-beats-target inside one candle, gaps at the worse open, and fees and slippage per side.

  • Evidence-based ranking

    A leaderboard that needs a minimum record and shrinks short lucky runs toward zero, with a by-market breakdown, average hold, worst streak and a monthly heatmap. Sponsorship never changes the order.

  • Commit-reveal visibility

    Hash, sequence and time are public at once. The body is revealed on close or after 24 hours, while paying subscribers see it live.

How an operator runs it as a marketplace

Receipts is a self-hosted product you run under your own brand, with providers who publish and subscribers who follow.

  • Provider Studio

    Providers publish and seal signals, set plans (1, 3, 6 and 12 months) and free trials, see MRR, subscribers, followers and churn, request payouts and embed an SVG badge.

  • Publishing from other tools

    A TradingView alert webhook with a per-provider token, or posting to a chat bot. The bot parser is unit-tested but has never been run against a real bot token.

  • Payments to you

    Stripe subscriptions with your own keys, or bank transfer and USDT/USDC to your own address with an approval queue. Coupons, trials and refunds are supported, and refunds reverse the split.

  • Operator console

    Built on the MIKODES Admin Kit: branding, legal pages, marketplace fees, payment methods, a ledger with CSV export, provider verification, member roles, team roles, 2FA, an audit log and settings import and export.

  • Subscriber side

    Follow, a live feed, notifications and Web Push with your own VAPID keys, an installable web app, a paper portfolio from real results and a position-size calculator.

  • Referral programme

    Off by default. It pays a share of your commission, never the provider's, with an optional second tier and a payout threshold.

  • Compliance tools

    Country blocking through the proxy's country header, a risk notice on every page, terms and privacy pages, and maintenance mode.

What it needs to run

None of these is included in the price.

  • Node.js 20.12 or newer and pnpm; build tools only if better-sqlite3 has no prebuilt binary for your platform
  • A server with a persistent disk; a 1 vCPU, 1 GB RAM VPS is enough, and serverless hosts without a disk will not work
  • A domain with HTTPS through Caddy or nginx, with PUBLIC_URL and TRUST_PROXY set
  • No API key for prices or timestamps: it uses public Binance and Bybit candles and public OpenTimestamps calendars
  • Optional: your own Stripe account, a chat bot token for delivery, group gating and publishing, and your own bank account or USDT/USDC addresses

What it does not do

  • It never trades. It does not connect to anyone's exchange account and never holds funds.
  • Stripe was tested with synthetic webhooks only. The chat-bot publishing and the VIP group gating have not been run against a real bot.
  • Market data covers crypto candles from Binance and Bybit. Forex or stock data is not included; add your own licensed provider.
  • Signal services are regulated in some countries. Legal advice is not included, and you must check the rules where you operate.
  • Hosting, the domain, the TLS certificate and any third-party account are not included.
  • Demo mode, with its labelled strategy bots and sandbox checkout, is for demos only and must never be used on a live site. A real install starts empty.
  • Provider signatures rely on the page code your site serves, so the operator is part of the trust chain.

Questions

Can providers fake or edit their results?

They cannot type in results: those are computed from public market candles. Signals and changes are sealed in an append-only hash chain that the database will not edit or delete, and the seals are timestamped on Bitcoin through OpenTimestamps.

Does it place trades or hold money?

No. It never trades or connects to an exchange account. Stripe pays into your Stripe account, and bank and stablecoin payments go straight to you, with an approval queue where you confirm them.

Can anyone verify a record without trusting me?

Yes. The hash, signature and Merkle path can be recomputed in the browser or with the offline Node script, and the .ots file verifies with the reference ots client.

Does it need paid data or API keys for prices?

No. It uses public Binance and Bybit candles and public OpenTimestamps calendars. Forex and stock data are not included.

Is there a hosted version I could just rent?

No. Receipts is self-hosted source code. You run it on your own server with a persistent disk, behind HTTPS, under your own brand.

How much does Receipts cost, and what does the licence allow?

$99, one payment, no subscription. One licence, no tiers: any number of projects and clients, a paid SaaS, every line changed. The only limit is reselling or publishing the source code itself. The services you connect bill you directly. See the licence.

Is setup included?

Yes. We install Receipts for you and put in your logo, colours and texts. Bigger changes or new features get a fixed price before we start.

What if it does not work?

Write to us within 14 days. We fix it, usually the same day. If we cannot fix it within 7 days, you get your money back. See the refund policy.