Auto Finance Onchain

Identification — Auto Finance Onchain (auto-oc)

• Canonical identity: Auto Finance, formerly Tokemak; website: auto.finance; documentation: docs.auto.finance. Category: DeFi automated-liquidity manager/yield vaults (“Autopools”), using ERC-4626 vaults to route deposits across configured DeFi destinations.
• Launch chronology: Tokemak’s original token/protocol launch was August 2021; the Autopilot v2 product opened for external LPs on September 16, 2024; the Auto Finance rebrand was announced September 18, 2025.
• Chains: The user-selected scope is Ethereum. Public product material also lists Arbitrum, Base, Plasma and Linea, but those are outside this review scope.
• Native token: AUTO is now the protocol token following the 1:1 TOKE migration launched February 3, 2026. Legacy TOKE remains relevant for migration/legacy positions. Ethereum addresses / cross-check status Official migration notice lists: AUTO 0x1Ec8eaa3f68261e793C48486b12092336A03c479; sAUTO 0x13ff49c4bf8dbBb6Fa8B2DEC9911438E6e588213; TOKE 0x2e9d63788249371f1DFC918a52f8d799F4a38C94; wallet migration 0xFc9e2a42A8fcB01c9A6fd62133c71da80fa78057; sTOKE migration 0xA374A62DdBd21e3d5716cB04821CB710897c0972. TOKE is independently cross-referenced by the project’s public GitHub repository. Verification limitation: Dune MCP is unavailable in this run, so no on-chain/Dune cross-check or query/ execution ID exists. Etherscan pages were inaccessible to the web tool; therefore explorer source-verification status is Not verifiable as of October 10, 2026. Autopool implementation addresses are likewise Not verifiable as of October 10, 2026. Fork lineage No evidence indicates Auto Finance is a code fork of an unrelated upstream protocol; it is the rebrand and v2 evolution of Tokemak. Changes include Autopools/ERC-4626 vaults, automated rebalancing, new staking/migration contracts, and the TOKE→AUTO token transition. The v2 code was audited by Hexens, with reported high/medium findings fixed or acknowledged and validated; Certora formal verification and Sherlock/Hats/bug-bounty processes were also cited. Malicious modifications in similar Tokemak forks: Not verifiable as of October 10, 2026.

Auto Finance’s web presence looks like a real, live product portal rather than a pure landing page: the app domain exposes user-facing pages for app guide, chains, tokens, and deposit/withdraw flow language, and the documentation site includes an app guide plus developer docs for integrating and contracts overview. The available public pages describe active vault actions such as connecting a wallet, approving tokens, depositing, and burning vault shares to withdraw, which indicates intended live app functionality rather than a static brochure. That said, a few maturity signals are still only partially verifiable from the web snapshot here: live deposit/withdraw success rates, broken-link prevalence, and whether every UI flow works end-to-end cannot be confirmed without hands-on testing, so those remain Not verifiable as of 2026-10-10.

The external pages also contain some templated or possibly syndicated wording, and one third-party page mislabels the product as a lending app, so any such claims should be treated cautiously. On API status, the evidence points to an open developer surface but not a traditional public REST API: the docs expose machine-readable pages and the APIs.io listing says the onchain surface is a public set of audited Solidity smart contracts rather than a REST API. In practice, that means the protocol appears to have open contract interfaces and documentation for integration, but not a clearly advertised public off-chain API endpoint.

Auto Finance states it has an active bug bounty program on Immunefi, but the available source does not expose the bounty parameters, payout tiers, or published results in a verifiable way. The protocol’s security page points to a Remedy bug bounty entry for its current program, while a third-party security summary also describes an active bounty, but neither source provides complete, independently verifiable program terms here.

Scope: Ethereum mainnet; Dune/on-chain verification was unavailable, so exact current allocation weights and live dependency status are not verifiable. Dependency map and failure modes

