> For the complete documentation index, see [llms.txt](https://j1tfyi.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://j1tfyi.gitbook.io/docs/utilities-and-future-plan/j1.cross-chain-portal.md). # J1.CROSS-CHAIN PORTAL The [J1.CROSS-CHAIN PORTAL](https://ccp.j1t.fyi/) (J1.CCP) is a pivotal component of the J1T.FYI ecosystem. It is engineered to overcome the fragmentation of the blockchain space. It is built upon the robust and secure deBridge Liquidity Network Protocol (DLN) through which it facilitates seamless, instant, risk-free, and cost-effective token swaps across an extensive network of 25+ blockchain networks. J1T.FYI has chosen to integrate the deBridge DLN as the foundational layer for its cross-chain portal. The DLN's architecture enables direct transfers of native assets without the need for wrapped tokens, significantly reducing inherent risks and complexities. ## Key Features ### Zero Slippage All swaps are executed at deterministic prices, removing volatility and arbitrage risks between chain hops. ### Zero Risk No wrapped tokens, no custodial intermediaries. Only native token swaps via protocol-verified liquidity pathways. ### 25+ Chain Support Seamless interoperability across major EVM and non-EVM blockchains without reliance on third-party bridges. These chains include: ***EVM-Compatible Chains*** 1. Abstract 2. Arbitrum 3. Avalanche (C-Chain) 4. Base 5. Berachain 6. Binance Smart Chain (BSC) 7. BOB 8. Ethereum (ETH) 9. Flow 10. Gnosis 11. HyperEVM 12. Hyperliquid 13. Linea 14. Mantle 15. Neon 16. Optimism 17. Plasma 18. Polygon (MATIC) 19. Sei 20. Sonic 21. Story 22. Zilliqa ***Non-EVM Chains*** 1. Solana 2. Solana xStocks 3. Tron ## J1.CCP Non-Custodial Architecture {% @mermaid/diagram content="graph TB A\[👤 User Initiates] --> B\[🔌 Connect Wallet] B --> C\[📝 Define Swap] C --> D\[✍️ Sign Transaction] D --> E\[⚙️ Lock in Contract] E --> F\[🤖 Solver Fulfills] F --> G\[🔍 Validators Verify] G --> H{Conditions Met?} H -->|Yes| I\[⚡ Atomic Settlement] H -->|No| J\[↩️ Revert & Refund] I --> K\[✅ Complete] J --> K ``` style A fill:#e1f5ff,color:#000 style D fill:#ff9800,color:#000 style E fill:#9c27b0 style I fill:#4caf50,color:#000 style K fill:#2e7d32" %} ``` ### Section 1: User Control & Wallet Connection Users maintain complete sovereignty over their private keys throughout the entire process. J1.CCP supports 30+ non-custodial wallets via industry-standard connection protocols (WalletConnect v2, Web3Modal, EIP-1193). {% @mermaid/diagram content="graph LR subgraph User\_Layer\["👤 USER CONTROL LAYER "] A\[User Initiates Swap] --> B{Select Wallet
30+ Options} B --> C1\[MetaMask] B --> C2\[WalletConnect] B --> C3\[Coinbase Wallet] B --> C4\[Phantom] B --> C5\[Other Wallets...] C1 & C2 & C3 & C4 & C5 --> D\[User Retains
Private Keys 🔐] style User\_Layer fill:#2e7d32,stroke:#0066cc,stroke-width:3px end" %} **Key Security Principle**: Private keys never leave the user's local environment. All wallet connections use read-only session tokens—J1.CCP has zero access to signing capabilities. ### Section 2: Transaction Initialization & User Signature Once connected, users define swap parameters and sign transactions locally. This is the **critical control point** where users explicitly authorize the cross-chain swap. {% @mermaid/diagram content="graph TB A\[📝 Define Swap Parameters] --> B\[Select Source Chaine.g., Ethereum] B --> C\[Select Destination Chaine.g., Solana] C --> D\[Amount & Asset Selection] D --> E\[Review Transaction Details] ``` E --> F{✍️ User Signs Transaction in Their Wallet?} F -->|Reject| G[❌ Transaction CancelledNo Assets Moved] F -->|Approve| H[✅ Signed TransactionBroadcast to Network] style A fill:#e8f5e9,stroke:#4caf50,stroke-width:2px,color:#000 style F fill:#ff9800,stroke:#e65100,stroke-width:3px,color:#000 style G fill:#ffebee,stroke:#c62828,stroke-width:2px,color:#000 style H fill:#c8e6c9,stroke:#2e7d32,stroke-width:2px,color:#000" %} ``` **User Approval Required**: Every transaction requires explicit signature approval from the user's wallet. Rejection stops the process immediately with zero asset movement. ### Section 3: Smart Contract Lock & Solver Network Approved transactions trigger asset locking in audited deBridge DLN smart contracts. Independent market-making solvers compete to fulfill orders on the destination chain. {% @mermaid/diagram content="graph TB A\[Solver Fulfills Order on Destination Chain] --> B\[Decentralized Validators Verify Transaction] B --> C{Settlement Conditions Met?} C -->|No| D\[Transaction Reverted - Assets Returned to User] C -->|Yes| E\[Atomic Cross-Chain Swap Executed] E --> F\[Destination Assets Released to User Wallet] D --> F F --> G\[Transaction Complete - User Maintains Full Control 🔐] ``` style E fill:#4caf50,stroke:#1b5e20,stroke-width:2px style G fill:#2e7d32,stroke:#1b5e20,stroke-width:3px" %} ``` **User Approval Required**: Every transaction requires explicit signature approval from the user's wallet. Rejection stops the process immediately with zero asset movement. {% @mermaid/diagram content="graph TB A\[Signed Transaction Broadcast] --> B\[⚙️ Assets Locked in Audited DLN Smart Contract] B --> C\[Lock Event Emitted on Source Chain] C --> D\[🔒 25+ Independent Security Audits Verified ✓
No J1.CCP Custody or Control] ``` D --> E[🤖 Solver Network Detects Cross-Chain Lock Event] E --> F[Competitive Solver Auction Begins
Best Rate Selection Process] F --> G[Winning Solver Selected Based on Optimal Terms] G --> H[Solver Fulfills Order by Releasing Native Assets
Directly to User Wallet on Destination Chain] style B fill:#9c27b0,stroke:#4a148c,stroke-width:3px style D fill:#f3e5f5,stroke:#9c27b0,stroke-width:2px,color:#000 style E fill:#e0f2f1,stroke:#009688,stroke-width:2px,color:#000 style H fill:#c8e6c9,stroke:#2e7d32,stroke-width:2px,color:#000 ``` " %} **No Custodial Intermediary**: Assets are locked in trustless smart contracts, not transferred to J1.CCP. Solver network operates independently with staked collateral incentives. **Audit References**: [deBridge Security Audits](https://github.com/debridge-finance/debridge-security) - Halborn, Ackee Blockchain, Zokyo, Pessimistic, ABDK. ### Section 4: Validator Consensus & Atomic Settlement Decentralized validators cryptographically verify cross-chain state before enabling atomic settlement. The protocol guarantees all-or-nothing execution. {% @mermaid/diagram content="graph TB A\[Solver Fulfillment Complete] --> B\[🔍 Decentralized ValidatorsVerify Transaction] B --> C\[Cross-ChainState Confirmation] C --> D\[Consensus Reached] ``` D --> E{⚡ Settlement ConditionsMet?} E -->|No| F[↩️ Transaction RevertedAssets Returned to User] E -->|Yes| G[✅ Atomic Cross-Chain SwapExecuted] G --> H[Destination Assets Released Directly to User Wallet] F --> H style B fill:#fce4ec,stroke:#e91e63,stroke-width:2px,color:#000 style E fill:#e8eaf6,stroke:#3f51b5,stroke-width:3px,color:#000 style F fill:#ffebee,stroke:#c62828,stroke-width:2px,color:#000 style G fill:#4caf50,stroke:#1b5e20,stroke-width:3px,color:#000 style H fill:#c8e6c9,stroke:#2e7d32,stroke-width:2px,color:#000" %} ``` **Atomicity Guarantee**: If any condition fails (timeout, insufficient liquidity, chain error), the entire transaction reverts and assets return to the user's source wallet. No partial states are possible. ### Section 5: Transaction Completion The swap concludes with direct asset delivery to the user's destination wallet. No wrapped tokens, no custodial bridges, no intermediary control. {% @mermaid/diagram content="graph TB A\[Assets Released] --> B\[✅ User Receives AssetsWallet-to-Wallet] B --> C\[No Wrapped TokensNative Asset Transfer] C --> D\[No Intermediary CustodyPeer-to-Peer Settlement] D --> E\[🔐 Transaction CompleteUser Maintains Full Control] ``` style B fill:#c8e6c9,stroke:#2e7d32,stroke-width:2px,color:#000 style E fill:#2e7d32,stroke:#1b5e20,stroke-width:4px" %} ``` **Final State**: Users receive native assets directly in their destination chain wallet. J1.CCP never held, controlled, or accessed user assets at any point in the transaction lifecycle. ### Architecture Summary The complete non-custodial flow ensures: | Security Property | Implementation | | ---------------------------- | --------------------------------------------------------------------------- | | **Private Key Control** | User retains keys at all times—never shared with J1.CCP | | **Zero Custody** | Assets locked in audited smart contracts, not protocol-controlled addresses | | **Atomic Execution** | Cryptographic guarantee of complete success or complete revert | | **Decentralized Validation** | Independent validator network verifies cross-chain state | | **Direct Settlement** | Peer-to-peer wallet-to-wallet transfers via smart contracts | | **No Wrapped Assets** | Native token transfers across chains without bridge wrapping | **Protocol Foundation**: Built on deBridge DLN with 25+ security audits. Supported across 24+ chains including Ethereum, Solana, Base, Arbitrum, Polygon, and Tron. ## **J1.CCP Streamlined 3-Stage Process:** ### 1. Order Creation A user (the maker) initiates a cross-chain swap by locking their tokens on the source blockchain via the DLN Source smart contract. In this process, the user specifies the desired destination token, the amount to be swapped, and the recipient address on the target blockchain. ### 2. Solver Fulfillment A network of independent solvers constantly monitors pending orders on the source chain. These solvers fulfill the maker's order instantly on the destination chain by sending the requested tokens to the specified recipient address using the DLN Destination smart contract. ### 3. Cross-Chain Confirmation Once the solver has fulfilled the order on the destination chain, a single, secure cross-chain message is relayed back to the source chain. Upon verification of this message, the maker's initially locked tokens are released to the solver, completing the atomic swap. This efficient mechanism minimizes latency and ensures that funds are only released to the solver after successful fulfillment. ## Non-Custodial Cross-Chain Swap Protocol ### Zero-Custody Architecture J1.CCP operates as a fully non-custodial protocol built on deBridge's DLN (DeFi Liquidity Network), enabling trustless asset transfers across 24+ blockchains without intermediary custody. Users retain exclusive control of their private keys and sign transactions locally using their own wallets—including MetaMask, Phantom, Coinbase Wallet, and 30+ others via WalletConnect v2. **Key Principle**: J1.CCP never gains custody, possession, or signing authority over user assets. This aligns with Bitcoin's foundational philosophy: "not your keys, not your coins." *** ### How It Works The protocol uses a three-phase atomic swap mechanism: #### **Phase 1: Asset Lock** Users lock source assets in audited DLN smart contracts that function as hash time-locked contracts (HTLCs) with built-in expiry conditions. #### **Phase 2: Solver Fulfillment** Decentralized solver networks—independent market makers with staked collateral—detect lock events and compete to fulfill orders. The winning solver releases native assets directly to the user's destination wallet. #### **Phase 3: Validator Verification** Validator networks cryptographically verify cross-chain state transitions and enable atomic settlement only upon proof of successful fulfillment. **Atomicity Guarantee**: If any phase fails (timeout, insufficient liquidity, or consensus failure), the entire transaction reverts and locked assets automatically return to the user's wallet. No partial states possible. *** ### Security Model #### **Defense-in-Depth** The DLN protocol has completed 25+ independent audits from leading security firms including Halborn Security, Ackee Blockchain, Zokyo, Pessimistic Security, and ABDK Consulting. #### **Eliminated Risks** By removing custodial intermediaries, J1.CCP eliminates vulnerabilities that caused $3.8 billion in industry losses during 2022: * **Exchange insolvency**: FTX ($8B user losses) * **Hot wallet exploits**: Mt. Gox (850K BTC) * **Bridge hacks**: Ronin ($625M), Wormhole ($325M) * **Regulatory seizures**: No pooled assets to confiscate * **Exit scams**: No centralized control #### **Remaining Risks** * **Smart contract vulnerabilities**: Mitigated through formal verification and multi-audit processes * **Private key management**: User responsibility, supported through hardware wallet integration (Ledger, Trezor) and multi-sig wallets (Gnosis Safe) *** ### Regulatory Status Under FinCEN guidance (FIN-2019-G001), non-custodial protocols that facilitate peer-to-peer transactions without taking custody are generally not classified as money services businesses (MSBs) or money transmitters. J1.CCP provides software infrastructure for direct wallet-to-wallet swaps—not custodial services. Users retain full legal responsibility for: * Private key security * Transaction verification * Tax reporting * Jurisdictional compliance This is consistent with the self-custodial DeFi model where users are their own custodians. ## Native & Meme Token Support ### Direct Native Asset Swaps J1.CCP enables direct cross-chain swaps of native blockchain assets and ecosystem tokens without intermediary wrapping or synthetic representations. Users swap **native-to-native**: ETH (Ethereum) directly to SOL (Solana), BNB (BNB Chain) directly to AVAX (Avalanche), or any supported asset pair across 24+ chains—receiving the actual native token on the destination chain, not a wrapped or bridged derivative. **Technical Implementation**: The deBridge DLN protocol eliminates wrapped token dependencies through its solver-based liquidity model[^1]. When a user swaps ETH for SOL, the protocol: 1. **Source Chain**: Locks ETH in the DLN smart contract on Ethereum 2. **Solver Network**: Independent market makers holding native SOL compete to fulfill the order 3. **Destination Chain**: Winning solver releases **native SOL** directly to the user's Solana wallet 4. **Settlement**: Solver claims the locked ETH after cryptographic proof of fulfillment This architecture contrasts fundamentally with **lock-and-mint bridges** (e.g., Wormhole, Multichain) that issue wrapped representations like wETH, wBTC, or bridged USDC[^2]. Lock-and-mint bridges create synthetic tokens pegged 1:1 to locked collateral, introducing: * **Liquidity fragmentation**: Wrapped tokens trade at different prices than native assets * **Depeg risk**: Wrapped token value can deviate from native asset (cf. Multichain USDC depeg, 2023) * **Additional redemption step**: Users must unwrap tokens to access native assets * **Smart contract attack surface**: Both lock and mint contracts must remain secure **Native Asset Advantages**: | Property | Native Assets (J1.CCP/DLN) | Wrapped Assets (Traditional Bridges) | | ------------------- | -------------------------------- | -------------------------------------------------- | | **Liquidity** | Unified native market depth | Fragmented across wrapped variants | | **Composability** | Full DeFi protocol compatibility | Limited to bridges supporting specific wraps | | **User Experience** | Single-step swap, native receipt | Multi-step: bridge → unwrap → use | | **Risk Profile** | Smart contract risk only | Smart contract + depeg + collateral custody risk | | **Market Pricing** | Native market rates | Premium/discount vs. native depending on liquidity | ### Meme Token & Long-Tail Asset Support Beyond established layer-1 tokens, J1.CCP supports cross-chain swaps for **meme tokens** and emerging ecosystem assets that typically lack bridge infrastructure. Examples include PEPE, SHIB, DOGE, BONK, WIF, and thousands of ERC-20, SPL, and other standard tokens across supported chains. **Why Most Bridges Don't Support Meme Tokens**: 1. **Liquidity Requirements**: Lock-and-mint bridges require significant locked collateral for each token pair 2. **Economic Viability**: Bridge operators won't lock capital for low-volume or volatile assets 3. **Smart Contract Deployment**: Each new token requires bridge contract deployment and auditing 4. **Governance Overhead**: Bridge DAOs must vote to whitelist new assets **DLN Solver Advantage**: The decentralized solver model eliminates these constraints. Any solver with liquidity can fulfill orders for any token—no protocol whitelisting required. If sufficient solver liquidity exists for a token pair, the swap executes. This creates a **permissionless long-tail asset market** similar to DEX models but with cross-chain capabilities. **Technical Constraint**: Token must have sufficient solver liquidity on both source and destination chains. Exotic token pairs may experience wider spreads or longer fulfillment times compared to high-volume pairs (ETH/USDC, SOL/USDC). ### Supported Asset Categories #### **Layer-1 Native Assets** * **Ethereum (ETH)**: Native gas token * **Solana (SOL)**: Native gas token * **BNB (BNB)**: BNB Chain native token * **Avalanche (AVAX)**: C-Chain native token * **Polygon (MATIC/POL)**: Native gas token * **Arbitrum (ETH)**: Arbitrum native ETH * **Base (ETH)**: Base native ETH * **24+ additional chains**: Full list at deBridge Network Status #### **Stablecoins** (Native, not wrapped) * **USDC**: Circle-issued native USDC on supported chains * **USDT**: Tether-issued native USDT * **DAI**: MakerDAO DAI on supported chains #### **Major DeFi Tokens** * **Wrapped BTC (WBTC)**: Note: This is a wrapped asset but treated as a standard ERC-20 * **Chainlink (LINK)**: Cross-chain oracle token * **Uniswap (UNI)**: Governance token * **Hundreds of additional tokens**: Based on solver liquidity availability #### **Meme & Community Tokens** * **PEPE, SHIB, DOGE**: Established meme tokens with multi-chain presence * **BONK, WIF**: Solana ecosystem meme tokens * **Long-tail assets**: Any token with solver liquidity support ### Key Differentiator: No Wrapped Representations When you swap ETH to SOL on J1.CCP: * ✅ You receive: **Native SOL** on Solana blockchain * ❌ You do NOT receive: wSOL, bridged SOL, or synthetic SOL * ✅ Immediate composability: Use SOL in any Solana DeFi protocol immediately * ✅ No unwrapping required: Native asset is directly usable This eliminates the multi-step process of traditional bridges: ``` Traditional Bridge: ETH → Bridge Lock → Receive wSOL → Unwrap to SOL → Use SOL (3-4 steps, additional gas fees, wrapped token risks) J1.CCP/DLN: ETH → Native SOL (1 step, native asset received) ``` ### Technical Architecture: Solver Liquidity Pools Solvers maintain their own liquidity inventories across chains. For a cross-chain swap: ```typescript // Conceptual representation interface SolverOrder { giveChain: "ethereum"; giveToken: "0x0000...0000"; // ETH native address giveAmount: "1000000000000000000"; // 1 ETH in wei takeChain: "solana"; takeToken: "So11111111111111111111111111111111111111112"; // SOL native takeAmount: "150000000000"; // ~150 SOL in lamports receiver: "UserSolanaWalletAddress"; deadline: 1735689600; // Unix timestamp } // Solver fulfills by sending NATIVE SOL from their own liquidity solverWallet.transfer({ to: order.receiver, token: NATIVE_SOL, // Not wrapped amount: order.takeAmount }); ``` **Economic Incentive**: Solvers profit from spread between locked and fulfilled amounts, similar to market makers on DEXs. Competition between solvers drives tight spreads on high-volume pairs[^3]. ### Verification: Native Asset Receipt Users can verify native asset receipt through block explorers: **Example ETH → SOL Swap**: 1. **Source Transaction** (Ethereum): Shows ETH locked in DLN contract * Contract: `0x...` (deBridge DLN Source) * Event: `OrderCreated` 2. **Destination Transaction** (Solana): Shows native SOL transfer to user wallet * Program: Solana System Program (native transfers) * Instruction: Transfer (not token program, confirming native SOL) **Red Flag for Wrapped Assets**: If you see transfers involving token programs like SPL Token Program or ERC-20 transfer events, you're receiving wrapped tokens, not native assets. *** [^1]: deBridge Foundation. (2023). "DLN Architecture: Solver-Based Cross-Chain Liquidity." [^2]: Qin, K., et al. (2021). "Attacking the DeFi Ecosystem with Flash Loans for Fun and Profit." *Financial Cryptography and Data Security 2021*. [^3]: Adams, H., et al. (2021). "Uniswap v3 Core." (Analogous market-making economics) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://j1tfyi.gitbook.io/docs/utilities-and-future-plan/j1.cross-chain-portal.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.