Stop dropping legitimate messages at ingest - #15
Merged
Merged
Conversation
Ankr closed its public Polygon endpoint: every call now answers -32000 Unauthorized. With rpcQuorum 1 a share of the node's chain reads land there and fail. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
The ERC-1271 branch verifies by calling the contract, so any RPC failure became INVALID_SIGNATURE. Callers that drop invalid messages, such as the storage node's ingest guard, were deleting legitimate history whenever a provider was down. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
An account that pays its way past a gate publishes right after, and the cached "no" from before the payment silently dropped everything it wrote until the entry expired. Measured at 9m27s of loss on a real channel. Same asymmetry the gate reads already use. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
In a gated channel the publisher is the gate contract, identical for every member, so a rejection did not say whose message was dropped. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
A signed read sends a custom header, so each one costs a preflight plus the read. Measured in the web client: 46% of reads were an OPTIONS 204 followed by the GET. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
On arm64 a dependency creates ~/.local while publishing, and the home was root-owned, so every assignment announcement failed with EACCES. Reproduced with the production image on an Ampere host; amd64 never takes that path. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A gated channel's messages are signed by the gate contract, so the ingest guard verifies them on chain. Two things made that verification destroy valid history:
Measured on a real channel: 9m27s of dropped key requests after a payment, and one of the three shipped RPC providers answering Unauthorized to every call.