Files

Deploy to Phoenix / deploy (push) Has been cancelled

Details

docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates

- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands
- CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround
- CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check
- NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere
- MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates
- LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-02-12 15:46:57 -08:00

41 KiB

Raw Blame History

Next Steps: Detailed Requirements & Information Needed

Date: 2026-01-26
Status: ✅ Complete requirements breakdown for all recommended integrations

1. Li.Fi Support Request

🔴 Priority: HIGH

⏱️ Estimated Timeline: 2-8 weeks (provider-dependent)

Contact Information

Primary Contact:

Email: support@li.fi
Discord: https://discord.gg/lifi
Contact Form: https://li.fi/contact
Website: https://li.fi/
GitHub: https://github.com/lifinance
Twitter: @lifiprotocol

Recommended Channel: Email or Discord (Discord may be faster for technical questions)

Required Network Information

Chain Metadata

{
  "chainId": 138,
  "chainName": "DeFi Oracle Meta Mainnet",
  "nativeCurrency": {
    "name": "Ether",
    "symbol": "ETH",
    "decimals": 18
  },
  "rpcUrls": [
    "https://rpc-http-pub.d-bis.org",
    "https://rpc-http-prv.d-bis.org"
  ],
  "blockExplorerUrls": [
    "https://explorer.d-bis.org"
  ],
  "chainlistUrl": "https://chainlist.org/chain/138",
  "networkType": "EVM-compatible",
  "consensus": "QBFT",
  "finality": "1 block"
}

Detailed Chain Information

Field	Value	Notes
Chain ID	`138` (0x8a)	Decimal and hex format
Network Name	DeFi Oracle Meta Mainnet	Official name
Network Type	EVM-compatible	Full EVM compatibility
Consensus	QBFT (Istanbul BFT)	1-block finality
Block Time	~2 seconds	Average block time
Native Currency	ETH	18 decimals
RPC Endpoint (Public)	`https://rpc-http-pub.d-bis.org`	Public access
RPC Endpoint (Permissioned)	`https://rpc-http-prv.d-bis.org`	Authorized access
WebSocket RPC	`wss://rpc-ws-pub.d-bis.org`	If available
Block Explorer	`https://explorer.d-bis.org`	Blockscout instance
ChainList Entry	`https://chainlist.org/chain/138`	Public registry

Token Information

Primary Tokens

Token	Address	Decimals	Status	Notes
WETH9	`0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2`	18	✅ Pre-deployed	Genesis allocation
WETH10	`0xf4BB2e28688e89fCcE3c0580D37d36A7672E8A9f`	18	✅ Pre-deployed	Genesis allocation
LINK	`0x514910771AF9Ca656af840dff83E8264EcF986CA`	18	✅ Deployed	Chainlink token
cUSDT	`0x93E66202A11B1772E55407B32B44e5Cd8eda7f22`	6	✅ Verified	Compliant USDT
cUSDC	`0xf22258f57794CC8E06237084b353Ab30fFfa640b`	6	✅ Verified	Compliant USDC

Status: ✅ VERIFIED - See TOKEN_ADDRESS_VERIFICATION_REPORT.md for details

Technical Requirements

Infrastructure Requirements

RPC Endpoints
- ✅ Public RPC: https://rpc-http-pub.d-bis.org
- ✅ Permissioned RPC: https://rpc-http-prv.d-bis.org
- ⚠️ WebSocket RPC: Verify availability
- Status: RPCs are operational and accessible
Network Stability
- ✅ Network uptime: [Provide percentage]
- ✅ Average block time: ~2 seconds
- ✅ Finality: 1 block (QBFT)
- Status: Network is stable and operational
Multicall Contract
- ✅ Address: 0x99b3511a2d315a497c8112c1fdd8d3606eB48
- ✅ Status: Pre-deployed
- Note: Multicall is available for batch calls
Token List
- ⚠️ Action Required: Create and host token list JSON
- Recommended Format: Token Lists standard (ERC-20)
- Hosting: GitHub or IPFS
- URL: [To be created]

Use Case Information

Primary Use Cases:

Cross-Chain Payment Routing
- Accept payments on public chains (Ethereum, Base, Arbitrum)
- Route to ChainID 138 for settlement
- Enable merchant withdrawals back to public chains
Token Swap Aggregation
- Multi-chain token swaps
- Optimal route discovery
- Gas optimization
Multi-Chain Payment Acceptance
- Accept payments from any Li.Fi-supported chain
- Automatic routing to ChainID 138
- Settlement in CompliantUSDC

Expected Volume:

Daily Transactions: [Provide estimate]
Monthly Volume: [Provide estimate]
Token Types: ETH, WETH, USDC, USDT

Integration Requirements

What Li.Fi Needs

Chain Metadata Configuration
- RPC URLs
- Explorer URLs
- Native currency info
- Block time and finality
Token List Integration
- Standard token list format
- Token addresses and metadata
- Logo URLs (optional but recommended)
Bridge/Exchange Integrations
- Existing bridge contracts (CCIP)
- DEX contracts (if available)
- Liquidity information
Multicall Contract
- ✅ Available at 0x99b3511a2d315a497c8112c1fdd8d3606eB48

