Echelon Market

Echelon Market is a Move-based decentralized, non-custodial lending protocol. Its official website is echelon.market and its docs are docs.echelon.market. The docs state it is deployed on Aptos, Movement, and Initia, while Aptos Foundation describes it as an “Efficient Move Money Market.” The protocol’s native token is ELON, with token-launch coverage appearing in independent reporting and exchange/market listings. Launch date: not fully verifiable from the available sources. The most defensible on-web signal is that Echelon says it launched on Aptos mainnet in April 2024 in its own article, but that is self-published and not independently confirmed here. Aptos Foundation later described Echelon v1 as already live and audited on Aptos, but did not restate the original launch date. Chains: Aptos, Movement, Initia, plus an Echelon Chain / Echelon appchain announcement built on Initia’s Interwoven Stack. Chain exposure split: Not verifiable as of 2026-08-30. Main contract addresses with >=2-source cross-check incl. Dune / explorer verification status: Not verifiable as of 2026-08-30. The current sources retrieved do not provide a reliable, independently cross-checked contract-address list, and no on-chain verification path is available in this run. Fork lineage: Echelon appears to be a Move-native lending-market design that may be inspired by prior Move lending architectures, but a specific upstream fork is not verifiable from the available sources. The sources do show it evolved from Aptos deployment to multi-chain Move deployment and then an Echelon Chain/appchain direction on Initia. Any claim that it is a direct fork, and any upstream-specific modifications, are Not verifiable as of 2026-08-30. Audits / malicious-modification history in similar forks: Aptos Foundation states Echelon v1 is audited, but the audit report itself was not retrieved here. A broader history of malicious modifications in similar forks is Not verifiable as of 2026-08-30.

Echelon Market appears to be a live product, not just a landing page: its homepage currently shows active protocol stats such as “TOTAL DEPOSITS” and “ACTIVE LOANS,” and the documentation describes concrete lending actions like supplying, borrowing, and withdrawing. The docs also reference a frontend at app.echelon.market and note that specific pool criteria are shown on the Borrow page, which is consistent with an operational dApp rather than a static marketing site. Product maturity looks moderate: the documentation is substantial, includes developer guidance and SDK references, and names an Aptos mainnet contract address, which suggests more than a template shell. The project also publishes technical docs for risk management and oracle configuration, which is a maturity signal for an active DeFi protocol. I could not verify live deposit/withdrawal execution, broken links, or fake metrics from the available web evidence alone, so those points are Not verifiable as of 2026-08-28. The homepage metrics should still be treated cautiously because they come from the protocol’s own site, not independent on-chain verification. An open API is likely available: the GitHub SDK includes programmatic borrow/supply/withdraw examples and points to API documentation, indicating developer-facing integration support. However, whether that API is fully public, stable, and documented for third-party use beyond SDK consumers is Not verifiable as of 2026-08-28.

Audit of Core Lending. The docs page lists this report as January 2025. Findings counts, fix status, and deployed-code coverage are Not verifiable as of 2026-08-28 from the snippet provided.

Audit of Core Lending. The docs page lists this report as March 2024. The snippet does not expose issue counts, fix status, or bytecode-match evidence, so those fields are Not verifiable as of 2026-08-28.

Audit of LPT (Liquidity Pool Token) Integration. The docs page lists the report date as April 2025. Finding counts, remediation status, and deployed-code coverage are Not verifiable as of 2026-08-28 from the available snippet.

Audit of Core Lending. The docs page lists this report as May 2025 and separately lists an earlier Ottersec Core Lending audit from March 2024. The docs page does not provide finding counts or fix-status details in the snippet, so critical/high/medium counts are Not verifiable as of 2026-08-28.

Audit of Core Lending. The docs page lists this report as April 2025. No issue breakdown or fix-status data is visible in the provided result, so critical/high/medium findings and whether the audit covers deployed code are Not verifiable as of 2026-08-28.

Audit of Isolated Pools. The docs page lists this report as July 2024. Finding counts, fix status, and deployed-code coverage are Not verifiable as of 2026-08-28 from the provided result.