• External DeFi: Autopools can allocate to Aave, Fluid, Morpho, Curve, Balancer and Convex-linked destinations. A failure, insolvency, oracle error, liquidity shock, LP imbalance or exploit in any selected venue can impair withdrawals/NAV.
• Oracle/manipulation: Auto Finance uses a RootPriceOracle combining Chainlink, RedStone, Tellor and AMM-derived spot prices. Rebalances compare spot prices against “safe” prices, but stale, unavailable, manipulated or incorrect feeds remain a material dependency. Stale debt reporting triggers floor/ceiling pricing, which limits—but does not eliminate—losses.
• Solver/keeper/administrative risk: Rebalancing depends on a solver and permissioned keeper processes; failed execution, malicious proposals, delayed debt reporting or compromised privileged roles could impair liquidity or accounting. The system supports flash-loan-based rebalancing.
• Stablecoin/LST/restaking: autoUSD’s documented destinations included USDC/USDT-oriented lending and LP venues plus sUSDe, sUSDS, sFRAX and scrvUSD. This creates nested stablecoin, issuer, yield-bearing-token and depeg risk. autoETH and related pools may carry LST/LRT depeg, slashing and liquidity risk.
• Bridges/custody/CEX/MM/RWA: No Ethereum bridge, custodian, CEX/MM, RWA issuer or SPV dependency was verified from the available evidence. Not verifiable as of October 10, 2026.
• Security evidence: Audits exist, but recent reviews still identified medium/low issues; a June 2026 review reported six findings, all fixed or acknowledged. This is not evidence that all live deployments are risk-free. Contradiction / data-quality callout: Protocol pages show aggregate TVL and historical AUM claims, but current Ethereum-only exposure by destination could not be independently verified. Treat headline figures as unverified marketing claims. Scenarios: venue exploit or oracle failure → NAV impairment; stablecoin/LST depeg → withdrawal loss and cascading LP losses; solver/keeper failure → stale pricing or delayed exits; external lending insolvency → principal loss. Structured fields: dependency_failure_active = null; max_exposure_pct = null.

Auto Finance is organized as a non-custodial DeFi protocol: user deposits are held in open-source smart contracts rather than by the Auto Finance team, and users can withdraw subject to on-chain liquidity. The protocol also describes its products as self-custodial and built on audited smart contracts, with institutional access provided through self-custody infrastructure rather than an intermediary custodian. Based on the available sources, custody is therefore organized as smart-contract custody with user-controlled redemption, not as a centralized custodial wallet model.

Withdrawal pauses are not evidenced in the available sources, so they are Not verifiable as of 2026-10-10.

Key-management organization — Ethereum Auto Finance uses a layered, contract-level authorization model:

• SystemRegistry: Uses an onlyOwner authority. The documentation states that ownership is intended to be assigned to a multisig, and eventually to a Governor contract. This is the highest-level control plane because the registry links the system’s core components.
• RBAC for other contracts: Other system contracts do not each maintain independent owners. They reference a shared, centralized AccessController, based largely on OpenZeppelin AccessControlEnumerable, which assigns operational roles to authorized addresses. The AccessController itself is described as non-upgradeable.
• Emergency controls: SystemSecurity coordinates system-wide security operations, including pausing across Autopools. This implies a separate privileged operational role rather than unrestricted control by every keeper or solver.
• Operational keys: Rebalancing is proposed by a permissioned Solver, while reward collection and related maintenance use a permissioned keeper process. These roles are constrained by on-chain strategy checks and immutable safety parameters, rather than being equivalent to unrestricted admin keys. Risk assessment: The design reduces single-key exposure through multisig-intended ownership and role separation. However, public documentation does not establish the currently active multisig address, signer count, signing threshold, geographic/key-storage controls, recovery process, rotation policy, timelock configuration, or whether governance has replaced the multisig. Not verifiable as of October 10, 2026. On-chain verification of the live Ethereum owner, role holders, and multisig configuration was unavailable in this run. The multisig/governor statements above therefore describe the documented architecture and intended setup, not independently verified current key custody.

