Architecture
A Solana gateway, a public-proof index and a separate radio research surface.
Solana is the settlement ledger
Next.js route handlers use @solana/kit for RPC reads, message compilation and transaction decoding. RPC credentials stay in server-only environment variables. Public endpoints expose specific application functions, not an unrestricted JSON-RPC proxy.
Only wallet-approved proof memo transactions can pass through the submission route. The server checks transaction size, the single-signer structure, the program address and the exact Bunkercoin memo namespace. Solana preflight verifies signatures and execution. The app has no server-held wallet key.
Persistence is a convenience, not consensus
Neon stores the public signature, digest, signer and finalized slot in a dedicated bunkercoin schema. Index insertion re-reads the finalized transaction and rejects failed or mismatching memos. The onchain transaction is authoritative; database rows are not certificates.
Schema creation is idempotent and does not alter unrelated tables. Configure a least-privileged database role for production. The app does not store email addresses, original files, raw questions, IP addresses or wallet private keys in its application tables. Hosting and third-party services have their own logs.
The radio adapter has a different trust boundary
RADIO_NODE_URL points to an operator-controlled compatible reference node. Only a fixed set of read-only paths is requested. Returned objects are schema-checked and stripped to public telemetry fields. A reported finalized radio block is not represented as a Solana block.
A successful memo does not make Solana consensus radio-native. A future certificate bridge needs an authenticated validator set, cryptographic verification, replay protection and an independently reviewed onchain verifier. None of those are implied by this v0 gateway.