Audit of Initia & Movement Deployment. The docs page lists this report as January 2025. Critical/high/medium counts, remediation status, and whether the reviewed code matches deployed bytecode are Not verifiable as of 2026-08-28 from the available snippet.

Echelon Market appears to have an active bug bounty program. The clearest public confirmation is on Echelon’s own documentation, which says it “offers a bug bounty program” for white-hat researchers, with rewards varying by severity and critical reports routed to a dedicated security email. The public website also advertises a bounty of “$250,000+”. What is verifiable about the program:

• Started: Not verifiable as of 2026-08-28. The available sources confirm the program exists, but none of the retrieved pages provide a launch date or start announcement for the bounty itself.
• Parameters: Echelon states rewards vary by severity, and its GitHub vulnerability-disclosure policy says it uses CVSS to assess severity, patches eligible releases privately, notifies the community before public fixes, and pays bounties after community notification. Aptos also reported a range of $500 for low-severity issues to $10,000 for critical vulnerabilities for the new mechanics. The public site’s headline bounty figure is $250,000+.
• Results: Not verifiable as of 2026-08-28. No retrieved source provides the number of reports paid, total payouts, or confirmed bounty-eligible findings. There is one internal inconsistency in the public materials: the website’s $250,000+ bounty claim is much broader than the Aptos article’s $500–$10,000 severity range, so the exact payout structure is unclear from the available sources.

Echelon Market’s main external risks stem from its chain dependencies (Aptos, Initia/Echelon, Move stack), oracle feeds, bridges, and stablecoin/LST exposure. Not verifiable as of 2026-08-30: any on-chain data (Dune MCP unavailable). 1. Core stack & chain dependencies

• Runs on Aptos and Initia/Echelon (Move-based), so protocol liveness, settlement finality, and asset safety depend on each chain’s consensus, validator set, and upgrade process.
• Any critical reliance on native DEXs, lending markets, or perps for pricing/liquidity (e.g., spot oracle anchors or hedging) introduces indirect counterparty risk from those venues (liquidation cascades, insolvency, MEV/extractive behavior). 2. Oracles & price manipulation
• Documentation and public materials indicate use of price oracles (likely Pyth / Switchboard / chain-native oracles) for mark prices, liquidations and AMM curves, typical for perp/options-style venues.
• Key risks:
• Short-window TWAP or single-source feeds can be manipulated via thin liquidity on reference DEXs.
• Cross-chain oracles (bridged prices from other ecosystems like Ethereum) add bridge and relayer risk.
• Oracle failure (downtime, stale prices, misconfigured feeds) can cause mass mispricing and wrongful liquidations. 3. Bridges & interoperability
• As a Move-based multi-chain protocol, asset onboarding from Ethereum and other L1s to Aptos/Initia likely uses third‑party bridges (e.g., LayerZero/Wormhole or similar), though specific bridges are not clearly attributable from available public information.
• Bridge risks:
• Smart contract exploits or validator collusion on the bridge.
• Depegs of wrapped assets if the bridge becomes undercollateralized or halts redemptions. 4. Stablecoin & LST/restaking exposure
• Echelon Market lists USDC/USDT-like stablecoins and major LSTs on supported chains for collateral and trading, based on general product positioning for perp/options markets.
• Counterparty risks:
• Centralized stablecoins (USDC/USDT) carry issuer, banking, and regulatory freeze risk.
• Algorithmic or exotic stables on Aptos/Initia can depeg or become insolvent during stress.
• LSTs and restaking tokens embed Ethereum/Aptos validator slashing and liquidity risk; extreme scenarios include LST depeg vs underlying and cascading liquidations across DeFi. 5. CEX/MM & off-chain counterparties
• Market-making appears at least partly non‑custodial (on-chain), but top‑of‑book liquidity may rely on professional MMs that hedge on CEXes or other perps.
• Indirect risks:
• MM failure or withdrawal (e.g., due to CEX issues) can cause slippage spikes, orphan positions, and wider spreads. Given limited independent data on exact oracle/bridge contracts and collateral lists, many specific dependencies are Not verifiable as of 2026-08-30 and should be confirmed directly with contract-level analysis and protocol disclosures.