Documentation to Prepare

Network Documentation
- Chain specification document
- RPC endpoint documentation
- Explorer documentation
Token Documentation
- Token contract addresses
- Token metadata (name, symbol, decimals)
- Token logos (if available)
Bridge Documentation
- CCIP bridge documentation
- Bridge contract addresses
- Supported tokens list
Business Information
- Organization name
- Contact information
- Expected transaction volume
- Use case description

Request Template

Email Subject: LiFi Support Request for ChainID 138 (DeFi Oracle Meta Mainnet)

Email Body Template:

Dear LiFi Team,

We are requesting LiFi (Li.Fi Pay) support for ChainID 138, an EVM-compatible blockchain network.

Chain Information:
- Chain Name: DeFi Oracle Meta Mainnet
- Chain ID: 138 (0x8a)
- Network Type: EVM-compatible
- Consensus: QBFT (1-block finality)
- Block Time: ~2 seconds
- Native Currency: ETH (18 decimals)

RPC Endpoints:
- Public: https://rpc-http-pub.d-bis.org
- Permissioned: https://rpc-http-prv.d-bis.org

Block Explorer:
- URL: https://explorer.d-bis.org
- Type: Blockscout

ChainList Entry:
- https://chainlist.org/chain/138

Token Information:
- WETH9: 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2 (18 decimals)
- WETH10: 0xf4BB2e28688e89fCcE3c0580D37d36A7672E8A9f (18 decimals)
- LINK: 0x514910771AF9Ca656af840dff83E8264EcF986CA (18 decimals)
- Token List: [URL to be provided]

Infrastructure:
- Multicall Contract: 0x99b3511a2d315a497c8112c1fdd8d3606eB48
- Network Status: Stable and operational
- Uptime: [Provide percentage]

Use Case:
We are building a cross-chain payment routing and settlement system that requires optimal cross-chain routing. LiFi integration would enable:
- Cross-chain payment routing from public chains to ChainID 138
- Token swap aggregation across multiple chains
- Multi-chain payment acceptance
- Optimal route discovery for cost efficiency

Expected Volume:
- Daily Transactions: [Your estimate]
- Monthly Volume: [Your estimate]
- Primary Tokens: ETH, WETH, USDC, USDT

Integration Requirements:
- Chain metadata configuration
- Token list integration
- Bridge/exchange integrations (we have CCIP bridge deployed)
- Multicall contract (available)

Additional Information:
- ChainID 138 is a production mainnet network
- Network is stable and operational
- We have CCIP bridge deployed for cross-chain transfers
- We can provide additional technical details as needed

We would appreciate any guidance on the process and timeline for LiFi support addition.

Thank you for your consideration.

Best regards,
[Your Name]
[Your Organization]
[Contact Information]

Prerequisites Checklist

Before submitting request:

Network Information Compiled
- Chain ID verified (138)
- RPC endpoints tested and accessible
- Block explorer URL verified
- ChainList entry verified
Token Information Prepared
- WETH9 address verified
- WETH10 address verified
- LINK address verified
cUSDT address verified: 0x93E66202A11B1772E55407B32B44e5Cd8eda7f22 ✅
cUSDC address verified: 0xf22258f57794CC8E06237084b353Ab30fFfa640b ✅
- Token list JSON created (if possible)
Infrastructure Verified
- RPC endpoints accessible
- Multicall contract address verified
- Network stability confirmed
- Block time measured
Documentation Prepared
- Use case description written
- Expected volume estimated
- Business information prepared
- Contact information ready
Follow-up Plan
- Reminder set for 2 weeks
- Monitoring script configured
- Update plan for when support is added

Follow-up Actions

After Submission:

Immediate (Day 1)
- Save confirmation of request submission
- Set reminder for 2-week follow-up
- Configure automated support checker
Week 2
- Follow up if no response
- Check Li.Fi API for updates
- Monitor Discord for announcements
Ongoing
- Run daily support checker script
- Monitor Li.Fi API: https://li.quest/v1/chains
- Check for ChainID 138 in response
When Support is Added
- Update alltra-lifi-settlement/src/config/chains.ts
- Set lifiSupported: true for ChainID 138
- Test Li.Fi routing
- Update documentation
- Notify team

Automated Monitoring

Script Location: alltra-lifi-settlement/scripts/scheduled-support-check.ts

Setup:

cd alltra-lifi-settlement

# Test script
ts-node scripts/scheduled-support-check.ts

# Set up daily cron job
crontab -e
# Add: 0 0 * * * cd /path/to/alltra-lifi-settlement && ts-node scripts/scheduled-support-check.ts --notify

2. LayerZero Integration

🔴 Priority: HIGH

⏱️ Estimated Timeline: 4-12 weeks

Contact Information

Primary Contact:

Website: https://layerzero.network
Documentation: https://docs.layerzero.network
Discord: https://discord.gg/layerzero
Twitter: @LayerZero_Labs
GitHub: https://github.com/LayerZero-Labs

Recommended Channel: Discord for technical questions, website contact form for partnership inquiries

Required Network Information

Chain Metadata

