Skip to content

MAINNET_FUNDING_OPTIONS.md

Latest commit

 

History

History
219 lines (162 loc) · 5.46 KB

MAINNET_FUNDING_OPTIONS.md

File metadata and controls

219 lines (162 loc) · 5.46 KB
Raw

Options for Mainnet Deployment Without Funds

If you don't have QIEV3 funds for mainnet deployment, here are your options:

Option 1: Testnet Demo (Recommended for Evaluation)

Show Testnet Deployment Working

You can demonstrate the full system on testnet, which shows:

  • ✅ All contracts deployed and verified
  • ✅ Full functionality working
  • ✅ System is production-ready
  • ✅ Mainnet deployment is just a configuration change

Create Testnet Demo Documentation

  1. Deploy to Testnet (if not already done):

    cd contracts
npx hardhat run scripts/deploy_all.ts --network qieTestnet

  2. Document Testnet Deployment:

    • Contract addresses on testnet
    • Explorer links showing verified contracts
    • Screenshots/videos of working features
    • Testnet transaction examples

  3. Show Mainnet Readiness:

    • All code is mainnet-ready
    • Just needs funds and environment variable change
    • Deployment scripts are ready
    • Verification scripts are ready

Option 2: Request Testnet Funds

QIE Testnet Faucet

Check if QIE has a testnet faucet:

  • Look for official QIE documentation
  • Check QIE Discord/Telegram communities
  • Contact QIE team for testnet tokens

Use Testnet for Full Demo

With testnet funds, you can:

  • Deploy all contracts
  • Show complete functionality
  • Demonstrate all features
  • Create comprehensive demo

Option 3: Request Mainnet Funds

Contact QIE Team

If this is for a competition/evaluation:

  • Explain you need mainnet funds for deployment
  • Show your testnet deployment as proof of readiness
  • Request small amount for deployment (1-2 QIEV3 should be enough)

Community Support

  • QIE Discord/Telegram
  • QIE developer channels
  • Competition organizers

Option 4: Document Mainnet Readiness

Create Comprehensive Documentation

Show evaluators that:

  1. Code is Mainnet-Ready:

    • All network configuration centralized
    • Mainnet safeguards implemented
    • RPC failover ready
    • Gas limits configured

  2. Deployment Infrastructure Ready:

    • Deployment scripts tested
    • Verification scripts ready
    • Environment configuration complete
    • All documentation prepared

  3. Testnet Proof:

    • Contracts deployed on testnet
    • All features working
    • Verified contracts on testnet explorer
    • Complete testnet demo

Create "Mainnet Ready" Report

Document:

  • What's been implemented
  • What's needed (just funds)
  • Testnet deployment proof
  • Mainnet deployment process (ready to execute)

Option 5: Partial Mainnet Deployment

If you can get minimal funds:

  • Deploy only critical contracts (CreditPassportNFT)
  • Show it working on mainnet
  • Document others as "ready to deploy"

Recommended Approach for Evaluation

Step 1: Deploy to Testnet

# Set to testnet
export QIE_NETWORK=testnet

# Deploy contracts
cd contracts
npx hardhat run scripts/deploy_all.ts --network qieTestnet

# Verify contracts
npx hardhat run scripts/verify-all.ts --network qieTestnet

Step 2: Create Testnet Demo

  • Document all testnet contract addresses
  • Create screenshots/videos
  • Show all features working
  • Provide testnet explorer links

Step 3: Document Mainnet Readiness

Create a document showing:

  • ✅ All code is mainnet-ready
  • ✅ Deployment scripts ready
  • ✅ Just needs funds to execute
  • ✅ Testnet proves functionality

Step 4: Create Evaluation Package

Include:

  1. Testnet Deployment:

    • Contract addresses
    • Explorer links
    • Working demo

  2. Mainnet Readiness:

    • Code review showing mainnet support
    • Deployment scripts
    • Configuration files
    • Documentation

  3. What's Needed:

    • Just QIEV3 funds for gas
    • Can deploy immediately when funds available

Quick Actions You Can Take Now

1. Verify Testnet Deployment

# Check if contracts are deployed on testnet
cd contracts
npx hardhat run --network qieTestnet -e "
  const addresses = {
    passport: process.env.CREDIT_PASSPORT_NFT_ADDRESS,
    vault: process.env.LENDING_VAULT_ADDRESS,
    staking: process.env.STAKING_CONTRACT_ADDRESS
  };
  console.log('Testnet addresses:', addresses);
"

2. Create Testnet Demo Guide

Document how to:

  • Connect to testnet
  • Use all features
  • View contracts on explorer
  • Show complete functionality

3. Prepare Mainnet Deployment Package

Even without funds, you can:

  • ✅ Show all code is ready
  • ✅ Show deployment scripts work (dry-run)
  • ✅ Document the process
  • ✅ Show testnet as proof of concept

For Evaluators/Judges

What to Show:

  1. Testnet Deployment (Working Now):

    • All contracts deployed and verified
    • Full functionality demonstrated
    • Complete feature set working

  2. Mainnet Readiness (Code Complete):

    • All mainnet configuration implemented
    • Deployment infrastructure ready
    • Just needs funds to execute deployment
    • Same code, different network

  3. Technical Excellence:

    • Proper network abstraction
    • RPC failover
    • Gas optimization
    • Security safeguards
    • Complete documentation

Next Steps

  1. Immediate: Deploy to testnet and create demo
  2. Document: Create "Mainnet Ready" documentation
  3. Request: Contact QIE team/community for funds if needed
  4. Prepare: Have everything ready for instant mainnet deployment when funds available

Remember: A working testnet deployment with complete mainnet-ready code is often sufficient for evaluation, especially if you can demonstrate the system works and is just waiting on funds for mainnet deployment.