What Product Builders Need to Understand About the Shift

Julie Zhuo spent years at Facebook building the product management discipline that became a template for a generation of product teams. Her central insight is that the hardest part of product work is not the feature but understanding what the user is actually trying to accomplish. That frame applies directly to the developer career question this article raises. Developers who misread the current shift are not missing data. They are using the wrong frame. The right frame changes both the interpretation and the response.

The wrong frame is replacement. The right frame is capability shift: a shift in which developer capabilities generate premium compensation and which ones are becoming commoditized. If the frame is replacement, the rational response is fear and credential accumulation. If the frame is capability shift, the rational response is deliberate positioning toward the capabilities that remain scarce after AI deflation reaches the mid-level developer market.

The capability that remains scarce is commercial judgment: the ability to translate a business outcome into a technical decision and back again. The Microsoft developer platform squeeze illustrates the structural pressure. Developers who are deeply embedded in a single platform stack have built their leverage on knowing a specific API or deployment model, and are exposed when the platform extracts rent from that dependency. Developers who understand why a customer buys, what drives renewal, and how technical decisions map to business outcomes have optionality that platform pricing cannot compress.

The behavioral dimension matters more than the technical dimension in the transition. Friction is the silent churn driver in developer tooling precisely because developers will abandon technically superior tools if the workflow integration is poor. The products surviving AI deflation pressure are not the ones with the best pricing adjustments. They are the ones that have reduced cognitive overhead on the workflows that matter most. The developer who builds products with that behavioral insight is practicing the commercial literacy that protects against commoditization.

The demand side of the transition is more optimistic than the churn narrative implies. Enterprise AI adoption is creating a category of developer work that did not exist three years ago: evaluation framework development, AI system integration, prompt architecture, and the organizational change management that makes AI deployment actually stick. This work requires more understanding of the business context than most abstraction-layer development, and it is in high demand from organizations discovering that buying an AI product and getting value from it are very different problems.

The Chinese AI open-source push through DeepSeek and Qwen is accelerating the economics of this transition by driving inference costs toward near-zero. When the marginal cost of AI inference drops from dollars to cents per million tokens, the development economics of AI-integrated products change entirely. More developers can build more AI-integrated products. The constraint shifts from access to the technology to understanding what to build with it. That understanding is the commercial judgment that neither AI tools nor cheap compute can substitute for.

Prediction markets on software engineering compensation show persistent wage premium for senior engineering talent even as mid-level compensation compresses. The market is expressing the same insight the article reaches: the scarce input after AI deflation is judgment, not execution speed. The developer who has built commercial literacy is not facing displacement. They are facing an expanded job description that pays better than the old one and is harder to replicate. That is not the crisis the churn narrative describes. It is the opportunity the churn narrative obscures.

“Better Software” Was Never a Strategy

Roger Martin has spent a career arguing that most of what companies call strategy is not strategy at all. It is aspiration dressed up as choice. A team that says it will win by building the best product has not made a strategic decision; it has stated a hope. Strategy, in Martin’s framing, is an integrated cascade of choices — where you will play, how you will win there, and what capabilities that particular way of winning actually demands. The viral churn story is a small monument to a company that skipped that cascade.

The vendor’s implicit plan was to be more polished than the internal alternative. But polish is a capability, not a winning aspiration, and it answers none of the questions that decide renewals. Where does this product win — for which customer, and at what point in their workflow does it become the thing they cannot cheaply replace? How does it hold that position against a good-enough internal build? Martin’s discipline is to ask what would have to be true for the chosen way of winning to keep working. Here, one of those conditions — that building internally stays expensive enough to be irrational — quietly stopped holding. AI deflation lowered the cost of the alternative, and a strategy that was never made explicit had nothing explicit to revise.

This is the deeper reason commercial literacy is becoming the builder’s real moat. A developer who can say where their work wins, and what would have to remain true for it to keep winning, is doing strategy rather than simply shipping. That judgment is what the market is now repricing upward — and it is exactly the judgment the churn crowd mistook for a story about machines.

TL;DR

Kadena, a Layer‑1 blockchain organisation that reached a multi‑billion valuation in the 2021 cycle, abruptly ceased operations in October 2025 via a tweet. They will not be the last Web3 organisation to end things this way.

From its 2016 founding as a JPMorgan spinout to its abrupt October 2025 shutdown, Kadena’s story underscores a critical divide in Web3: innovative technology undermined by organisational fragility. The core organisation ceased operations and maintenance, citing market conditions, leading to a sharp price drop and a series of delistings.

As of 18 January 2026, KDA trades around $0.009 USD with a market cap around $3.0 million, remaining over 99% below its ~$27.64 all-time high in 2021. CoinMarketCap snapshot. The network persists under miners and community maintainers, but the company’s end highlights weak execution, unclear revenue, and poor governance signals.

This is not a tech failure. Chainweb’s scalable Proof‑of‑Work and Pact’s security‑focused contracts held promise, but this was a business failure, exposing Web3’s lack of operational guardrails. Comparable in trust erosion to major collapses like FTX (impact-wise, not alleging fraud), Kadena signals the first of many cases where engineering excellence meets organisational inadequacy.

 

Why did Kadena fail? Kadena failed because its core organization could not sustain operations through the 2025 downturn. In October 2025 the team announced it would cease all business activity and active maintenance, citing market conditions and an inability to continue development. The Defiant · Binance.US notice. The shutdown, combined with unclear revenue, weak governance signals, and sudden communication, triggered a price crash and exchange delistings even though the chain can still run under miners.

 

What Happened to Kadena in October 2025: Shutdown Announcement and Market Fallout

Around 21 to 22 October 2025, Kadena’s core organization announced that it would cease all business operations and active maintenance of the Kadena blockchain, citing market conditions and an inability to sustain development. This was an organizational shutdown rather than a technical failure; the chain can continue under miners and community maintainers. Primary reporting · Exchange notice referencing shutdown

Market reaction was immediate. Within roughly 24 hours of the shutdown post, KDA fell about 60% (some reporting put the drawdown closer to ~65%), before continuing to trade more than ninety-nine percent below its peak. Source (The Defiant) · Source (Decrypt)