Echelon Market is described as non-custodial and permissionless, which means the protocol itself does not take possession of users’ crypto; users interact through lending/borrowing pools rather than handing assets to a centralized custodian. Its materials also describe it as a decentralized lending protocol for the Move ecosystem, with users supplying or accessing liquidity through capital-efficient markets. Based on the available sources, custody appears organized as self-custody at the user wallet level plus smart-contract / pool-based custody for protocol operations, not as third-party institutional custody.

No incident since launch is clearly documented in the provided sources. The only directly relevant source says Echelon Market’s team is running a bug bounty for new mechanics, but it does not report an exploit, loss, affected users, reimbursement, or a post-incident fix, so incident details are not verifiable as of 2026-08-28.

Echelon Market does not publicly document a formal *key-management* architecture for the protocol itself in the provided sources. The clearest verifiable information is that Echelon is described as non-custodial and permissionless, meaning users retain control of their own private keys rather than handing custody to the protocol. For protocol administration, the docs show that risk and market controls are organized through governance proposals and Asset Listing Admins appointed by governance, which indicates that administrative authority is separated from user asset custody. The protocol website also describes Echelon as a modular lending market, but it does not specify multisig signers, hardware-key procedures, or other concrete operational key controls in the available materials. Based on the evidence available, the safest answer is that end-user key management is left to users, while protocol-level permissions appear to be governed by on-chain governance and appointed admins; details of signer setup are Not verifiable as of 2026-08-28.

Echelon Market appears to be an Aptos-based perpetuals/derivatives DEX with additional deployment on the Initia Echelon L2, built in Move, but detailed contract/admin data is fragmented and largely non‑standardized. Because Dune/on‑chain tooling is unavailable in this run, all on‑chain specifics are: Not verifiable as of 2026‑08‑28. ### 1. Contract identification & verification

• Core contracts (Aptos, Initia, Move): Public lists of module addresses, verification status, and proxy layouts are Not verifiable as of 2026‑08‑28.
• Browser verification (Aptos explorer, Initia explorer) and move.toml / GitHub references exist, but I cannot reliably map them to a full architecture without on‑chain queries. ### 2. Upgradeability & proxy / module governance
• Move‑based protocols typically use governance-controlled module upgrade capability rather than EVM-style proxies; however, whether Echelon has:
• upgrade capability still active,
• any timelock on upgrades,
• multi‑sig governance, is Not verifiable as of 2026‑08‑28. ### 3. Admin / owner / emergency roles For each of the following, concrete role addresses, quorum rules, and thresholds are Not verifiable as of 2026‑08‑28:
• Admin / owner of main trading, margin, and collateral modules.
• Any emergency/pause role for trading, withdrawals, liquidations.
• Fee‑setting and oracle configuration rights.
• Control over listing/delisting markets or changing risk parameters. Given typical Move DeFi patterns, there is a meaningful chance that:
• A concentrated governance entity can halt trading, change fees, or modify key parameters.
• Users’ ability to exit may depend on whether withdrawals remain unpaused in emergencies. These are informed general Move‑ecosystem inferences, not protocol‑specific facts. ### 4. Timelock, role renouncement, user exit
• Timelock delay for upgrades or parameter changes: Not verifiable as of 2026‑08‑28.
• Whether upgrade/admin capabilities have been fully renounced: Not verifiable as of 2026‑08‑28.
• Assurance that users can always exit (close positions / withdraw collateral) without admin cooperation: Not verifiable as of 2026‑08‑28. ### 5. Key‑compromise / worst‑case scenarios (risk framing) Given standard non‑fully‑immutable DeFi architectures on new L1/L2s:
• If governance or emergency keys are compromised, plausible worst cases include:
• Trading pause or freeze, blocking position management.
• Parameter or oracle manipulation, causing forced liquidations or mispriced PnL.
• Fee or transfer‑rule changes that impair withdrawals. Because we cannot confirm contract code or roles, rug/freeze risk and admin concentration must be treated as high and unquantified pending direct explorer + code review.

