Noel Tock invited me to join a Twitter Space he was hosting about Web3 and WordPress in mid-September 2022. Noel’s a partner at Human Made – one of the premier WordPress agencies – and a tech enthusiast deeply invested in the intersection of AI, web technologies, and blockchain.
This was part of a series he was running, exploring where decentralized technologies might intersect with the WordPress ecosystem. The format – a one-hour audio conversation on Twitter – created a different dynamic than a conference talk or traditional podcast. More casual, more conversational, more reactive to audience questions.
So yeh. Let me walk you through what we likely discussed.
Why This Conversation Mattered
By September 2022, I’d been at Automattic as Web3 Lead for about six months. I’d given my WCEU talk in June, done the WP Tavern podcast in July. The WordPress community had heard the arguments, seen the possibilities, expressed the skepticism.
But Noel’s audience was different – Human Made’s clients are enterprise organizations running complex WordPress installations. Fortune 500 companies, universities, media organizations. Not crypto-native startups.
The question for them isn’t "What’s Web3?" but "Is there a business case for integrating these technologies into our WordPress infrastructure?"
That’s a harder question. And more important.
The State of Play (September 2022)
Context matters. By mid-September 2022:
The market was down. Crypto winter was in full effect. Ethereum had dropped 70% from its peak. NFT trading volume was way down. The "number go up" crowd had gone quiet.
But building continued. Ethereum’s merge to proof-of-stake was happening (literally that same week). Infrastructure was maturing. Real projects solving real problems kept shipping.
WordPress remained curious but cautious. Some enthusiasm from creators and developers. Lots of skepticism from the broader community. Automattic exploring possibilities but not making grand pronouncements.
This wasn’t the time for hype. It was the time for honest assessment.
What Web3 Offers WordPress Users
I would have focused on practical use cases that were working (or close to working):
Creator Monetization
NFTs for content creators: WordPress bloggers could mint articles as NFTs. Not speculation – actual collectibles for fans who want to support and own a piece of their favorite creator’s work.
Token-gated memberships: Premium content accessible only to NFT holders. More flexible than traditional subscription models. Transferable if the holder wants to sell their membership.
Crypto tips and patronage: Direct wallet-to-wallet payments. No platform fees, no payment processor cuts. Especially valuable for international creators dealing with expensive transaction costs.
This wasn’t theoretical. Creators were doing this, though the UX was still clunky.
WooCommerce Merchants
Cryptocurrency payments: Accept Bitcoin, Ethereum, stablecoins. Lower fees than credit cards. Faster settlement for international transactions.
NFT-based loyalty programs: Instead of points in a database, issue NFT rewards. Transferable, tradeable, provably scarce. Actually owned by customers.
Digital collectibles as products: Sports teams, artists, brands – selling NFTs alongside physical products. New revenue streams.
Token-gating for exclusive products: Limit access to drops or special editions based on token ownership. Community rewards that are provable and programmable.
WooCommerce plugins were emerging to enable this. Not perfect, but functional.
Content Verification
WordProof integration: Blockchain timestamping to prove when content was published. Combat plagiarism. Establish copyright claims.
Decentralized storage: IPFS integration for media files. Content that can’t be censored or taken down by hosting providers.
Less exciting than "make money with NFTs" but solving real problems for publishers and journalists.
The Challenges We’d Discuss
I wouldn’t have sugarcoated the problems:
User experience remains terrible: Wallets, private keys, gas fees, transaction failures. Most people don’t want to deal with this complexity.
Scams are everywhere: Rug pulls, fake projects, phishing attacks. WordPress’s reputation for security would be at risk if we made it easy for users to get scammed.
Regulatory uncertainty: What happens when governments start cracking down on cryptocurrency or NFTs? WordPress operates globally – how do you build features that are legal in some jurisdictions but not others?
Environmental concerns: Pre-merge, Ethereum’s proof-of-work consensus was environmentally costly. Even post-merge, the perception problem remained.
The speculation overshadows utility: Most people hear "NFT" and think "million-dollar monkey JPEGs," not "practical membership tokens."
Noel’s Perspective
What made this conversation interesting was Noel’s position. Human Made serves enterprise clients. They’re not going to implement something because it’s trendy. They need business cases, risk assessments, security guarantees.
I imagine Noel pushed on questions like:
"How do we explain this to our clients?"
Enterprise clients don’t want to be early adopters of unproven technology that could damage their brand.
"What’s the support burden?"
If a customer’s crypto payment fails, who handles that support ticket? The complexity ripples through the entire organization.
"Is the WordPress core team supportive?"
WordPress is a community project. Major feature additions need community buy-in. Was that there for Web3 integration?
"What about our agency’s liability?"
If we build Web3 features and users lose money due to hacks or scams, what’s our exposure?
These are the right questions. And I hope I gave honest answers rather than dismissive "you’ll see" tech-bro responses.
The Twitter Space Format
Twitter Spaces are ephemeral (at least they were in 2022 – recording features were limited). Audio-only. Often casual and reactive rather than heavily structured.
That format suited this kind of conversation. Less "presenting arguments" and more "thinking through problems together."
The audience could jump in with questions. Noel could steer toward topics his community cared about. I could respond to skepticism in real-time rather than delivering a one-way talk.
It’s also why Twitter Spaces are hard to preserve or reference later. The conversation happened, people who attended got value from it, and then it’s mostly gone except for impressions and notes.
That’s both a feature and a bug.
What I Learned
Conversations like this with Noel reinforced something important: Enterprise adoption of Web3 requires dramatically better tooling and risk management than enthusiast adoption.
Crypto-native users will tolerate clunky UX, accept personal responsibility for security, and navigate regulatory gray areas. They’re opting into that.
Enterprise organizations won’t. They need:
- Reliable support
- Clear liability frameworks
- Regulatory compliance guarantees
- Insurance options
- Professional-grade security
- Seamless UX that doesn’t expose end users to complexity
WordPress serving enterprise clients through agencies like Human Made means thinking about Web3 integration through that lens.
It’s not enough for the technology to work. It has to work reliably, at scale, with support infrastructure, in a legally defensible way.
That’s a much higher bar. And one that Web3 infrastructure wasn’t (and arguably still isn’t) fully meeting.
The Bigger Picture
By late 2022, I’d been having versions of this conversation dozens of times. WordPress contributors, WooCommerce merchants, agency partners, enterprise clients, individual creators.
The pattern was consistent:
- Curiosity about possibilities
- Skepticism about practicality
- Concerns about risks
- Questions about business cases
All valid. All important.
The conversations worth having aren’t "Web3 is the future, get on board" or "Web3 is a scam, ignore it." They’re "Here’s what works, here’s what doesn’t, here’s what’s uncertain, let’s figure out together if there’s something valuable here."
That’s what I hope Noel’s Twitter Space provided – a space (ha) to think through these questions without hype or dismissal, just honest exploration.
Thanks to Noel for hosting and to everyone who joined the conversation.
Event: Twitter Space – Web3 & WordPress
Host: Noel Tock (Partner at Human Made)
Date: September 16, 2022
Duration: 1 hour
Format: Audio conversation on Twitter Spaces
Find Noel: @noeltock, noeltock.com
Find me: Contact form, @divydovy, hi@divydovy.com
Note: Twitter Spaces are ephemeral audio conversations. This writeup is based on my recollection of typical discussion topics from that period. I was having similar conversations repeatedly in mid-2022, so the themes here reflect the questions and concerns that were top-of-mind across the WordPress community at that time.
Sources: