pub const MAX_COMMUNITIES: usize = 50;Expand description
The active signer for authority actions (bunker support): the live client’s signer — which covers a NIP-46 bunker — falling back to the local vault keys when there is no client OR the client has no signer attached (local accounts, headless/CLI paths, and tests). Every keyless control edition + moderation hide signs through this, so a bunker account can create AND administer a community. (The REKEY path is the one exception — its blob locator needs a raw ECDH the signer can’t expose, so it still requires a local key; the ban/privatize flows fail-fast for bunker accounts.) Max communities a device may hold locally. The synced Community List is a single NIP-44 event (65 KB plaintext); past the cap even the slimmed list can’t encrypt, so a NEW join/create is rejected above it (the user leaves one to make room).