Echelon Market appears to be a derivatives / perp DEX ecosystem built around the Echelon Initia chain, with activity also referenced on Aptos and broader Move ecosystem, but founder and corporate reality are poorly documented and largely not verifiable as of 2026-08-30. ## 1. Founders & Team

• Public materials (site, docs, X, Medium) describe Echelon as a “team of experienced traders and DeFi natives” but do not name any founders, executives, or core contributors by legal name or link to LinkedIn/GitHub in an obviously identifiable way.
• No independent profile (Crunchbase, AngelList, major VC blogs, credible interviews) clearly attributes Echelon Market to specific, KYC’d founders.
• Therefore, team is effectively anonymous/pseudonymous from an institutional risk standpoint. Not verifiable as of 2026-08-30:
• Exact founder identities and prior track record.
• Any history of their earlier projects, exits, or hack involvement. ## 2. Prior Projects / Outcomes / Hacks
• No reliable cross-reference (auditor blogs, incident postmortems, exploit databases) explicitly ties named individuals or entities behind Echelon Market to prior DeFi protocols.
• No major hacks/exploits publicly attributed to “Echelon Market” itself in mainstream incident trackers; absence of evidence is not confirmation of safety. ## 3. Public vs Anonymous; Credibility
• Given lack of doxxed leadership, Echelon should be classified as an anonymous/pseudonymous team protocol.
• Credibility relies mainly on:
• Technical content and product shipping cadence (code, UI, integrations).
• Any audits or formal reviews (none clearly surfaced from top-tier firms within 7 days; older mentions are either generic or unclear and thus not relied upon).
• From an institutional lens, anonymity materially raises key-person, governance, and recourse risk. ## 4. Office, Jurisdiction, Business Substance
• No clearly stated registered company name, jurisdiction, or physical office address on the main site/docs.
• No obvious corporate registry entries or regulatory filings found that are conclusively tied to “Echelon Market” rather than similarly named entities.
• This places Echelon in the category of offshore / undefined jurisdiction, web-native protocol, with no verifiable real-world operating company. Not verifiable as of 2026-08-30:
• Onshore vs offshore incorporation.
• Any real office or employees. ## 5. Reality Check – Institutional Risk View
• Founder and corporate opacity is high; governance, legal recourse, and key-person transparency are weak.
• Treat Echelon Market as:
• Anonymous DeFi protocol with unclear legal wrapper.
• Dependent on smart-contract and market risk controls rather than enforceable off-chain obligations.
• Any institutional exposure should assume elevated counterparty and enforcement risk and require compensating controls (position limits, independent technical review, and conservative collateral/tiering).

Echelon Market currently has a positive, “emerging blue-chip” reputation in the Move ecosystem, with multiple top-tier audits and no public records of hacks, rugs, insolvency, or regulatory sanctions as of 2026-08-28. ### Team, investors, and institutional positioning

• The protocol positions itself as a core lending layer for Move-based chains (Aptos, Initia, Movement) and targets institutional-grade markets.
• A 2024 seed round of $3.5m is reported, framed as funding “to revolutionize DeFi lending on Move-based blockchains,” indicating VC backing and institutional ambitions, though specific investors are not named in retrieved materials.
• Echelon joined the Aptos LFM program, a curated ecosystem initiative, which is a soft signal of ecosystem-level endorsement. ### Audits and external security review
• The audit page lists a multi-auditor stack, including OtterSec, Quantstamp, Code4rena (Zenith), and Zellic, with repeated coverage of core lending, isolated pools, and integrations from March 2024 through at least May 2025.
• Multiple audits from independent firms and a competitive audit contest (Code4rena) materially strengthen perceived technical diligence, though real exploit absence is *Not verifiable as of 2026-08-28*. ### Market footprint and sentiment
• Ecosystem and media coverage (Aptos directory, Bybit learn article, press releases) describe Echelon as a high-efficiency, non-custodial lending market inspired by Aave’s E-Mode, emphasizing rehypothecation and capital efficiency.
• Analytics platforms list Echelon with hundreds of millions in TVL, positioning it among the larger Move money markets, but exact values are Not verifiable as of 2026-08-28.
• Narrative across ecosystem posts and listings is broadly positive/neutral, focused on growth, efficiency, and cross-chain expansion, with no mainstream negative coverage detected. ### Criticisms, incidents, and regulatory/legal profile
• No credible reports of fraud, rug pull, insolvency, major loss events, or sanctions were found in news, ecosystem directories, or exchange listings as of 2026-08-28.
• No specific regulatory actions or court cases associated with Echelon Market, its token (ELON), or core team appear in retrieved sources as of 2026-08-28. Not verifiable as of 2026-08-28.
• Explicit community criticisms (e.g., governance disputes, opaque tokenomics) are not surfaced in the retrieved set. Not verifiable as of 2026-08-28. ### Unresolved concerns / data gaps
• On-chain behavior, real-time risk metrics, and incident history cannot be independently checked in this run: Not verifiable as of 2026-08-28.
• Identity details of founders and exact investor roster are incomplete in public summaries: Not verifiable as of 2026-08-28.

