Quick check
Which limit binds your endpoint?
Two queries at spans 10, 100, 1,000 and 10,000, run from this page against the endpoint you enter. Refusals are classified by bracketed's own classifier. The two queries are a stress test (every ERC-20 transfer) and a sparse control (logs from the zero address): a refusal on the dense one is the measurement, not an error in this page.
Where your data goes
- Requests go from your browser to your endpoint and use your quota.
- Your endpoint URL and key never reach bracketed.
- Error text is sent to bracketed, scrubbed, for classification. The page removes the endpoint, any key-shaped text, and any URL first.
The risks, plainly
- You are trusting the page bracketed serves. It is one file you can read, but if it were changed it could send your URL anywhere. The list below and your browser's Network tab show what it actually sends.
- Browser extensions can read anything you type into a page, including this URL.
- If a request fails CORS, your browser's developer console may show the full URL. That stays on your machine. Anyone who can open that console can read it.
- The scrub is imperfect: it removes your endpoint, URLs and key-shaped text, but a key a provider echoes back in a shape it does not recognise (under 10 characters, or split up) would pass.
- Use a key you can rotate, not your production key. If you are unsure, rotate it afterwards.
What was sent to bracketed 0 requests
Every request this page has sent to bracketed in this session, exactly as sent: the scrubbed message, the HTTP status and the RPC code. Besides your requests to your own endpoint, nothing else leaves your browser.
Check it yourself: open your browser's developer tools, Network tab. You should see requests only to your endpoint and to /v1/decode.
No endpoint of your own? Try a public endpoint
Plan a query
Find a chunk size for your own eth_getLogs query on the endpoint you just checked.
Leave a field empty to leave it out of the filter.
At most 10 requests to your endpoint: up to 6 to sample your query, and the rest to verify a chunk size and search upward for a larger one. Error text from any failure is sent to bracketed, scrubbed, for classification, as above.