{
  "chainId": 138,
  "chainName": "DeFi Oracle Meta Mainnet",
  "networkType": "EVM",
  "rpcUrls": [
    "https://rpc-http-pub.d-bis.org",
    "https://rpc-http-prv.d-bis.org"
  ],
  "blockExplorerUrls": [
    "https://explorer.d-bis.org"
  ],
  "nativeCurrency": {
    "name": "Ether",
    "symbol": "ETH",
    "decimals": 18
  }
}

Detailed Information Needed

Field	Value	Notes
Chain ID	`138`	Decimal format
Network Name	DeFi Oracle Meta Mainnet	Official name
Network Type	EVM	Full EVM compatibility
RPC Endpoint	`https://rpc-http-pub.d-bis.org`	Public RPC
Block Explorer	`https://explorer.d-bis.org`	Blockscout
Block Time	~2 seconds	Average
Finality	1 block	QBFT consensus
Gas Token	ETH	Native currency

Technical Requirements

Infrastructure Requirements

RPC Endpoints
- ✅ Public RPC: https://rpc-http-pub.d-bis.org
- ✅ Permissioned RPC: https://rpc-http-prv.d-bis.org
- Status: Operational
Network Stability
- ✅ Network operational
- ✅ Block time: ~2 seconds
- ✅ Finality: 1 block
- Uptime: [Provide percentage]
Contract Deployment
- ⚠️ Action Required: Deploy LayerZero contracts
- Endpoint Contract: Required
- Ultra Light Node (ULN): Required
- Estimated Gas: [To be calculated]

Integration Requirements

What LayerZero Needs

Chain Information
- Chain ID
- RPC endpoints
- Block explorer
- Network parameters
Contract Deployment
- LayerZero Endpoint contract
- Ultra Light Node (ULN) configuration
- Relayer configuration
Token Support
- Token contract addresses
- Token metadata
- Liquidity information
Security Audit
- ⚠️ May be required for production
- Contract audit
- Network security review

Deployment Requirements

Contracts to Deploy

LayerZero Endpoint
- Purpose: Main entry point for cross-chain messages
- Deployment: Required on ChainID 138
- Configuration: Connect to LayerZero network
Ultra Light Node (ULN)
- Purpose: Light client for message verification
- Deployment: Required
- Configuration: Configure for ChainID 138
Token Contracts
- Purpose: Token contracts for bridging
- Status: Already deployed (WETH9, WETH10)
- Action: Configure for LayerZero

Documentation to Prepare

Network Documentation
- Chain specification
- RPC documentation
- Explorer documentation
Security Documentation
- Network security measures
- Validator information
- Consensus mechanism details
Business Information
- Organization details
- Expected volume
- Use case description

Request Template

Contact Form/Email Subject: LayerZero Integration Request for ChainID 138

Message Template:

Hello LayerZero Team,

We are requesting LayerZero integration for ChainID 138 (DeFi Oracle Meta Mainnet), an EVM-compatible blockchain network.

Chain Information:
- Chain ID: 138
- Network Name: DeFi Oracle Meta Mainnet
- Network Type: EVM-compatible
- RPC Endpoint: https://rpc-http-pub.d-bis.org
- Block Explorer: https://explorer.d-bis.org
- Block Time: ~2 seconds
- Finality: 1 block (QBFT consensus)
- Native Currency: ETH (18 decimals)

Use Case:
We are building a cross-chain payment and settlement system that requires secure cross-chain messaging and token transfers. LayerZero integration would enable:
- Cross-chain payment routing
- Secure token bridging
- Cross-chain messaging
- Multi-chain dApp functionality

Expected Volume:
- Daily Transactions: [Your estimate]
- Monthly Volume: [Your estimate]

Integration Requirements:
- LayerZero Endpoint deployment
- Ultra Light Node (ULN) configuration
- Token contract integration
- Relayer configuration

We are ready to deploy LayerZero contracts and configure the network. We would appreciate guidance on the integration process and timeline.

Thank you for your consideration.

Best regards,
[Your Name]
[Your Organization]
[Contact Information]

Prerequisites Checklist

Network Information
- Chain ID verified
- RPC endpoints tested
- Block explorer verified
- Network parameters documented
Technical Readiness
- Deployment team ready
- Gas estimation completed
- Security review planned
- Testing environment prepared
Business Information
- Use case documented
- Expected volume estimated
- Contact information ready

3. Wormhole Integration

🔴 Priority: HIGH

⏱️ Estimated Timeline: 6-16 weeks

Contact Information

Primary Contact:

Website: https://wormhole.com
Documentation: https://docs.wormhole.com
Discord: https://discord.gg/wormhole
Twitter: @wormholecrypto
GitHub: https://github.com/wormhole-foundation

Recommended Channel: Discord for technical questions, website for partnership inquiries

Required Network Information

Chain Metadata

{
  "chainId": 138,
  "chainName": "DeFi Oracle Meta Mainnet",
  "networkType": "EVM",
  "rpcUrls": [
    "https://rpc-http-pub.d-bis.org",
    "https://rpc-http-prv.d-bis.org"
  ],
  "blockExplorerUrls": [
    "https://explorer.d-bis.org"
  ],
  "nativeCurrency": {
    "name": "Ether",
    "symbol": "ETH",
    "decimals": 18
  },
  "consensus": "QBFT",
  "finality": "1 block"
}