Scope/name match: “Auto Finance Onchain” matches Auto Finance, formerly Tokemak, and its Ethereum Mainnet Autopools. Known Ethereum addresses: System Registry 0x2218F90A98b0C070676f249EF44834686dAa4285; Access Controller 0x37767cBfF88Cb623E9404e959560984F7D742dF6; System Security 0x027a3359b803885261B140415873845f72238833; Autopool Registry 0x7E5828a3A6Ae75426d739E798140513A2E2964E4; autoETH 0x0A2b94F6871c1D7A32Fe58E1ab5e6deA2f114E56; autoUSD 0xa7569A44f348d3D70d8ad5889e50F78E33d80D35; Autopool Factory 0x7fEd74094B7010c6FB3010ed5EfC00772fD2ED1f. Architecture: ``text Users -> Autopool/ERC-4626 -> idle assets + Destination Vaults |-> Strategy/hooks -> swaps/oracles -> external DeFi System Registry -> Access Controller / System Security Autopool Registry -> Factory -> Autopool instances ` Verification/admin: Contract addresses and source repository are public, but proxy slots, implementation addresses, proxy-admin type, current owners/roles, role renunciations, and timelock delay were not independently verified from Ethereum state. Not verifiable as of October 10, 2026. Dune decoded-event checks were unavailable. Control surface: Public code includes deposit/withdraw/redeem, rebalancing, strategy/destination management, fee/pricing/oracle components, and a recover()` transfer routine. The displayed library code has important asset-exclusion checks commented out; authorization and whether this path can reach tracked user assets require deployment-level verification. Pause, emergency withdrawal, upgrade, fee, oracle, and strategy permissions are therefore Not verifiable as of October 10, 2026. Exit/risk: Documentation claims withdrawals are instant only when idle liquidity is available; otherwise strategy liquidity and external-protocol conditions matter.

A compromised privileged key could plausibly upgrade/configure components, redirect fees, manipulate supported destinations/oracles, pause operations, or potentially extract assets if recovery controls are reachable—but exact worst-case authority is Not verifiable as of October 10, 2026. Users may face freeze, valuation, integration, or liquidity risk. Audit evidence: Auto Finance lists multiple audits; Hexens reports reviewed core Autopilot code and states findings were fixed or acknowledged. Exact deployed-bytecode coverage and any unresolved findings remain Not verifiable as of October 10, 2026. Contradiction callout: “Audited,” “full liquidity,” and “withdraw anytime” are protocol claims; they are not equivalent to verified current deployment permissions or guaranteed immediate liquidity.

Hats.Finance — Autopilot Crowd Competition Smart Contract Audit

Hexens — Tokemak Autopilot Core Contracts Security Review

Hexens — Autopilot Full System Follow-Up / Updates Audit

Halborn — Autopilot Pricing Contracts Formal Verification Report

Hexens — autoUSD Audit

Certora — Tokemak V2 LMPStrategy Security Assessment & Formal Verification

Sherlock — Autopilot Contracts Crowd Competition

Identification. The available results identify the target as Auto Finance (formerly Tokemak), an Ethereum-originated DeFi liquidity and yield-management protocol—not the unrelated automotive-finance project “Automatic USA.” The match is supported by the Tokemak-to-Auto Finance continuity and the reported 2020 founding date. Founders and team. The only specifically identified founder is Carson Cook. RootData attributes to him prior founding roles at Membrane and Fractal Wealth, digital-asset trading/market-making experience, and prior work at McKinsey; it also lists Sterling Archer as head of strategy. These identities are public-facing, but the available evidence does not establish the full current team, employment verification, or beneficial ownership. Not verifiable as of October 10, 2026. Prior outcomes and hacks. The sources reviewed do not provide an independently verified record of the founders’ prior project outcomes, exits, insolvencies, or security incidents. Not verifiable as of October 10, 2026. No conclusion that the protocol has never been hacked should be drawn. Credibility and operating reality. The project has indicators of a real operating protocol: a stated multi-year history, continuing product and brand evolution from Tokemak, identified leadership, and described smart-contract-based Autopools.

