Auto Finance

Identification (Ethereum scope)

• Name: Auto Finance (formerly Tokemak); official website: app.auto.finance; docs: docs.auto.finance. Category: automated DeFi liquidity/yield-management protocol using ERC-4626 Autopools that rebalance across DEXs, lending markets and other destinations.
• Launch dates: original Tokemak genesis/initial deployment dates to August 2021; Tokemak v2 was introduced May 18, 2023; Autopilot open launch was September 16, 2024; the Auto Finance rebrand was announced September 18, 2025.
• Chains: Ethereum, Base, Arbitrum, Plasma and Linea are listed by the protocol; this review is limited to Ethereum.
• Native token: AUTO, migrated 1:1 from TOKE beginning February 3, 2026. Ethereum AUTO: 0x1Ec8eaa3f68261e793C48486b12092336A03c479; TOKE legacy: 0x2e9d63788249371f1DFC918a52f8d799F4a38C94. Ethereum contract cross-check Dune MCP is unavailable in this run; therefore no address below satisfies the requested two-source cross-check including Dune. On the available sources, official docs and Etherscan agree on:
• System Registry: 0x2218F90A98b0C070676f249EF44834686dAa4285 — Etherscan source verified; constructor references TOKE and WETH.
• autoETH Autopool: 0x0A2b94F6871c1D7A32Fe58E1ab5e6deA2f114E56 — official address match; Etherscan exposes verified contract ABI/source.
• autoUSD Autopool: 0xa7569A44f348d3D70d8ad5889e50F78E33d80D35 — official address match; explorer identifies it as Tokemak autoUSD and shows proxy implementation data. Fork lineage Auto Finance is not an external fork; it is the same Tokemak project, rebranded and materially evolved from Tokemak v1 to v2. The principal change was from manually directed liquidity to LMPs/Autopools and automated rebalancing. Auditing exists: Hexens’ May 2024 review found seven high- and eight medium-severity issues; all were fixed or acknowledged and validated. Malicious-modification history in similar forks: Not verifiable as of October 10, 2026.

Auto Finance appears to have a real, functioning dApp rather than just a marketing landing page: the app domain exposes pool pages, token pages, chain pages, and a full app guide, and the docs site includes a dedicated developer/contracts section. The product also appears to support live deposits and withdrawals, with the app pages stating that users can connect a wallet, deposit into Autopools, and withdraw at any time subject to on-chain liquidity; the docs similarly describe how to use the app. The UX is reasonably mature on the surface because the site publishes product-specific pages for pools/tokens/chains, plus contract-address documentation and an app guide, which is consistent with an operational protocol rather than a static brochure site.

I did not find evidence in the retrieved material of broken links, fake metrics, or obvious template-only behavior, but that absence is not a verification of quality; those issues are Not verifiable as of 2026-10-10. On open API: there is no clearly documented public trading/deposit API in the retrieved sources. The only explicit API-related result was a third-party listing that says Auto Finance’s onchain surface is a public set of audited Solidity contracts rather than a REST API, while the docs expose contract information and an HTTP GET-style ask parameter for documentation pages, not a product API for deposits/withdrawals.

So an open protocol API for integration is Not verifiable as of 2026-10-10, and the safest statement is that users interact through the web app and smart contracts, not a clearly advertised public REST API.

Auto Finance appears to have an active bug bounty program hosted on Remedy, with public references on the protocol docs and third-party bounty listing pages. The docs state the current program is on Remedy and the bounty scope includes the protocol’s domain, smart contracts, Solidity, and source code. A third-party listing shows a reward range of $25,000-$125,000 and dates the listing to Sep 19, 2024.

The protocol site also says it has an active bug bounty on Immunefi, but that conflicts with the docs/third-party references pointing to Remedy, so the platform attribution is not fully consistent. I could not verify published payout results or disclosed bounties from the gathered sources, so those are Not verifiable as of 2026-10-10.

Assessment — Ethereum / Auto Finance (formerly Tokemak) Dependency stack. Auto Finance is an allocation layer, not a standalone yield source. Its Ethereum Autopools can route assets into Balancer, Curve, Aura, Convex, Maverick and Uniswap V3 liquidity venues; documented destinations also include LST/LRT assets such as wstETH, rETH, osETH, cbETH, frxETH, ETHx, ezETH, weETH, rsETH and rswETH. This creates correlated smart-contract, liquidity, validator/operator and depeg risk across the underlying venues and asset issuers. Oracles / manipulation. The system uses multiple oracle adapters, including Chainlink, RedStone, Curve, Balancer, custom-set and asset-specific LST/LRT oracles.

