Skip to content

rfcs: add rfc19 tenant multicast rules#3294

Open
juan-malbeclabs wants to merge 2 commits intomainfrom
rfcs/rfc19-tenant-multicast-rules
Open

rfcs: add rfc19 tenant multicast rules#3294
juan-malbeclabs wants to merge 2 commits intomainfrom
rfcs/rfc19-tenant-multicast-rules

Conversation

@juan-malbeclabs
Copy link
Contributor

Summary of Changes

  • Introduces RFC-19, which proposes adding a multicast_rules field to the Tenant onchain account so that all users of a tenant automatically receive multicast group access (publisher, subscriber, or both) without per-user AccessPass authorization
  • Defines three new smart contract instructions (AddTenantMulticastRule, UpdateTenantMulticastRule, RemoveTenantMulticastRule), the dual-authorization model for Add/Update, and the daemon reconciler changes needed to compute the effective multicast set
  • Documents backward compatibility (empty Vec for existing accounts), security considerations (dual auth for Add/Update, tenant-only for Remove, PDA validation), and open questions on rule removal behavior and the 32-rule cap

Diff Breakdown

Category Files Lines (+/-) Net
Docs 1 +227 / -0 +227

Single RFC document, no code changes.

Testing Verification

  • RFC reviewed against existing multicast provisioning patterns (RFC-15, RFC-17)
  • Dual-authorization model validated against the existing AddMulticastGroupPubAllowlist pattern

Based on feedback from Steve: scoping rules by user type prevents
unintended publisher access for non-validator user types (e.g. IBRL,
EdgeFiltering). An empty user_types list applies to all types.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant