# MetaMask Business Development Guide

Guide for engaging with Consensys/MetaMask for native feature support.

## Overview

This guide outlines the process for requesting native MetaMask feature support for ChainID 138, including Swaps, Bridge, and on-ramp integration.

## Current Status

ChainID 138 is **not** currently supported in:
- MetaMask Swaps aggregator
- MetaMask Portfolio Bridge
- MetaMask Buy/Sell on-ramps

## Contact Information

### Consensys Business Development

- **Website**: [consensys.io](https://consensys.io)
- **Contact**: Business development team
- **Email**: [To be provided]
- **Twitter**: [@Consensys](https://twitter.com/Consensys)

### MetaMask

- **Website**: [metamask.io](https://metamask.io)
- **Documentation**: [docs.metamask.io](https://docs.metamask.io)
- **Support**: [support.metamask.io](https://support.metamask.io)

## Integration Requirements

### Swaps Integration

**Requirements**:
- Sufficient liquidity on ChainID 138
- DEX integration with aggregator
- Security audit completion
- Regulatory compliance
- User base and volume

**Timeline**: 3-6 months (estimated)

**Cost**: Negotiable (partnership terms)

### Bridge Integration

**Requirements**:
- Bridge provider partnership
- Security audit completion
- Liquidity on both sides
- Monitoring and alerts
- Regulatory compliance

**Timeline**: 3-6 months (estimated)

**Cost**: Negotiable (partnership terms)

### On-Ramp Integration

**Requirements**:
- On-ramp partner integration
- Regulatory compliance
- KYC/AML compliance
- User experience optimization
- Payment processing

**Timeline**: 6-12 months (estimated)

**Cost**: Negotiable (partnership terms)

## Outreach Template

### Initial Contact

**Subject**: ChainID 138 Integration Request - DeFi Oracle Meta Mainnet

**Body**:

Dear Consensys Business Development Team,

We are reaching out to request native MetaMask feature support for ChainID 138 (DeFi Oracle Meta Mainnet).

**About ChainID 138**:
- ChainID: 138 (0x8a)
- Network: DeFi Oracle Meta Mainnet
- Consensus: IBFT 2.0 (Istanbul BFT)
- Block Time: ~2 seconds
- Finality: Immediate (BFT)
- RPC: https://rpc.d-bis.org
- Explorer: https://explorer.d-bis.org

**Current Status**:
- Network is listed on Chainlist
- Token list is published
- Blockscout explorer is deployed
- RPC endpoints are operational
- User base is growing

**Integration Request**:
We would like to request integration for:
1. MetaMask Swaps aggregator
2. MetaMask Portfolio Bridge
3. MetaMask Buy/Sell on-ramps

**Next Steps**:
We would appreciate the opportunity to discuss:
- Integration requirements
- Timeline and milestones
- Partnership terms
- Technical specifications

Please let us know if you would like to schedule a call to discuss this further.

Best regards,
[Your Name]
[Your Organization]

## Proposal Template

### Executive Summary

- **Network**: DeFi Oracle Meta Mainnet (ChainID 138)
- **Use Case**: Oracle data aggregation and cross-chain oracle synchronization
- **User Base**: [Number] users
- **Volume**: [Transaction volume]
- **Liquidity**: [Liquidity metrics]

### Technical Specifications

- **ChainID**: 138
- **Consensus**: IBFT 2.0
- **Block Time**: ~2 seconds
- **Finality**: Immediate
- **RPC Endpoints**: 2+ high-availability endpoints
- **Explorer**: Blockscout with full API
- **Token List**: Official token list published

### Integration Plan

1. **Phase 1**: Swaps integration (3-6 months)
2. **Phase 2**: Bridge integration (3-6 months)
3. **Phase 3**: On-ramp integration (6-12 months)

### Benefits

- **User Experience**: Seamless wallet integration
- **Liquidity**: Access to MetaMask's user base
- **Visibility**: Increased network visibility
- **Adoption**: Faster network adoption

## Regulatory Considerations

### Swaps

- **SEC Scrutiny**: Swaps have been under SEC scrutiny
- **Compliance**: Ensure regulatory compliance
- **Legal Review**: Legal review required
- **Risk Assessment**: Risk assessment required

### Bridge

- **Security**: Security audit required
- **Regulatory**: Regulatory compliance required
- **Monitoring**: Monitoring and alerts required
- **Risk Management**: Risk management required

### On-Ramp

- **KYC/AML**: KYC/AML compliance required
- **Regulatory**: Regulatory compliance required
- **Payment Processing**: Payment processing compliance
- **User Protection**: User protection measures

## Tracking

### Milestones

- [ ] Initial contact made
- [ ] Proposal submitted
- [ ] Technical discussion scheduled
- [ ] Partnership agreement signed
- [ ] Integration development started
- [ ] Testing completed
- [ ] Integration launched

### Updates

Track updates and communications:

- **Date**: ___________
- **Update**: ___________
- **Next Steps**: ___________

## References

- [MetaMask Documentation](https://docs.metamask.io)
- [Consensys Website](https://consensys.io)
- [MetaMask Support](https://support.metamask.io)
- [SEC Swaps Scrutiny](https://www.reuters.com/legal/us-sec-sues-blockchain-software-technology-company-consensys-2024-06-28/)