Exchanges responded quickly. Bybit ended KDA/USDT spot trading on 28 October and OKX delisted KDA spot pairs on 29 October, Binance.US scheduled delisting for 28 October, KuCoin followed with removal on 4 November, and Binance announced global delisting of all KDA spot pairs effective 12 November. Bybit · OKX · Binance.US These delistings reduced liquidity for KDA and made it harder for holders to adjust their positions.

This sequence created a clear pattern: a sudden organisational exit, a sharp price crash, and rapid delistings. Most reporting distinguished between Kadena the company, which ended, and Kadena the proof-of-work chain, which may continue as a community-run network.

The tweet that crystallised the continuity crisis: a shutdown communicated as a short public post rather than a managed transition.

The Communication Gap: Why the Shutdown Hit Like a Rug Pull (Without Being One)

A project can end without being a fraud, but still create a rug-pull-like experience for holders if the shutdown is sudden and unmanaged. The key issue is not intent; it is continuity risk. When an organisation that stewards a chain exits abruptly, the market reacts as if the floor has disappeared. Reporting on the shutdown communication

• Suddenness: an immediate cessation creates maximum uncertainty for users, builders, and exchanges.
• No clear transition plan: without a communicated handover path, even a technically live network becomes operationally fragile.
• No runway framing: in downturns, holders and builders want to understand whether a shutdown is preventable, planned, or forced.

This is where operational guardrails matter: the market can tolerate bad news, but it cannot tolerate surprise.

X / Tweet History Snapshot: How Sentiment Shifted Into a Continuity Crisis

One of the most useful public signals in Web3 is not a quarterly report; it is the project’s own communication trail. A tweet history is not proof of anything by itself, but it is a reliable way to track whether a team is managing expectations, acknowledging risk, and preparing stakeholders for negative outcomes.

Business as usual, one day before shutdown: conference travel messaging that implied continuity.

Below is a snapshot of key public communications leading into the shutdown. The goal is simple: map what was being communicated against what happened next.

How we’ll use this: if “business as usual” messaging continues right up until a sudden shutdown, that is a measurable governance and disclosure failure, even if the underlying chain keeps producing blocks.

Timeline: From Shutdown Announcement to Delistings

• 21–22 October 2025 – Kadena’s core organization announces it will cease all business operations and active maintenance of the blockchain.
• Within ~24 hours – KDA fell about 60% (some reporting put the drawdown closer to ~65%). The Defiant · Decrypt
• 28 October 2025 (08:00 UTC) – Bybit delists the KDA/USDT spot pair (spot trading ends). Bybit notice
• 29 October 2025 (08:00–10:00 UTC) – OKX delists KDA spot trading pairs (KDA/USDT, KDA/USDⓈ). OKX notice
• 28 October 2025 – Binance.US schedules KDA delisting. Binance.US notice
• 4 November 2025 – KuCoin schedules removal of KDA. KuCoin notice
• Early November 2025 – Network upgrade / hard-fork window referenced by mining infrastructure (payouts temporarily suspended during upgrade coordination). f2pool note
• Mid‑Nov to Dec 2025 – Community maintainers publish fork / continuity efforts (KDA “Community Edition”) and supporting repositories. Community posts · GitHub
• 12 November 2025 – Binance announces global delisting of all KDA spot pairs. Binance notice
• 12 January 2026 (03:00 UTC) – Binance ended withdrawals support for KDA on the community‑maintained chain (withdrawal window closed). Binance notice

Post-shutdown, parts of the community attempted to keep the network alive through miner-led maintenance and fork initiatives, while exchanges treated continuity as time-bounded (for example, Binance had communicated a withdrawals-support window for the community-maintained chain that ended on 12 January 2026). Reporting and exchange notices also reference a network upgrade / hard-fork window around early November 2025. Separately, community discussion on X reflected ongoing disputes about transparency, remaining issuance schedules, and what continuity should look like without a core team. These debates matter less for the chain’s raw uptime than for whether an ecosystem can retain credibility and users without an accountable operating organization.

A Decade of Promise and Peril – Kadena’s Timeline

Kadena’s trajectory, from a Wall Street‑backed innovator to a community‑maintained survivor, illustrates how execution gaps can eclipse technical achievements. The public record shows meaningful technical milestones and repeated ecosystem pushes, followed by an abrupt organisational end. The table below consolidates the highest‑signal events that frame the failure as organisational rather than technical.

Methodology note: this timeline is constructed from publicly verifiable announcements, exchange notices, and archived communications. It does not rely on internal disclosures or private reporting.

Case Study: Ecosystem Funding Announcements vs Ecosystem Outcomes

Kadena repeatedly signaled ecosystem intent through funding announcements. That approach can work, but only if the downstream outcomes are publicly measurable: shipped products, retained developers, users, and durable liquidity. Where this became fragile for Kadena was not the existence of ecosystem programs, but the difficulty of verifying results through the cycle.

Outcomes proxy (TVL): DeFiLlama-reported total value locked (TVL) for Kadena fell to roughly $128k in late October 2025 (reported as down ~71% in 24 hours), versus an estimated peak near $11M in August 2022. This is not a perfect measure of adoption, but it is a public, comparable signal of retained liquidity through a cycle. DeFiLlama (Kadena) · Reporting citing DeFiLlama This TVL collapse is widely cited as evidence that ecosystem funding announcements did not translate into retained liquidity or user demand through the downturn.

Public adoption signals (triangulation): to avoid relying on a single metric, here are three public proxies that tend to move together when real usage is present:

• Liquidity retained (TVL): DeFiLlama TVL (above) shows how much value remains deployed in the ecosystem through time.
• On-chain activity (proof-of-life, not demand): transaction and chain activity trackers can confirm the network is still producing blocks and processing transactions, but they do not prove that the ecosystem has retained users or builders. BitInfoCharts (Kadena) · Chainweb explorer
• Developer activity (maintenance signal): repository and commit activity can indicate whether a chain is being actively maintained after an organisational shutdown. Community repos

Why this matters: large numbers and big programs are easy to announce. What investors need is an outcomes ledger: who received funding, what shipped, and what adoption followed.

Technical Strength Was Not the Problem: Where Kadena’s Layer-1 Fell Short

