The largest current Concord Community is 70 members large (the largest Encrypted group on Nostr, I believe!). On paper, Concord is designed to scale in to the 1,000s of members without *runtime* slowdown, where the slowdown will be felt however is for Community Admins that perform rekeys (typically after a ban), rekey speed and bandwidth is proportional to member count O(n). Outside of rekeys, every other action is atomic, O(1), Concord scales fantastically for large public communities. The linear slowdown of rekeys is something solveable, perhaps in a Concord v3 proposal, but I do not foresee it being an issue for a long time, and if communities grow large enough for it to become a priority, there are ways we can solve it.