Technical Requirements

Infrastructure Requirements

RPC Endpoints
- ✅ Public RPC: https://rpc-http-pub.d-bis.org
- ✅ Permissioned RPC: https://rpc-http-prv.d-bis.org
- Status: Operational
Network Stability
- ✅ Network operational
- ✅ Block time: ~2 seconds
- ✅ Finality: 1 block
Guardian Network
- ⚠️ Action Required: Join Wormhole Guardian network
- Requirements: Validator nodes
- Security: High security requirements

Integration Requirements

What Wormhole Needs

Chain Information
- Chain ID
- RPC endpoints
- Block explorer
- Network parameters
Guardian Network Participation
- Validator nodes
- Security requirements
- Network configuration
Contract Deployment
- Wormhole Core contract
- Token Bridge contract
- NFT Bridge contract (if needed)
Security Audit
- ⚠️ Required for production
- Contract audit
- Network security review

Deployment Requirements

Contracts to Deploy

Wormhole Core
- Purpose: Core messaging contract
- Deployment: Required
- Configuration: Connect to Guardian network
Token Bridge
- Purpose: Token bridging functionality
- Deployment: Required
- Configuration: Configure for supported tokens
NFT Bridge (Optional)
- Purpose: NFT bridging
- Deployment: Optional
- Configuration: If NFT support needed

Documentation to Prepare

Network Documentation
- Chain specification
- RPC documentation
- Security documentation
Security Documentation
- Validator information
- Network security measures
- Consensus mechanism
Business Information
- Organization details
- Expected volume
- Use case description

Request Template

Contact/Email Subject: Wormhole Integration Request for ChainID 138

Message Template:

Hello Wormhole Team,

We are requesting Wormhole integration for ChainID 138 (DeFi Oracle Meta Mainnet), an EVM-compatible blockchain network.

Chain Information:
- Chain ID: 138
- Network Name: DeFi Oracle Meta Mainnet
- Network Type: EVM-compatible
- RPC Endpoint: https://rpc-http-pub.d-bis.org
- Block Explorer: https://explorer.d-bis.org
- Consensus: QBFT (1-block finality)
- Block Time: ~2 seconds
- Native Currency: ETH (18 decimals)

Use Case:
We are building a cross-chain payment and settlement system that requires secure, audited cross-chain bridging. Wormhole integration would enable:
- Secure token bridging across 30+ chains
- Cross-chain messaging
- Multi-chain dApp functionality
- Trusted bridge infrastructure

Expected Volume:
- Daily Transactions: [Your estimate]
- Monthly Volume: [Your estimate]

Integration Requirements:
- Wormhole Core contract deployment
- Token Bridge contract deployment
- Guardian network participation (if applicable)
- Security audit coordination

We are ready to deploy Wormhole contracts and configure the network. We would appreciate guidance on the integration process, Guardian network requirements, and timeline.

Thank you for your consideration.

Best regards,
[Your Name]
[Your Organization]
[Contact Information]

Prerequisites Checklist

Network Information
- Chain ID verified
- RPC endpoints tested
- Network parameters documented
Technical Readiness
- Deployment team ready
- Security audit planned
- Guardian network requirements reviewed
- Testing environment prepared
Business Information
- Use case documented
- Expected volume estimated
- Contact information ready

4. Uniswap Integration

🔴 Priority: HIGH

⏱️ Estimated Timeline: 8-20 weeks

Contact Information

Primary Contact:

Website: https://uniswap.org
Documentation: https://docs.uniswap.org
Discord: https://discord.gg/uniswap
Twitter: @Uniswap
GitHub: https://github.com/Uniswap

Recommended Channel: Discord for technical questions, website for partnership inquiries

Required Network Information

Chain Metadata

{
  "chainId": 138,
  "chainName": "DeFi Oracle Meta Mainnet",
  "networkType": "EVM",
  "rpcUrls": [
    "https://rpc-http-pub.d-bis.org",
    "https://rpc-http-prv.d-bis.org"
  ],
  "blockExplorerUrls": [
    "https://explorer.d-bis.org"
  ],
  "nativeCurrency": {
    "name": "Ether",
    "symbol": "ETH",
    "decimals": 18
  }
}

Technical Requirements

Infrastructure Requirements

RPC Endpoints
- ✅ Public RPC: https://rpc-http-pub.d-bis.org
- ✅ Permissioned RPC: https://rpc-http-prv.d-bis.org
- Status: Operational
Liquidity Requirements
- ⚠️ Action Required: Provide liquidity for trading pairs
- Minimum Liquidity: [Uniswap requirements]
- Initial Pairs: ETH/USDC, ETH/USDT, USDC/USDT
Contract Deployment
- ⚠️ Action Required: Deploy Uniswap V3 contracts
- Factory Contract: Required
- Router Contract: Required
- NFT Position Manager: Required (for V3)

Integration Requirements

What Uniswap Needs

Chain Information
- Chain ID
- RPC endpoints
- Block explorer
- Network parameters
Liquidity Commitment
- Initial liquidity amounts
- Trading pairs
- Liquidity provider incentives
Contract Deployment
- Uniswap V3 Factory
- Uniswap V3 Router
- NFT Position Manager
- Quoter Contract
Token Support
- Token contract addresses
- Token metadata
- Token logos