Kadena’s design combined Chainweb for parallelized Proof of Work throughput with Pact for safer, readable smart contracts. Chainweb’s architecture uses multiple parallel chains designed to scale throughput without abandoning PoW security assumptions. Pact’s human-readable approach and verification-oriented design aimed to reduce common smart-contract failure modes. The repositories and documentation show sustained technical effort, and ecosystem features like NFTs and bridging reflected real engineering output.

None of this saved investors when basic company functions failed: revenue clarity, runway discipline, communication, and governance. Kadena is a clean example of a recurring Web3 gap: a project can be technically serious and still be organisationally brittle. When that brittleness shows up as an abrupt shutdown, markets don’t reward architecture. They punish continuity risk.

Market Timing Headwind: Proof-of-Work in a Proof-of-Stake Narrative

Beyond execution, Kadena faced a worsening narrative environment. From 2021 onward, market preference shifted decisively toward proof-of-stake systems, driven by ESG concerns, institutional mandates, and Ethereum’s transition. Even highly efficient proof-of-work designs were increasingly filtered out at the allocation stage.

This does not invalidate Chainweb’s technical merits. It does, however, raise the bar for operating credibility. When a project swims against prevailing market narratives, it must compensate with exceptional clarity on revenue, governance, and continuity. Kadena entered this phase without those buffers.

Key implication: timing does not determine success on its own, but it amplifies weaknesses. As proof-of-work became harder to justify externally, operational fragility became less survivable.

Token Emissions and Sell Pressure (Design-Level Observation)

Kadena’s collapse cannot be explained by token design alone, but emissions dynamics likely amplified downside pressure once confidence broke. As with many proof-of-work networks, ongoing token issuance rewarded miners regardless of demand conditions. In the absence of sustained organic usage or offsetting demand, those emissions can translate into continuous sell pressure during downturns.

This is a general structural observation, rather than a claim about precise allocations. Public sources vary on exact supply schedules, circulating supply figures, and long-term emission curves. Those numbers also change over time. Without a single authoritative and current tokenomics disclosure, it would be misleading to present fixed percentages or caps as settled facts.

The more important point for investors is not the exact split, but the interaction between emissions and demand. When a project lacks clear revenue, strong governance signals, and visible ecosystem pull, token issuance becomes a stress multiplier rather than a growth tool. Kadena’s experience fits that broader pattern.

RMA™ Alignment Assessment (Public-Record View)

This assessment applies VaaSBlock’s RMA™ framework strictly to what could be independently verified from public-facing information at the time of Kadena’s shutdown. It does not rely on private data, internal access, or post-hoc assumptions. Where evidence is insufficient, the outcome is recorded as Unverified, rather than inferred or scored.

Important: “Unverified” reflects insufficient public evidence, not proof of failure. The absence of disclosure itself still represents a material risk signal for investors evaluating continuity and downside protection.

About CertiK: What Smart-Contract Audits Do, and What They Don’t Cover

CertiK is a smart-contract and protocol security firm. Their scope is code and security posture. It is not a verdict on business viability. Historical snapshots show Kadena present on Skynet with an audit workflow visible at one point; the current page shows different status. Status changes on these portals can occur for a range of reasons and are best cross-checked against official project communications and other independent sources. That is a reminder to investors: security portals evolve with new information, and a code review cannot replace governance, revenue clarity or transparent communication.

For company-level assurance, look at standards that address organization and controls: SOC 2 and ISO/IEC 27001. These do not prove market fit, but they signal maturity in how a team manages risk.

This is part of a broader credibility gap: standards can exist, but verification and interpretation still break down in practice. For a deeper dive on why the “standards layer” itself can be gamed without verifiable proof, see: From Paper to Proof: Why On-Chain Verification Closes the Trust Gap in Industry Standards.

Investor Harm and the Confidence Problem After the Kadena KDA Price Crash

The shutdown, the price fall and the subsequent delistings produced direct losses for holders and a broader shock to market trust. From a risk-analysis perspective, my view is that the confidence damage from this episode sits in the same league as prior collapses that shook the market. Again, this is a comparison of impact, not intent, grounded in observable market behaviour rather than legal findings. When assumptions about continuity vanish in a day, retail holders usually bear the loss. This dynamic mirrors broader exchange operational risk patterns, where continuity assumptions break faster than users can react.

Second-Order Effects: Why These Failures Compound Beyond One Project

• Regulatory pressure increases: high‑profile organisational failures strengthen the case for stricter disclosure, governance, and consumer‑protection rules across the sector.
• Talent exits accelerate: experienced operators become more reluctant to join crypto projects where business failure, not technical risk, dominates outcomes.
• Trust costs rise: investors demand higher risk premiums, exchanges de‑risk faster, and builders hesitate to commit to ecosystems without clear continuity signals.

For an example of the kind of failure analysis journalists keep citing, see our report on continuous failures at a major exchange: Upbit CEX: a continuous pattern of failure.

If this pattern feels familiar, see our longer analysis of recurring execution failures across Web3: Amateur Hour in Web3.

Why Kadena’s Collapse Was Predictable: A Pattern Across Layer-1 Projects

We have seen other chains with credible engineering and weak operating models stumble for the same reasons. Without governance, revenue clarity and disciplined communication, engineering cannot defend investor capital through a cycle. There are strong indications it will not be the last time. Prolonged downturns and tighter scrutiny tend to expose organisations without disciplined governance and clear revenue structures. The same forces shaping Kadena’s collapse are visible across broader markets, as outlined in AI, SaaS and Crypto in 2026: the reality check.

Case Study: Terra (2022 Collapse)

Terra’s UST model promised innovation and scale, but weak governance and brittle assumptions amplified risk when market conditions turned. The lesson is similar: without operational guardrails and disciplined decision-making, even sophisticated engineering narratives can collapse into a confidence crisis that retail holders pay for.

Case Study: RChain (2017–2023 Fade)

RChain pursued ambitious scalability ideas and raised significant capital early, yet execution delays, unclear adoption, and weak operational follow‑through led to a long fade. The parallel to Kadena is not the technology—it is the pattern: building complex systems without proving durable demand and organisational competence through a cycle.

What Credible Layer‑1 Organisations Look Like to Investors