Rebalances depend on cached pricing and documented price-refresh controls. Main risks are stale prices, oracle-source failure, thin-pool manipulation, and incorrect valuation during rapid LST/LRT depegs; a bad price can trigger unfavorable rebalances or impair withdrawals. Counterparties and liquidity. Withdrawals may require liquidation through Balancer, Curve or Uniswap V3 routes, so a pool imbalance, exploit, pause, or severe slippage event can convert into loss or delayed redemption. Aura/Convex add additional staking-contract and reward-token dependencies.

No evidence was found of custodians, CEX market-makers, fiat banks, or RWA issuers/SPVs being required for the Ethereum Autopools reviewed. This does not exclude indirect exposure through third-party tokens. Bridges / cross-chain. The protocol has deployments on multiple chains and includes messaging infrastructure, but the requested Ethereum-only exposure to bridges could not be quantified from the available sources. Not verifiable as of October 10, 2026. Failure scenarios. Key scenarios are: (1) Balancer/Curve/Aura/Convex exploit; (2) oracle manipulation or stale cache; (3) LST/LRT or stablecoin depeg causing impermanent loss and impaired exits; (4) liquidity fragmentation causing withdrawal slippage; and (5) governance/strategy misconfiguration selecting a compromised destination. Audits and formal-verification reports exist, but they do not eliminate dependency or market risk.

Exact dependency weights, stablecoin/LST/restaking percentages, and maximum counterparty exposure require on-chain attribution. Not verifiable as of October 10, 2026.

Not verifiable as of 2026-10-10. I could not confirm, from the available web results, how Auto Finance specifically organizes custody for user crypto on Ethereum. The results only provide general custody-market information, not protocol-specific disclosures tied to Auto Finance’s contracts or documentation.

In the absence of protocol-specific evidence, I cannot verify whether custody is self-custodial, third-party custodial, pooled, or segregated. Structured fields:

• withdrawal_paused: null
• segregated_assets: null

## Key-management organization Auto Finance’s Ethereum contracts use a layered permission model, rather than one universal administrator:

• SystemRegistry: documented as the main privileged contract, using an onlyOwner model. Auto Finance’s documentation says ownership is intended to be held by a multisig, with eventual migration to a Governor contract. This creates a high-impact control point because the registry links core system components.
• Other core contracts: use a shared RBAC (role-based access control) design. Permissions are centralized through an AccessController, which contracts reference via SecurityBase, rather than each contract independently managing roles. The AccessController itself is described as non-upgradeable.
• Emergency controls: SystemSecurity coordinates system-wide actions including pausing, implying dedicated operational roles separate from ordinary configuration roles.
• Upgradeable components: some deployed vault/token contracts expose proxy-admin and upgrade functions at the proxy layer. Therefore, the security of the controlling admin address remains material even where user funds are held non-custodially. An independent Balancer governance record historically described Tokemak contract ownership as being held by a DAO multisig, with an additional multisig used for operations; this supports the existence of separated governance/operations custody, but does not establish the current setup. ### Verification gaps Not verifiable as of October 10, 2026:
• current multisig addresses;
• signer identities, signer count, and approval threshold;
• whether hardware wallets, MPC, HSMs, or key sharding are used;
• documented key-generation, rotation, backup, and compromise-recovery procedures;
• whether the stated transition from multisig ownership to Governor has occurred. Risk assessment: the architecture reduces single-key risk through multisig/RBAC separation, but the registry owner, AccessController roles, pause authority, and any proxy-admin keys remain material centralization and key-compromise risks. The protocol’s public documentation does not provide enough current evidence to quantify those risks.

