Source retrieved 2026-07-05Official documentation root used for curated protocol background; it still describes GG20 at review time, but current safety and migration state require dated incident and release sources.
Source retrieved 2026-07-05Official archived feature index marking Savers and Lending as deprecated, no longer available, and preserved only for historical reference.
Source retrieved 2026-07-14Official high-level app-layer overview; economic examples are design framing, while current WASM, secured-asset, and trade-account availability still needs live controls.
Source retrieved 2026-07-04Historical 2022 educational explainer for Asgard vault, TSS, and churn mechanics; fixed node-count and cadence examples are not current configuration proof.
Source retrieved 2026-07-05Official RUNE and TCY tokenomics overview, including TCY supply, revenue share, and no-governance-rights caveat; current amounts and distributions still require live evidence.
Source retrieved 2026-07-14Official RUNEPool overview for aggregate POL participation, units, deposits, withdrawals, and PnL fields; its fixed pool-count prose is not current POL-scope proof.
Source retrieved 2026-07-14Current-only RUNEPool accounting endpoint; production evidence pins it to the same Liquify provider and THORChain height as Mimir before interpreting global, provider, reserve, value, PnL, or deposit fields.
Source retrieved 2026-07-05Developer-facing TCY mechanics, claim, staking, and recovery caveats, including the explicit warning that full debt recovery is market dependent and not guaranteed.
Source retrieved 2026-07-05Dated THORFi unwind postmortem with January-February 2025 liability, pause, and Proposal 6 milestones; its implementation-status section is historical, not current TCY availability proof.
Source retrieved 2026-07-04Official root-cause report for the May 2026 GG20/TSS vault exploit, patched v3.19.1 recovery, and still-planned migration away from GG20.
Source retrieved 2026-07-14Official user-facing explanation of native cross-chain swaps routing internally through RUNE-paired pools; current execution still needs quote and operational evidence.
Source retrieved 2026-07-14Official RUNE settlement, liquidity, security, governance, and incentive framing; broad value/security statements remain design claims rather than current market or safety proof.
Source retrieved 2026-07-14Official CLP mechanism and historical IL-protection reference; it explicitly says IL protection was removed, while current route, depth, and yield claims still need live evidence.
Source retrieved 2026-07-05Official technology docs for Bifrost, TSS, Asgard vaults, vault migration, and churn-related mechanics; pair with dated security sources for the current signing scheme and incident posture.
Source retrieved 2026-07-02Official documentation root used for curated protocol background; it still describes GG20 at review time, but current safety and migration state require dated incident and release sources.
Source retrieved 2026-07-14Official LP role, symmetric/asymmetric deposit framing, withdrawal model, fee income, and impermanent-loss risk; current LP controls and APY still need live evidence.
Source retrieved 2026-07-14Official FAQ for asymmetric deposit and withdrawal rules, fees, liquidity-unit ownership, and position caveats; live controls own current action availability.
Source retrieved 2026-07-05Current-only network totals; pair with visible source freshness before treating values as live.
Start with the liquidity-action evidence ladder, then use RUNEPool/POL boundaries, live network diagnostics, and Midgard stats before interpreting CLP mechanics, APY, or transaction evidence.
Source retrieved 2026-07-14Official asset-notation reference for chain.asset and token identifiers used in quotes, pools, and memos.
Start with the build/query plan, then connect source-family boundaries, halt controls, quote/refund behavior, and interface checks before shipping a data or transaction workflow.
Source retrieved 2026-07-14Official node lifecycle and churn reference for Whitelisted, Standby, Ready, Active, and Disabled status, churn-out criteria, and the Standby-only unbond boundary.
Source retrieved 2026-07-14Official LEAVE and UNBOND procedure reference; a node must be Standby and outside vault migration before unbonding, and the original operator address controls the action.
Source retrieved 2026-07-05Official technology docs for Bifrost, TSS, Asgard vaults, vault migration, and churn-related mechanics; pair with dated security sources for the current signing scheme and incident posture.
Source retrieved 2026-07-14Pinned official THORNode source-tree snapshot for observer/signer roles, Active and Retiring vault observations, 67% consensus, finality, re-orgs, and outbound evidence.
Source retrieved 2026-07-14Pinned official THORNode source-tree snapshot for physical-vault lifecycle, inbound-vault selection, migration, and the distinction between slash points and bond-principal slashing.
Source retrieved 2026-07-04Official root-cause report for the May 2026 GG20/TSS vault exploit, patched v3.19.1 recovery, and still-planned migration away from GG20.
Source retrieved 2026-07-14Official high-level app-layer overview; economic examples are design framing, while current WASM, secured-asset, and trade-account availability still needs live controls.
Source retrieved 2026-07-14Official permissioned-mainnet and sandbox-boundary reference; current contract execution still depends on live scoped controls.
Source retrieved 2026-07-14Developer reference for secured-asset share mechanics, SECURE memo syntax, conversion exclusions, and a different "replace Trade Accounts" wording; syntax is not current action availability proof.
Source retrieved 2026-07-14Official historical Savers mechanics and explicit permanent-deprecation date of 2025-01-04; not current deposit, yield, synth, or redemption instructions.
Source retrieved 2026-07-14Official historical Lending mechanics and explicit permanent-deprecation date of 2025-01-04; not current borrow, repay, collateral, or TOR instructions.
Source retrieved 2026-07-05Dated THORFi unwind postmortem with January-February 2025 liability, pause, and Proposal 6 milestones; its implementation-status section is historical, not current TCY availability proof.
Source retrieved 2026-07-05Developer-facing TCY mechanics, claim, staking, and recovery caveats, including the explicit warning that full debt recovery is market dependent and not guaranteed.
Source retrieved 2026-07-05Official RUNE and TCY tokenomics overview, including TCY supply, revenue share, and no-governance-rights caveat; current amounts and distributions still require live evidence.
Source retrieved 2026-07-05Official initial May 2026 exploit timeline and then-pending ADR-028 recovery framing; use Report #2 and the accepted ADR for later root-cause and conciliation status.
Source retrieved 2026-07-04Official root-cause report for the May 2026 GG20/TSS vault exploit, patched v3.19.1 recovery, and still-planned migration away from GG20.
Source retrieved 2026-07-13Official 2026-06-25 post-restart update confirming trading resumed while DKLS/FROST migration and TSS-library publication remained future work.
Start with the TCY recovery timeline, then read historical Savers/Lending mechanics and the security mechanics that shaped later incident-recovery claims.
How to choose between Midgard dashboard data and THORNode raw protocol state without overclaiming live evidence, route availability, or recovery state.
Use For
A source-selection guide for deciding when to use THORNode operational evidence versus Midgard indexed dashboard metrics.
Verify First
Current provider, source freshness, block height, endpoint family, warning list, and whether the claim needs THORNode or Midgard evidence.
How THORChain's constant-function, slip-priced pools support native swaps, and where formula evidence stops before current route, refund, LP, or yield claims.
Use For
A mechanism and evidence-boundary guide for CLP pricing, slip/liquidity fees, route availability, and refund non-claims.
Verify First
Current quote, route availability, pool depth, LP action state, source quality, transaction evidence, and whether the claim belongs in the refund or liquidity-action evidence ladder.
Source retrieved 2026-07-05Official documentation root used for curated protocol background; it still describes GG20 at review time, but current safety and migration state require dated incident and release sources.
Source retrieved 2026-07-14Official user-facing explanation of native cross-chain swaps routing internally through RUNE-paired pools; current execution still needs quote and operational evidence.
Source retrieved 2026-07-14Official LP role, symmetric/asymmetric deposit framing, withdrawal model, fee income, and impermanent-loss risk; current LP controls and APY still need live evidence.
Source retrieved 2026-07-14Official FAQ for asymmetric deposit and withdrawal rules, fees, liquidity-unit ownership, and position caveats; live controls own current action availability.
Source retrieved 2026-07-14Official RUNEPool overview for aggregate POL participation, units, deposits, withdrawals, and PnL fields; its fixed pool-count prose is not current POL-scope proof.
Source retrieved 2026-07-14Current-only RUNEPool accounting endpoint; production evidence pins it to the same Liquify provider and THORChain height as Mimir before interpreting global, provider, reserve, value, PnL, or deposit fields.
Automatic reward balancing between node bond security and pooled liquidity, with current APY and health claims kept live-source dependent.
Use For
A mechanism guide for explaining THORChain incentive balancing without turning design incentives into live yield, APY, revenue, or price claims.
Verify First
Current Midgard health, visible metric source, earnings intervals, APY calculation, reward distribution, token value, and whether the claim is a design incentive or measured outcome.
Source retrieved 2026-07-14Official Incentive Pendulum, emission, and reserve-flow design; its original 500M maximum-supply framing must not be presented as the newer tokenomics page's current approximate supply.
Source retrieved 2026-07-14Official security/governance overview for the Incentive Pendulum and approximate 2:1 bonded-security-to-liquidity target; live ratios and reward splits need current evidence.
Source retrieved 2026-07-05Official documentation root used for curated protocol background; it still describes GG20 at review time, but current safety and migration state require dated incident and release sources.
How distributed signing protects cross-chain vault keys, what v3.19.x recovered, and why GG20, DKLS/FROST, Paillier, and vault-safety wording remain dated-source claims.
Use For
A security explainer for threshold signing, vault-key risk, GG20 incident language, and what current signing-health claims must verify separately.
Verify First
Current signing state, vault safety, validator upgrade coverage, active TSS implementation, or whether GG20, DKLS, or Schnorr wording applies to the running release.
Source retrieved 2026-07-05Official documentation root used for curated protocol background; it still describes GG20 at review time, but current safety and migration state require dated incident and release sources.
Source retrieved 2026-07-04Historical 2022 educational explainer for Asgard vault, TSS, and churn mechanics; fixed node-count and cadence examples are not current configuration proof.
Source retrieved 2026-07-04Official root-cause report for the May 2026 GG20/TSS vault exploit, patched v3.19.1 recovery, and still-planned migration away from GG20.
Source retrieved 2026-07-05Official initial May 2026 exploit timeline and then-pending ADR-028 recovery framing; use Report #2 and the accepted ADR for later root-cause and conciliation status.
Validator rotation, node lifecycle, vault migration, standby competition, and why current churn state must be checked live.
Use For
A validator-lifecycle guide for churn timing, vault rotation, membership changes, and why scheduled rotation is not the same as current signing health.
Verify First
Current churn schedule, active validator set, vault migration state, signing availability, node status, and whether a chain is paused during rotation.
Source retrieved 2026-07-14Official node lifecycle and churn reference for Whitelisted, Standby, Ready, Active, and Disabled status, churn-out criteria, and the Standby-only unbond boundary.
Source retrieved 2026-07-14Official LEAVE and UNBOND procedure reference; a node must be Standby and outside vault migration before unbonding, and the original operator address controls the action.
Source retrieved 2026-07-05Official technology docs for Bifrost, TSS, Asgard vaults, vault migration, and churn-related mechanics; pair with dated security sources for the current signing scheme and incident posture.
Source retrieved 2026-07-14Pinned official THORNode source-tree snapshot for physical-vault lifecycle, inbound-vault selection, migration, and the distinction between slash points and bond-principal slashing.
Bonded RUNE, slash exposure, and why current constants should be source checked.
Use For
An economic-security guide for bond risk, punishment mechanics, and the evidence needed before calling current validator behavior safe or unsafe.
Verify First
Current validator evidence, bond state, slash event records, protocol version, source freshness, and whether a safety claim is economic design or observed behavior.
Source retrieved 2026-07-14Pinned official THORNode source-tree snapshot for physical-vault lifecycle, inbound-vault selection, migration, and the distinction between slash points and bond-principal slashing.
How active nodes observe external chains, run chain clients, and why observation evidence is not the same thing as route execution.
Use For
A chain-client and observation guide for external-chain monitoring, finality, solvency proofs, and why observations are not complete swap-settlement proof by themselves.
Verify First
Current inbound-address state, observation lag, finality assumptions, chain halts, signing state, transaction evidence, and whether a chain-client claim is live or architectural.
Source retrieved 2026-07-05Official technology docs for Bifrost, TSS, Asgard vaults, vault migration, and churn-related mechanics; pair with dated security sources for the current signing scheme and incident posture.
Source retrieved 2026-07-14Pinned official THORNode source-tree snapshot for observer/signer roles, Active and Retiring vault observations, 67% consensus, finality, re-orgs, and outbound evidence.
Source retrieved 2026-07-14Pinned official THORNode source-tree snapshot for physical-vault lifecycle, inbound-vault selection, migration, and the distinction between slash points and bond-principal slashing.
How THORChain App Layer contracts, secured assets, trade-account boundaries, and WASM halt controls fit together without overclaiming current availability.
Use For
A source-boundary guide for app-layer contracts, secured assets, trade accounts, and live control checks.
Verify First
Current Mimir app-layer controls, contract/deployer/checksum state, secured/trade-asset enablement, source warnings, and dated product scope.
Source retrieved 2026-07-14Official high-level app-layer overview; economic examples are design framing, while current WASM, secured-asset, and trade-account availability still needs live controls.
Source retrieved 2026-07-14Official permissioned-mainnet and sandbox-boundary reference; current contract execution still depends on live scoped controls.
Source retrieved 2026-07-14Official high-level secured-asset overview, which says secured assets replace Trade Assets; compare the developer guide terminology and live controls before making module or availability claims.
Source retrieved 2026-07-14Developer reference for secured-asset share mechanics, SECURE memo syntax, conversion exclusions, and a different "replace Trade Accounts" wording; syntax is not current action availability proof.
Why RUNE-paired liquidity explains the base settlement model without proving current route health, value, or availability.
Use For
A settlement-role guide for RUNE as the pool-pairing and security asset without turning mechanism language into price, fair-value, or investment claims.
Verify First
Current RUNE price, supply framing, pooled RUNE, security constants, route liquidity, source freshness, and whether the claim belongs to live metrics or tokenomics records.
Source retrieved 2026-07-14Official RUNE settlement, liquidity, security, governance, and incentive framing; broad value/security statements remain design claims rather than current market or safety proof.
Source retrieved 2026-07-14Official user-facing explanation of native cross-chain swaps routing internally through RUNE-paired pools; current execution still needs quote and operational evidence.
Source retrieved 2026-07-05Official RUNE and TCY tokenomics overview, including TCY supply, revenue share, and no-governance-rights caveat; current amounts and distributions still require live evidence.
Source retrieved 2026-07-05Official documentation root used for curated protocol background; it still describes GG20 at review time, but current safety and migration state require dated incident and release sources.
Source retrieved 2026-07-05Dated THORFi unwind postmortem with January-February 2025 liability, pause, and Proposal 6 milestones; its implementation-status section is historical, not current TCY availability proof.
Source retrieved 2026-07-05Developer-facing TCY mechanics, claim, staking, and recovery caveats, including the explicit warning that full debt recovery is market dependent and not guaranteed.
Source retrieved 2026-07-05Official RUNE and TCY tokenomics overview, including TCY supply, revenue share, and no-governance-rights caveat; current amounts and distributions still require live evidence.
Source retrieved 2026-07-05Official archived feature index marking Savers and Lending as deprecated, no longer available, and preserved only for historical reference.
Source retrieved 2026-07-05Official initial May 2026 exploit timeline and then-pending ADR-028 recovery framing; use Report #2 and the accepted ADR for later root-cause and conciliation status.
Source retrieved 2026-07-04Official root-cause report for the May 2026 GG20/TSS vault exploit, patched v3.19.1 recovery, and still-planned migration away from GG20.
Source retrieved 2026-07-13Immutable v3.19.0 source marking ADR-028 Accepted and specifying the one-time Migrate15to16 conciliation waterfall; not proof that every affected user recovered every loss.
Historical overview of deprecated Savers/Lending mechanics, proof boundaries, evidence ladder, and TCY aftermath checks.
Use For
A historical-product guide for archived Savers/Lending context, THORFi unwind boundaries, and why old yield mechanics are not current user instructions.
Verify First
Current product availability, archived Savers/Lending status, TCY recovery context, THORFi unwind records, and whether old yield or lending behavior is being misread as live.
HistoricalChecked 2026-07-14·Review due 2026-08-14·
Source retrieved 2026-07-14Official historical Savers mechanics and explicit permanent-deprecation date of 2025-01-04; not current deposit, yield, synth, or redemption instructions.
Source retrieved 2026-07-14Official historical Lending mechanics and explicit permanent-deprecation date of 2025-01-04; not current borrow, repay, collateral, or TOR instructions.
Source retrieved 2026-07-05Dated THORFi unwind postmortem with January-February 2025 liability, pause, and Proposal 6 milestones; its implementation-status section is historical, not current TCY availability proof.
Source retrieved 2026-07-05Developer-facing TCY mechanics, claim, staking, and recovery caveats, including the explicit warning that full debt recovery is market dependent and not guaranteed.
Source retrieved 2026-07-05Official RUNE and TCY tokenomics overview, including TCY supply, revenue share, and no-governance-rights caveat; current amounts and distributions still require live evidence.
Source retrieved 2026-07-05Official documentation root used for curated protocol background; it still describes GG20 at review time, but current safety and migration state require dated incident and release sources.