For investors evaluating other Layer‑1 blockchains after Kadena, credible organisations usually:

• State a plain business model and show confirmed demand; do not hide behind slogans.
• Publish governance, runway, and decision rules so holders understand how choices are made.
• Adopt the right standards: code audits for code; SOC 2 or ISO/IEC 27001 for company controls; RMA™ to connect it all to results and transparency.
• Disclose methods when you present results. If you publish numbers, publish how you got them.

In practice, investors can look for verifiable artefacts, such as publicly accessible policies, attestation reports, or transparent release notes, rather than relying on slogans alone.

See our trust framework note: Transparency Score launched.

For a deeper exploration of how credibility, revenue discipline and governance will determine which organisations survive the next cycle, review our new 2026 foresight editorial.

FAQs: Why Kadena Failed and What It Means for Layer-1 Investors

For traders, the key questions are usually: continuity risk (can this happen to other holdings?), liquidity (can I still exit or withdraw?), and the technical post‑mortem (did the protocol actually break?). The FAQs below address each of those lenses using publicly verifiable sources.

• Why did Kadena fail? Kadena failed at the organisational level, not because of a protocol flaw. In October 2025, the core team announced it would cease operations and active maintenance after failing to sustain the business through the downturn. The abrupt shutdown, unclear revenue model, and weak governance signals destroyed confidence, triggering delistings and a price collapse.
• Did Kadena’s technology fail? No. Kadena’s blockchain technology did not “fail” in the way a protocol exploit or consensus bug fails. Chainweb (its parallel‑chain Proof‑of‑Work design) and Pact (its security‑focused smart‑contract language) remained technically functional, and the network could continue producing blocks under miners and community maintainers. The failure was organisational: the company responsible for maintenance, ecosystem coordination, and continuity planning shut down, and markets repriced that stewardship risk immediately.
• Is Kadena still running after the shutdown? Yes, the Kadena blockchain can still run as a Proof‑of‑Work network maintained by miners and community developers. However, the original operating organisation no longer exists. The key issue is not uptime, but whether a network without accountable stewardship can sustain ecosystem value, development, and exchange support.
• What does “community-maintained” mean in practice? It usually means the original company is no longer paying engineers, publishing official releases, running core infrastructure, or coordinating exchanges—so maintenance depends on independent developers and miners. In practice this can include community-run forks, volunteer release management, and ad-hoc infrastructure support (explorers, nodes, and tooling). A chain can keep producing blocks under miners, but continuity for users depends on whether the community can sustain software updates, security responses, and exchange integrations over time.
• Can KDA still be traded? In limited form, yes—but access is constrained. After major exchange delistings, KDA trading shifted to fewer venues and thinner liquidity. Availability depends on your jurisdiction and which exchanges still list KDA, and some platforms may support withdrawals only for a limited period. This is not trading advice; it is a continuity note: once large venues delist, price discovery and exit liquidity typically deteriorate.
• Can I still withdraw KDA from exchanges? It depends on the exchange and your jurisdiction. Some platforms set time‑bounded withdrawal windows after delisting. For example, Binance communicated a withdrawals‑support window for KDA on the community‑maintained chain that ended on 12 January 2026 (03:00 UTC). Binance notice. Always check your exchange’s latest notice before assuming withdrawals remain available.
• When did Kadena shut down? Kadena’s core organisation announced it would cease business operations and active maintenance around 21–22 October 2025. The announcement was followed within weeks by major exchange delistings and a sharp market repricing, even though the blockchain itself did not immediately halt.
• Why did exchanges delist Kadena so quickly? Exchanges delisted Kadena because the shutdown created continuity and maintenance risk. When the organisation responsible for development and stewardship exits abruptly, exchanges reassess operational liability, liquidity, and user protection. Even if a chain keeps running, the loss of an accountable operator is often enough to trigger delistings.
• Why did Kadena’s shutdown feel like a rug pull to some holders? A project can end without being a fraud and still create a rug‑pull‑like experience if the shutdown is sudden and unmanaged. The key issue is continuity risk. When the floor disappears overnight, holders experience the outcome as a shock, even if no theft is proven.
• Is Kadena a rug pull or a scam? There is no confirmed evidence that Kadena was a rug pull in the classic sense of stolen funds. The harm came from an abrupt organisational shutdown, a sharp KDA price crash and rapid exchange delistings, not a documented theft event. It remains a serious failure of stewardship and communication, which is different from a proven fraud case.
• Was there a transition plan when Kadena shut down? Not in a form that was clearly documented and publicly verifiable at the time of the announcement. Community efforts later attempted to maintain continuity, but the initial shutdown communication did not provide a fully transparent handover framework.
• Were there warning signs before the shutdown? The most visible warning signs were not technical. They were operational: limited verifiable disclosure around revenue, runway, and governance decision rules, plus difficulty validating ecosystem outcomes through the cycle.
• Did Kadena have a clear revenue model? Based on the public record, the company did not provide audited or consistently verifiable disclosures that allowed investors and analysts to assess recurring revenue, sustainability, or runway with confidence.
• What happened to Kadena’s ecosystem and grants? Kadena announced multiple ecosystem programs and initiatives over time, but it became difficult for external observers to verify outcomes, recipients, and measurable adoption through the downturn. Investors should look for an outcomes ledger: who received funding, what shipped, and what usage followed.
• Is Kadena’s collapse similar to Terra or other Layer‑1 failures? The mechanisms differ, but the pattern overlaps: when governance, transparency, and operational discipline are weak, confidence can collapse rapidly, even if the underlying technology story is sophisticated.
• What does Kadena’s failure say about Web3 more broadly? It reinforces that engineering is not enough. Many Web3 organisations can explain consensus and token mechanics but cannot demonstrate durable revenue, governance clarity, and continuity planning through a down cycle.
• Were insiders accused of wrongdoing? Allegations of insider shorting and other misconduct circulated in secondary reporting and community discussion, but these remain unconfirmed in the public record. This article focuses on systemic operational gaps that are observable without relying on unproven claims.

Sources and Evidence

Evidence tiers: Tier 1 = primary notices and official announcements (highest reliability). Tier 2 = reputable journalism and major data aggregators. Tier 3 = community/social sentiment (context only, not factual proof).

