Your signal marketplace. Every call has a receipt.

Providers sell signals, subscribers pay them monthly, and you take a commission on every payment. Each signal is sealed the second it is published, timestamped in Bitcoin and scored from real market prices, so a track record is evidence, not a screenshot.

Try the live demo Open the demo admin panel Read the docs

One click, no password: try it as operator, provider or subscriber. Real market prices, labelled strategy bots, sandboxed payments. Hosted on our own machine, so it can be briefly offline.

Signal marketplace
source code
self-hosted
16 docs pages

Receipts home page of the live demo with a sealed signal card and live counters

Revenue calculatorWhat could it earn you?Your users, volume and fee — the caps come from the code.Revenue calculator →

commission cap in code≤ 50%

A sealed receipt in the live demo on a phone: sealed, batched, waiting for a Bitcoin block

A Receipts signal card: the sealed / batched / Bitcoin status strip, the open SHORT BTCUSDT receipt with source, entry, stop, target, expiry and fill, the chart with entry, stop and target drawn on it, and the Verify, Proof JSON and .ots actions.

The product's own receipt view. The seal, the hash chain and the timestamp proof are what the buyer is paying for, so this is the screen that has to be legible.

Built on

Node
SQLite
OpenTimestamps
USDT/USDC on 6 chains
Node
SQLite
OpenTimestamps
USDT/USDC on 6 chains
Node
SQLite
OpenTimestamps
USDT/USDC on 6 chains
Node
SQLite
OpenTimestamps
USDT/USDC on 6 chains

PublishA provider posts from the Studio, Telegram or a TradingView alert.
SealSHA-256, chained to the previous signal; the database refuses edits.
AnchorEvery 10 minutes by default, a Merkle root goes to OpenTimestamps and into Bitcoin.
MeasureResults come from public 1-minute candles, at a price a follower could get.

Business plan

A signal marketplace.
You keep the take.

Buy the source code once. Run it under your brand. The revenue lines are already in the code — they pay you, not us.

01Buy the sourceMarketplace, provider studio, verification, admin.
02Brand itYour commission, plans and payment methods in the console.
03LaunchOne small VPS with SQLite.
04GrowRecruit providers; each brings subscribers.

Who runs it

Trading communities with signal providers
Crypto media and educators
Operators of paid Telegram channels

Where the money comes from

CommissionOn every subscription payment
Provider ProPaid plans for providers

Running costs One small VPS.

Earnings calculator

What could Receipts
earn you?

Move the sliders. Caps come from the code; prices and traffic are yours to set.

Signal providersPaying subscribers per providerSubscription price / monthYour commissioncap in code: 50% · off by defaultProvider Pro plansPro plan price / month

Realistic example · revenue per month

—

— per year

Commission
Provider Pro

Est. running cost—

Left for you / month—

Buy source code Live demo

Example scenarios, not a forecast or a promise. Your revenue depends on your providers, their subscribers and your work. Signal services are regulated in some countries; trading carries risk for your users.

For the buyer

You run the marketplace.
You keep the take.

Commission on every subscription payment, set by you — off by default, capped at 50% in code.
Optional paid Provider Pro plans and a verification fee for providers who want the badge.
Labelled sponsored rows and per-venue trade links; sponsorship never changes the ranking.
Operator console from the MIKODES Admin Kit: fees, payment methods, plans, payouts, ledger with CSV, team, 2FA and audit log.

≤ 50%commission cap in code

6chains for USDT/USDC

1 fileSQLite, one small VPS

Operator operations page with payments, providers, members and ledger

Open the operator demo →

What is in the box

Everything a signal business needs.
Nothing it can fake.

Receipt page: the sealed signal card and the candle chart the result was computed from

Sealed receipts

Every signal and every change is a new sealed event with its own public page, chart of the candles it was scored on, proof JSON and .ots file.

Public verifier showing a proof bundle that matches the seal

Verify in the browser

/verify recomputes the hash, the provider's signature and the Merkle path locally. An offline script and the reference ots client do the same.

Provider Studio

Publish and seal, plans and free trials, analytics, payouts, a public badge, and an optional Ed25519 signing key made in the provider's own browser.

Leaderboard: providers still building the public record needed for ranking

Ranked by evidence

By default the leaderboard needs 30 closed signals and 60 days, shrinks short lucky runs toward zero, and paid placement never changes the order.

Payments without lock-in

Stripe with your keys, bank transfer, or USDT/USDC straight to your own wallet on 6 chains, with an approval queue. Coupons, 1-, 3-, 6- and 12-month plans, referrals.

Delivery

Telegram VIP chat gating with personal join-request invites (a forwarded link is useless) that end with the subscription, Discord, Web Push with your own keys, and an installable web app.

The rest of the product

What you cannot see from the front.
The operator side, the studio, and what fails loudly.

The demo shows the reader's side. These are the three screens a buyer actually has to judge: where the money is set, how a provider connects, and what the product says when a check fails.