However, much of the available material is profile, partner, or protocol-originated content rather than independent corporate evidence. The available results do not verify a staffed physical office, legal entity, domicile, onshore/offshore status, audited financials, or operating revenue. Not verifiable as of October 10, 2026. > Reality-check finding: The evidence supports “an identifiable DeFi protocol with a public founder and product continuity,” but does not establish a transparent, conventionally incorporated operating company. Claims about office location, jurisdiction, or business substance remain unverified marketing or profile claims unless corroborated by corporate-registry, regulator, audit, or independent reporting evidence.

## Reputation assessment Auto Finance Onchain appears to refer to AUTO Finance, formerly Tokemak, an Ethereum-based automated liquidity-management protocol—not the unrelated “onchain.org” investment platform. The search record identifies Carson Cook as founder and reports a 2021 $4 million financing round involving Framework Ventures, Coinbase Ventures, Electric Capital, Delphi Digital, North Island Ventures, and ConsenSys Mesh. These identity and financing details are sourced from third-party aggregators and were not independently verified against Ethereum contracts.

The protocol claims audited, non-custodial ERC-4626 vaults and automated allocation across lending and liquidity venues. A third-party risk review reports eight audits and an AA / 84-of-100 rating, but also flags five medium- and five low-risk issues spanning smart-contract, economic, governance, and sustainability risks. The audit list and whether all findings were remediated were not independently confirmed. ### Findings and unresolved concerns

• Fraud, rug, insolvency: No credible search result established a fraud, rug-pull, or insolvency allegation against AUTO Finance itself. A Trustpilot result alleging a fake investment dApp concerns “onchain.org,” not this protocol, and is excluded by the name-collision check.
• Legal, regulatory, sanctions: Not verifiable as of October 10, 2026.
• Founders and investors: The reported founder and investor information is aggregator-sourced; corporate entities, beneficial ownership, and continuing investor involvement were not independently verified.
• Auditors: The existence of audits is supported by protocol claims and a third-party review, but auditor reports, scope, deployment correspondence, and unresolved findings were not independently established from the available results.
• Sentiment: Available coverage is predominantly descriptive or promotional. Independent, sufficiently broad user sentiment was not verifiable as of October 10, 2026.
• Core risk: Even if audited, automated vaults retain smart-contract, oracle, integration, liquidity, strategy, governance, and counterparty risks; the protocol’s own description confirms allocation across external DeFi venues. Because on-chain verification was unavailable in this run, TVL, exposure by Ethereum contract, holder concentration, treasury control, and current solvency/liquidity are not verifiable as of October 10, 2026.

Scope/verification. Dune MCP was unavailable; therefore all on-chain metrics, contract-level balances, product TVL, APY history, and leverage are Not verifiable as of October 10, 2026. DeFiLlama data below is an analytics snapshot and is stale (>7 days). Economic model. Auto Finance uses ERC-4626-style Autopools. Users deposit a base asset (e.g., ETH or stablecoins) and receive a yield-bearing receipt token.

Assets are routed among configured DEX LPs and, for some pools, lending markets. Rebalancing considers base yield, swap fees, incentive APR, price return, slippage, gas, and trading costs. Yield source / risk profile. Yield is a mixture of organic sources—ETH/LST staking yield, DEX trading fees, and lending yield—and potentially subsidized token incentives. The organic portion cannot be isolated from available public data: organic_yield_pct = null.

The strategy is not market-neutral: correlated ETH/LST/LRT pools reduce, but do not eliminate, directional ETH, depeg, liquidity, impermanent-loss, and smart-contract exposure. External exposure includes configured DEXs, lending markets, and reward systems such as Curve/Convex, Balancer/Aura, and Maverick. Leverage / looping / restaking. No protocol-level leverage or looping was verified. Receipt tokens are composable and may be used elsewhere as collateral, creating potential user/integration leverage, but the protocol leverage ratio is Not verifiable as of October 10, 2026; leverage_ratio = null.

Restaking was not verified. Liquidity mechanics. No deposit lock-up or cooldown is documented. Users may withdraw on demand; staked receipt tokens must first be unstaked. Large withdrawals can require unwinding underlying LP positions and may incur slippage; withdrawal pricing uses conservative valuation. Fees/revenue. Autopools support periodic and performance/streaming fees; exact live rates were not verified.