• Tier 1–2: Kadena shutdown announcement (Oct 2025): The official Kadena communication was issued as an X post stating the organization would cease business operations and active maintenance immediately. For durability, this article relies on third-party sources that reproduce the wording and on exchange notices that reference the shutdown context. Binance.US notice · Binance withdrawals support notice (community-maintained chain) · Reporting (The Defiant)
• Tier 1: Exchange delistings (named notices): Binance.US delisting notice (Oct 28, 2025) · Bybit delisting notice (Oct 28, 2025) · OKX delisting notice (Oct 29, 2025) · KuCoin delisting notice (Nov 5, 2025) · Binance withdrawals support notice (ended Jan 12, 2026)
• Tier 2: Price and market data: Historical and current KDA price, market cap, and all-time-high data from CoinMarketCap. CoinMarketCap (KDA market data)
• Tier 1: Protocol documentation: Kadena technical documentation covering Chainweb and the Pact smart-contract language. Kadena Docs (Chainweb + Pact)
• Tier 2: Security scope reference: CertiK Skynet profile for Kadena (current and historical context via archives where applicable). CertiK Skynet
• Tier 1–2: Ecosystem funding announcements: Primary announcements for Kadena ecosystem programs (2022 and 2025). $100M grants (Business Wire, Apr 2022) · $50M grants (Kadena, May 2025)

Where social-media posts or community commentary are referenced, they are treated as sentiment indicators rather than factual proof and should be cross-checked against primary announcements and archived sources.

Last reviewed: 18 January 2026

The Credential Trap and What It Costs an Ecosystem

There is a recurring mistake in evaluating blockchain projects that Kadena exemplifies with unusual clarity. The mistake is treating institutional pedigree as a proxy for institutional competence. Ex-JPMorgan researchers who built production-grade blockchain infrastructure at scale are credible people. That credibility is real. What it does not transfer to is the organisational capability to run an ecosystem — to maintain developer relationships, to navigate funding cycles, to sustain community trust through technical turbulence, to make strategic pivots that keep a chain relevant when the competitive landscape shifts.

Those are different skills. They are not scarcer than cryptographic engineering talent, but they are different, and the crypto industry has a persistent blind spot about the distinction. Technical pedigree has become the primary signal investors use to evaluate teams, partly because it is legible and partly because the early history of the space produced cases where technical depth correlated with long-term value. Kadena had the technical depth. What it lacked was the operational layer — the unglamorous capacity to convert engineering excellence into a functioning ecosystem that developers wanted to build on and users wanted to use. That gap is not visible in a whitepaper. It only becomes visible in the years after launch, when the technical foundation is in place and what determines survival is everything that happens around it. The credential trap is that the evaluation framework that surfaces the good technical teams also obscures the bad operators — until it is too late for the ecosystem that trusted them.

The Discipline Deficit: What Kadena’s Collapse Says About Leadership When Technical Excellence Is Not Enough

Jocko Willink’s leadership framework begins with extreme ownership: every failure in an organisation traces back to a failure of leadership, and the leader’s job is to own that failure completely rather than distributing it across team members, market conditions, or circumstances beyond control. Kadena’s shutdown is a leadership autopsy that Willink’s framework reads with uncomfortable clarity: the technical architecture was genuinely excellent — the PoW scalability work, the Chainweb consensus mechanism — and the organisation still collapsed. When a technically excellent organisation fails, Willink’s framework identifies one root cause: the leadership failed to translate technical excellence into the organisational priorities, resource allocation, and communication discipline that would have given the technical work a chance to find the market it needed.

Willink’s four-law leadership framework — cover and move, simple, prioritise and execute, decentralised command — provides a diagnostic for where Kadena’s leadership failed. Cover and move means teams support each other toward the overall mission rather than optimising locally. Simple means the strategy is communicated clearly enough that every team member can explain it and act on it without a decision from above. Prioritise and execute means the leader identifies the most critical problem and dedicates resources to solving it before moving to the next. Decentralised command means the leader trains subordinates to make good decisions at their level without constant escalation. The pattern of blockchain organisations that fail after genuine technical achievement consistently shows the same leadership failure profile: brilliant engineers solving technically difficult problems in isolation, without the cover-and-move dynamic that would align the technical work with the ecosystem development work and the business development work into a coherent campaign.

The specific failure mode that Willink’s framework identifies in Kadena is the prioritise-and-execute breakdown. The organisation was simultaneously attempting to build a novel consensus mechanism, develop a new smart contract language (Pact), grow a developer ecosystem, attract institutional capital, and compete for DeFi TVL against established networks — each of these is a significant mission on its own, and pursuing all of them simultaneously with limited resources is a failure of prioritisation that leadership owns. Willink’s combat-derived observation is that units that attempt to accomplish too many objectives simultaneously accomplish none of them well enough to create the conditions for the next objective: the team that is split between five simultaneously executing missions will be outmanoeuvred by the team executing one mission with full commitment and then pivoting to the next. Kadena’s competition set — Ethereum, Solana, and later Sui and Aptos — were not technically superior in every dimension but were operationally more disciplined in their go-to-market sequencing. Enterprise AI adoption discipline faces the same prioritise-and-execute test: the enterprise AI teams that are attempting pilots across ten use cases simultaneously are exhibiting the same leadership failure that Willink identifies as the root cause of Kadena’s resource diffusion.

Willink’s principle of decentralised command has a specific implication for blockchain protocol development that the post-mortem on failed protocols rarely examines: the protocol teams that built the best technical foundations were often the ones where the leadership had not trained the team to operate independently. When the founding technical leadership’s attention was divided — between fundraising, conferences, and media — the teams that had been given clear enough intent to execute independently continued to make progress, while the teams that required leadership attention for key decisions stalled. Kadena’s developer ecosystem never achieved the self-sustaining growth that Ethereum’s ecosystem achieved partly because the Ethereum developer community had been given sufficient conceptual independence to build without waiting for core team direction. Crypto’s press release problem is the communications failure that Willink’s “simple” principle directly addresses: the organisation that communicates its mission through press releases rather than through demonstrated results has not internalised Willink’s simplicity requirement — the simple message is what the team can execute on, not what the marketing department can announce. Independent credibility is the Willink “results” test applied to ecosystem development: Wikipedia notability is what the mission looks like when it has been executed well enough that independent observers document it, rather than when the leadership has announced it. VC allocation to the next generation of Layer 1 protocols is a leadership quality test in aggregate: the protocols that attract the next funding cycle will be the ones whose leadership demonstrates the operational discipline that Kadena’s technical excellence could not substitute for. Prediction markets on new Layer 1 protocol launches in 2026 are pricing continued activity at the technical layer — which Willink’s framework reads as the market betting on founders rather than on whether the leadership discipline gap that killed Kadena will be avoided this cycle.