Deployment Requirements

Contracts to Deploy

Uniswap V3 Factory
- Purpose: Create and manage pools
- Deployment: Required
- Configuration: Set fee tiers
Uniswap V3 Router
- Purpose: Execute swaps
- Deployment: Required
- Configuration: Connect to factory
NFT Position Manager
- Purpose: Manage liquidity positions
- Deployment: Required
- Configuration: Connect to factory
Quoter Contract
- Purpose: Price quotes
- Deployment: Required
- Configuration: Connect to factory

Liquidity Requirements

Initial Liquidity Pools

Pair	Minimum Liquidity	Recommended	Fee Tier
ETH/USDC	[TBD]	$100,000+	0.05%
ETH/USDT	[TBD]	$100,000+	0.05%
USDC/USDT	[TBD]	$50,000+	0.01%

Action Required: Determine liquidity amounts and funding sources

Documentation to Prepare

Network Documentation
- Chain specification
- RPC documentation
- Explorer documentation
Liquidity Plan
- Initial liquidity amounts
- Liquidity provider incentives
- Trading pair strategy
Business Information
- Organization details
- Expected trading volume
- Use case description

Request Template

Contact/Email Subject: Uniswap Integration Request for ChainID 138

Message Template:

Hello Uniswap Team,

We are requesting Uniswap V3 integration for ChainID 138 (DeFi Oracle Meta Mainnet), an EVM-compatible blockchain network.

Chain Information:
- Chain ID: 138
- Network Name: DeFi Oracle Meta Mainnet
- Network Type: EVM-compatible
- RPC Endpoint: https://rpc-http-pub.d-bis.org
- Block Explorer: https://explorer.d-bis.org
- Block Time: ~2 seconds
- Native Currency: ETH (18 decimals)

Token Information:
- WETH9: 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2
- USDC: [Address to be provided]
- USDT: [Address to be provided]

Liquidity Commitment:
- Initial Liquidity: [Your commitment]
- Trading Pairs: ETH/USDC, ETH/USDT, USDC/USDT
- Liquidity Provider Incentives: [Your plan]

Use Case:
We are building a DeFi ecosystem on ChainID 138 that requires a high-quality DEX for token swaps. Uniswap integration would enable:
- Token swaps for users
- Liquidity provision
- DeFi ecosystem growth
- Integration with payment systems

Expected Volume:
- Daily Trading Volume: [Your estimate]
- Monthly Trading Volume: [Your estimate]

Integration Requirements:
- Uniswap V3 Factory deployment
- Uniswap V3 Router deployment
- NFT Position Manager deployment
- Initial liquidity provision

We are ready to deploy Uniswap contracts and provide initial liquidity. We would appreciate guidance on the integration process and requirements.

Thank you for your consideration.

Best regards,
[Your Name]
[Your Organization]
[Contact Information]

Prerequisites Checklist

Network Information
- Chain ID verified
- RPC endpoints tested
- Network parameters documented
Liquidity Planning
- Initial liquidity amounts determined
- Funding sources identified
- Liquidity provider incentives planned
Technical Readiness
- Deployment team ready
- Contract deployment plan prepared
- Testing environment prepared
Business Information
- Use case documented
- Expected volume estimated
- Contact information ready

5. 1inch Integration

🔴 Priority: HIGH

⏱️ Estimated Timeline: 4-12 weeks

Contact Information

Primary Contact:

Website: https://1inch.io
Documentation: https://docs.1inch.io
Discord: https://discord.gg/1inch
Twitter: @1inch
GitHub: https://github.com/1inch

Recommended Channel: Discord for technical questions, website for partnership inquiries

Required Network Information

Chain Metadata

{
  "chainId": 138,
  "chainName": "DeFi Oracle Meta Mainnet",
  "networkType": "EVM",
  "rpcUrls": [
    "https://rpc-http-pub.d-bis.org",
    "https://rpc-http-prv.d-bis.org"
  ],
  "blockExplorerUrls": [
    "https://explorer.d-bis.org"
  ],
  "nativeCurrency": {
    "name": "Ether",
    "symbol": "ETH",
    "decimals": 18
  }
}

Technical Requirements

Infrastructure Requirements

RPC Endpoints
- ✅ Public RPC: https://rpc-http-pub.d-bis.org
- ✅ Permissioned RPC: https://rpc-http-prv.d-bis.org
- Status: Operational
DEX Integration
- ⚠️ Action Required: Integrate with existing DEXs
- Requirement: At least one DEX must be available
- Options: Uniswap (if integrated), custom DEX
API Integration
- ⚠️ Action Required: Integrate 1inch API
- API Key: Required for production
- Rate Limits: [1inch requirements]

Integration Requirements

What 1inch Needs

Chain Information
- Chain ID
- RPC endpoints
- Block explorer
- Network parameters
DEX Information
- Available DEXs on ChainID 138
- DEX contract addresses
- Liquidity information
Token Information
- Token contract addresses
- Token metadata
- Token logos

Documentation to Prepare