DeFiLlama’s stale snapshot showed approximately $40.1m total TVL, $35.4m on Ethereum (~88%), average APY ~5.4%, and 30-day fees about $104k, but product-level TVL, historical APY volatility, and sustainability are Not verifiable as of October 10, 2026. Contradiction callout: DeFiLlama snapshots vary materially (~$40m–$43m TVL); without Dune, the discrepancy cannot be resolved. On-chain TVL trend and Dune-vs-DeFiLlama reconciliation are Not verifiable as of October 10, 2026.

Protocol identity: Auto Finance Onchain is the rebranded Tokemak protocol; the legacy Ethereum treasury attribution is supported by Auto Finance’s rebrand materials and independent explorer labels. Treasury / reserve address: Ethereum Safe multisig 0x8b4334d4812C530574Bd4F2763FcD22dE94A969B (Tokemak/Auto Finance legacy treasury). Historical governance documentation identifies it as a 5-of-9 multisig controlling treasury funds and liquidity-deployment boundaries. Composition: The latest indexed Etherscan portfolio snapshot found shows approximately $5.18 million, entirely on Ethereum: ~83.3% stETH, 7.8% sUSDS, 6.8% TOKE, 1.3% USDC, 0.7% WETH, with smaller positions in SYND, MORPHO, CVXPRISMA, TCR, FXS and other assets. This is explorer/aggregator data, not Dune raw-data verification, and is stale relative to October 10, 2026. Custody and control: Custody is smart-contract-based through a Safe proxy.

Historical documentation supports 5-of-9 signer control; current signer set, threshold, and whether this remains the sole active treasury are Not verifiable as of October 10, 2026. Reserve policy: Auto Finance previously stated that treasury assets could be deployed through Autopilot and that revenue/treasury assets could fund AUTO/TOKE buybacks. No current formal reserve-ratio, liquidity-buffer, or segregation policy was located. The policy is Not verifiable as of October 10, 2026. Attestations: No independent proof-of-reserves, financial attestation, or liabilities reconciliation was located. Not verifiable as of October 10, 2026. Dune on-chain balances: Not verifiable as of October 10, 2026 (Dune MCP unavailable in this run; no on-chain balance claims are treated as Dune-verified). Contradiction / data-quality callout: The protocol previously marketed treasury value at approximately $30 million, while the latest indexed explorer snapshot is approximately $5.18 million.

The difference may reflect asset migration, valuation timing, or address scope; it is unresolved without current Dune coverage.

Token: Auto Finance AUTO, Ethereum contract 0x1Ec8eaa3f68261e793C48486b12092336A03c479. This is the post-TOKE migration token (1:1 migration began February 3, 2026); do not confuse it with the unrelated/legacy “Auto” contract 0xa184…b827. Supply/valuation (analytics, not on-chain verified): CoinGecko reports 100M circulating, 100M total, and 100M max supply; market cap and FDV were both approximately $4.37M at the latest page snapshot, implying no reported dilution. Because Dune was unavailable, these figures are not independently on-chain verified. Utility, staking and value capture: AUTO is used for staking in sAUTO, with a stated 16-week lock.

Protocol-owned-asset yield and, when enabled, protocol fees are intended to fund market buybacks of AUTO, distributed to sAUTO stakers. Legacy autopool incentives were TOKE and were being transitioned to AUTO. No separate burn mechanism or guaranteed revenue share was identified.

Governance voting rights or a current governance framework: Not verifiable as of October 10, 2026. Emissions/unlocks/allocations: A documented emissions schedule, team/investor/treasury/community allocation table, and proof that announced unlocks occurred on-chain: Not verifiable as of October 10, 2026. The migration itself is documented, but its completed on-chain volume cannot be independently confirmed without Dune. Contract controls: The verified proxy implementation exposes upgradeable ERC-20, access control, minting, burning and pausing components. Exact current minter/admin role holders and whether roles are multisig-controlled: Not verifiable as of October 10, 2026.

