Native

What’s known (and what isn’t)

Native reports $68.5M (24h), $445.6M (7d), and $2.26B (30d) in swap volume across Binance, Ethereum, Polygon, Arbitrum, Mantle, ZetaChain, Avalanche, Manta, zkLink, with only $7.6K TVL. This volume/TVL profile is consistent with an RFQ / inventory-based execution design rather than a classic constant-product AMM where TVL and fee APR are directly observable.

Fee rates (per tier)

• Swap fee percentages: N/A (not published)
• Tier structure: N/A

Fee split (LPs vs protocol)

• LP / liquidity supplier share: N/A
• Protocol take rate: N/A
• Fee capture ratio (fees ÷ volume): Cannot be computed because 24h/30d fees are N/A.

Practical implication for earnings

Without a disclosed fee schedule and fee distribution policy, users cannot reliably forecast:

• Whether “Earn / Credit Pools” returns come from trading fees, spreads, interest on credit, liquidation penalties, or other mechanisms.
• The extent to which returns are variable with volume (which is large) versus fixed/interest-like.

What to verify before deploying capital

Institutional-grade diligence items to confirm inside the app/docs before sizing positions:
1) Exact fee bps charged per swap by chain and route.
2) Who earns the fee/spread (credit pool lenders, inventory providers, protocol treasury).
3) Any rebates or maker/taker logic tied to the “auto-sign orderbook” design.

Score rationale: high volume is attractive, but earnings visibility is currently low due to missing fee and revenue disclosure.

How “LPing” appears to work on Native

Native positions itself as an on-chain liquidity platform with “Credit Pools” and an “Earn” section, plus PMM pricing and an auto-sign orderbook that uses real-time on-chain inventory. That strongly suggests liquidity supply may be routed through credit/inventory pools rather than public AMM pair pools.

Current observability

Native’s headline TVL is $7.6K, which is extremely small relative to its $2.26B (30d) volume. However, the app-facing materials available do not enumerate public pool lists, pool TVL, or APYs, so risk-adjusted ranking must be treated as not yet transparent.

Top pools (public metrics)

The following table reflects what can be stated with hard numbers today; pool-level yields are not published in the available materials.

Strategy notes (conservative vs aggressive)

• Conservative: If Credit Pools allow lending against overcollateralized inventory, the conservative edge would be stable-asset denominated lending with strict risk limits. This must be confirmed in-product because pool composition and collateral rules are not published here.
• Aggressive: If earnings are tied to providing inventory that backs RFQ quotes, returns may be higher but will be exposed to inventory risk (holding volatile assets), fill/slippage dynamics, and potential credit events.

Bottom line

Native may offer capital-efficient earnings via credit/inventory mechanics, but pool-level APY/TVL and stable vs volatile exposure are not currently auditable from public pool data, limiting any precise risk-adjusted ranking.

Staking availability

There is no explicit evidence of single-token staking, LP token staking, or veToken/lock-based staking in the available product surface. The navigation includes “Credit Pools” and “Earn”, but does not describe a staking token, lock duration, or APR.

What this means for passive income seekers

• No published staking APR/APY: N/A
• No published lock durations: N/A
• No token requirements (e.g., governance token stake): N/A

Practical alternatives on Native

If the goal is passive yield, the only evidenced avenues are:
1) Credit Pools — likely a lender/inventory-supply product (exact rate mechanics not disclosed here).
2) Participating as a liquidity/inventory provider supporting the on-chain quoting mechanism described (PMM pricing + inventory-aware quoting), which may resemble market making more than classic passive staking.

What to confirm before treating it as “staking-like”

To underwrite passive income, confirm in docs/app whether Credit Pools provide:

• A fixed/variable interest rate display (APR) and how it’s set.
• Withdrawal terms (instant, queued, or epoch-based).
• Loss waterfall in adverse events (defaults, inventory drawdowns).

Score rationale: staking yield is not currently presented as a defined product with disclosed APR/lock terms.

What’s evidenced

Native’s interface exposes product areas titled “Credit Pools” and “Earn” (alongside Swap, Analytics, Integration, Docs). However, there is no disclosed liquidity mining program, no points system, no trading fee rebate schedule, and no referral program details visible in the available materials.

Incentive program status (today)

• Liquidity mining / reward tokens: Not evidenced
• Points / seasons / loyalty: Not evidenced
• Trading rebates: Not evidenced
• Referrals: Not evidenced

How users can still “earn” absent explicit incentives

Given the product naming, earning is most plausibly tied to:

• Credit Pools participation (interest/spread-based return, depending on how credit is extended and repaid).
• Supplying inventory that improves quote quality (the platform highlights “reliable quotes” and “real-time on-chain inventory”), which can generate spread/fee-based income if the protocol routes economics to liquidity suppliers.

What would make incentives investable

Before allocating capital specifically for rewards farming, look for:
1) A published rewards schedule (emissions per day/week) per pool/chain.
2) Eligibility rules (minimum liquidity, time-weighting, exclusions).
3) Clawback/slashing conditions if credit pools socialize losses.

Score rationale: there is a clear “Earn” surface but no concrete incentive mechanics or reward disclosures to model.

