# What You Can Build

Sig Network gives an application on one chain its own accounts on every other chain — and, when it matters, cryptographic proof of what happened there. No bridges, no wrapped assets, no custodians: the assets stay native on their home chain, and your application controls them directly.

## Multichain smart account

One smart account or multisig on Ethereum that natively holds and moves Bitcoin, assets on Base, Cosmos tokens — any chain, one identity. The account's existing approval process (signers, spending limits, timelocks) governs every action, while the assets themselves never leave their home chains. Treasury operations that today need a bridge, a wrapped asset, or a custodian become ordinary account operations.

## Cross-chain DEX on Solana

A Solana exchange taps Ethereum liquidity directly: users trade on Solana, the swap executes on Uniswap, and the venue credits the exact proceeds back to the trader on Solana — with proof the trade really happened. The same venue can put idle inventory to work on Ethereum, staking it or lending it out, all managed from Solana.

## Institutional settlement from Canton

Institutions that run on Canton — where privacy, parties, and compliance live on-ledger — can custody and settle public-chain assets without leaving it. Entitlements and approvals stay on Canton; execution happens on Ethereum; every settlement is verified before the books move. This one is live today: the [Canton ERC-20 vault](https://github.com/sig-net/canton/blob/main/daml-packages/signet-vault-v1/README.md) custodies Ethereum assets under Daml-governed rules.

***

Everything above composes two capabilities: **execute** (have any transaction signed and sent from an account your app controls on another chain) and **verify** (receive proof of the result back on your own chain before your app acts on it). The two full walkthroughs — [Holding Ethereum Assets from Solana](/examples/cross-chain-deposit) and [Staking on Ethereum from Solana](/examples/solana-stake-ethereum) — show the mechanics.

If it can be phrased as "an application on chain A wants something done on chain B — and maybe proof that it happened," it fits. Start with the [Sign Bidirectional Flow](/architecture/sign-bidirectional) for the verified variant, or the [staking example](/examples/solana-stake-ethereum) for fire-and-forget execution.