What does the operator side look like?

Receipts operator console, Marketplace fees: commission on subscriptions in basis points with the hard cap the server enforces, Provider Pro per month, a one-off verification fee, performance billing and a lowest monthly price, each with the cap written next to it.

The console's own words: everything is off until you set it, providers see each fee on the pricing page, and every share has a hard cap the server enforces.

What does setting it up involve?

Receipts provider studio, Automation: the webhook address to POST signals to, a TradingView alert message template, a Telegram panel showing no bot connected yet, a Discord channel webhook field and an embeddable live badge.

How a signal provider publishes from their own tools. The Telegram row says plainly that no bot is connected on this site.

What happens when something goes wrong?

Receipts Status page: one failing check with a Fix button, then blocker and warning rows for wallet addresses, Stripe keys, signal pricing, seal batching, the Telegram bot, OpenTimestamps calendars and Bitcoin confirmation, each with when it last ran.

The product's own health checks. Blockers stop a launch, warnings are worth a look, and each row says what it measured and when.

What does it look like on a phone?

Feed

A single receipt on a phone: the signal, its hash, the seal and the result computed from the market

A receipt

Verify

The reader's three screens. Nothing here needs an account to check a receipt.

Desktop and phone

One product.
Every screen it ships.

Real screens from the Receipts demo build, on the devices your users will hold.

Interactive tour

See every screen.
Then try it live.

Real screens from the product. Click a screen to enlarge it.

Try the live demo Documentation Buy source code

The live demo, as a visitor sees it.

Real market prices, labelled strategy bots, a public record anyone can check.

Open it live →

Operator console

A marketplace is a thing you operate.
This is the room you operate it from.

Sign in to the live console and look around before you buy. It is the same console that ships in the source — nothing here is a mock-up.

MoneyThe commission you take on every provider payment, with the hard cap that lives in the code.

RevenueRealised payments only, with a reference for each one. An unmeasured ratio shows a dash, never an estimate.

ProvidersWho may publish signals, what they may charge, and the moderation queue when a call is disputed.

AuditOperations, anchors, status, audit log and history — every change with who made it and when.

receipts-demo.mikodes.com/admin

Open the operator console How the console works

This one is a read-only demo: it refuses every change in the server, so nothing you click can break it for the next visitor. On your own install the same screens write for real.

Honest by construction.

KeylessNever trades for anyone and never holds funds. Payments go to your Stripe or your wallet.

No backdatingResults are measured from the server's seal time, after a reaction window, with fees and slippage on each side.

Profit claimsNone. No invented ROI, no seeded providers; the demo uses labelled strategy bots on live prices.

Your rulesSignal services are regulated in some countries. Country blocking and a risk notice are built in; the law is yours to check.

Anything published in a provider's name without their key shows as unsigned or as a key change, including by the operator.

Documentation

Installed in an afternoon.
Every step written down.

16 pages written from the real code — requirements, install, configuration, deployment, troubleshooting.

Documentation

Start

Set up

Ship

Reference

Buy source code

Own Receipts.
Ship it as yours.

Full source code, yours to rebrand and run
Documentation — 16 pages, also online
A live demo to click through before you pay
Item support through CodeCanyon

Installation & customization

Want it installed on your servers, rebranded or extended? The team that built it does that — write to us.

Telegram E-mail

Receipts · source code

Coming to CodeCanyon

MIKODES on CodeCanyon

The source code will be sold on CodeCanyon (Envato Market).

Click through it yourself.

Try the live demo Documentation Operator console Buy source code Verify a receipt

Live demo runs from our own machine and may be briefly offline · source code coming to CodeCanyon

Installation & custom work

The download is not the end of it.
Tell us what you need.

The code is sold on CodeCanyon. The work around it — getting it live, changing it, or building you something of your own — is ours, and it starts as a conversation on Telegram, not a form.

Install it for me

You bought the code and you want it running, not a folder of files.

On your own servers, your domain, your keys
Your name and colours, not ours
Handed over working, with what we changed written down

Add features

Receipts plus the one thing it does not do yet.

A screen, a chain, a payment method, a report
Built into your copy, so updates still apply
We say up front if it is a bad idea

Build something custom

A product of your own, on foundations that already work.

Starts from what is proven here, not a blank page
Yours alone — we do not resell it
Same standard as the products on this page

MIKODES is a Slovak company and has been selling on CodeCanyon since April 2019. 17 products run in the open at mikodes.com — Solana, Hyperliquid, Base, Telegram and WordPress. Tell us what you need and we will tell you what it takes; we will also say when we are the wrong people for it.

Talk to us

Start the conversation.

Telegram is fastest and it reaches the person who built this, in English. Describe what you need and you get an honest answer about what it takes. The source code itself is sold on CodeCanyon.

Telegram · fastest

Talk on Telegram

E-mail

For installation and customization quotes.

Other MIKODES products