Scope: Ethereum mainnet; reviewed 10 October 2026. Dune MCP was unavailable, so admin/event/timelock conclusions requiring decoded on-chain data are Not verifiable as of October 10, 2026. Identified addresses (protocol-published; not independently on-chain reconciled): System Registry 0x2218…4285; Access Controller 0x3776…2dF6; System Security 0x027a…8833; Autopool Registry 0x7E58…64E4; Destination Vault Registry 0x3AaC…52aE; Vault Factory 0x37De…f124; Swap Router 0x6201…A3f2; Root Price Oracle 0x61F8…2CaC; LiquidationRow 0xBf58…0ff5; Autopilot Router 0x37dD…aE21; autoETH 0x0A2b…4E56; autoLRT 0xE800…5AF3; balETH 0x6dC3…34c5; autoUSD 0xa756…0D35. Verification / architecture: autoETH’s explorer source is published and references OpenZeppelin Initializable, while deployed system components expose upgrade/pause-style interfaces; the exact proxy-admin chain and implementation slots were not independently verified. ``text AccessController ─┬─ SystemRegistry ─ Oracle / Registries / Router └─ SystemSecurity ─ Autopools Autopool ─ Strategy/Solver ─ DestinationVaults ─ Aave/Curve/Balancer/etc. └─ Rewarders → LiquidationRow `` Admin-risk findings:

• Pause, upgrade, registry, oracle, strategy, fee, emergency-exit and withdrawal-admin permissions: Not verifiable as of October 10, 2026.
• Proxy-admin type (EOA, Safe, timelock), role holders, renounced roles, and timelock delay: Not verifiable as of October 10, 2026.
• Therefore whether one key/multisig can drain user funds without governance is Not verifiable as of October 10, 2026. A compromised privileged role could plausibly upgrade logic, redirect registries/oracles, pause operations, or manipulate strategy execution; this is a threat scenario, not a confirmed capability.
• The protocol states withdrawals have no lockup/cooldown, but withdrawals depend on available idle liquidity; this is an unverified marketing claim, not an independently verified exit guarantee. Audits: Hexens reports a June 2026 ExitDestinations audit with findings marked fixed/acknowledged, but this does not establish that every Ethereum deployment and current implementation is audited. Risk conclusion: Medium–high unresolved administrative uncertainty; freeze and upgrade risk cannot be bounded without live role/proxy/timelock verification. Structured fields:
• admin_can_drain: null
• audited_deployment: null
• upgradeable: true
• unresolved_critical: null
• unresolved_high: null

Hats.Finance — Autopilot Crowd Competition — February–March 2024.

Hexens — Tokemak Autopilot Core Contracts Security Review — May 2024.

Hexens — autoUSD / Tokemak V2 Update Audit — March 2025.

Certora — LMPStrategy Security Assessment & Formal Verification — January/March 2024.

Hexens — Autopilot Follow-Up / Updates Audit — July 2024.

Halborn — Autopilot Pricing Contracts Formal Verification — September 2023.

Hexens — Tokemak V2 Autopilot & SwapRouter Update — December 2024.

## Founders, team, and operating reality Auto Finance is the rebranded continuation of Tokemak, reportedly rebranded in September 2025; available profiles describe the same team, contracts, documentation, and migrated TOKE-to-AUTO token. The project originated from Fractal, described as a digital-asset trading and market-making firm, and was founded by Carson Cook. Publicly associated personnel are limited.

Carson Cook is identified as founder, while Sterling Archer is listed as head of strategy. A separate institutional case study identifies Craig Braun as a co-founder. These records do not establish a complete, independently verified staff roster, biographies, or current control structure. Public team transparency: partial. ### Prior projects and outcomes The predecessor, Tokemak, launched as a decentralized liquidity-management protocol and raised approximately $4 million in April 2021 before its Ethereum mainnet launch.

The available evidence identifies Fractal as the originating trading firm but does not independently verify Fractal’s full corporate history, audited financial outcomes, or the founders’ complete prior-project record. Not verifiable as of October 10, 2026. ### Security and credibility Auto Finance’s own application claims professional audits, formal verification, bug bounties, and continuous monitoring; this is an unverified marketing claim because the retrieved evidence does not independently establish the auditor reports, scope, deployment coverage, or remediation history. No independently sourced, protocol-specific exploit or hack was identified in the retrieved results. Not verifiable as of October 10, 2026. The protocol’s continuity from Tokemak, open-source positioning, named senior personnel, institutional-facing custody integration, and operation of Ethereum Autopools are positive credibility indicators. They do not by themselves prove sound governance, solvency, or absence of undisclosed incidents. ### Office, jurisdiction, and business reality A real office, registered operating entity, headquarters, jurisdiction, and onshore/offshore status were not established by independent sources. Not verifiable as of October 10, 2026. The evidence supports a functioning on-chain product rather than merely a web front: Auto Finance describes Ethereum Autopools as smart-contract vaults, and the Ethereum-specific product page confirms deployment on Ethereum.

