Neutron emerged from a practical argument about where Cosmos applications should run. The Hub was primarily a coordination and security network, while developers wanted a permissionless CosmWasm environment. In its March 2025 retrospective, Neutron connected its founding to Hub funding and the original shared-security arrangement. It described a relationship in which the Hub supplied security and Neutron supplied application execution. That was an institutional bargain between networks and contributors, rather than a claim that every Neutron contract became part of the Hub itself.

Informal Systems' engineering account records the consumer-chain launch on May 11, 2023. Its discussion of validator keys, genesis preparation and launch problems is a useful counterweight to a frictionless launch story. Replicated Security required real operators to coordinate another chain, and the first deployment exposed operational assumptions that software descriptions could conceal. Historical announcements also used May 10 for the coordinated launch effort.

The engineering retrospective anchors the successful consumer-chain event here, while preserving the difference between preparation and an operating network.

The documented Interchain Queries module let a CosmWasm contract request information from another chain and verify submitted results against an IBC client. A relayer gathered the data and proofs, while Neutron checked them before passing results to the contract. That division matters: a valid proof establishes a particular remote state, but does not make a slow relayer timely or an application decision sensible. The documentation also records an empty-value limitation for key-value queries, an important warning against treating missing output as a confirmed zero balance.

Interchain Transactions served a different purpose. A contract could manage an account on a connected chain and send instructions through IBC, then process acknowledgments or timeouts. The module documentation specifically excludes direct registration through ordinary user CLI commands. Its asynchronous callbacks mean a cross-chain action is a sequence with intermediate states, rather than one instantaneous operation across all ledgers.

These documents explain Neutron's original development proposition; current contract availability and compatibility still require checking the deployed software and application involved.

Neutron's Cron documentation describes recurring contract execution measured in blocks. A schedule specified messages and a block interval, subject to governance approval and limits on work per block. This could support maintenance or distributions without each beneficiary submitting a transaction. It also connected automation to administrative authority: a useful schedule was still a privileged decision, and block-based timing was not a promise about a precise wall-clock minute.

The retained documentation is evidence of that design, not assurance that an old schedule remains active after later migrations.

The historical wstETH bridge used an Axelar General Message Passing connection and a Neutron tokenfactory representation. The bridge documentation distinguishes Ethereum custody from the representation circulating on Neutron and describes validator, administrative and upgrade dependencies. An asset name therefore did not erase its route into the chain. A reader examining an old pool must identify the exact denomination and bridge arrangement, rather than infer that any token labelled wstETH has the same exit process as Ethereum wstETH.

In March 2025, Neutron proposed leaving Replicated Security and funding a sovereign validator set. It argued that the Hub's changing priorities and Neutron's own development justified a new relationship. The proposal also sought to redistribute NTRN held through the earlier arrangement and compensate validators during the transition. These were linked economic decisions, not merely a software switch. Claims that one side had failed the other belong to the proposal's political argument and should remain attributed to its authors.

Govmos supported reconsidering the old replicated model but preferred Partial Set Security to complete separation. Its March 19 response challenged the account that the Hub had failed to provide the promised service and questioned returning community-held NTRN. That disagreement reveals competing ideas of ownership: one side treated unused allocations as resources for the next stage, while the other emphasized the original funding agreement. Neither position can be reduced to a technical benchmark, and the disagreement did not make all Hub participants opponents of Neutron.

Cosmic Validator challenged both the size of the proposed security budget and the selection of roughly twenty operators. Its March 18 post compared the proposed arrangement with earlier compensation for the much larger Hub set and asked why longstanding contributors were excluded. This is evidence of an operator's distributional objection, not proof of the favoritism alleged in the post. It does show why a smaller set could be controversial even when proponents believed it would simplify coordination and make infrastructure spending more predictable.

The retained Mercury-era validator guide described treasury-funded compensation, a monthly dollar target converted into NTRN, and a separate delegator reward target. It also described jailing and rotation instead of ordinary slashing. Those arrangements depended on treasury resources and an operating payment mechanism. They were not interest owed by an external guarantor.

More importantly, this is historical documentation: the subsequent v11 release explicitly reported failing payments and changed the network's economic machinery, so its old reward descriptions cannot responsibly be advertised as present terms.

The earlier governance architecture used customized DAO DAO contracts, voting vaults and subordinate committees. Vaults could recognize NTRN represented in different positions, including staking and liquidity-related holdings. Committees could handle routine work while tokenholders retained an overrule mechanism. This addressed a real participation problem: requiring every holder to vote on every operational detail can exhaust attention.

It also meant that understanding a vote required following the relevant contract and permission, rather than assuming every action passed through a single familiar Cosmos voting screen.