Available information on Echelon Market is extremely sparse and fragmented; key economic parameters cannot be reliably established. Below is what can be said under the given evidence standard. ### Protocol scope & strategy Public data suggests Echelon is a perpetuals / derivatives-focused venue in the Initia ecosystem, with references to “Echelon Initia” and Move-based environments (Aptos/Move), but there is no consistent, independent description of a live production protocol with verifiable contracts or markets. Name collisions and vague mentions make it unclear whether this is a launched product or an announced component in the broader Echelon/Initia stack. As of 2026‑08‑28, core elements of the economic model are Not verifiable:

• Precise strategy (orderbook vs AMM perps, vaults, or structured products)
• Asset flows in/out (collateral types, settlement asset, margining model)
• Yield sources (trading fees, funding, staking, or external DeFi integrations) ### Yield, risk profile, leverage No independent analytics (DeFiLlama, Token Terminal, L2Beat) offer a dedicated “echelon-market” listing with TVL, APY, or product breakdown. Therefore, as of 2026‑08‑28:
• Yield source: Not verifiable.
• Organic vs subsidized (incentives, points, token emissions): Not verifiable.
• Market neutrality vs directional exposure (delta‑neutral vaults vs leveraged perps): Not verifiable.
• Leverage/looping/restaking/external exposure: Not verifiable. ### Mechanics: lock‑ups, withdrawals, fees There is no independently confirmed documentation (audits, explorers, analytics) that describes:
• Lock‑up terms or withdrawal queues.
• Fee schedule (trading, funding, performance, protocol fee splits).
• Gates/limits (KYC, caps per user, risk parameters). All such details would be unverified marketing claims if taken solely from any promotional material; they are therefore excluded. ### Collateral, TVL, revenue, APY history Because contract addresses and chain deployments (Aptos, Initia) cannot be matched to a verified, active “Echelon Market” instance in explorers or analytics:
• Collateral types and haircuts: Not verifiable as of 2026‑08‑28.
• Protocol revenue (fees accrued, PnL split): Not verifiable as of 2026‑08‑28.
• TVL total / by product / by chain / trend (Dune vs DeFiLlama): Not verifiable as of 2026‑08‑28.
• APY history, volatility, sustainability: Not verifiable as of 2026‑08‑28. ### Analyst takeaway Given the absence of independent, chain‑linked data, Echelon Market currently cannot be underwritten for institutional exposure. Any economic‑model assessment would be speculative and fall outside the required evidence standard.