Network Documentation
- Chain specification
- RPC documentation
- Explorer documentation
DEX Documentation
- Available DEXs
- DEX contract addresses
- Liquidity information
Business Information
- Organization details
- Expected volume
- Use case description

Request Template

Contact/Email Subject: 1inch Integration Request for ChainID 138

Message Template:

Hello 1inch Team,

We are requesting 1inch integration for ChainID 138 (DeFi Oracle Meta Mainnet), an EVM-compatible blockchain network.

Chain Information:
- Chain ID: 138
- Network Name: DeFi Oracle Meta Mainnet
- Network Type: EVM-compatible
- RPC Endpoint: https://rpc-http-pub.d-bis.org
- Block Explorer: https://explorer.d-bis.org
- Block Time: ~2 seconds
- Native Currency: ETH (18 decimals)

DEX Information:
- Available DEXs: [List available DEXs]
- DEX Contract Addresses: [Provide addresses]
- Liquidity: [Provide liquidity information]

Token Information:
- WETH9: 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2
- cUSDC: 0xf22258f57794CC8E06237084b353Ab30fFfa640b (6 decimals)
- cUSDT: 0x93E66202A11B1772E55407B32B44e5Cd8eda7f22 (6 decimals)

Use Case:
We are building a DeFi ecosystem on ChainID 138 that requires optimal token swap routing. 1inch integration would enable:
- Best price routing across DEXs
- Gas optimization
- Multi-hop swaps
- Aggregated liquidity

Expected Volume:
- Daily Swap Volume: [Your estimate]
- Monthly Swap Volume: [Your estimate]

Integration Requirements:
- 1inch API integration
- DEX integration
- Token list integration

We are ready to integrate 1inch and provide necessary information. We would appreciate guidance on the integration process and requirements.

Thank you for your consideration.

Best regards,
[Your Name]
[Your Organization]
[Contact Information]

Prerequisites Checklist

Network Information
- Chain ID verified
- RPC endpoints tested
- Network parameters documented
DEX Information
- Available DEXs identified
- DEX contract addresses documented
- Liquidity information prepared
Technical Readiness
- API integration plan prepared
- Testing environment prepared
Business Information
- Use case documented
- Expected volume estimated
- Contact information ready

6. MoonPay Integration

🔴 Priority: HIGH

⏱️ Estimated Timeline: 4-8 weeks

Contact Information

Primary Contact:

Website: https://www.moonpay.com/business
Documentation: https://developers.moonpay.com
Support: support@moonpay.com
Sales: sales@moonpay.com

Recommended Channel: Business contact form or sales email for partnership inquiries

Required Network Information

Chain Metadata

{
  "chainId": 138,
  "chainName": "DeFi Oracle Meta Mainnet",
  "networkType": "EVM",
  "rpcUrls": [
    "https://rpc-http-pub.d-bis.org",
    "https://rpc-http-prv.d-bis.org"
  ],
  "blockExplorerUrls": [
    "https://explorer.d-bis.org"
  ],
  "nativeCurrency": {
    "name": "Ether",
    "symbol": "ETH",
    "decimals": 18
  }
}

Technical Requirements

Infrastructure Requirements

RPC Endpoints
- ✅ Public RPC: https://rpc-http-pub.d-bis.org
- ✅ Permissioned RPC: https://rpc-http-prv.d-bis.org
- Status: Operational
API Integration
- ⚠️ Action Required: Integrate MoonPay API
- API Key: Required (provided after partnership)
- Webhook URL: Required for transaction notifications
Compliance Requirements
- ⚠️ Action Required: KYC/AML compliance
- Requirements: Varies by jurisdiction
- Documentation: Business registration, compliance certificates

Integration Requirements

What MoonPay Needs

Chain Information
- Chain ID
- RPC endpoints
- Block explorer
- Network parameters
Token Information
- Token contract addresses
- Token metadata
- Token logos
Business Information
- Company registration
- Business license
- Compliance documentation
- Expected transaction volume
Technical Integration
- API integration
- Webhook configuration
- Widget integration

Documentation to Prepare

Network Documentation
- Chain specification
- RPC documentation
- Explorer documentation
Business Documentation
- Company registration
- Business license
- Compliance certificates
- Tax identification
Technical Documentation
- Integration plan
- API requirements
- Webhook specifications

Request Template

Contact/Email Subject: MoonPay Integration Request for ChainID 138

Message Template:

Hello MoonPay Team,

We are requesting MoonPay integration for ChainID 138 (DeFi Oracle Meta Mainnet), an EVM-compatible blockchain network.

Chain Information:
- Chain ID: 138
- Network Name: DeFi Oracle Meta Mainnet
- Network Type: EVM-compatible
- RPC Endpoint: https://rpc-http-pub.d-bis.org
- Block Explorer: https://explorer.d-bis.org
- Native Currency: ETH (18 decimals)

Token Information:
- ETH: Native currency
- WETH9: 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2
- cUSDC: 0xf22258f57794CC8E06237084b353Ab30fFfa640b (6 decimals)
- cUSDT: 0x93E66202A11B1772E55407B32B44e5Cd8eda7f22 (6 decimals)

Business Information:
- Company Name: [Your Company]
- Registration Number: [Your Registration]
- Business License: [Your License]
- Compliance: [Your Compliance Status]

