Bringing Blockchain to Conservation with WordPress

The Challenge

Sylvester Rewilding is a German non-profit creating collectively owned wildlife sanctuaries across Europe. Their funding model is unusual: WildTokens, NFTs that represent guardianship over real land being rewilded. A buyer isn’t just donating; they gain a voice in how the land is restored.

The constraint: Sylvester’s team consists of ecologists and community organizers, not blockchain engineers. Their website runs on WordPress, and a large part of their audience has never used a crypto wallet. Yet the entire funding model depends on making a token purchase feel as routine as any other online order.

The brief, therefore, was clear: build a WordPress plugin that lets anyone buy blockchain tokens: a supporter paying by credit card and a crypto-native paying in ETH, through the same flow, with the same outcome.

The Approach

Blockchain technology is powerful, but it puts most people off. WordPress is the opposite: universally familiar, but never designed to talk to smart contracts. The plugin had to close exactly that gap.

Three principles guided the design:

• A normal WordPress plugin: installed like any other. Settings page, shortcodes, done. No server configuration, no containers, no command line.
• No crypto knowledge required: social logins, in-app wallets, and standard credit card payments mean supporters never encounter gas fees or seed phrases. The blockchain layer stays in the background.
• Sylvester operates it independently: chain ID, contract address, and token presentation are all configurable through wp-admin. The team can switch networks without involving a developer.

Technical Implementation

React Inside WordPress

Running React inside WordPress is technically possible but notoriously messy. The solution: Vite compiles three independent React apps into a single IIFE bundle, and WordPress shortcodes create the mounting points:

• [rewilding_buy]: the token purchase flow
• [rewilding_member]: the personal dashboard
• [rewilding_connect]: a standalone wallet button

Each app validates its own environment before rendering: HTTPS, contract configuration, network connectivity. When something is wrong, users see a clear explanation instead of a blank component.

Styling runs through Tailwind with an rw- prefix, isolating the plugin from whatever WordPress theme is active.

Thirdweb SDK as the Web3 Layer

Building wallet management, payment processing, and contract interactions from scratch would have taken months. Instead, the plugin builds on thirdweb’s SDK v5, which handles these layers reliably.

Five wallet strategies work simultaneously through the ConnectButton:

• In-app wallets with social login: Google, Apple, Facebook, email, phone
• MetaMask
• Coinbase Wallet
• WalletConnect
• MEW Wallet

The social login path is the decisive one for non-crypto users. Someone clicks “Sign in with Google,” and thirdweb provisions a wallet behind the scenes. The person never sees a seed phrase and never installs an extension. They don’t need to know they have a wallet at all.

Fiat and Crypto Payments

This was the make-or-break feature. Thirdweb’s PayEmbed component covers both sides:

• Credit card: select a currency, pay as usual. The processor handles the fiat-to-crypto conversion and mints the token on-chain.
• Crypto: pay directly from a connected wallet.

Both paths lead to the same result: an ERC-721 in the buyer’s wallet. The purchase widget presents the next available token (name, image, and attributes from on-chain metadata) and lets buyers choose a quantity before checkout.

Both options were essential because Sylvester’s community is genuinely split: crypto-experienced supporters on one side, and on the other, people who care about conservation but have never touched Ethereum. Excluding either half would have broken the model.

The Member Area

After purchase, the member area becomes the supporter’s home base. It fetches every NFT tied to the connected wallet and displays them in a grid, each card with token image, name, and ID.

Transfers are built in: a modal validates the receiving address and executes the ERC-721 transferFrom call with proper loading and error states.

The member area is more than portfolio management. A WildToken is the membership card to Sylvester’s governance community, and the dashboard makes that tangible: what you hold, what it represents, and that you belong to the project.

Multi-Chain Support

The plugin is not locked to one chain. The WordPress settings page offers Ethereum, Base, Polygon, Arbitrum, Optimism, BNB Chain, Avalanche, and several testnets. Sylvester currently runs on Base for its low transaction fees. Migrating means changing one dropdown.

Under the hood, thirdweb’s wrapper lazy-loads chain clients and contracts. Base and Polygon ship with static configurations for speed; everything else resolves dynamically. Switching chains requires no rebuild and no redeployment.

WordPress Admin Integration

The plugin adds a “Rewilding Token” page to wp-admin with two sections:

Thirdweb Configuration: client ID, active chain, and contract address, accompanied by a step-by-step checklist for creating a thirdweb project, enabling in-app wallets, and whitelisting domains.

Token Display: fallback name, description, and image URL for when on-chain metadata isn’t loaded yet, so the buy widget looks finished even during initial setup.

Everything hooks into WordPress’s native Settings API with proper sanitization and validation. The shortcodes check their configuration silently and surface warnings to admins only. Visitors never see half-finished states.

Results

What could have become a sprawling custom Web3 application now runs on any WordPress installation:

• Card and crypto side by side: no supporter is excluded by how they prefer to pay
• Zero blockchain literacy required: social login and credit cards remove every technical hurdle
• Pure WordPress: install, configure through the admin, place shortcodes
• Chain-flexible: the network is a configuration setting, not an architectural commitment
• Tokens transfer freely: members can pass WildTokens on to others

In practice: a supporter in rural Galicia buys a WildToken with her credit card and Google account, while someone in Berlin pays in ETH from MetaMask. Both end up in the same community, co-governing the same stretch of rewilding land. That is the entire point of the project.

Technical Stack

• Plugin Runtime: WordPress (PHP) + React 18 (TypeScript)
• Build: Vite 6 (IIFE bundle)
• Web3: thirdweb SDK v5 (ERC-721, PayEmbed, In-App Wallets)
• Styling: Tailwind CSS 3 (prefixed, isolated)
• Blockchain: Base (EVM-compatible, configurable)
• Payments: Fiat via thirdweb Pay, Crypto via connected wallets

Every choice was deliberate, and deliberately boring where it should be. WordPress, because that is where Sylvester already lives. React, because thirdweb’s SDK requires it. Vite, because it produces one self-contained bundle that WordPress enqueues like any other script: no build servers, no CDN dependency, no external runtime to maintain.

Blockchain tooling inside WordPress sounds like a contradiction. That contradiction is the thesis: the best infrastructure is invisible. Sylvester’s supporters aren’t “using a dApp”. They’re browsing a WordPress site that happens to mint NFTs underneath. That is how blockchain earns its place in conservation: by getting out of the way.

Considering whether Web3 fits your product? We’ll give you a clear answer. Talk to us.