Weld for WP

CIP-30 Cardano wallet connect, transaction building, and server-side signing for WordPress. 6 KB frontend, no WASM.

Weld for WP brings native Cardano wallet connectivity and transaction signing to WordPress — without the bloated infrastructure that dApp development typically demands. Built on the CIP-30 standard, this plugin lets your visitors connect browser wallets like Eternl, Lace, and Nami directly on your WordPress site, while keeping their private keys entirely non-custodial and never exposed to your server. The frontend bundle weighs just 6 KB gzipped, and the PHP transaction signer adds only 18 KB — a radical departure from solutions that drag in 1.5+ MB of WASM dependencies.

At its core, Weld for WP offers drop-in shortcodes for wallet connection, balance display, and ADA transfers, plus a clean REST API for developers who need programmatic transaction building and submission. The server-side signing layer, powered by pure PHP-Cardano, handles automated treasury operations and custodial workflows with AES-256-CBC encrypted key storage — no binary dependencies required. Every external call is proxied server-side so API keys are never leaked to the browser, and all mutations require WordPress nonce verification and proper authentication.

Whether you are accepting ADA payments on a WooCommerce storefront, gating premium content behind wallet-based access control, or running automated disbursement workflows from a custodial treasury wallet, Weld for WP provides the foundational plumbing without forcing you into a JavaScript framework or a full dApp stack. The plugin exposes a global JavaScript interface with state subscriptions, giving theme and plugin developers reactive hooks to build sophisticated Cardano-powered experiences on any WordPress site.

Weld for WP requires WordPress 5.8+, PHP 7.4+, and the OpenSSL and BCMath extensions. API keys for Ada Anvil and Blockfrost are configured in the admin panel — no external data is transmitted until you explicitly set them up.

Trust Model

Hybrid Non-custodial

This plugin uses a hybrid custody model. The server holds an encrypted policy wallet for co-signing, while the user’s browser wallet provides the second signature. Neither party can act alone.

Installation

Install Steps
1. Download the ZIP from the Download button above
2. Go to Plugins > Add New > Upload Plugin
3. Upload the ZIP file and click Install Now
4. Activate the plugin
5. The wallet connect button will appear in your theme header automatically

Documentation

Weld for WP

Cardano wallet connectivity and transaction signing for WordPress.

Built using the Anvil API. Not an official Anvil product.
Frontend wallet architecture inspired by Weld v0.6.0 by Anvil.
Server-side signing powered by PHP-Cardano.

A pb project.


What is this?

Weld for WP brings Cardano to WordPress without the typical dApp stack. No Next.js, no Webpack, no CSL WASM blobs. Just a clean WordPress plugin that:

  • Connects browser wallets (Eternl, Lace, Nami, etc.) via CIP-30
  • Builds and submits transactions through the Anvil API
  • Signs transactions server-side with pure PHP (no binaries, no CLI tools)
  • Manages custodial wallets with encrypted key storage
  • Queries the blockchain for balances and native assets via Blockfrost

The entire frontend bundle is 6 KB gzipped. The PHP transaction signer is 18 KB. Compare that to the typical 1.5+ MB CSL WASM dependency.


Architecture

                     Browser                          WordPress Server
               +-----------------+              +------------------------+
               |  CIP-30 Wallet  |              |   Weld for WP Plugin   |
               |  (Eternl/Lace)  |              |                        |
               +--------+--------+              |  +------------------+  |
                        |                       |  |  REST API        |  |
  [weldpress_connect]   |   enable()            |  |  /weldpress/v1/  |  |
  [weldpress_badge]     +<--------------------->+  +--------+---------+  |
  [weldpress_send]      |   signTx()            |           |           |
                        |   getAddress()        |  +--------v---------+ |
                        |                       |  |  Anvil Client    | |
                        |                       |  |  (build/submit)  | |
                        |                       |  +--------+---------+ |
                        |                       |           |           |
                        |                       |  +--------v---------+ |
                        |                       |  | Blockfrost Client| |
                        |                       |  | (balance/assets) | |
                        |                       |  +------------------+ |
                        |                       |                        |
                        |                       |  +------------------+  |
                        |                       |  |  PHP-Cardano     |  |
                        |                       |  |  (generate keys, |  |
                        |                       |  |   sign tx)       |  |
                        |                       |  +------------------+  |
                        |                       |                        |
                        |                       |  +------------------+  |
                        |                       |  |  Wallet Model    |  |
                        |                       |  |  (encrypted DB)  |  |
                        |                       |  +------------------+  |
                        |                       +------------------------+

Two signing paths

Browser-side (CIP-30): User connects their wallet extension. Transactions are built via Anvil, signed in the browser wallet, and submitted back through the REST API. The server never sees private keys.

Server-side (custodial): The admin generates a wallet in the plugin. Keys are encrypted with AES-256-CBC and stored in a custom database table. Transactions are built via Anvil, signed with PHP-Cardano's pure-PHP Ed25519 implementation, and submitted via Anvil. Useful for automated payments, treasury management, or any flow where a browser wallet popup isn't practical.


Frequently Asked Questions

Which wallets does Weld for WP support?
Any CIP-30 compliant wallet including Nami, Eternl, Flint, Typhon, Lace, and GeroWallet.
Does this require any JavaScript frameworks?
No. The entire frontend bundle is 6 KB gzipped with zero framework dependencies.
Can I use wallet connect with WooCommerce?
Yes. Weld for WP provides shortcodes and PHP functions that can be integrated into any WordPress page or plugin.