No blacklist or transfer-fee switch was identified in the surfaced verified interface; definitive confirmation: Not verifiable as of October 10, 2026. Concentration/liquidity: Top-holder concentration and insider-wallet attribution: Not verifiable as of October 10, 2026. CoinGecko listed Curve AUTO/TOKE and Uniswap v4 AUTO/ETH; displayed ±2% depth was roughly $0.87k/$0.87k and $2.57k/$2.57k, respectively, with about $10.6k combined 24h volume—very thin institutional liquidity.

For Auto Finance Onchain on Ethereum, the impact of Bitcoin falling below $10,000 is not verifiable as of 2026-10-10 because the provided sources do not include protocol-specific on-chain exposure, collateral composition, leverage, liquidation rules, or treasury data for this protocol. The only directly relevant protocol source says deposits are held in open-source smart contracts and withdrawals are subject to on-chain liquidity, but it does not disclose BTC-linked assets or stress behavior under a BTC crash. What can be said from the broader market context is that BTC moves below major support levels have historically triggered liquidation cascades and deleveraging across crypto markets, with funding turning negative and forced liquidations amplifying downside pressure.

If Auto Finance has any BTC-denominated vaults, LPs, or strategy dependencies, a BTC drop below $10,000 would likely stress collateral values, reduce strategy NAV, and potentially impair withdrawals if the protocol’s own liquidity buffers are thin; however, that is an inference and not verifiable from the available evidence. Because there is no protocol-specific evidence here, the prudent risk conclusion is: unknown direct exposure, unknown liquidation risk, and unknown loss severity for Auto Finance Onchain under this scenario. Any claim about exact losses, insolvency risk, or user redemption outcomes would be unsubstantiated from the provided sources.

Not verifiable as of 2026-10-10. The available web results do not identify Auto Finance Onchain (slug: auto-oc) on Ethereum with enough protocol-specific detail to quantify a 20% depeg stress on its largest collateral asset. The only relevant general evidence is that DeFi lending protocols typically liquidate when collateral falls below a liquidation threshold, and that a 20% price shock can generate bad debt in some systems under instantaneous stress assumptions.

However, there is no protocol-specific, independently verifiable source here showing Auto Finance Onchain’s collateral composition, largest collateral exposure, liquidation thresholds, or stress-test outputs, so the requested scenario result cannot be calculated reliably from the provided material.

Scope / limitation. Dune was unavailable, so the largest Ethereum counterparty and its exposure cannot be ranked: Not verifiable as of October 10, 2026. The scenarios below therefore apply to the largest underlying destination by exposure, not to a named counterparty. ### 1) Lending-market counterparty becomes insolvent

• Expected loss path: collateral shortfall or bad debt makes the destination position worth less than its cached debt value; recovery may be delayed or incomplete.
• Who absorbs it: the affected Ethereum autopool’s receipt-token holders absorb the loss pro rata through lower NAV/share. There is no documented senior-loss tranche or protocol-level principal guarantee in the reviewed materials.
• Compensation: Not verifiable as of October 10, 2026. TOKE/reward emissions are incentives, not documented loss insurance.
• Smart-contract path: DestinationVault valuation is updated during debt reporting; the RootPriceOracle/statistics machinery feeds valuation into the Autopool, reducing NAV. Withdrawals then redeem fewer base assets, potentially with additional exit slippage. ### 2) LST/LRT issuer or underlying staking counterparty fails
• Expected loss path: the derivative token depegs or becomes partially unrecoverable; oracle valuation marks the position down, with further losses if liquidation depth is inadequate.
• Who absorbs it: autopool LPs, pro rata; other destinations in the same autopool are not a documented capital backstop.
• Compensation: Not verifiable as of October 10, 2026.
• Smart-contract path: cached prices are refreshed at least periodically; debt reporting revalues destination LP tokens. Strategy gates can stop or restrict further swaps, but they do not restore principal. ### 3) DEX/LP venue is exploited or becomes illiquid
• Expected loss path: LP-token impairment plus unwind slippage and fees reduce recoverable base assets.
• Who absorbs it: autopool receipt holders; losses are reflected in redemption value rather than charged to the solver or keeper.
• Compensation: Not verifiable as of October 10, 2026.
• Smart-contract path: Strategy constraints may pause swaps when NAV lookback tests fail; otherwise rebalancing can exit into available liquidity. ERC-4626-style withdrawals are not guaranteed at par and may experience slippage. Bottom line: the documented loss waterfall is principally destination impairment → debt reporting/oracle repricing → lower autopool NAV → pro-rata LP loss. No verified external compensation mechanism was identified.