Use Case:
We are building a payment and settlement system on ChainID 138 that requires fiat on-ramp functionality. MoonPay integration would enable:
- Fiat to crypto purchases
- Credit card payments
- Bank transfer support
- Global payment methods

Expected Volume:
- Daily Transactions: [Your estimate]
- Monthly Volume: [Your estimate]
- Average Transaction Size: [Your estimate]

Integration Requirements:
- MoonPay API integration
- Widget integration
- Webhook configuration
- Compliance verification

We are ready to integrate MoonPay and provide all necessary documentation. We would appreciate guidance on the integration process and requirements.

Thank you for your consideration.

Best regards,
[Your Name]
[Your Organization]
[Contact Information]

Prerequisites Checklist

Network Information
- Chain ID verified
- RPC endpoints tested
- Network parameters documented
Business Documentation
- Company registration
- Business license
- Compliance certificates
- Tax identification
Technical Readiness
- API integration plan prepared
- Webhook endpoint prepared
- Testing environment prepared
Business Information
- Use case documented
- Expected volume estimated
- Contact information ready

7. Ramp Network Integration

🔴 Priority: HIGH

⏱️ Estimated Timeline: 4-8 weeks

Contact Information

Primary Contact:

Website: https://ramp.network
Documentation: https://docs.ramp.network
Support: support@ramp.network
Sales: sales@ramp.network

Recommended Channel: Business contact form or sales email for partnership inquiries

Required Network Information

Chain Metadata

{
  "chainId": 138,
  "chainName": "DeFi Oracle Meta Mainnet",
  "networkType": "EVM",
  "rpcUrls": [
    "https://rpc-http-pub.d-bis.org",
    "https://rpc-http-prv.d-bis.org"
  ],
  "blockExplorerUrls": [
    "https://explorer.d-bis.org"
  ],
  "nativeCurrency": {
    "name": "Ether",
    "symbol": "ETH",
    "decimals": 18
  }
}

Technical Requirements

Infrastructure Requirements

RPC Endpoints
- ✅ Public RPC: https://rpc-http-pub.d-bis.org
- ✅ Permissioned RPC: https://rpc-http-prv.d-bis.org
- Status: Operational
API Integration
- ⚠️ Action Required: Integrate Ramp API
- API Key: Required (provided after partnership)
- Webhook URL: Required for transaction notifications
Compliance Requirements
- ⚠️ Action Required: KYC/AML compliance
- Requirements: Varies by jurisdiction
- Documentation: Business registration, compliance certificates

Integration Requirements

What Ramp Needs

Chain Information
- Chain ID
- RPC endpoints
- Block explorer
- Network parameters
Token Information
- Token contract addresses
- Token metadata
- Token logos
Business Information
- Company registration
- Business license
- Compliance documentation
- Expected transaction volume
Technical Integration
- API integration
- Webhook configuration
- Widget integration

Documentation to Prepare

Network Documentation
- Chain specification
- RPC documentation
- Explorer documentation
Business Documentation
- Company registration
- Business license
- Compliance certificates
- Tax identification
Technical Documentation
- Integration plan
- API requirements
- Webhook specifications

Request Template

Contact/Email Subject: Ramp Network Integration Request for ChainID 138

Message Template:

Hello Ramp Network Team,

We are requesting Ramp Network integration for ChainID 138 (DeFi Oracle Meta Mainnet), an EVM-compatible blockchain network.

Chain Information:
- Chain ID: 138
- Network Name: DeFi Oracle Meta Mainnet
- Network Type: EVM-compatible
- RPC Endpoint: https://rpc-http-pub.d-bis.org
- Block Explorer: https://explorer.d-bis.org
- Native Currency: ETH (18 decimals)

Token Information:
- ETH: Native currency
- WETH9: 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2
- cUSDC: 0xf22258f57794CC8E06237084b353Ab30fFfa640b (6 decimals)
- cUSDT: 0x93E66202A11B1772E55407B32B44e5Cd8eda7f22 (6 decimals)

Business Information:
- Company Name: [Your Company]
- Registration Number: [Your Registration]
- Business License: [Your License]
- Compliance: [Your Compliance Status]

Use Case:
We are building a payment and settlement system on ChainID 138 that requires fiat on-ramp functionality. Ramp Network integration would enable:
- Fiat to crypto purchases
- Fast KYC process
- Competitive fees
- European market focus

Expected Volume:
- Daily Transactions: [Your estimate]
- Monthly Volume: [Your estimate]
- Average Transaction Size: [Your estimate]

Integration Requirements:
- Ramp API integration
- Widget integration
- Webhook configuration
- Compliance verification

We are ready to integrate Ramp Network and provide all necessary documentation. We would appreciate guidance on the integration process and requirements.

Thank you for your consideration.

Best regards,
[Your Name]
[Your Organization]
[Contact Information]

Prerequisites Checklist

Network Information
- Chain ID verified
- RPC endpoints tested
- Network parameters documented
Business Documentation
- Company registration
- Business license
- Compliance certificates
- Tax identification
Technical Readiness
- API integration plan prepared
- Webhook endpoint prepared
- Testing environment prepared
Business Information
- Use case documented
- Expected volume estimated
- Contact information ready