ISO 27001 and VaaSBlock’s Risk Management Authentication (RMA™) work together to strengthen security and credibility for blockchain organisations. ISO 27001 provides a globally recognised framework for managing information security, while RMA™ evaluates blockchain-specific risks such as governance, operational integrity and technical robustness. When a crypto platform holds both, it sends a clear signal to investors, partners and regulators that security and credibility are treated as core disciplines.

Introduction

As blockchain technology matures, crypto platforms, custodians and tokenisation projects are being asked tougher questions about security and governance. Institutional investors and regulated counterparties often look for ISO 27001 certification for crypto platforms, because it is a familiar standard in traditional finance. At the same time, they also want assurance about blockchain-specific risks such as smart contract behaviour, token design, team integrity and governance.

VaaSBlock’s Risk Management Authentication (RMA™) is designed to complement, not replace, ISO 27001. ISO 27001 focuses on information security management systems. RMA™ looks more broadly at how a Web3 organisation behaves, discloses risk and runs its operations. Organisations that achieve both can demonstrate that they manage information security through a formal framework and that their wider business practices have been independently reviewed.

Understanding ISO 27001 and Related ISO Standards

ISO 27001 is one of the best known international standards for information security management. In many financial institutions, cloud providers and large enterprises it is treated as a baseline expectation rather than a “nice to have”. For blockchain organisations, ISO 27001 can be the first serious step toward aligning security practices with the expectations of traditional finance and regulators.

What is ISO 27001?

ISO 27001 is published by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). It sets out how to establish, implement, maintain and continually improve an Information Security Management System (ISMS). An ISMS is a structured way of managing sensitive information so that confidentiality, integrity and availability are protected over time.

Key Objectives of ISO 27001

• Confidentiality: Make sure information is accessible only to authorised people.
• Integrity: Keep information accurate, complete and reliable.
• Availability: Ensure authorised users can access information and systems when needed.

Practical Applications Across Industries

ISO 27001 is widely used outside blockchain and is already familiar to many of the counterparties that crypto platforms want to work with:

• Financial institutions: Protect customer data, trading systems and payment flows.
• Healthcare providers: Safeguard patient records and meet privacy obligations.
• Technology companies: Secure cloud platforms, APIs and user information.
• Government agencies: Protect citizen data and sensitive internal systems.

Core Components

• Risk assessment: Identify information security risks and evaluate how serious they are.
• Security controls: Put policies, procedures and technical measures in place to reduce those risks.
• Continuous improvement: Review incidents, audits and changes so the ISMS is kept up to date.

ISO 27001 is valued because it provides a structured and repeatable way to manage information security. For crypto and digital asset custody platforms, it helps answer questions such as “how are private keys protected?”, “how are incidents handled?” and “how are security risks reviewed over time?”.

Understanding VaaSBlock’s RMA™

The Risk Management Authentication (RMA™) is VaaSBlock’s independent review framework for Web3 and digital asset organisations. The RMA™ badge is a tokenised credential that signals a project has been assessed for governance, operational integrity, transparency and technical security, not just code-level issues.

RMA™ fills the gap between narrow smart contract audits and broad but non-specialised certifications. It is relevant for wallets, custodians, token issuers and also for service firms such as marketing agencies, legal advisors and technology providers that work with blockchain clients.

The framework was built by a team with experience in Web3, insurance and international risk. It brings together lessons from traditional assurance practices and the practical realities of decentralised markets. Rather than focusing on one narrow dimension, RMA™ sets minimum expectations across multiple categories so that weak projects find it hard to pass.

RMA™ is not positioned as “better than” ISO 27001. Instead, it sits alongside ISO 27001 and other standards. ISO 27001 focuses on information security management. RMA™ focuses on blockchain-specific credibility and business conduct. Together, they provide a more complete picture for investors, partners and regulators.

Key Objectives of RMA™

• Enhance credibility: Help investors and communities distinguish serious projects from unreliable ones.
• Promote transparency: Encourage clear explanation of structures, risks and dependencies.
• Foster trust: Provide an independent view of how a project manages security, governance and operations.

Core Components

• Comprehensive verification: Structured questionnaires and workshops covering technical design, legal position, governance, operations and market behaviour.
• Technical reviews: Assessment of smart contract architecture, cybersecurity posture and supporting infrastructure, which may include specialist audits.
• Business evaluation: Review of compliance, governance arrangements, crisis planning and evidence of responsible decision-making.

Comparing RMA™ and ISO 27001

Scope and Focus

ISO 27001

• Information security: Focuses on policies, procedures and controls to manage information security risks.
• Cross-industry use: Designed for organisations in any sector that handle sensitive information.
• Formal risk process: Requires documented risk assessment, treatment and review.
• Internal practice: Concentrates on how the organisation manages its own systems and data.

RMA™

• Blockchain-specific credibility: Built for decentralised and token-based business models.
• Multi-dimensional evaluation: Combines technical, legal, governance and reputation considerations.
• Trust in Web3: Helps address scepticism by showing how an organisation behaves in practice.
• External reputation: Considers how the organisation is perceived by users, partners and regulators.

Certification Process

ISO 27001

1. ISMS implementation: Design and implement an information security management system.
2. External audit: Undergo an audit by an accredited certification body.
3. Ongoing monitoring: Maintain compliance through surveillance audits and internal reviews.

RMA™

1. Questionnaire and workshops: Provide detailed information and participate in review sessions.
2. Rigorous examination: Assessment of controls, governance, legal posture, team reliability and market risks.
3. Badge issuance: If standards are met, a tokenised RMA™ badge with a verifiable QR code is issued.
4. Optional communication support: VaaSBlock may assist with communicating the result, without promising specific marketing outcomes.

