StripChain launched a public testnet proposing a vertical architecture to address limitations of current intent protocols in token routing.

Background

Intent protocols aimed to let users express desired outcomes while networks determined optimal execution paths, promising seamless cross-chain exchanges.

In practice, many intent implementations function as simple swap buttons that borrow liquidity, complete trades, then rebalance through conventional cross-chain bridges.

Problems with current implementations

Existing solutions such as Across and Near Intents rely on solvers that act as market makers, lending assets from rented liquidity pools.

Those liquidity pools are scattered across networks and managed by relayers and third parties, which limits composability and prevents building more advanced applications on top.

StripChain’s architecture

Rather than renting liquidity, StripChain implements a vertical stack that includes native asset custody, cross-chain account derivation and an integrated application layer.

• Asset Layer — a decentralized validator network holds native assets such as $BTC and $SOL, and mints synthetics like sBTC, sSOL, sETH and sSUI, plus an internal DEX.
• Signing & Custody Layer — connecting one existing wallet (for example, Ethereum or Solana) seeds a unified account that spans multiple networks.
• Application Layer — solvers become full applications that users can interact with regardless of the network where they are deployed.

Testnet and security model

Testnet v1 runs on Arbitrum Sepolia and supports 5 networks: Bitcoin, Solana, Ethereum, Sui and Arbitrum.

Using StripWallet, users connect an existing wallet and receive a single multi‑chain account with native addresses across all supported networks.

When the validator set changes, the bridge generates a new key and physically transfers assets to new addresses, a process designed to preserve custody continuity.

Roadmap

The immediate objective is full liquidity unification via the native DEX so assets can move freely between applications rather than merely entering networks.

Subsequent steps include staking mechanisms for token holders as the validator set grows; initial testnet access is open, with plans to limit participation through a Community Program.