“Sandbox” environment for testing endpoints

When I’m integrating new networks (like Polygon, Arbitrum, or Near), I usually start by testing basic RPC calls — things like eth_getBlockByNumber, eth_call, or getBalance. The problem is, every one of these tests consumes real Compute Units (CU), even if I’m just debugging payloads, checking response formats, or running quick CI/CD checks.

It would be super helpful to have a Sandbox Mode directly in the dashboard — a lightweight environment where we can run limited read-only RPC requests without burning CU.

Here’s what I imagine:

  • A simple toggle or section in each network tab: “🔧 Sandbox Mode.”

  • When enabled, requests go through a sandbox endpoint

  • The sandbox would return limited blockchain data (for example, the last 100 blocks), and only support read-only methods.

That kind of setup would be perfect for:

  • CI/CD health checks

  • SDK testing

  • Quick debugging before moving to production endpoints

Even small limits (say, 50 requests per minute) would make a big difference.

This feature would save a lot of CU during development and make it easier to experiment with new networks safely inside the dashboard.

Thanks for considering! 🙌


Please authenticate to join the conversation.

Upvoters
Status

In Review

Board
💡

Feature Request

Date

4 months ago

Author

Max M

Subscribe to post

Get notified by email when there are changes.