Native’s main evidenced earning surface is Credit Pools / Earn, while swap volume is very large ($2.26B over 30d) relative to TVL ($7.6K). Because fee rates and pool APYs are not disclosed here, the playbooks below focus on execution steps and risk controls; expected APY ranges are not publishable without in-app rate/fee data.

🛡️ Conservative (capital preservation focus)

1) Use Credit Pools only if you can select stable-asset exposure (confirm the denomination and withdrawal terms).

2) Start with a small allocation and validate realized yield vs stated rates over 7–14 days.

3) Avoid inventory/volatile exposure until loss waterfall and collateral rules are clear.

Expected APY: N/A (not disclosed). Range cannot be estimated from volume alone.

⚖️ Balanced (moderate risk/reward)

1) Split capital: a core allocation to the most transparent Credit Pool option (clearest rates/terms), plus a smaller allocation to any pool that is explicitly linked to swap activity.

2) Rebalance monthly based on utilization and any displayed borrow/credit metrics.

3) Keep chain exposure diversified (Native supports multiple chains) to reduce idiosyncratic operational risk.

Expected APY: N/A (not disclosed).

🔥 Aggressive (max yield focus)

1) If allowed, provide inventory for quoting (the design emphasizes “real-time on-chain inventory” and an “auto-sign orderbook”)—treat this as active market-making risk, not passive LPing.

2) Rotate across chains with the deepest realized activity (Native reports large aggregate volume; verify chain-level breakdown in Analytics).

3) Monitor inventory drift and unwind quickly if adverse selection increases.

Expected APY: N/A (not disclosed); outcomes can vary widely with spreads/fills.

Audit posture

• Audits: 0
• Audit firms / dates / scope: N/A
• Bug bounty: N/A
• Known incidents: N/A (no incident record provided)

Why this matters more for Native’s design

Native highlights atomic swaps with on-chain credit management, plus a high-frequency auto-sign orderbook using real-time on-chain inventory. Credit- and inventory-aware systems tend to introduce additional risk surfaces versus a simple AMM:

• Credit accounting correctness (debt, collateral, liquidation logic).
• Inventory solvency and potential bank-run dynamics if withdrawals are allowed.
• Signing/authorization flows (auto-signing increases the importance of permissioning and key management assumptions).

Impermanent loss (IL) estimates (general reference)

If any Native earning route behaves like a 50/50 AMM LP position, the standard IL profile applies:

(These are mathematical references; actual outcomes depend on the pool model and whether returns come from credit/spreads instead of AMM fees.)

Governance & safeguards

No evidence is provided for multisig controls, timelocks, pausability, or formal upgrade processes.

Score rationale: unaudited status with credit/inventory complexity materially elevates smart contract and mechanism risk.

1) Credit Pools (credit-based liquidity)

Native’s navigation explicitly includes “Credit Pools” and “Earn”, and the protocol describes “atomic Swaps with on-chain credit management.” This suggests a model where participants may supply capital into credit/inventory pools that support execution. Potential earning sources (to be confirmed in-product) typically include:

• Interest paid by credit users (if borrowing is involved).
• Spread capture if inventory is used to quote trades.
• Penalties/liquidation fees if undercollateralized positions are possible.

2) PMM pricing + auto-sign orderbook (inventory-aware quoting)

Native states it enables PMM pricing and runs a “high-frequency, auto-sign orderbook” that aligns with prevailing market prices, providing reliable quotes with low latency and a high success rate using real-time on-chain inventory.

For earners, this is distinct from classic LPing:

• Returns may be more like market making (spread-based), where performance depends on fill rate, adverse selection, and inventory drift.
• Capital efficiency can be high, consistent with the observed footprint: $2.26B 30d volume on $7.6K TVL.

Participation requirements (what to check)

To evaluate whether this is an opportunity or a trap, confirm:
1) Whether Credit Pools are permissionless or curated.
2) Whether pool participants bear loss socialization from credit events.
3) Whether yields are stablecoin-denominated or primarily inventory PnL.

Native’s earning potential is primarily tied to Credit Pools / inventory-backed quoting rather than transparent AMM fee APR; the protocol shows exceptional volume throughput ($2.26B 30d) but provides limited public yield disclosures and has 0 audits, making it best suited to sophisticated users who can independently verify mechanics and monitor risk.

Top 3 strengths

1) Exceptional activity vs capital: $2.26B 30d volume on $7.6K TVL implies highly capital-efficient execution.
2) Distinct mechanism: PMM pricing + auto-sign orderbook + on-chain inventory/credit management is differentiated.
3) Multi-chain reach: supports 9 chains, enabling operational and routing flexibility.

Top 3 weaknesses

1) No published fee schedule or revenue split: fees and LP/protocol take rates are not disclosed.
2) No audit history (0 audits): elevated smart contract and mechanism risk, especially with credit features.
3) No public pool/APY transparency: cannot rank pools or model risk-adjusted returns from public data.

One-sentence recommendation

Use Native for earning only if you can verify Credit Pool terms and economics inside the product and you are comfortable underwriting unaudited credit/inventory risk.