PHP-Cardano
Pure PHP Cardano wallet generation and transaction signing. Zero dependencies, triple-fallback Ed25519 crypto, CIP-1852 compliant.
Plug-and-play Cardano utilities for WordPress — minting, payments, wallet connect, content signing, and more. Server-side signing. Pure PHP. Tiny bundles.
Most Cardano dApps ship 1.5 MB of WASM crypto to the browser. We don't.
6 KB gzipped frontend bundle. 18 KB PHP signer. Compare that to the typical 1.5 MB CSL WASM dependency most Cardano dApps require.
Secrets never leave the server. All transaction construction and signing happens behind WordPress capability-gated endpoints with nonce verification.
No Node.js. No Python. No compiled binaries. Ed25519 signing with triple-fallback: native sodium, FFI, or pure PHP BCMath. Runs anywhere WordPress runs.
A signer-first architecture where blockchains are pluggable settlement layers.
Minimal frontend. Wallet connection via CIP-30. No crypto in the browser unless explicitly chosen.
REST & AJAX endpoints with nonce verification, capability checks, and input validation.
Deterministic Ed25519 signing. Keys encrypted at rest. Multi-sig ready. 18 KB total.
Cardano (today). The chain is a pluggable backend — the application logic stays the same.
Open-source Cardano tools built for WordPress. Download, install, and extend.
Pure PHP Cardano wallet generation and transaction signing. Zero dependencies, triple-fallback Ed25519 crypto, CIP-1852 compliant.
CIP-30 Cardano wallet connect, transaction building, and server-side signing for WordPress. 6 KB frontend, no WASM.
Cardano NFT minting for WordPress with dual-signature security, mystery boxes, weighted rarity, CIP-25 metadata, and CIP-27 royalties.
Peer-to-peer Cardano marketplace for WordPress. Products as NFTs, blockchain payments, tamper-proof receipts, zero middlemen.
One-click Cardano content signing for WordPress. Prove authorship on-chain with ADA Handle identity and a built-in SEO suite.
LLMs excel at generating features within stable constraints. This stack provides exactly the guardrails they need.
Large language models can safely scaffold UI flows, admin tools, and integration logic without accidentally violating core security assumptions. The architecture acts as a guardrail, making rapid AI-assisted development both productive and safe.
Paste these rules into any LLM session to extend our plugins safely.
1. Never put API keys in JS; server calls only.
2. All sensitive actions go through WP REST/AJAX endpoints with:
- capability checks
- nonce verification
- strict input validation
3. Signing logic stays server-side unless explicitly
set to CIP-30 wallet signing.
4. Downloads served via controlled endpoint;
compute and display SHA-256.
5. Keep frontend minimal; prefer server-rendered
pages and small scripts.