ACA belongs to the Acala network, while DOT belongs to Polkadot and LDOT represents participation in Acala's DOT liquid-staking protocol. The current introduction organizes the project around liquid staking and liquidity distribution through Euphrates. This is different from describing every asset on Acala as a stablecoin or assuming ACA itself represents deposited DOT. The distinction also matters economically: using a financial application, holding a receipt token and owning the chain's governance token expose a person to different rules and sources of demand.

The EVM network configuration identifies Acala mainnet as chain 787 with ACA, alongside separate Karura and test environments. That number identifies an Ethereum-style transaction domain, not Ethereum settlement. A shared development stack can serve multiple chains without merging balances or governance. The documentation also distinguishes production endpoints from beta infrastructure. An application that connects successfully to some Acala-branded endpoint has not, through that fact alone, demonstrated that it is interacting with the intended production network.

The launch record describes a sequence rather than one moment when every feature became available. Genesis, token distribution, technical checks, council governance, removal of the sudo module, transfers and financial protocols were separate stages. Polkadot validation and local collator operation also served different roles. The page retains an old current-phase heading despite marking later stages complete, illustrating why archived rollout pages require careful reading. Their sequence explains initial administrative control; it should not be copied as the current operating phase.

The crowdloan FAQ distinguished a direct Polkadot contribution from the optional Liquid Crowdloan route. The latter initially required trust in a Foundation-managed vault and provided lcDOT, a transferable claim associated with the locked contribution. Selling that receipt meant giving up the corresponding redemption claim while leaving the separate ACA reward entitlement intact. This was not ordinary DOT staking, and lcDOT was not LDOT. The historical arrangement offered liquidity for a locked position, with a custody transition that the project's own documentation explicitly disclosed.

Acala's EVM+ rationale argued that another cheap Ethereum imitation was insufficient. Its proposed advantage was access to financial modules in the Substrate runtime, including swaps and liquid staking, through familiar contract tools. That architecture allows the chain's economic and governance logic to evolve alongside application contracts. It also means compatibility should be assessed at the interface actually used. A Solidity developer cannot infer that every fee rule, upgrade permission or native-asset interaction behaves exactly as it does on Ethereum.

The account documentation describes linking an Ethereum address with a Substrate account by proving control of both. This supports interaction through a more unified account experience rather than requiring users to manage every operation as a separate identity. The link is an explicit mapping, not a claim that any two similar-looking addresses belong to the same person. For application designers, the useful question is which account authorizes the operation and which balance it touches. Simplifying the interface does not remove those underlying authorization boundaries.

Flexible-fee documentation says an accepted token can pay transaction costs while the fee is ultimately settled in ACA. A supported liquidity route makes that conversion possible. The convenience is therefore conditional on token support and available liquidity, rather than a promise that any arbitrary asset can pay fees. It separates the token a user sees leaving a wallet from the native token used by the fee system. Demand generated by fees depends on actual transactions and their costs, not just the existence of this feature.

Acala's exchange-transfer guide addresses another practical boundary: an exchange may support DOT without supporting DOT deposits on Acala. Native ACA support and support for other representations must be checked independently. A ticker on a deposit screen is insufficient to identify its network route. This is not evidence that all exchange routes are unavailable today; the document establishes the distinction users need to make. Historical lists of supported venues should never be treated as a permanent guarantee that a particular deposit method remains open.

The September 20, 2022 incident report traces the August 14 failure to a misconfigured parameter in deprecated DEX-saving reward logic. Claiming incentives from the iBTC/aUSD pool produced unintended aUSD, which some recipients exchanged and moved elsewhere. Urgent governance actions paused affected functions. This was an application-runtime failure, not proof that Polkadot's consensus had been broken. The number of erroneous tokens is also not a dollar-loss estimate: swaps, recoveries and remaining liabilities need separate accounting.

Bette Chen's August 22 update reported tracing 3.022 billion erroneous aUSD and burning approximately 2.97 billion through governance actions at that stage. It also described transfers into other chains and exchanges and the work still required to restore pool balances. These are dated recovery figures from the team, not an assertion that every affected person was made whole. The update makes clear that correcting token supply and restoring ordinary services were related but different tasks.

In a November 2022 interview, Chen described reopening liquidity withdrawals, then debt-position management and finally other trading functions. She argued that collateral backing would eventually restore aUSD's price relationship. The interview records the co-founder's expectation, not a guarantee or a later verified outcome. Its distinction between collateral and a market trading price remains useful. A collateralized position can still have constrained exits, governance dependencies or a secondary-market discount, so technical recovery should not be equated with immediate economic recovery.

The token-transfer documentation records the conversion from aUSD to aSEED on July 20, 2023 while retaining the internal AUSD currency identifier. An unchanged code identifier therefore does not mean the product kept its old monetary promise. Wallets and integrations need the current display name and economic description, not only the storage key. This is also why an old screenshot or contract interface can remain recognizable even when the rights and intended use associated with that asset have changed.

The integration guide explicitly states that aSEED has no pegged price and provides different EVM representations on Acala and Karura. Its value must be considered in relation to the relevant underlying treasury assets and redemption rules. Similar branding does not establish a single common pool across both chains. Nor does a one-for-one conversion of the old token count establish one dollar of redemption value. Some wording about future redemption remains in this guide and must be read alongside the later activation record.