Benefits

ISO 27001 Benefits

• Recognised security baseline: Familiar to banks, institutional investors and regulators.
• Supports compliance: Helps align with data protection and security obligations.
• Clear governance structure: Encourages well-defined roles, processes and documentation.
• Improved resilience: Reduces the likelihood and impact of security incidents.

RMA™ Benefits

• Web3-relevant credibility: Addresses concerns specific to crypto, such as scams and weak governance.
• On-chain verification: Tokenised badges and QR codes make verification straightforward.
• Broader scope: Looks beyond security to behaviour, communication and team integrity.
• Network effects: Connects verified organisations within the RMA™ ecosystem.

Diving Deeper: Differences and Synergies

Technical vs. Business Focus

• ISO 27001: Concentrates on information security management inside the organisation.
• RMA™: Covers both technical security and how the organisation runs and presents itself to the market.

Industry Challenges Addressed

ISO 27001

• General information security risks: Suitable for any organisation that stores or processes sensitive data.

RMA™

• Blockchain’s credibility gap: Responds to concerns about scams, poor governance and limited disclosure.
• Regulatory uncertainty: Encourages proactive compliance and clear explanations of risk.
• Smart contract and token risks: Promotes thoughtful design and scenario planning.

Tokenization and Verification

RMA™ Badge Tokenization

• Tokenised certification: Each RMA™ badge is represented on-chain and linked to a unique QR code.
• Simple verification: Third parties can confirm the status of a badge without relying on screenshots or static PDFs.
• Aligned with blockchain principles: Uses verifiable, tamper-resistant infrastructure.

ISO 27001 Certification

• Traditional certification: Issued as a formal certificate by an accredited body.
• Verification: Usually confirmed through the certifying body or the organisation’s compliance team.

Cost and Time Investment

ISO 27001

• Resource heavy: Requires significant time and effort to implement and maintain an ISMS.
• Ongoing commitment: Needs internal audits, management reviews and periodic external audits.

RMA™

• Focused but detailed: Designed to be practical for blockchain teams while still thorough.
• Variable duration: Time depends on project complexity and how quickly information is supplied.

Which Certification is Right for You?

Many blockchain organisations will benefit from pursuing both ISO 27001 and RMA™. ISO 27001 demonstrates that information security risks are handled through a formal management system. RMA™ shows that blockchain-specific risks, governance and communication have been independently reviewed. Together, they support stronger conversations with exchanges, institutional investors and regulators.

Consider Pursuing ISO 27001 if:

• Your organisation handles sensitive customer or transaction data across multiple systems.
• You work with banks, funds or institutions that already use ISO 27001 as a benchmark.
• Regulators or counterparties ask for documented information security controls.
• You are ready to invest in a long-term security management framework.

Consider Pursuing RMA™ if:

• Your organisation operates in the blockchain or Web3 space.
• You want independent validation of credibility, governance and operational integrity.
• Your users, investors or partners are concerned about scams, weak governance or limited transparency.
• You want to be visible within a network of projects that have passed an external review.

Consider Pursuing Both if:

• You want to demonstrate that information security and broader business conduct are both taken seriously.
• You work with counterparties in both traditional finance and Web3 communities.
• You plan to scale digital asset products that must satisfy multiple layers of scrutiny.

For organisations that handle both internal data and on-chain value, ISO 27001 and RMA™ together provide a more complete picture than either in isolation. ISO 27001 addresses information security management. RMA™ extends that foundation into blockchain-specific credibility and risk.

Benefits of Dual Certification

• Stronger trust signal: Combines a familiar global standard with a blockchain-specific review.
• Better positioning with institutions: Helps bridge the gap between Web3 projects and traditional financial stakeholders.
• Regulatory readiness: Supports future regulatory engagement by showing proactive risk management.
• Broader risk coverage: Addresses both information security and industry-specific vulnerabilities.

The Jobs-To-Be-Done Diagnosis: Why RMA And ISO 27001 Compete For Different Customer Jobs

The standard comparison between RMA and ISO 27001 treats them as overlapping frameworks that a company should pick between based on cost, time to certify, and industry preference. The jobs-to-be-done lens produces a different and more useful framing: the two frameworks compete for fundamentally different customer jobs, and the “which one should we get” question only resolves cleanly once the customer’s underlying job is named accurately.

ISO 27001 is hired for one job most reliably: signalling baseline information-security maturity to enterprise procurement teams who use the certification as a gating criterion. The job is, in practice, “let me through the procurement firewall.” ISO 27001 does this well. It also does some other things, including establishing internal governance discipline, formalising risk-management practice, and producing audit-able documentation. But the procurement-signalling job is the one customers consistently report as the primary reason for getting certified, and it is the job that determines whether the certification is worth its considerable cost.

RMA is hired for a different job — establishing credibility in markets where conventional certifications either do not apply or do not yet carry the signal. The job is, in practice, “let me operate where my Web3 counterparties want operating-discipline evidence and ISO 27001 does not translate.” For a Web3-native business selling to other Web3-native counterparties, ISO 27001 does not consistently move the conversation; the framework was designed for an enterprise environment that crypto’s customer base often is not. RMA fills the gap not by being a better certification in any abstract sense, but by being a certification calibrated to a customer job that the existing certification market does not serve cleanly.

The implication of the JTBD framing is that “which should we get” is a poorly-posed question. The right question is “which customer job is load-bearing for our growth, and which framework is calibrated to that job.” A Web3 business selling primarily to traditional enterprises through traditional procurement should pursue ISO 27001 because the procurement-signalling job is the binding constraint. A Web3 business selling to Web3-native counterparties whose evaluation criteria are different should pursue RMA because the credibility-establishment job in that customer base is what RMA was designed for. A business selling to both — increasingly common — has a more complex decision, and the JTBD framing helps it pick which framework to pursue first based on which customer segment is more urgent rather than on which framework is “better.”

