Skip to main content

Monaco Protocol SDK v0.4.0

Custom RPC Configuration & Network Flexibility

This release introduces configurable RPC endpoints and custom network support, giving developers full control over their infrastructure and network connectivity.

What’s New

Required RPC Configuration
  • Custom RPC Endpoint: seiRpcUrl is now a required parameter when initializing the SDK
  • Rate Limit Control: Each application can now use their own RPC provider to avoid shared rate limits
  • Network Flexibility: Pass custom Monaco network configurations for different environments
Breaking Changes
  • The SDK now requires seiRpcUrl to be provided during initialization
  • This change affects all SDK instantiations in both TypeScript and React packages

Why This Change?

Public RPC endpoints are heavily rate-limited and can cause reliability issues in production applications. By requiring each application to configure their own RPC provider, Monaco SDK enables:
  • Better Performance: Dedicated RPC endpoints provide consistent performance
  • No Rate Limiting: Avoid throttling from shared public endpoints
  • Production Ready: Use premium RPC providers for mission-critical applications
  • Custom Infrastructure: Full control over your blockchain connectivity

Technical Details

TypeScript SDK - New Initialization
React Package - MonacoProvider Updates
Custom Network Configuration For advanced use cases, you can now pass custom network configurations:

RPC Provider Options

You can use various RPC providers for Sei: Sei Public RPCs (Rate Limited)
  • Testnet: https://evm-rpc.sei-apis.com
  • Mainnet: https://evm-rpc.sei-apis.com (update to mainnet endpoint)
Recommended Providers (For Production)

Migration from v0.3.x

Before (v0.3.x)
After (v0.4.0)
React Migration Before (v0.3.x)
After (v0.4.0)

Environment Variables Best Practice

Store your RPC URL in environment variables:

Packages Updated

Installation

Breaking Changes Summary

Documentation Updates

This SDK release corresponds to infrastructure improvements:
  • Better separation between Monaco API and blockchain RPC
  • Improved reliability through dedicated RPC endpoints
  • Foundation for multi-network support
  • Enhanced developer control over infrastructure

Support

If you need help choosing an RPC provider or configuring your SDK, join our Discord community or contact the Monaco Protocol team.
Note: While public Sei RPCs work for development and testing, we strongly recommend using a dedicated RPC provider for production applications to ensure reliability and performance.