Repository navigation
Gate v3: one gate, wire identity, read-only as a declaration - #1
Merged
Merged
Conversation
… price params - isValidSignature now answers checkAccess plus the read-only filter; sticky membership (everMember/erased/join) removed - asymmetric token failure: fail-open at ingest, strict for checkAccess - initialize validates the gate token interface (balanceOf probe) - ban/unban owner-only; allow reverts on banned - new: states(address[]), membersCount/membersAt (NONE), setPrice/setDuration - tests rewritten for the v3 semantics
The contract only sees a hash, never the stream, so the filter cut a member's reactions, presence and key requests along with the messages. Sealed enforces read-only through key distribution; Visible through readers at ingest and the validating storage node.
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.
isValidSignature and checkAccess now answer the same question. readOnly is not consulted there: the contract only sees a hash, never the stream, so a filter would cut a member's reactions and key requests along with their messages.