Echelon Market’s publicly documented treasury / reserves are only partially verifiable from the web results provided. The clearest disclosed item is a token treasury allocation: the ELON tokenomics page says 20,000,000 ELON is reserved for the treasury to fund future development and long-term sustainability, and the risk-management page says the protocol’s reserve factor allocates a portion of interest to the ecosystem treasury. What is not verifiable as of 2026-08-28 from the available sources: the treasury wallet addresses, on-chain balances via Dune, custody arrangement, control / multisig signers, reserve policy details beyond the reserve factor concept, and any independent attestation of treasury holdings. The results provided do not include a verified on-chain dataset, explorer page, audit report, or governance record establishing those facts. For chain scope, the available sources confirm Echelon is present on Aptos and list a broader Echelon Initia / Move context, but they do not disclose chain-by-chain reserve balances or a treasury split across those chains. The only concrete composition detail found is that treasury funding is described in ELON token units and via protocol revenue allocation through the reserve factor; no stablecoin, native coin, or other asset breakdown is disclosed in the provided material. In short: disclosed treasury size exists only as a token allocation and reserve-flow policy; custody, balances, and control remain not verifiable as of 2026-08-28.

Echelon Market does have a native token: ELON. The docs list the token name as Echelon Token, ticker $ELON, with 100,000,000 total and maximum supply, and give the token address as 0xfc087a394c203d62c43eecfeba79db01441d39dd9d234131b78415626a26750e and the contract as 0x51964f09020498a1421a2a3bafe8e1d9fa72574b60446486c599bc6f3e9fae29. The protocol states ELON is used for governance, protocol incentives, and directing emissions; the docs also describe governance over risk parameters, asset listings, and treasury management. Public tokenomics on the protocol docs allocate 8.5% to airdrops, 30% to community/ecosystem, 2.5% to liquidity/exchanges, 20% to treasury, 20% to investors, and 19% to core contributors. The docs do not provide a complete, verifiable unlock calendar in the material gathered here. The launch was reported in secondary sources as having occurred on 2026-02-02, but whether all announced unlocks have actually happened on-chain is Not verifiable as of 2026-08-30. Market cap / FDV / circulating supply: a market-data page reports 13.5M ELON circulating and therefore implies an FDV close to total supply, but that figure is an aggregator estimate, not on-chain verified. Because Dune/on-chain checks are unavailable in this run, supply in circulation, holder concentration, insider wallets, actual unlock execution, and control over mint/blacklist/fee-switch functions are Not verifiable as of 2026-08-30. Revenue share, buybacks, burns, staking rewards: not clearly evidenced in the gathered sources beyond protocol incentives and rewards language; specific mechanisms are Not verifiable as of 2026-08-30. Chain / liquidity / listings: Echelon is deployed on Aptos, Movement, and Initia per the docs, but chain-by-chain TVL or exposure split is Not verifiable as of 2026-08-30. Main listing/liquidity venue details are also Not verifiable as of 2026-08-30 beyond the docs’ statement that 2.5% is reserved for CEX listings and DEX liquidity.

Not verifiable as of 2026-08-28. The available search results do not provide on-chain or protocol-specific evidence for Echelon Market’s Aptos / Echelon Initia / Move exposure under a Bitcoin drop below $10,000, and the protocol website result is only a general product description. The external results about Bitcoin falling to $10,000 are market commentary and do not establish how Echelon Market would be affected. For this stress scenario, the only defensible statement is that a BTC crash to sub-$10,000 would likely create broad risk-off pressure across DeFi lending markets, but the magnitude of Echelon Market’s impairment, liquidations, bad debt, or chain-by-chain TVL impact is Not verifiable as of 2026-08-28. No reliable source in the provided set confirms Echelon’s collateral composition, borrow exposures, liquidation thresholds, reserve buffers, or chain-level TVL split. Because on-chain verification is unavailable in this run, I cannot confirm whether BTC-linked collateral exists on Aptos, Echelon Initia, or Move, nor whether the protocol has direct or indirect BTC price dependency. If you want, I can still produce a qualitative risk memo with explicit assumptions, but it would remain unverified marketing-adjacent inference rather than a sourced exposure analysis.

For Echelon Market, a 20% depeg of the largest collateral would likely push a meaningful share of positions into liquidation, and any debt left uncovered after liquidation would become bad debt socialized to lenders in the affected pool. Echelon’s own risk docs say liquidations are triggered when a position’s Health Factor falls below 1, and that if collateral cannot fully cover debt, the shortfall is socialized among pool lenders. I can verify the protocol’s liquidation mechanics, but the size of the 20% depeg impact is not verifiable as of 2026-08-28 because no on-chain exposure data, collateral composition, or largest-collateral balance by chain was provided, and Dune-based on-chain verification is unavailable in this run. Echelon supports multiple assets and separates global collateral pool markets from isolated markets, so the effect can differ materially by chain and market structure. What can be said with confidence is:

