bch_qzjqnzgjz7w9tdflpz6u/deviant
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
deviant/Parameters/ASM DEX
History
walerikus 850afd651d feat(t6): validate BTC↔BCH end-to-end + bonded M-of-N + wallet UX (ADR-0046) 
"Bitcoin Cash as a better Lightning" (T6) and the BTC-IOU trust floor, validated
end-to-end on BCH chipnet + BTC signet with real coins.

- LN→T6 routing: a routed payment received into a T6 channel; one preimage settles
  both chains (BCH board reveal -> BTC HTLC claim). Scripts: chipnet-ln-to-t6-routing,
  btc-signet-ln-leg, btc-claim-htlc.
- T6c unilateral exit complete: honest CSV-delayed self-close (ELSE branch) added
  alongside the penalty branch (btc-signet-honest-close).
- T4 real BTC↔BCH atomic swap: one hashlock over a signet P2WSH HTLC + chipnet
  AtomicSwapHTLC; claim + refund (btc-bch-htlc-swap). Fixes btc-htlc.mjs bigint bug.
- Model-3 bonded M-of-N redemption: BondedSignerSlash.cash (equivocation -> slash) +
  2-of-3 signet release; BTC enforces the threshold, BCH enforces the punishment
  (chipnet-bonded-signer-test, btc-signet-mofn-release).
- T6-aware wallet UX: one-tap send/receive over the validated stack, every tap a real
  on-chain BchChannelBoard update (t6-wallet-server + design/t6-wallet); fresh-provider
  + retry hardening for flaky-chipnet broadcasts.
- Docs: ADR-0046, spec §16, Observability-and-privacy companion (the auditability
  property + the three-baseline privacy framing), complete-record/model-explainer/
  tracker updates, snapshots 0177–0179.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-28 00:27:04 +02:00
..
ASM-Multichain.md feat(crosschain): SafeERC20 refund fix + robustness suite + naming model 2026-06-23 23:05:48 +02:00
ASM-Orbital-Swap-native.md design: ASM/DEX swap taxonomy docs + interactive mockup 2026-06-21 18:22:09 +02:00
btc-on-bch-rails_test-program.md feat(t6): validate BTC↔BCH end-to-end + bonded M-of-N + wallet UX (ADR-0046) 2026-06-28 00:27:04 +02:00
build-B_usdt-tron-bch_scope.md feat(build-b): B1 TronHTLC primitive validated on Nile + DGB in landscape 2026-06-27 20:28:07 +02:00
cross-chain-asm-concept-and-state.md feat(crosschain): BTC↔BCH test program — HTLC swap, native channel, on-chain rails, BTC-IOU 2026-06-24 22:28:34 +02:00
cross-chain-send-receive_chain-landscape.md feat(build-b): B1 TronHTLC primitive validated on Nile + DGB in landscape 2026-06-27 20:28:07 +02:00
DEX-Multichain-Atomic-Swaps.md design: ASM/DEX swap taxonomy docs + interactive mockup 2026-06-21 18:22:09 +02:00
DEX-native-Order-book.md design: ASM/DEX swap taxonomy docs + interactive mockup 2026-06-21 18:22:09 +02:00
README.md docs(asm-dex): cross-chain send/receive chain & asset landscape 2026-06-27 03:30:02 +02:00

README.md

ASM vs DEX — the Deviant swap taxonomy

Two ways to move value, separated by the single question: does anyone have to take the other side?

  • ASM — Automated Swap Mechanism. Single-party (SP), zero counterparty. You alone act. No maker, no liquidity provider, no order, no human on the other end. The swap is a machine — a covenant (and, cross-chain, an oracle) executes a conversion against the asset's own backing or claim. It does not match a trade; it executes one.

  • DEX — Decentralized P2P Exchange. Two-party (P2P), needs a counterparty. Someone must provide the other side — a maker/LP on an order book, or a swap partner in an atomic swap. Non-custodial and on-chain, but counterparty-dependent by construction. This is the classical exchange paradigm, automated.

A second, orthogonal axis is chain:

  • Native — one chain (Bitcoin Cash).
  • Multichain — cross-chain.

The 2×2

Native (one chain, BCH) Multichain (cross-chain)
ASM (SP, zero counterparty) Orbital Swap — covenant-fixed rate, no order book, zero slippage Lock → oracle → mint IOU — lock under a VM condition, mint a transferable IOU on the other chain
DEX (P2P, needs counterparty) Order book — manual limit orders (CLOB) + optional AMM liquidity Atomic swap — HTLC, two parties agree, trustless

Each cell is documented separately:

Which real chains & stablecoins each multichain cell reaches (the landscape, with data): cross-chain-send-receive_chain-landscape.md — List A populates DEX·Atomic, List B populates ASM·Multichain.

Why ASM is not "just another DEX"

A canonical on-chain DEX is the classical exchange, automated and on-chain — it still requires a counterparty. An AMM or CLOB both rely on someone providing the other side, so both carry price discovery, spread, slippage, and price impact. The price is the market clearing between two sides.

ASM removes the market, not the exchange. "Exchange" is a function — the user still exchanges two assets (asset A for asset B). What ASM removes is the P2P market: there is no order book, no matchmaking, no LP, no maker, no human. You feed an MBA into the covenant and it converts at a rate fixed by consensus (units × backingRate) — the same for 1 unit or 1,000,000. Zero slippage, zero price impact regardless of size, because there is no curve to move. So ASM is not a P2P exchange — it is how you perform the exchange function through an automated mechanism instead of a P2P market.

The automation ladder (inside DEX only)

CLOB and AMM are the same species — one order book, one matching engine — differing only in who makes the orders:

Order-making Order book + matchmaking Liquidity from Human in loop
CLOB manual — you place each order yes counterparties' resting orders yes (both sides)
AMM automated — a preconfigured bot makes & maintains orders yes (the pool is the book) LPs who fund the pool yes (the LPs)
ASM none — no orders exist no the asset's own BCH backing none

An AMM is a CLOB with the order-making automated: you preconfigure (deposit liquidity + a curve) and a bot runs that configuration onto the same book, matched the same way. (A constant-product curve is mathematically equivalent to a continuum of resting limit orders.) ASM is off this ladder entirely.

Two cross-chain modes, split by the same counterparty test

Both move value across chains, but they fall on opposite sides of the SP/P2P line:

  • ASM · Multichain = single-party, no counterparty. You lock under a VM condition; an oracle attests; a covenant mints a transferable IOU whose identity is its CashToken category (one per source chain); displayed as the asset name
    • a network badge (USDt · Tron), with a τ/ε prefix as the text-only fallback (see naming). Trust = the lock VM + the oracle (not a person). Requires the source chain to support VM scripts.
  • DEX · Atomic swap = two-party, needs a counterparty, but trustless via a shared hashlock (no oracle, no escrow). Requires both chains to support HTLCs (hashlock + timelock).

Related project records

  • ASM = the counterparty-free protocol swap validated on chipnet (snapshot 0008).
  • wiki/decisions.md: ADR-0007 (reservoir model), ADR-0016 (route by asset class: MBAs → ASM, Token-class → external market), ADR-0025 (obligor-free MBA), ADR-0031 (synthetic USD), ADR-0035 (USD-rail bridge trilemma — a covenant verifies a signature, not a claim's truth), ADR-0036 (on-ramp).
  • Interactive model: design/mockups/bch-dex.html — all four cells are live and testable (ASM rate is size-independent; DEX shows slippage/matchmaking; cross-chain shows the oracle-mint vs HTLC trust split).