For Auto Finance Onchain on Ethereum, I found no verified evidence of committed fraud by the DAO or its owners in the provided sources. The available material is either generic DAO-risk discussion or Auto Finance documentation/audits, neither of which establishes a fraud event for this protocol. What can be said is narrower: Auto Finance’s own docs indicate it has published audits/security assessments for components such as autoUSD and LMPStrategy, which is a *risk-control signal* but not proof against fraud or misconduct.

The protocol website also describes the product as an autonomous LP rebalancing system, but that is an *unverified marketing claim* unless corroborated by independent sources. Stress-scenario assessment:

• Committed DAO/owner fraud: Not verifiable as of 2026-10-10.
• Known governance-fraud pattern relevant to this class of protocol: DAO governance can be abused via malicious proposals, flash-loan voting, or treasury-draining attacks in other protocols, including Beanstalk and similar cases.
• Protocol-specific evidence of such abuse here: Not verifiable as of 2026-10-10. If you want, I can next do a tighter adverse-screening memo focused on ownership structure, admin keys, upgradeability, and treasury-control risk for Auto Finance.

For Auto Finance Onchain (auto-oc) on Ethereum, the primary yield source in a 30-day negative-yield stress is not verifiable as of 2026-10-10 because the available results do not include protocol-specific on-chain data or a verified primary-yield breakdown for this protocol. What can be said from the provided materials is only general stress-methodology context: rating agencies model scenarios where asset yield falls below liabilities/fees, creating negative carry / negative spread risk that must be covered by reserves, spread accounts, or other credit support. That is a generic structured-finance concept, not evidence about this DeFi protocol.

I cannot confirm whether Auto Finance Onchain’s primary yield source is lending interest, staking rewards, LP fees, or another mechanism, nor can I quantify a 30-day negative return on-chain. Any protocol-specific claim here would be an unverified marketing claim or speculation, and the on-chain answer is Not verifiable as of 2026-10-10.

Governance assessment — Auto Finance Onchain (Ethereum; formerly Tokemak/Autopilot). Dune MCP was unavailable; therefore holder concentration, voting power, current contract-admin relationships, timelock state, and signer independence are Not verifiable as of October 10, 2026. No Dune query/execution IDs are available.

• Developer/contracts: The frontend and interface are operated by the Tokemak Foundation under the Terms of Use. The Foundation states it continues to operate the protocol; a separate V2 entity is being formed, but its formal name is still TBA. This indicates Foundation/company control rather than demonstrated token-holder control.
• Frontend: Foundation-controlled; Terms reserve unilateral rights to modify, restrict, or terminate interface access.
• Funds: The published Ethereum treasury is Safe 0x8b4334…A969B. Historical governance documentation identifies it as a 5-of-9 multisig controlling treasury funds and liquidity-deployment boundaries. Current signer identities, overlap, and independence are not verifiable.
• DAO/proposals: Historical Tokemak governance used staked-TOKE/CoRE voting for liquidity direction, while operational execution remained with multisigs. Current Auto Finance proposal rules and an executable token-holder governance path are not verifiable. Thus the DAO is symbolic/limited for the current system, not proven to control upgrades and parameters.
• Powers/risk: Multisig-administered treasury and contract-management functions create material centralization risk. Whether any current admin can arbitrarily drain depositor assets, and whether emergency bypasses exist, is Not verifiable as of October 10, 2026.
• Legal entity: “Tokemak Foundation” is named as the interface provider. Jurisdiction, registration number, directors, and legal form are Not verifiable as of October 10, 2026. Delaware law governs the Terms, but that does not establish incorporation in Delaware. Structured fields: timelock: null; timelock_delay_hours: null; multisig_threshold: 5; multisig_owners: 9; admin_can_drain: null; emergency_bypass: null; dao_governance: false