However, because on-chain verification was unavailable in this run, contract activity, asset balances, administrator permissions, and current business scale are Not verifiable as of October 10, 2026. > Reality-check finding: The brand’s continuity and product presence are documented, but claims about audits, team completeness, corporate domicile, office presence, and security history remain insufficiently independently verified.

Auto Finance is the current brand of Tokemak, an Ethereum-origin DeFi liquidity-management protocol founded by Carson Cook. Independent project databases report approximately $4 million raised in 2021 from Framework Ventures, Coinbase Ventures, Electric Capital, Delphi Digital, North Island Ventures, ConsenSys Mesh and others. These funding and founder records are corroborated by more than one independent database, but investor participation does not establish ongoing endorsement or protocol safety. Audits and security. Search results indicate multiple audit engagements, including Certora formal verification, and an active Remedy bug bounty; a third-party security summary also identifies important trust boundaries: pausable redemptions, upgradeable pool generation, oracle dependence and keeper dependence.

Auto Finance’s own pages claim audits and formal verification, but those claims are protocol-controlled and therefore remain an unverified marketing claim absent direct review of auditor reports. I could not independently verify the complete auditor list, report scope, remediation status, or current bounty terms. Reputation and sentiment. Available results are predominantly descriptive or promotional. One independent educational source explicitly emphasizes residual smart-contract, market and integration risk despite audits.

The protocol’s automated allocation across external venues creates dependency and composability risk, including losses or impaired withdrawals caused by an underlying venue, oracle, keeper, liquidity, or upgrade-control failure. Fraud, rug, insolvency and exploit allegations. I found no reliable independent evidence in the reviewed results of a rug pull, fraud finding, insolvency event, sanctions designation, or regulatory enforcement action specifically involving Auto Finance/Tokemak. A generic CoinPaprika page alleges a 2023 exploit, but it is not sufficiently specific or authoritative to establish that the incident involved this protocol; treat the allegation as unverified rather than as a confirmed event. Unresolved concerns. The protocol’s rebrand from Tokemak to Auto Finance may complicate historical due diligence and attribution. The most material unresolved issues are the exact scope and recency of audits, governance and upgrade-admin concentration, oracle/keeper controls, underlying-protocol exposure, and whether any historical incidents or liabilities carried over from Tokemak.

On-chain verification, including current Ethereum exposure and contract-admin analysis, was unavailable: Not verifiable as of October 10, 2026.

Scope / identity: Auto Finance is the rebrand of Tokemak; Ethereum contracts and product pages match the selected protocol. On-chain verification is unavailable in this run: Not verifiable as of October 10, 2026. Strategy and asset flows: ERC-4626 Autopools accept a base asset—Ethereum products currently list ETH, USDC and DOLA—and issue yield-bearing receipt tokens. Assets are autonomously rebalanced among approved DEX liquidity and lending destinations, including Curve, Balancer, Aave, Morpho, Fluid and, for some pools, Ethena.

Returns are auto-compounded into the pool’s base asset. This creates external-protocol, smart-contract, oracle, liquidity and—in Ethena-related strategies—basis/funding exposure. Risk profile: The strategy is primarily market-neutral or low-directional for stablecoin/correlated-pair pools, but not risk-free: ETH pools retain ETH price exposure, while LP positions can incur impermanent loss and destination-specific risks. No evidence was found that the Autopools themselves use native borrowing, leverage, looping or restaking.

Receipt tokens are composable and may be used as collateral or for external leverage; therefore system-level leverage cannot be excluded. leverage_ratio: null. Yield: Sources include DEX trading fees, lending interest and third-party incentives. The organic/subsidized split is not disclosed in a verifiable, pool-level time series. organic_yield_pct: null. Current protocol-reported Ethereum APYs were autoUSD 6.41%, autoDOLA 5.61% and autoETH 2.74%; these are marketing/interface figures, not independently verified. APY history, volatility and sustainability: Not verifiable as of October 10, 2026. Liquidity and fees: Docs state no lock-up or cooldown and withdrawals at any time, subject to on-chain liquidity.