📊 Summary: Information Needed for All Integrations

Common Requirements Across All Integrations

1. Network Information (Required for All)

✅ Chain ID: 138
✅ Network Name: DeFi Oracle Meta Mainnet
✅ RPC Endpoints: https://rpc-http-pub.d-bis.org, https://rpc-http-prv.d-bis.org
✅ Block Explorer: https://explorer.d-bis.org
✅ Native Currency: ETH (18 decimals)
✅ Network Type: EVM-compatible
✅ Block Time: ~2 seconds
✅ Finality: 1 block (QBFT)

2. Token Information (Required for Most)

✅ WETH9: 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2
✅ WETH10: 0xf4BB2e28688e89fCcE3c0580D37d36A7672E8A9f
✅ LINK: 0x514910771AF9Ca656af840dff83E8264EcF986CA
✅ cUSDT: 0x93E66202A11B1772E55407B32B44e5Cd8eda7f22 (6 decimals) - Verified
✅ cUSDC: 0xf22258f57794CC8E06237084b353Ab30fFfa640b (6 decimals) - Verified

3. Business Information (Required for On-Ramps)

⚠️ Company registration
⚠️ Business license
⚠️ Compliance certificates
⚠️ Tax identification
⚠️ Expected transaction volume

4. Technical Readiness (Required for All)

✅ RPC endpoints operational
✅ Network stable
⚠️ Deployment team ready
⚠️ Testing environment prepared
⚠️ Security audit planned (for bridges)

🎯 Action Items Summary

Immediate Actions (This Week)

Verify Token Addresses

Verify cUSDT address on ChainID 138 ✅ 0x93E66202A11B1772E55407B32B44e5Cd8eda7f22
Verify cUSDC address on ChainID 138 ✅ 0xf22258f57794CC8E06237084b353Ab30fFfa640b
- Document all token addresses

Prepare Network Documentation
- Create network specification document
- Document RPC endpoints
- Document block explorer
Prepare Business Information
- Gather company registration documents
- Prepare business license copies
- Estimate transaction volumes

Short-Term Actions (Next 2 Weeks)

Submit Integration Requests
- Submit Li.Fi support request
- Submit LayerZero integration request
- Submit Wormhole integration request
- Submit Uniswap integration request
- Submit 1inch integration request
- Submit MoonPay integration request
- Submit Ramp Network integration request
Set Up Monitoring
- Configure Li.Fi support checker
- Set up daily monitoring scripts
- Configure alerts

Medium-Term Actions (Next Month)

Prepare for Deployments
- Prepare deployment environments
- Plan security audits
- Prepare liquidity (for DEXs)
Follow Up on Requests
- Follow up on submitted requests
- Respond to provider questions
- Provide additional information as needed

📝 Notes

All templates are ready to use - Fill in [Your estimate] and [Your information] placeholders
Contact information is current - Verify before submission
Timeline estimates are approximate - Actual timelines depend on provider response
Prerequisites should be completed - Before submitting requests
Follow-up is important - Set reminders for 2-week follow-ups

Last Updated: 2026-01-26
Status: ✅ Complete requirements documentation for all recommended next steps

41 KiB Raw Blame History

Next Steps: Detailed Requirements & Information Needed

📋 Table of Contents

1. Li.Fi Support Request

🔴 Priority: HIGH

⏱️ Estimated Timeline: 2-8 weeks (provider-dependent)

Contact Information

Required Network Information

Chain Metadata

Detailed Chain Information

Token Information

Primary Tokens

Technical Requirements

Infrastructure Requirements

Use Case Information

Integration Requirements

What Li.Fi Needs

Documentation to Prepare

Request Template

Prerequisites Checklist

Follow-up Actions

Automated Monitoring

2. LayerZero Integration

🔴 Priority: HIGH

⏱️ Estimated Timeline: 4-12 weeks

Contact Information

Required Network Information

Chain Metadata

Detailed Information Needed

Technical Requirements

Infrastructure Requirements

Integration Requirements

What LayerZero Needs

Deployment Requirements

Contracts to Deploy

Documentation to Prepare

Request Template

Prerequisites Checklist

3. Wormhole Integration

🔴 Priority: HIGH

⏱️ Estimated Timeline: 6-16 weeks

Contact Information

Required Network Information

Chain Metadata

Technical Requirements

Infrastructure Requirements

Integration Requirements

What Wormhole Needs

Deployment Requirements

Contracts to Deploy

Documentation to Prepare

Request Template

Prerequisites Checklist

4. Uniswap Integration

🔴 Priority: HIGH

⏱️ Estimated Timeline: 8-20 weeks

Contact Information

Required Network Information

Chain Metadata

Technical Requirements

Infrastructure Requirements

Integration Requirements

What Uniswap Needs

Deployment Requirements

Contracts to Deploy

Liquidity Requirements

Initial Liquidity Pools

Documentation to Prepare

Request Template

Prerequisites Checklist

5. 1inch Integration

🔴 Priority: HIGH

⏱️ Estimated Timeline: 4-12 weeks

Contact Information

Required Network Information

Chain Metadata

Technical Requirements

Infrastructure Requirements

Integration Requirements

What 1inch Needs

41 KiB

Raw Blame History