Legal/regulatory assessment (as of October 10, 2026): Auto Finance’s interface identifies its provider as the Tokemak Foundation. The Terms state that the interface is deemed based in Delaware, uses Delaware law, and requires individual JAMS arbitration in Delaware; this establishes contractual forum/law, but the Foundation’s legal domicile or registration jurisdiction is Not verifiable as of October 10, 2026. The protocol is described as a decentralized, non-custodial Ethereum protocol offering staking, liquidity provision, and automated yield vaults.

The interface is nevertheless operated by an identifiable foundation, creating a legal-structure-versus-actual-risk gap: users interact with smart contracts, but contractual claims, interface availability, geographic blocking, and privacy processing involve the Foundation. The Terms disclaim fiduciary duties, warranties, broad liability, and most remedies, including class actions and—in large part—injunctive relief. Restrictions/KYC/AML: Users must be 18+, comply with applicable law, and not be located in U.S.-sanctioned jurisdictions or otherwise prohibited jurisdictions. The Terms say the interface is directed solely to persons/entities in the United States and reserves geographic blocking rights.

The pool page states “No KYC required”; this is an unverified marketing claim, and no independent AML/KYC policy or regulated VASP/MSB status was located. Classification: No formal regulator classification of Auto Finance, Tokemak Foundation, AUTO, or the vault receipt tokens as securities, commodities, investment contracts, money-market instruments, or regulated collective-investment products was located. Not verifiable as of October 10, 2026. Economic exposure remains yield-bearing digital-asset/vault exposure, with smart-contract, liquidity, loss-of-value, liquidation, and regulatory risks expressly disclosed. Enforcement, litigation, sanctions: No regulator action, court case, warning, or sanctions designation specifically against Auto Finance or Tokemak Foundation was located in the searched sources. Not verifiable as of October 10, 2026. The sanctions clause restricts users; it does not establish that the protocol or Foundation is sanctioned. Data practices include wallet/public-chain data, IP-derived location, PostHog/Plausible analytics, and possible cross-border processing; an explicit GDPR/CCPA compliance analysis was not located.

No exact GLEIF LEI record for 'Tokemak Foundation', 'Auto Finance Onchain'. OFAC SDN screening of 'Tokemak Foundation', 'Auto Finance Onchain': no match. SEC litigation and administrative release feeds: no mention.

Auto Finance Onchain (Ethereum) appears to use external stablecoins in its autoUSD/Autopool products, but no verifiable evidence of a stablecoin depeg event was found in the gathered web sources. The protocol does not appear to issue its own stablecoin; its native token is AUTO, while autoUSD is a vault/share token rather than a stablecoin. Not verifiable as of 2026-10-10.

Auto Finance’s main risk is complexity: Ethereum Autopools automate rebalancing across multiple external DeFi venues, so losses can arise from the vault code, destination protocols, valuation logic, or liquidity conditions. Independent audits found historically significant high- and medium-severity issues, although reported findings were fixed or acknowledged; current on-chain exposure, concentration, and contract-control verification are Not verifiable as of October 10, 2026 because Dune MCP is unavailable.

Auto Finance’s top strengths are: full automation of position management, non-custodial smart contracts that keep users in control, and a solver-based rebalancing design that only trades when net gains exceed costs. It also stands out for on-chain strategy validation of rebalances (Certora-verified), range-priced debt reporting, and execution-accurate previews, which improve transparency and reduce mismatch between quoted and executed outcomes. The protocol’s Autopools are described as automated onchain vaults that optimize, rebalance, and auto-compound LP yield across major DeFi venues, abstracting away manual LP management.

Another strength is its multi-venue and multi-chain reach, with support described across Ethereum, Arbitrum, and Base in the search results, plus additional network mentions in some sources. Finally, Auto Finance emphasizes transparency through fully onchain fund flows and rebalance visibility, allowing users to see where capital is allocated and track each rebalance.