Referendum 140 is marked executed and sets out the decision to enable Acala aSEED collateral redemption without waiting for the indicative basket value to reach one dollar. The author qmzm emphasized optional exits rather than compulsory redemption. The proposal's asset quantities and estimated value were snapshots used in that decision. They are evidence of the reasoning and approved mechanism, not current treasury balances. It would be misleading to turn the proposal's old dollar estimate into a standing exchange rate.

The subsequent redemption guide confirms that the feature went live after referendum 140. It instructs holders to inspect the current aSEED value and receive underlying assets, with LDOT, DOT and USDCet shown in its example. Those are assets with their own price, staking or bridge properties, rather than cash paid by a bank. This record supersedes older roadmap language that still presents redemption as future work. It does not establish that every redemption at every later block has the same composition.

Council motion 347 separately proposed unlocking aSEED held in twenty-eight accounts, with a stated aim of treating holders fairly and improving circulation. Its execution record is distinct from the redemption feature. Unlocking a balance, permitting a transfer and allowing redemption are different actions. The proposer also discussed exchange-held assets, but an onchain change does not automatically prove that every exchange credited its customers. The actual chain record and the custodian's account policy remain separate pieces of evidence.

The LDOT documentation describes a token representing DOT staked through Homa, with uses in liquidity pools and validator selection. Its central promise is preserving a transferable position while the underlying stake works on Polkadot. That does not make LDOT identical to unencumbered DOT in every circumstance. Exiting through a market and exiting through the staking protocol are different routes. Their prices, waiting periods and available liquidity need to be understood separately instead of collapsed into a single advertised yield.

The Homa SDK guide distinguishes delayed unbonding, matching against new deposits for a fee and swapping through liquidity pools. Its worked example describes a twenty-eight-day slow route and conditions fast redemption on pending liquidity. The example is an explanation of mechanisms, not a live quote or a permanent timing warranty. A liquid token gives its owner another way to transfer exposure; it does not force a buyer to pay the underlying redemption value or guarantee an immediate protocol exit.

Euphrates' October 2023 launch explanation separates underlying DOT staking rewards, ACA incentives chosen through governance and additional partner rewards. Combining those sources in an interface does not make them equally durable. Native staking economics, a subsidy budget and a partner promotion can change independently. The article also records Euphrates' September 26, 2023 inception and the transition of earlier liquid-crowdloan positions. That history helps explain the product's audience without presenting launch-period rewards as rates available to readers today.

The September 2023 Exodus announcement described governance-approved ACA emissions of one hundred million annually for six years, split between staking and liquidity or application incentives. Burns were intended to offset some issuance under specified policies. This replaced the simple historical fixed-supply narrative. A burn mechanism can coexist with net inflation, and rewarding participation can dilute holders who do not participate. The substantive economic question is whether subsidized liquidity remains useful once the subsidy changes, not whether the word burn appears in the design.

The governance guide describes referenda, a General Council, a Technical Committee and specialized financial or staking bodies. It also describes emergency fast-tracking and an authorized oracle collective. Some passages are explicitly a phased design, so they should not be treated as proof that every promised election transition occurred. The important control distinction is that network validity, price inputs, financial parameters and emergency intervention are not one mechanism. A reader should examine the relevant decision path for the particular action being assessed.

The LDOT candidate guide requires an insurance bond and selection through nominators, and warns that the bond can be slashed. It contains inconsistent example amounts for the minimum bond, so this entry does not present either number as a verified live threshold. The durable point is that eligibility and actual selection differ. Candidate incentives and an insurance mechanism can help organize accountability, but their existence alone does not guarantee that all losses are covered or that a particular validator is currently selected.

DFG's November 2021 investment essay explains its conviction through an integrated DeFi suite, developer tools and the expectation that Polkadot would need a financial hub. The firm disclosed a planned five-hundred-thousand-DOT crowdloan contribution. Its projections and comparisons belong to an interested investor's thesis, not an independent verdict on future success. This source is valuable precisely because it states why a backer participated, including assumptions that readers can compare with the network's later technical and economic history.

The Old Friend NFT record shows another kind of attachment: early testnet participants received recognition for helping explore the platform before mainnet. Those community objects mark participation and memory, rather than automatically granting a financial claim. They help explain why a project's supporters are not exclusively traders evaluating a price chart. Developers, testers and longtime users may value a common history, while still expecting governance and communications to respond honestly when an important product fails.

The May 19, 2025 ecosystem report says aSEED conversion and redemption were completed and describes progress on Sinai, liquid-staking integrations and cross-chain infrastructure. Snowbridge and Hyperlane integration were still described as nearing completion. The report also records coretime renewals for both networks at that time. It supports those dated statements, not an unlimited renewal guarantee or an assertion that every listed integration is currently operational. Its concrete completed items should be separated from its forward-looking integration language.

The August 2025 JAMVerse article presents a roadmap toward JAM-native services, including a Swift client, testing, security work and eventual production deployment. Its milestones describe an intended future architecture. The reviewed source does not establish that Acala completed a mainnet migration to JAM by September 2026. New naming and ambitious diagrams are insufficient evidence for changing the network's identity. An implemented migration would require actual activation records and a clear account of how existing balances and services moved.

The August 13, 2026 release page provides a more recent but narrower maintenance signal: maintainers published governance-parameter changes intended to prevent spam. Its title names Acala and Karura 2.37.0, while the embedded Karura details still name 2.36.0 and June artifacts. That inconsistency is retained as a verification limit rather than silently resolved. A published release proves maintenance activity, not its activation on either network or the absence of operational problems after publication.