Inception Bridge
The Inception Bridge enables secure cross-chain asset transfers between Inception and other blockchain networks. This guide covers how the bridge works, security measures, and usage guidelines.
Overview
The Inception Bridge uses a lock-and-mint mechanism for Phase I operations:
- Lock: Assets are locked on the source chain
- Verify: A signer set validates the lock transaction
- Mint: Equivalent wrapped assets are minted on the destination chain
- Reverse: Burn wrapped assets to unlock originals on source chain
Bridge Architecture
Signer Set
The bridge is secured by a distributed signer set:
- Multi-signature validation: Multiple independent signers must approve transfers
- Geographic distribution: Signers located in different regions
- Diversity: Mix of validators, institutions, and community members
- Threshold signatures: Requires M-of-N signatures for security
- Regular rotation: Signer set updated periodically
Phase I uses a trusted signer set. Future phases will incorporate more decentralized security mechanisms like optimistic verification and zero-knowledge proofs.
Security Measures
Daily Caps
To limit risk exposure:
- Daily transfer limits: Maximum amount per 24-hour period
- Per-transaction limits: Maximum single transfer amount
- Dynamic adjustments: Caps may adjust based on network conditions
Example limits (subject to change via governance — check status for current caps):
Asset | Daily Cap | Per-Tx Limit |
---|---|---|
ETH | TBA | TBA |
USDC | TBA | TBA |
USDT | TBA | TBA |
If you hit a daily cap, wait until the 24-hour window resets. Track current usage on the bridge interface.
Circuit Breakers
Automatic safety mechanisms pause the bridge if suspicious activity is detected:
- Anomaly detection: Unusual transfer patterns trigger investigation
- Price oracle failures: Bridge pauses if price feeds become unreliable
- Signer threshold: Bridge pauses if too many signers are offline
- Manual override: Bridge operators can pause in emergencies
When triggered:
- Immediate pause: No new transfers initiated
- Investigation: Team investigates the trigger cause
- Communication: Users informed via status page and social media
- Resolution: Bridge resumes once safety confirmed
Pause and Unpause Rules
Bridge can be paused for:
- Security incidents or exploits
- Significant smart contract bugs discovered
- Signer set threshold not met
- Critical infrastructure failures
- Planned maintenance or upgrades
Unpause requirements:
- Issue resolved and verified
- Signer set quorum restored
- Multi-signature approval from governance
- Waiting period after announcement (typically 24-48 hours)
- Comprehensive post-mortem published
When the bridge is paused, in-flight transactions are not affected. Your funds remain secure in the bridge contracts and will be processed when the bridge resumes.
Supported Assets
Phase I Assets
Initial bridge support includes (subject to governance approval and security audits):
- ETH: Wrapped as wETH on Inception
- USDC: Major stablecoin
- USDT: Major stablecoin
- DAI: Decentralized stablecoin
For live endpoints, caps, and incident updates, always check the Inception Status page: https://inceptionera.com/status
All bridged assets are subject to governance approval and comprehensive security audits before being enabled.
Adding New Assets
Assets are added through governance proposals. Criteria include:
- Sufficient liquidity on both chains
- Established price feeds
- Community demand
- Security considerations
- Technical compatibility
Using the Bridge
Prerequisites
- Wallet with assets on source chain
- INCP for gas fees on Inception (for bridging to Inception)
- Native gas token on source chain (ETH for Ethereum, etc.)
Bridge Process (Source Chain → Inception)
- Connect Wallet: Visit the bridge interface at bridge.inceptionera.com (when live)
- Select Asset: Choose the asset to bridge
- Enter Amount: Specify how much to transfer
- Review Details:
- Amount to receive (after fees)
- Estimated time
- Gas fees
- Approve Token: Allow bridge contract to access your tokens
- Initiate Transfer: Submit the lock transaction
- Wait for Confirmations: Source chain requires finality
- Signer Verification: Signers validate the lock
- Receive Assets: Wrapped assets minted on Inception
Estimated time: 15-30 minutes depending on source chain finality
Bridge Process (Inception → Source Chain)
- Connect Wallet: Ensure connected to Inception network
- Select Asset: Choose wrapped asset to bridge back
- Enter Amount: Specify how much to unlock
- Review Details: Check fees and estimated time
- Initiate Burn: Burn wrapped assets on Inception
- Wait for Finality: Inception finality (~12.8 minutes)
- Signer Verification: Signers validate the burn
- Unlock Assets: Original assets released on source chain
Estimated time: 20-40 minutes depending on network conditions
Fees
Bridge fees cover operational costs and security:
- Bridge Fee: Small percentage (typically 0.1-0.3%)
- Gas Fees: Paid on both source and destination chains
- Signer Compensation: Portion allocated to signer set
- Protocol Treasury: Portion to Inception treasury
Fee distribution (example):
- 0.05% to signer set
- 0.05% to protocol treasury
- 0.1% total bridge fee
Fees may adjust based on network congestion and operational costs. Check current fees on the bridge interface.
Safety Guidelines
Before Bridging
- Verify URL: Ensure you're on the official bridge interface
- Check limits: Confirm your transfer is within daily and per-tx limits
- Test first: Bridge a small amount before large transfers
- Sufficient gas: Ensure you have gas tokens on both chains
- Understand fees: Account for bridge fees and gas costs
During Bridge
- Don't refresh: Let the process complete
- Save transaction hash: Record the source chain transaction
- Monitor status: Watch the bridge interface for updates
- Be patient: Transfers require multiple confirmations
After Bridge
- Verify receipt: Check your destination wallet received assets
- Add tokens: Add wrapped token to your wallet if needed
- Keep records: Save transaction hashes for both chains
- Fake bridge sites: Only use official URLs
- Discord/Telegram support scams: Never share private keys
- Too-good-to-be-true rates: Verify fees on official bridge only
- Urgent action requests: Legitimate bridge never requires urgency
Monitoring Bridge Health
Check bridge status before transferring:
- Status Page: inceptionera.com/status
- Bridge Interface: Real-time health indicators
- Signer Uptime: Number of active signers
- Daily Volumes: Current usage vs. daily caps
Troubleshooting
Transfer Stuck
If your transfer appears stuck:
- Check confirmations: Ensure source chain reached finality
- Verify signer quorum: Check sufficient signers are online
- Look for pause: Bridge may be temporarily paused
- Wait longer: Some transfers take 30+ minutes
- Contact support: If >1 hour with no progress
Transfer Failed
Reasons a transfer might fail:
- Insufficient gas: Transaction reverted due to low gas
- Daily cap reached: Transfer exceeds remaining daily limit
- Invalid amount: Below minimum or above maximum per-tx limit
- Unsupported asset: Asset not yet bridged by bridge
- Bridge paused: Security measure activated
Recovery: Failed transactions on source chain don't lose funds. The lock transaction will revert and funds remain in your wallet.
Wrong Network
If you sent to the wrong address or network:
- Cross-chain transfers are irreversible
- Ensure correct destination address and network before confirming
- Contact support immediately if error occurred, but recovery may not be possible
Bridge Contracts
Always verify bridge contract addresses from official documentation:
- Inception Documentation
- Status Page
- GitHub Repository (when available)
Never trust contract addresses from social media or unofficial sources.
Contract addresses will be published here once deployed.
Governance and Upgrades
Bridge parameters are controlled by governance:
- Signer set updates
- Fee adjustments
- Daily and per-tx limit changes
- Adding/removing supported assets
- Protocol upgrades
Upgrade process:
- Proposal submitted to governance
- Community discussion period
- Voting period (7 days)
- If approved: Timelock delay (7-14 days)
- Execution of changes
Future Phases
Phase II (Planned):
- Optimistic verification mechanism
- Increased decentralization
- Lower fees through efficiency gains
- Additional source chains
Phase III (Future):
- Zero-knowledge proof verification
- Fully trustless operation
- Expanded asset support
- Cross-chain DEX integration
Important Notes
- Bridged assets are wrapped representations, not native tokens
- Liquidity on Inception may differ from source chains
- Bridge downtime prevents new transfers (existing transfers complete)
- Always verify bridge health before large transfers
- Keep transaction records for support requests
Resources
- Bridge Interface: https://bridge.inceptionera.com (when live)
- Status Page: https://inceptionera.com/status
- Governance: Governance Portal
- Documentation: Inception Docs
- Support: Contact through main site
Security Audits
The bridge contracts will undergo comprehensive security audits before launch. Audit reports will be published at:
Need Help?
- Review this documentation thoroughly
- Check the Status Page
- Visit the FAQ section below
- Contact support through official channels only
FAQ
What happens if signers go offline?
The bridge requires an M-of-N threshold. If too many signers are offline, the bridge pauses automatically to prevent security risks. Transfers resume when quorum is restored.
Can I cancel a bridge transfer?
Once initiated, bridge transfers cannot be canceled. Ensure all details are correct before confirming.
How long do transfers take?
Typically 15-40 minutes depending on source chain finality and network conditions. The bridge interface shows estimated times.
Are bridge fees refundable?
Bridge fees are non-refundable as they compensate signers and cover operational costs.
What if I send the wrong amount?
The bridge will process whatever amount you sent, subject to minimum and maximum limits. Double-check amounts before confirming.
Can I bridge directly to another address?
Yes, most bridge interfaces allow specifying a different destination address. Ensure the destination address is correct and under your control.