This is also a useful frame for evaluating the broader question of whether the certification landscape will consolidate. The standard prediction is that one framework eventually dominates and the others fade. The JTBD reading suggests the opposite — frameworks calibrated to genuinely different customer jobs tend to coexist indefinitely, because each one is the right answer for its specific job. ISO 27001 and SOC 2 have coexisted for two decades for exactly this reason: they were designed to do different jobs, and the markets that hire one rarely hire the other interchangeably. RMA is positioned to coexist with ISO 27001 in the same way, in the customer segments where the Web3 evaluation criteria differ structurally from the enterprise procurement criteria.

The connection to the broader operating-standards conversation in Web3 is that frameworks are tools, not destinations. The professional Web3 protocols will be the ones who picked the framework that matched the customer job they were trying to serve, ran it competently, and renewed it. The amateur Web3 protocols will be the ones who picked the framework that sounded most impressive, ran it as a checkbox exercise, and discovered the customer job was somewhere else.

The Accountability Discipline Behind the Certificate: What Either Framework Actually Demands

Jocko Willink’s extreme ownership principle is that accountability cannot be delegated — the leader who says “my team failed to execute” has already failed, because the leader’s job is to create the conditions where the team executes. Applied to compliance frameworks, the extreme ownership principle identifies the most common failure mode in certification programs: organisations that pursue the certificate without building the accountability culture that the certificate is supposed to attest to. The document exists; the discipline does not. The audit passes; the operating posture it was designed to measure does not exist in day-to-day operations. ISO 27001 and RMA both fail in the same way when applied by organisations that treat them as documentation exercises rather than operating disciplines.

Willink’s distinction between decentralised command and delegated responsibility is the one that maps most precisely to the compliance framework question. Decentralised command means the individual at every level of the organisation has clear decision-making authority and clear accountability for the outcomes of those decisions within their domain. Delegated responsibility means the person at the top of the hierarchy has assigned accountability to someone else. The compliance certificate that is earned through delegated responsibility — a dedicated compliance officer who manages the certification process while the rest of the organisation operates independently of the framework — produces a certificate that represents the compliance officer’s competence, not the organisation’s operating posture. The certificate that is earned through decentralised command — where every team lead understands what the framework requires of their domain and owns the accountability for maintaining it — represents a genuine operating state.

The specific operating disciplines that distinguish the two approaches are visible in the audit preparation cycle. The delegated-responsibility organisation’s audit preparation looks like a sprint: documentation is gathered, processes are temporarily adjusted to match the required controls, and the organisation returns to its normal operating posture after the audit completes. The decentralised-command organisation’s audit preparation looks like a normal period: the controls are already in place because they are part of the operating culture, and the audit is a verification of an existing posture rather than a temporary correction toward a posture that will be abandoned afterward. Enterprise AI compliance adoption is exhibiting the delegated-responsibility pattern at scale: organisations are assigning AI governance accountability to a dedicated function (Chief AI Officer, AI Governance committee) rather than building the decentralised command accountability where every product team owns its AI-related risk posture. The result is AI governance that exists in the committee’s documentation but not in the product team’s daily decision-making.

Willink’s prescription for building genuine accountability culture — as opposed to compliance documentation culture — is to make the accountability visible and immediate at the level where the decisions are actually made. For ISO 27001, this means the engineer who makes a deployment decision that affects the security control environment owns the accountability for that decision’s compliance implications, not the compliance officer who reviews the deployment log two weeks later. For RMA, this means the business development team that onboards a new counterparty owns the accountability for that counterparty’s RMA verification status, not the compliance team that processes the verification paperwork. Corporate governance accountability in the capital allocation context shows the same discipline gap: companies that have clear accountability frameworks for operating decisions but vague accountability for capital allocation decisions produce the same pattern — the accountability culture exists where it is incentivised and disappears where it is delegated. Wikipedia’s decentralised editorial accountability is an unusual example of Willink’s principle applied to a non-hierarchical structure: each Wikipedia editor owns the accountability for the accuracy of the content they touch, and the decentralised accountability is maintained not by a compliance officer but by a community norm that makes individual accountability both visible and consequential. VC portfolio governance in the crypto infrastructure cycle faces the same choice: build decentralised command accountability into portfolio companies’ compliance structures during the funding process, or accept delegated responsibility structures that produce certificates without operating disciplines. Berachain’s validator accountability architecture is attempting to encode Willink’s extreme ownership at the protocol level: the proof-of-liquidity mechanism makes each validator’s accountability for liquidity provision immediate and financially consequential, not delegated to a governance committee that reviews validator behavior quarterly. Prediction markets on enterprise compliance audit failure rates are pricing the delegated-responsibility compliance posture at a discount — which is the market applying Willink’s discipline principle to the question of which certification actually represents an operating posture versus which represents a documentation exercise.

Certificates as Shared Fictions: What a Standard Actually Does

A certificate contains no security. It is a piece of paper, or lately a record in a database, and it protects nothing on its own. What it does is allow two organisations that have never met, share no legal system, and have no basis for trusting each other to behave as though they do. That is not a small thing. It is one of the more durable technologies humans have built, and it long predates information security.

English silver has carried assay marks since a statute of 1300 required them, because a buyer holding a spoon cannot determine its silver content by looking. Lloyd’s Register began classifying ships in the eighteenth century so that an underwriter in London could price a hull he would never see, in a port he would never visit. In each case the same move is being made: an unobservable property is converted into an observable mark, and a shared willingness to treat the mark as meaningful does the rest. The mark has no power. The agreement to honour it does.

Read this way, the comparison between ISO 27001 and the RMA is less a contest between two documents than a question about which shared fiction a given counterparty already participates in. ISO 27001 works because procurement departments, insurers, and regulators across a large part of the world have agreed in advance what its mark means; its value derives from the size and age of that agreement rather than from the controls themselves, which any organisation could implement without ever being audited. The RMA is a younger agreement addressing a population — crypto counterparties, token issuers, on-chain treasuries — that the older one was never designed to describe.

The mechanism differs in one way worth noticing. Historically these marks were expensive to check: you trusted the assay office because verifying it yourself was impractical. On-chain verification changes that cost structure, because the mark and its provenance can be inspected by anyone at effectively no cost. Whether that produces a stronger fiction or merely a cheaper one is genuinely open. Cheap verification removes the forgery problem that hallmarking existed to solve, but it does not by itself create the thing that made hallmarks matter, which was several centuries of everyone agreeing to care.