• Liquidations would increase first, as accounts breaching the liquidation threshold become eligible for liquidation.
• Bad debt risk rises if liquidations cannot be executed quickly enough due to volatility, slippage, or insufficient liquidity.
• The stress outcome depends on the largest collateral’s share of total collateral, its liquidation threshold, and the liquidity available for liquidation execution. If you want a quantified loss estimate, the missing inputs are the largest collateral token, its total outstanding collateral on Aptos / Echelon Initia / Move, and the protocol’s borrowed exposure against that collateral. Without that, the stress result cannot be responsibly calculated.

Echelon Market is a derivatives/structured-product DEX on Aptos and Initia; positions are intermediated by smart contracts rather than traditional bilateral OTC. Detailed on-chain views are Not verifiable as of 2026-08-28. Below is a generic stress path for “top counterparty becomes insolvent” under credible designs used by Echelon-style protocols (orderbooks/perps/options on Move chains). Treat this as a risk-mapping, not a TVL-specific quantification. ### 1. Perpetuals / leveraged products Trigger: Top LP / market-maker account cannot meet margin; positions fall below maintenance. Loss path:

• Smart contract auto-liquidates the insolvent account’s positions against oracle prices and AMM/orderbook liquidity.
• If liquidation proceeds < liabilities, the shortfall hits the protocol-level insurance fund, if any.
• If insurance fund is exhausted, mechanisms typically impose haircuts on profitable traders (socialized loss) or negative funding adjustments. Who absorbs:
• First: insolvent LP’s own margin and collateral in the smart contract.
• Second: dedicated insurance/treasury pool if implemented.
• Last: all open traders via loss socialization or bad-debt spread. Impact through contracts:
• Liquidation & margin-engine contracts change balances and close positions.
• Funding-rate / PnL accounting contracts re-mark positions and possibly apply haircuts. Compensation:
• No external compensation; users are made whole only up to margin/insurance capacity.
• Any ex-post compensation (treasury grants, governance vote) is a discretionary, off-chain decision, not guaranteed. ### 2. Structured notes / vaults Trigger: Top issuer / vault of structured products cannot honor payoff. Loss path:
• Smart contract computes payoff using oracle inputs and transfers available assets.
• If underlying collateral in the vault < promised notional, the payout is mechanically reduced; there is no hidden balance sheet. Who absorbs:
• End-users holding note tokens; losses are strictly limited to assets held by the vault contract. Impact through contracts:
• Settlement contract executes payoff; if available_collateral < required_payout, users simply receive less. Compensation:
• Same pattern: at most protocol treasury / governance-based top-ups; otherwise users bear the loss. ### 3. Cross-chain / wrapped exposure (Aptos ↔ Initia ↔ Move) Trigger: Insolvent bridge or wrapper used by top counterparty. Loss path:
• On affected chain, wrapped assets become partially or fully unbacked.
• Echelon positions using those assets as collateral become undercollateralized. Who absorbs:
• Holders of the wrapped asset and traders whose margin was in that token, via liquidations and haircuts. Impact through contracts:
• Collateral valuation module marks wrapped asset down, triggering forced deleveraging. Because Dune/on-chain queries are unavailable for this run, all protocol-specific metrics and contract-level implementations are Not verifiable as of 2026-08-28.

No public evidence in the provided results supports a finding that Echelon Market’s DAO or owners have committed fraud. The only directly relevant Echelon Market source is its Terms of Service, which prohibit fraudulent or manipulative trading and the use of criminal proceeds; that is a policy statement, not evidence of actual fraud by the DAO or owners. The other provided results are low-credibility or likely misaligned: several discuss a different entity/domain (“echelondao.io”) rather than Echelon Market, so they cannot be used to assess this protocol without a confirmed name/address match. One Reddit post speculates that high APRs may indicate a scam, but it is unverified opinion, not evidence. For the requested stress scenario, the correct risk conclusion is: fraud by the DAO or owners is not verifiable as of 2026-08-28. If you want a fraud-stress assessment, the next step would be to verify team identity, governance control, and contract/admin-key structure from independent sources; those checks are not available in the supplied results.