The interface states zero management, performance, deposit and withdrawal fees; no minimum deposit is advertised. Gates, per-pool caps and stressed-withdrawal behavior were not independently verified. Revenue: DeFiLlama reports approximately $104,462 fees and $33.76 protocol revenue over 30 days, but this is aggregator data, not raw-chain verified. TVL contradiction: Auto Finance reports $72.73M total TVL; DeFiLlama reports $40.6M, with Ethereum at 88.4% (about $35.9M). Ethereum product figures on the interface total about $28.45M.

The discrepancy is unresolved; on-chain winner: Not verifiable as of October 10, 2026.

Scope / identity. Auto Finance is the current brand of Tokemak; the protocol’s app states that the Tokemak contracts and documentation continue under Auto Finance. Treasury address and custody. The public Tokemak contracts repository identifies Ethereum treasury multisig 0x8b4334d4812C530574Bd4F2763FcD22dE94A969B; Etherscan identifies it as a Safe/proxy multisig. The repository also lists coordinator multisig 0x90b6C61B102eA260131aB48377E143D6EB3A9d4B. The signing threshold, signer identities, and whether this treasury remains the sole current Auto Finance reserve wallet are Not verifiable as of October 10, 2026. Size and composition. DeFiLlama’s analytics treasury page reports approximately $10.47 million for AUTOfinance, comprising about $3.71m stablecoins, $6.30m majors, $451k own-token exposure, and $1.5k other assets; this is an analytics-platform estimate, not raw on-chain verification.

Etherscan’s address widget separately showed approximately $5.11m, with 83.17% stETH, 7.84% sUSDS, and 6.84% TOKE, creating an unresolved data contradiction. > Contradiction: reported treasury values differ materially ($10.47m vs. $5.11m). Because Dune was unavailable in this run and explorer dashboard values are not equivalent to a reproducible balance query, the true reserve size and composition are Not verifiable as of October 10, 2026. On-chain balances / reserve policy / attestations. Dune verification, latest block height, token-by-token balances, liabilities, formal reserve policy, proof-of-reserves, and independent attestations are Not verifiable as of October 10, 2026. Protocol documentation describes operational multisig/governance controls for system contracts, but does not establish a reserve policy or solvency attestation. Risk conclusion: custody appears multisig-based, but reserve transparency is insufficient for a verified liquidity-reserve conclusion; treasury estimates should be treated as analytics-only and potentially stale.

AUTO tokenomics — Ethereum (as of October 10, 2026)

• Native token: Auto Finance AUTO. Contract: 0x1Ec8eaa3f68261e793C48486b12092336A03c479. AUTO replaced/migrates from TOKE at 1:1 beginning February 3, 2026.
• Supply / valuation: DeFiLlama reports 100M circulating, 100M maximum/total supply, approximately $5.14M market cap and $5.14M FDV; price was about $0.051. These are analytics-platform figures, not Dune-verified on-chain values.
• Utility and governance: AUTO is used for staking in sAUTO and historically for directing liquidity/rewards across Autopools. The protocol states that AUTO holders receive governance rights and protocol-revenue exposure; current sAUTO reportedly no longer votes on individual Autopools. These are unverified marketing/governance claims without an accessible governance-state audit.
• Revenue share / buybacks / staking: The protocol states that treasury/Protocol-Owned Assets and future TVL fees fund market buybacks, with purchased AUTO distributed to sAUTO stakers. sAUTO has a single 16-week lock, with withdrawal requested during the final week; the protocol advertised historical staking returns of approximately 40% APR, recently 58%. These figures are protocol claims and not independently verified.
• Emissions: Legacy TOKE tokenomics allocated 30M TOKE (30%) to rewards over 104 weekly cycles/approximately 24 months. Current AUTO emissions after migration are Not verifiable as of October 10, 2026.
• Allocations: Historical allocation: rewards 30%, Cycle Zero 5%, DAO reserve 9%, contributors 16.5%, team 14%, investors 17%, DAOs/market makers 8.5%. Whether these allocations remain economically applicable after migration is Not verifiable as of October 10, 2026.
• Unlocks / insider concentration: Whether announced vesting unlocks occurred on-chain, current top-holder concentration, and insider-wallet attribution are Not verifiable as of October 10, 2026.
• Admin controls: Mint, blacklist, transfer-fee, fee-switch, proxy-admin, and pause-control authority are Not verifiable as of October 10, 2026.
• Liquidity/listings: Main Ethereum venues identified are Uniswap V4 AUTO/ETH, Curve AUTO/TOKE, and Sushi migration liquidity. DeFiLlama showed roughly $134K Uniswap V4 TVL and $51K Curve TVL; CoinGecko reported only about $2.8K ±2% depth for Uniswap V4, indicating thin liquidity.

