EmProps Job Queue

Appearance

Development Plan ​

Navigation

Development Phases ​

Phase 1: Contract Deployment (Week 1-2) ​

The first phase focuses on getting contracts deployed and tested on Arbitrum Sepolia.

What we're doing: Taking our existing ERC721A contract suite and deploying it to Arbitrum's testnet. The contracts already work—we've tested them on Ethereum Sepolia and Base Sepolia. The goal is validating that everything behaves identically on Arbitrum.

Specific tasks:

  • Configure Hardhat for Arbitrum Sepolia network
  • Deploy NFTContractFactory and Emerge_721 V1 implementation
  • Verify contracts on Arbiscan
  • Test factory deployment flow end-to-end
  • Integrate 0xSplits and verify revenue distribution
  • Document any Arbitrum-specific quirks

Success criteria: A creator can deploy a collection on Arbitrum Sepolia, mint tokens, and see revenue flow correctly to split recipients. All contracts verified and readable on Arbiscan.

Phase 2: Indexer Integration (Week 1-2) ​

With contracts deployed, we need to index their events so our UI can display real-time data.

What we're doing: Configuring our Ponder indexer to watch Arbitrum contracts. Ponder already indexes our Ethereum and Base deployments; adding Arbitrum is configuration rather than new code.

Specific tasks:

  • Add Arbitrum network configuration to Ponder
  • Register contract addresses and ABIs
  • Test event processing (mint, transfer, deployment events)
  • Verify WebSocket updates work for real-time UI
  • Load test with batch minting scenarios

Success criteria: When someone mints on Arbitrum, our database updates within seconds and the WebSocket broadcasts the event. Historical queries return accurate data.

Phase 3: Frontend Integration (Week 3) ​

The frontend needs to support Arbitrum as a deployment target.

What we're doing: Updating EmProps Studio to include Arbitrum in chain selection, handle Arbitrum-specific wallet interactions, and display Arbitrum collections alongside existing chains.

Specific tasks:

  • Add Arbitrum to chain configuration (wagmi config, chain constants)
  • Update collection creation flow with Arbitrum option
  • Test wallet connection and transaction signing
  • Implement gas estimation for Arbitrum transactions
  • Update collection display to show chain badges
  • Test cross-chain scenarios (creator has collections on multiple chains)

Success criteria: A user can connect their wallet, select Arbitrum, create a collection, generate art, and deploy—all without leaving the Studio interface.

Phase 4: Production Deployment (Week 4) ​

Moving from testnet to mainnet.

What we're doing: Deploying to Arbitrum One (mainnet), monitoring initial usage, and onboarding early creators.

Specific tasks:

  • Deploy contracts to Arbitrum One
  • Verify on Arbiscan (mainnet)
  • Update Ponder to index mainnet
  • Configure production environment variables
  • Monitor first deployments closely
  • Gather creator feedback
  • Document any mainnet-specific issues

Success criteria: Real creators launching real collections on Arbitrum One, with revenue flowing correctly and no critical issues.

Risk Factors and Mitigations ​

Contract behavior differences: L2s can have subtle differences in gas estimation, block timing, or precompile behavior. Mitigation: extensive testnet testing before mainnet, and starting with smaller collections.

Indexer latency: Arbitrum produces blocks faster than Ethereum mainnet; Ponder needs to keep up. Mitigation: load testing on testnet with realistic transaction volumes.

User confusion: Multi-chain options can overwhelm users. Mitigation: clear UI guidance, default to Arbitrum for cost-conscious creators, provide gas estimates before deployment.

0xSplits integration: First time integrating with 0xSplits on this chain. Mitigation: test thoroughly on Sepolia; the 0xSplits team is responsive to questions.

Dependencies ​

External:

  • Arbitrum Sepolia RPC endpoints (Alchemy, Infura)
  • Arbitrum One RPC endpoints (production)
  • 0xSplits contracts deployed on Arbitrum (already available)
  • Arbiscan API for contract verification

Internal:

  • EmProps Studio codebase (Next.js frontend)
  • Ponder indexer infrastructure
  • Existing ERC721A contract code
  • CI/CD pipeline for contract deployment

Cost Projections ​

Development: Primarily engineering time. No significant new infrastructure costs.

Deployment:

  • Arbitrum Sepolia: Free (testnet)
  • Arbitrum One: ~$5-20 for initial contract deployment (factory + implementation)

Ongoing:

  • Additional RPC calls to Arbitrum nodes (covered by existing Alchemy plan)
  • Ponder indexing compute (marginal increase to existing infrastructure)

The infrastructure cost delta is minimal because we're extending existing systems rather than building new ones.

Success Metrics ​

Technical:

  • 99%+ uptime for Arbitrum contract interactions
  • ❤️ second indexer latency for event processing
  • Zero critical bugs in first month of production

Business:

  • First 10 collections deployed within 2 weeks of mainnet launch
  • Creator feedback score >4/5 for Arbitrum deployment experience

What Comes After ​

Once Arbitrum is stable, we have options:

Arbitrum Nova: Lower-cost chain for high-volume, lower-value mints Additional L2s: Optimism, Base (already in dev), zkSync Cross-chain features: Bridge NFTs between chains, unified collection view

These are future considerations. The immediate focus is making Arbitrum One work reliably for creators.

Related Documentation:

Released under the MIT License.

Copyright © 2024 EmProps