Echelon Market’s primary yield source negative 30d is not verifiable as of 2026-08-28 from the available web results. The strongest available source is DefiLlama, which reports Holders Revenue (30d) = $0 and Holders Revenue (7d) = $0 for Echelon Market, but that is an aggregator metric and does not prove the protocol’s underlying primary yield source was negative over the last 30 days. What can be said with confidence is that Echelon Market is a fixed-yield protocol built around PT/YT mechanics: users split SY into PT + YT, PT represents principal at expiry, and YT accrues the yield stream until expiry. The docs also state that Echelon relies on external oracle feeds and fallback pricing mechanisms for risk management, but that does not answer the 30-day primary-yield question. For a stress scenario assessment, the practical interpretation is:

• Yield compression / zero revenue: supported only at the aggregator level by DefiLlama’s zero holders revenue over 30d.
• Negative primary yield source: Not verifiable as of 2026-08-28.
• Chain breakdown across Aptos, Echelon Initia, and Move: Not verifiable as of 2026-08-28 from the provided results. If you need a risk note, the defensible statement is that the protocol shows no observable holders revenue in the last 30 days on DefiLlama, but there is insufficient evidence here to conclude the underlying primary yield source itself turned negative.

I could not verify which *stablecoin* Echelon Market used from the available sources, so the depeg history is not verifiable as of 2026-08-28. The sources only confirm Echelon Market’s existence and price pages, but they do not identify the protocol’s stablecoin or provide a reliable price history for it. If you want, I can next help identify the exact stablecoin/token pair used by Echelon Market and then assess whether it depegged, how many times, and by how much.

Echelon Market’s top protocol risks are: smart contract risk, oracle/price-feed risk, collateral/liquidation risk, asset listing / concentration risk, and centralization or governance risk. Its own documentation explicitly highlights undetected bugs, oracle dependencies, liquidation failures and black-swan bad debt, plus the risk added by onboarding new or more centralized assets.

• Smart contract risk: even after testing and third-party audits, unknown bugs or exploits could still cause loss of protocol funds, user funds, unrealized yield, or parameter tampering through governance exploits.
• Oracle / price-feed risk: Echelon relies on partnered oracle providers, and inaccurate or manipulated prices can trigger unexpected liquidations or poor market decisions; some assets use different oracle sources, increasing complexity.
• Collateral / liquidation risk: if collateral value falls below debt, positions can be liquidated; in volatile or illiquid markets, slippage, gas, or thin liquidity can prevent timely liquidation and leave bad debt that is socialized to lenders in the affected pool.
• Asset listing / concentration risk: listing new collateral increases insolvency risk, especially for long-tail or higher-risk assets; the docs note supply caps, borrow caps, isolated markets, and restrictions on oracle-manipulation-prone assets to contain this risk.
• Centralization / governance risk: Echelon flags centralized assets as introducing single points of failure, and some assets are limited to isolation mode specifically because of centralization concerns; protocol parameters like LTV, liquidation thresholds, reserve factors, and caps are governance-configured and can be mis-set or misused. Not verifiable as of 2026-08-28: chain-by-chain exposure or TVL split across Aptos, Echelon Initia, and Move, because on-chain verification was unavailable in this run.

Echelon Market’s top strengths are: 1) capital efficiency through E-Mode and high-LTV borrowing on correlated assets; 2) risk isolation via modular, isolated markets that limit contagion; 3) multi-product breadth spanning lend/borrow, fixed-yield trading, leverage, and looping; 4) Move-native, multi-chain deployment across Aptos, Movement, and Initia; and 5) strong ecosystem integration with support for major stablecoins, BTC-related assets, and LSTs, which helps it serve as a core liquidity layer for Move DeFi.