Auto Finance (TOKE) could face no direct protocol-specific impact that is verifiable from the available sources. The web results do not confirm this protocol’s Ethereum contracts, TVL composition, collateral model, or liquidation rules, so the effect of Bitcoin falling below $10,000 is Not verifiable as of 2026-10-10. What can be said at a high level is that a BTC crash to that magnitude would likely intensify *broad crypto deleveraging*, weaken risk appetite, and increase stress on DeFi credit markets generally.

Recent market commentary says large liquidation cascades can force collateral sales, tighten liquidity, and depress yield-bearing assets across DeFi venues. For Auto Finance specifically, the key stress questions would be:

• Whether the protocol has BTC-linked collateral or exposure to BTC-denominated assets.
• Whether it relies on short-term liquidity that could be withdrawn in a market shock.
• Whether its positions are subject to margin calls, liquidation thresholds, or depegging risk in correlated assets. None of those protocol-specific points are confirmed by the provided sources, and the protocol website is not available here as a primary verification source. Therefore, the only defensible answer is that the BTC<$10k scenario represents a severe market-wide stress event, but Auto Finance’s actual loss path, solvency risk, or user impact are Not verifiable as of 2026-10-10.

For Auto Finance on Ethereum, a 20% depeg in the largest collateral asset would be a material but protocol-specific stress test, and the loss cannot be quantified from the provided results because the collateral composition, debt structure, and liquidation parameters are not verifiable as of 2026-10-10. What can be stated from the results is that Auto Finance’s Ethereum deployment includes autoETH and autoUSD autovaults, with Ethereum being the flagship chain for the protocol. The public materials also indicate that autoETH’s current Ethereum allocation is split between Instadapp ETH v2 on Fluid and weETH/WETH-ng on Curve, which implies collateral exposure is concentrated in ETH-adjacent liquid restaking and LP venues rather than a single simple spot asset.

However, the results do not provide a verifiable Ethereum-only collateral table, so the identity and size of the “largest collateral” remains Not verifiable as of 2026-10-10. Under a 20% depeg, the direct economic effect would be approximately a 20% mark-to-market hit on that collateral sleeve, with second-order risk depending on whether the depegged asset is used in leveraged or borrow-backed positions. If the asset is also a source of borrowed yield or liquidation-triggered unwind, losses could exceed the simple 20% price move due to forced rebalancing and slippage, but that is an inference rather than a verified protocol fact.

Because Dune/on-chain verification is unavailable in this run, the exact downside to TVL, user equity, and liquidation count is Not verifiable as of 2026-10-10.

Stress scenario — top counterparty becomes insolvent (Ethereum) Identification. The exact largest Ethereum counterparty and its exposure share are Not verifiable as of October 10, 2026 because Dune/on-chain verification is unavailable in this run. Auto Finance routes capital through external “Destinations,” including DEX pools and staked LP venues such as Balancer/Aura and Curve/Convex. Expected loss path 1. The counterparty fails, freezes withdrawals, or its LP/staked position becomes unrecoverable.

The affected DestinationVault’s claim is worth less or cannot be redeemed. 2. During debt reporting—normally at least every 24 hours—or when valuation thresholds are breached, the Autopool revalues DestinationVault shares.

The loss reduces cached NAV and therefore the exchange value of the ERC-4626 receipt token (e.g., autoETH). 3. Withdrawals draw first on idle assets, then unwind positions in the withdrawal queue.

If the failed venue cannot return assets, the withdrawal may be delayed/revert for that portion, or execute only against recoverable assets. This is an inference from the documented withdrawal architecture, not an observed incident. 4.

Any recovered assets, liquidation proceeds, or rewards are returned to the relevant DestinationVault/Rewarder; they do not restore the original NAV unless sufficient value is recovered. Who absorbs it

