What works. What comes next.

Home, catalog, artist profiles, pitch and brand manual in Portuguese, Spanish and English

Astro 7 on a Cloudflare Worker

Published website; expanded local version checked by build and type checks

Artist documents, bank and Pix details are encrypted; the server cannot decrypt them

RSA-OAEP + AES-GCM in the Worker; private key stays on the founder’s Mac

Payment profiles store only the encrypted envelope

Email-code login and master WAV uploads in 20 MB chunks

Worker + R2 storage + Resend email

Code written; waiting for Resend credentials and active R2 storage

AI reads only application type and message and suggests priority; a person decides

TypeSafe (Jev), Worker cron

Disabled until TypeSafe credentials are configured

Two schemas: site for applications, uploads and payment profiles; catalog for rights

Neon, Postgres 18, São Paulo; Hyperdrive connection

7 migrations applied; SHA-256 matches the repository

The website can access only site; catalog is owner-only

RLS enabled; site_writer role

Checked in migrations and access roles

Each music right holder’s share in basis points, from 1 to 10,000

catalog.recording_splits and work_splits, with recording locks

Same basis-point convention as the Solana program

Checks whether an uploaded WAV meets release requirements

TypeScript + FFmpeg

46 tests passed in the inventory review

Label ISRCs, splits, contracts and SGP batches

TypeScript, founder’s local app

58 tests passed (run on October 13)

Calculates tax by country and royalty type

TypeScript

18 tests passed in the inventory review

Recording amount to each holder’s share in integer token units; totals conserve funds

TypeScript, bigint integers, basis points

4 split-rule tests passed, using the same vectors as Rust (42 TypeScript tests in the solana folder)

Creates splits, updates wallets and distributes tokens to holders

Anchor (Rust): create_split, update_wallet, distribute

Deployed to devnet (executable program, checked October 13); 6 end-to-end tests passed on GitHub on October 13View in explorer →

Each paid batch creates a Batch account on-chain with the ledger hash. On devnet, amounts and wallets are public

Batch account of the Anchor program

Batches 601 and 701 read on devnet on October 13: number, amount and hash match the evidence

Writes only the batch hash to the Memo program, after checking it is the one in the Batch account

Memo program (BMZ1 format)

Batch 801 written on devnet on October 13 and read back: same hash as the approved manifest and the Batch account

Rights and statement → risk gate → approval → manifest → signature → payout → receipt, in one batch

TypeScript + Anchor program, run by GitHub Actions

Batch 801 on devnet on October 13, with sample data: the same hash in the manifest, the approval, the Batch account and the Memo; audited by script (25 checks; rejects tampered evidence); dispute before sending and the wait for confirmation tested (5 tests)

Fixed rules and AI check batch and row risks; uncertainty goes to a person and unchecked payments are held

Jev gate (TypeSafe)

7 gate tests; invalid responses block payment; 3 tampered calibration batches

GitHub reruns the checks on code changes

GitHub Actions: website, database, 3 services, Solana TypeScript, Rust and Anchor

6 of 6 stages passed in the October 13 run

Queries Solana without exposing provider credentials

JSON-RPC (Helius); HTTPS required, devnet by default

Tested against a simulated node

Proposed shielded payments, visible to viewing-key holders

Cloak, shielded pool

Integration written; no demonstrated private mainnet payout

Spend with the label card or withdraw in local currency

White-label issuer + USDC/Pix exchange through an authorized institution

No contracted card issuer