That documentation distinguished unrestricted privileged authority from permissions limited to particular message types. It described a Security SubDAO with pause powers and timelocks for subordinate decisions. These distinctions matter when reading later attacks, but the old contract diagram is not a forensic description of every later governance path. In particular, an overrule delay attached to one committee did not establish that all administrator changes everywhere were delayed. Authority must be traced through the actual version and execution path involved.

By March 2026, public application notices were already about unwinding particular services. Astroport's March 25 announcement relayed instructions for holders to return bridged wstETH to Ethereum by June 30. This was a concrete exit deadline for a particular asset route, not a declaration that every IBC connection or Neutron token had disappeared. It is also why an old integration page can mislead a current reader: documentation may preserve the original mechanism after the operator has asked users to leave it.

Astroport's April 20 notice told users to withdraw liquidity from Neutron Supervaults. The linked Neutron announcement described the DEX as withdrawal-only and said SuperVaults were no longer actively trading. For a strategy that relied on active management, continued ownership of a position was not equivalent to continued operation of the strategy. These warnings predated the September attack. Keeping the chronology straight prevents an unrelated later incident from becoming the explanation for every earlier product closure or disappointing position.

The May 12 v11 release said Hadron Labs' maintenance engagement would end on June 30. It also stated that token voting had failed to reach quorum since April 1 and that a previously elected privileged multisig submitted the upgrade height. The release warned that the old binary was already failing to provide validator payments. This primary record is unusually important: an upgrade described as a stability measure followed a breakdown in the ordinary governance process, rather than a routine successful tokenholder vote.

Operator instructions scheduled an in-place migration at height 56,277,000, approximately May 13. They retained the chain identifier neutron-1 and emphasized backups, validator signing state and coordinated restart. Continuity of a chain identifier means continuity of a ledger, not continuity of every economic rule. The instructions also contain inherited rollback language about a successful yes vote, which should not override the explicit explanation of the multisig submission. The specific release account is clearer evidence of how this upgrade was authorized.

The versioned upgrade code deactivates the old DAO voting vaults and initializes Cosmos governance, minting and distribution parameters. Its mint configuration contains nonzero minimum and maximum inflation parameters, while its governance configuration includes ordinary and expedited voting periods. It also transfers specified administrative roles and funds to the governance module. These are observations of the published migration code, not a live query of today's parameters.

They are sufficient to reject an undated claim that the old fixed-supply, custom-vault model remained unchanged indefinitely.

Cosmos Labs' September 25 recovery account dates the Neutron governance attack to September 22. It reports that the attacker obtained contract administration, drained application liquidity and bridged stolen ATOM to the Hub. The Hub itself was not exploited, according to that account. Its validators nevertheless halted the Hub to contain funds, creating an availability cost for users on another network. Interoperability therefore mattered twice: it enabled asset movement before the intervention and required coordination across independent communities afterward.

Astroport's September 29 announcement linked the post-mortem and described a bought vote passing Proposal 9, followed by the transfer of administration over eight Astroport contracts. Astroport distinguished that path from an exploit in the contracts' own logic. This distinction does not make the losses less real. It identifies a different security boundary: code can behave as instructed after governance gives an attacker permission to replace or administer it. A reassuring audit of application logic alone would not answer that authority question.

The Hub recovery account states that 1,227,121 ATOM was moved into a four-of-six recovery multisig when the Hub resumed. It also describes a later THORChain refund that escaped the initial containment and says distribution required further coordination and governance. These details rule out a simple claim that every stolen asset had been recovered and returned. Emergency custody, a restoration plan and a completed repayment are different events, each requiring its own evidence and transaction record.

Astroport's September 25 update said Neutron was producing blocks again and affected contracts had been restored. At the same time, it told users not to interact with affected pools or unstake xASTRO because those actions remained paused. Its September 29 notice preserved that distinction. As of this review, those original notices support restored network operation with outstanding application-level restrictions. They do not support treating an old dashboard balance, a recovery multisig balance and immediately spendable funds as interchangeable.

Finessence's September 24 community draft proposed treating governance as a security-critical system. It suggested mature voting power, snapshots, delays and separate review of dangerous administrative actions. The author explicitly invited technical criticism and described the document as a discussion draft. Its value is the set of questions it raises about rapid conversion of economic ownership into administrative control. It is not evidence that those safeguards were deployed, nor a substitute for the operators' own forensic account of the incident.

Neutron's retained tokenomics document is now useful partly as a historical artifact. It records initial allocations to treasury, reserve, team, investors, airdrops and liquidity bootstrapping, together with a fixed-supply narrative from an earlier period. That narrative helped holders frame the asset as scarce infrastructure exposure. The document cannot by itself settle the economics after a later minting-module migration.

A serious investment thesis must identify the current rules, funding obligations and recoverable application use, rather than recycle a supply slogan from an obsolete operating model.