Repository navigation
Serve browser (gRPC-web) clients with an operator origin policy - #18
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UPeo6Zru7gaUynCCBbcBSe
|
@elicbarbieri thanks for this. It is the piece browser wallets need: today our in-browser scan benchmark (konclave-benchmark) reaches public light wallet servers only through gRPC-web proxies we host, and this would let it talk to a zingod directly. We read the diff. We have not run it yet. One point on A ceiling for exempt slots (for example a configurable quota above A smaller one: We can test the gRPC-web path with our browser client after November 17 and report back here. |
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UPeo6Zru7gaUynCCBbcBSe
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UPeo6Zru7gaUynCCBbcBSe
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UPeo6Zru7gaUynCCBbcBSe
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UPeo6Zru7gaUynCCBbcBSe
d2e6e8e to
3524181
Compare
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Enables browser wallets to connect to zingod directly via gRPC-web, with a per-origin kill switch and rate-exemption operated from the CLI.