FORUM

Demo

About

The problem it solves # The Problems FORUM Solves—and How It Makes Your Life Easier & Safer ## 1. Fragmented Liquidity Across Chains - **Pain Point**: Liquidity is siloed on each blockchain, so users chase rates manually across multiple bridges and DEXes. - **FORUM Fix**: One unified order-routing engine taps pools on Solana, Ethereum, Avalanche, BNB, Polygon, etc., finding the best price in a single trade. No more hopping between apps. ## 2. Complex Multi-Chain UX - **Pain Point**: Switching wallets, networks, bridges, and token standards for each new chain—confusing and error-prone. - **FORUM Fix**: Single interface + CCIP under the hood. Connect your wallet once, choose source & destination chains, and trade—no manual bridging, no extra approvals. ## 3. Bridge-Related Security Risks - **Pain Point**: Many bridges are custodial or rely on a small set of validators—big targets for hacks and rug pulls. - **FORUM Fix**: Leverages Chainlink CCIP’s trust-minimized, fraud-proof messaging network. Funds are locked on the source chain, relayed by permissionless CCIP nodes, and minted on the target—no single point of failure. ## 4. Slippage & Latency - **Pain Point**: Manually stitching multiple transactions inflates gas fees and slippage, especially when moving assets across chains. - **FORUM Fix**: Atomic cross-chain swaps and multi-hop routing in one CCIP message. You get end-to-end settlement in one ticket, reducing both slippage and overall gas costs. ## 5. Gas-Token Fragmentation - **Pain Point**: Need to hold native gas tokens (ETH, BNB, AVAX, MATIC…) on each chain to transact. - **FORUM Fix**: Pay gas in any asset you’re moving. FORUM auto-swaps a small fee portion into the destination chain’s native token just in time for settlement. --- # Key B2B & DAO Infrastructure Use Cases | Use Case | Problem | FORUM Solution | Revenue Model | |-------------------------------|-------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------| | **Cross-Chain Payroll** | DAOs & companies struggle to pay employees across different chains | Schedule salaries in one dashboard—CCIP routes payments to each employee’s preferred chain & wallet. | SaaS subscriptions + transaction fees | | **Cross-Chain Invoicing** | B2B customers demand to pay in their favorite blockchain/tokens | Issue invoices denominated in any asset; FORUM collects and disburses across chains automatically. | Payment processing fees + SaaS fees | | **Multi-Chain Treasury Ops** | Fragmented treasury management, complex fund allocation across chains | Consolidate treasury movements via FORUM: rebalancing, vesting, and yield-harvesting anywhere. | Consulting + premium features | | **DAO Governance Bridge** | Voting tokens locked to one chain can’t count elsewhere | FORUM bridges governance tokens trustlessly so a DAO can snapshot & tally votes across multiple networks | Integration fees + governance tokens | --- # How You Benefit - **One-Click Cross-Chain Trades** Eliminate manual bridging, approvals, and network toggles. - **Built-In Security** Chainlink CCIP’s off-chain relayer mesh with on-chain fraud-proofs keeps your funds safe. - **Cost & Time Savings** Atomic routing slashes gas overhead and reduces trade execution time. - **Scalable B2B Tools** Payroll & invoicing modules plug into any corporate or DAO workflow—no bespoke bridge development needed. - **Full Transparency & Analytics** Real-time dashboards show you volumes, fees, and latency metrics across every chain. --- Kickstart your FORUM integration today—ditch the siloed bridges, consolidate your liquidity, and bring enterprise-grade cross-chain payments to your users or team.

How it's made

Challenges we ran into Here are a few of the stickiest bugs and hurdles we hit while building **FORUM**, and exactly how we untangled them: --- ## 1. Out-of-Order Relayer Messages **The Bug:** Our CCIP relayer network occasionally delivered messages in the wrong order—so a “mint LP token” call would land *before* the corresponding “lock assets” event. Trades silently failed, leaving user funds in limbo. **How We Solved It:** - Added a monotonically increasing `sequenceId` to every CCIP payload. - On the FORUM DEX contract, we reject any message whose `sequenceId` ≤ last processed. - Built an idempotent dispatcher pattern so replayed or delayed messages simply revert without side-effects. --- ## 2. Cross-Chain Gas & Fee Abstractions **The Hurdle:** Users wanted to pay Ethereum gas fees using SOL or BNB tokens when bridging in. Naively swapping on-chain caused high slippage and occasional out-of-gas errors. **How We Overcame It:** - Introduced a “fee escrow” module: users pre-deposit a small amount of native gas token on each destination chain. - Built an internal DEX router (via Chainlink Functions) to auto-rebalance gas pools off-peak, minimizing slippage. - Fallback: if gas pool dips too low, we pull from a communal “FORUM treasury” to top it up, then auto-reimburse. --- ## 3. Token-Standard & Decimal Mismatches **The Bug:** We bridged an SPL token (6 decimals) into an ERC-20 (18 decimals) but forgot to adjust the conversion factor—users saw 0.000001 USDC or 1,000,000 USDC. **How We Fixed It:** - Created a unified **AssetAdapter** library that: 1. Reads on-chain `decimals()` (or config map for non-EVM). 2. Normalizes all amounts to a 10⁸-precision intermediate before final mint/burn. - Wrote exhaustive unit tests across every supported chain’s testnet token to catch regressions. --- ## 4. Solana ↔ EVM Address Canonicalization **The Hurdle:** Solana’s Base58 addresses and EVM’s hex addresses don’t map one-to-one. Our first attempt simply hex-decoded the Solana key, which collided for some vanity addresses. **How We Overcame It:** - Deployed a tiny on-chain **AddressRegistry** on each chain that stores a Solana→EVM mapping. - In the “lock” step on Solana, we require users to register their EVM address. That mapping gets bundled in the CCIP payload. - The destination contract verifies the mapping via a Merkle-proof against the on-chain registry before minting. --- ## 5. Front-End Wallet & Chain-Switch UX **The Bug:** Switching nets (e.g. from Phantom to MetaMask) mid-workflow dropped our React state. Users would click “bridge” twice, end up with duplicate orders or stuck in “awaiting signature.” **How We Fixed It:** - Introduced a global **ConnectionManager** component that: 1. Detects provider changes. 2. Gracefully tears down and re-initializes CCIP listeners. 3. Persists pending order metadata in `localStorage` so workflows can resume after a wallet swap. - Added a “Confirm network” modal before any cross-chain action, so users know exactly which wallet & chain they’re transacting on. --- Each of these refinements took us from an intermittent, hard-to-debug “ghost” behavior to a rock-solid, production-ready DEX experience. If you want code snippets or a deep dive into our testing harness, just let me know!