Receipts docs
v1.0.0
Live demo Get help
● Reference · Versions

Changelog
what changed, when.

Every release, newest first, and how to update. Read the entry for your target version before you update.

011.0.0 · 2026-09-29

Current First CodeCanyon release. It contains everything built during development (listed below under Development history) plus the changes listed here. Built only from the project's git history.

Changed

  • Version 1.0.0. package.json and /healthz report 1.0.0.
  • Licence. LICENSE.md now points at the Envato Market licence (Regular or Extended) you buy on CodeCanyon.
  • Admin console. Viewers can open the marketplace pages inside the console (Operations, Payments, Providers and the rest); every change there still needs a manager.
  • Pages are sent with Cache-Control: no-transform, so a CDN in front of the site never rewrites them.
  • Demo mode. The demo console logins read stored passwords through one helper. Affects DEMO_MODE=1 only.
  • SPEC.md is written for buyers.
  • .env.example documents DEMO_PUBLIC.
  • First run. One setup code claims the site and creates the console owner; setup codes print also with WORKERS=0; a fresh install writes no admin-import.json.

Fixed

  • Phones. The Method page and the become-a-provider Studio page no longer scroll sideways.
  • Checkout. The payment-method icons have a fixed size; before, an unsized icon could fill the whole option.

Known limits

  • 107 automated tests pass and the typecheck is clean on this release.
  • Stripe is tested with synthetic webhook events only, not with a real Stripe account. Make one small test payment in Stripe test mode before you go live.
  • The Telegram bot (account linking, delivery, VIP groups, publishing) is covered by unit tests but has never been run against a real bot token. Test it with your own bot first.
  • The Ubuntu, systemd and Caddy steps in Installation and Deployment are standard procedures that were not run while writing these docs.

02Development history

Pre-release builds from 2026-09-23 to 2026-09-25. They were never sold, so there is nothing to migrate from; the list shows how the 1.0.0 feature set came together.

0.4 · 2026-09-24 to 2026-09-25

  • Admin console: the MIKODES Admin Kit 0.3.0 at /admin with roles, two-factor, audit log, history, export and import, status checks and a revenue centre; the ledger CSV and the database backup are owner-only.
  • Payments without card keys: bank transfer and USDT/USDC to your own wallets with an approval queue; plans of 1 to 12 months, trials, coupons, referrals.
  • Notifications: in-app centre, follows, keyless Web Push with the site's own VAPID keys, installable web app.
  • Redesign with an app shell, ⌘K search and themes; paper portfolio, charts, calculator, provider analytics, operator dashboard.
  • Demo: five labelled strategy bots on live prices (EMA, RSI, Donchian, Bollinger, MACD), one-click demo logins, a public read-only demo mode (DEMO_PUBLIC=1).

0.3 · 2026-09-23 to 2026-09-24

  • Provider signatures with an Ed25519 key made in the provider's browser; a signed seal re-runs the market check.
  • Anchoring every 10 minutes by default (configurable), late performance-billing catch-up; 18 fixes from an internal review of signing, billing and anchoring.

0.2 · 2026-09-23

  • Provider Pro and verification, refunds and disputes, OpenTimestamps proof upgrade to a Bitcoin block, operator claim by ADMIN_EMAIL or setup code, sign-in limits keyed on the visitor address.

0.1 · 2026-09-23

  • Core: sealing and hash chains, the follower-honest resolver, statistics, OpenTimestamps, the database schema; the web app, Stripe, Telegram, background jobs, the verifier and integration tests.

03How to update

  1. Read the changelogFor your target version.
  2. Back upThe databases and .env (how).
  3. Stopsudo systemctl stop receipts
  4. Replace the program filesKeep your .env and the data/ folder.
  5. Installsudo -u receipts pnpm install --frozen-lockfile (or npm install).
  6. Startsudo systemctl start receipts and watch journalctl -u receipts -f.

The database schema is applied automatically at start-up. If a release needs a manual step, its entry says so. If you changed code, keep your changes in git so an update is a merge.