• Primary absorber: Autopool depositors, pro rata through a lower NAV/share.
• Secondary impact: holders using autoETH or another receipt token as collateral may face liquidation or loss of collateral value.
• The protocol’s Strategy can stop or restrict unfavorable rebalances, but this is loss prevention, not credit protection. Compensation A protocol-level insurance fund, senior-loss tranche, guaranteed repayment, or AUTO-token compensation is Not verifiable as of October 10, 2026. Expected compensation is therefore limited to recoveries from the failed counterparty and any residual LP/reward value; no guaranteed shortfall coverage is evidenced. Contract impact chain external venue → DestinationVault → Autopool debt reporting/oracle valuation → ERC-4626 NAV/share → withdrawal queue + swapper → user redemption. The key control point is valuation: lower safe/spot pricing is used for withdrawals, transferring realized loss to remaining and exiting depositors.

For Auto Finance (auto-finance) on Ethereum, a stress scenario of *committed fraud by the DAO or owners* is not verifiable as of 2026-10-10 from the available web results. The search results do not provide chain-specific evidence of DAO/owner fraud, treasury diversion, insider theft, or governance abuse for this protocol. What can be stated is only a general risk framing: DAO fraud and governance abuse can involve vote manipulation, treasury draining, phishing, or insider control of proposals, and these patterns are documented in broader DAO literature and case studies such as The DAO and other governance attacks.

However, those sources are *generic to DAOs* and do not establish that Auto Finance has committed such conduct. The only Auto Finance-specific result is a market listing that describes the protocol’s Autopools product, which is insufficient to verify governance, treasury, or owner behavior and should be treated as *unverified marketing claim* rather than evidence of fraud or integrity. So the appropriate stress-case assessment is: fraud risk exists in principle, but actual committed fraud by the DAO/owners is not verifiable from the provided sources.

For Auto Finance on Ethereum, the primary yield source is the protocol’s Autopools deploying assets into external DeFi positions on Aave, Morpho, Curve, and Balancer v3, with yield coming from trading fees, lending interest, and protocol incentives. Because this is not a single endogenous cashflow, a negative 30d stress case means one or more of those underlying sources have turned net negative after fees, slippage, and any incentive decay; in that scenario, the protocol’s reported APY would compress sharply and could become negative in net terms if losses from positioning and rebalancing exceed earned fees and interest. The key stress implication is that Auto Finance’s yield is not guaranteed by the protocol itself; it depends on the health of third-party markets and rebalancing effectiveness.

If the 30-day window is negative, the most likely drivers are lower utilization/borrowing demand on lending venues, weaker AMM fee generation, and/or adverse pool composition changes during rebalances. Because Dune/on-chain verification is unavailable in this run, the exact 30d negative contribution, pool-level split, and Ethereum-only exposure are Not verifiable as of 2026-10-10. The protocol site does state that Autopools are deployed on Ethereum and other chains, but that claim remains an unverified marketing claim here without on-chain confirmation.

As of October 10, 2026, Auto Finance is the rebranded Tokemak protocol. Governance appears company/foundation-led rather than DAO-controlled. The frontend is operated by Tokemak Foundation under the Terms of Use; the site footer also identifies Tokemak Foundation.

The Foundation’s jurisdiction, registration number, and directors are: Not verifiable as of October 10, 2026. Control surface: The Ethereum deployment uses a System Registry with onlyOwner; documentation says ownership is to be held by a multisig and “eventually” a Governor. Other contracts use a centralized RBAC AccessController. System Security can globally pause Autopools, while authorized roles coordinate rebalances and NAV-affecting operations.

This indicates meaningful operational control by designated administrators, not autonomous token-holder control. Funds: The published deployment registry identifies a Treasury multisig (0x8b4334d4812C530574Bd4F2763FcD22dE94A969B) and Coordinator multisig (0x90b6C61B102eA260131aB48377E143D6EB3A9d4B). A historical governance record described the Treasury Safe as 5-of-9 and holding the Manager Admin role, but the current threshold, signer list, signer independence, and whether this remains unchanged are: Not verifiable as of October 10, 2026. Proposal process / DAO reality: Historical Tokemak governance used C.o.R.E. community voting for liquidity/reactor decisions, with governance linked through Snapshot. Current AUTO-holder proposal mechanics and whether votes execute upgrades, parameters, or treasury actions are: Not verifiable as of October 10, 2026.

The available evidence supports limited or symbolic governance, not a DAO that demonstrably controls upgrades and contracts. Concentration: Top AUTO holders, voting concentration, and holder-adjusted governance power via Dune: Not verifiable as of October 10, 2026. On-chain verification was unavailable in this run. Contradiction: Marketing describes governance as token-based, while contract documentation still describes multisig/RBAC administration and a Governor only as a future state. The governance claim therefore does not establish effective DAO control.

Legal & regulatory assessment — Auto Finance (Ethereum)

• Entity / structure: The front end identifies its provider as Tokemak Foundation. The protocol is described as open-source software operating on Ethereum, while the Foundation controls the branded interface. Terms use Delaware law, Delaware arbitration, class-action waiver, liability caps, and a one-year claims limitation.
• Jurisdiction: Delaware is the contractual governing-law/forum choice, not verified evidence that the Foundation is incorporated, domiciled, or regulated there. Legal entity registration and beneficial ownership were not located.
• Access restrictions / sanctions: Users must be at least 18, comply with applicable law, and represent that they are not in U.S.-sanctioned jurisdictions or otherwise prohibited jurisdictions. The interface may geoblock or terminate access.
• KYC/AML: The interface states that it has no user accounts and does not request or store names or emails; the pool page states “no KYC required.” These are protocol/operator disclosures, not evidence of a regulator-approved AML program. No publicly identified KYC/AML policy or licensing record was verified.
• Classification: No formal regulatory classification was verified. Functionally, Auto Finance provides automated yield/liquidity-management vaults investing across DeFi protocols. Depending on facts and jurisdiction, activities could raise securities, collective-investment, investment-company, money-transmission, financial-promotion, or AML questions; the decentralized/open-source description does not eliminate interface/operator exposure.
• Warnings / enforcement / litigation / sanctions: Not verifiable as of October 10, 2026 regarding regulator enforcement, court cases, or sanctions specifically against Auto Finance or Tokemak Foundation. No conclusion should be drawn that none exist.
• Data protection: The privacy policy describes collection of public wallet data, approximate IP-derived location, analytics and session replay through PostHog, and third-party processing that may occur abroad; an analytics opt-out is offered. It does not identify a corporate legal address, DPO, governing privacy law, retention schedule, or formal GDPR/CCPA rights process. Actual risk: The Foundation’s contractual presence and interface create a plausible legal contact point, while the smart-contract layer may be permissionless and non-custodial. The legal structure therefore reduces neither regulatory classification risk nor user recourse risk; the Terms heavily allocate smart-contract, loss, compliance, and jurisdictional risk to users.

Legal entity per GLEIF: AUTO-FINANCE (LEI 9695000DW1YK0M0IOP79; jurisdiction FR; registration ACTIVE). OFAC SDN screening of 'Tokemak Foundation', 'Auto Finance': no match. SEC litigation and administrative release feeds: no mention.

Auto Finance on Ethereum does not appear to issue its own protocol stablecoin; the stablecoin pools shown are based on external assets such as USDC, crvUSD, frxUSD, USDT, and USDS, while Auto Finance’s own receipt tokens are pool share tokens, not stablecoins. The queried stablecoin used by the protocol was therefore not verifiably identifiable as a protocol-issued asset, so depeg history cannot be established from the available evidence. Not verifiable as of 2026-10-10.

Auto Finance’s principal risks arise from complex, composable vault logic, dependence on external DeFi destinations, oracle/NAV synchronization, privileged administration, and exit liquidity. External audits identified serious historical vulnerabilities, including seven high-severity findings in 2024 and one critical swap-router issue in December 2024; these were reported fixed and validated, but residual smart-contract and integration risk remains. On-chain exposure, current TVL, and concentration are Not verifiable as of October 10, 2026 because Dune MCP is unavailable.

Auto Finance’s top strengths are: 1) automated yield optimization through Autopools that rebalance capital across DeFi venues to improve returns; 2) reduced manual management and gas burden, because rebalancing is handled by the protocol rather than the user; 3) broad composability, with receipt tokens like autoETH designed to be usable across DeFi; 4) diversified deployment across multiple blue-chip protocols and chains, which can improve access to varied yield sources; and 5) transparent, smart-contract-based vault design, which is presented as an ERC-4626 Autopool system with onchain rebalancing logic.