Token gating (with either NFTs or ERC-20 tokens) is one of the most important web3 social features.
Orbis contexts can have different access rules where token gating can be implemented. But there's a limited amount of supported chains (Ethereum, Arbitrum, Optimism, Gnosis Chain, and Polygon).
Instead of adding support for each new chain manually, the system should be designed in a way that any EVM chain is supported by default.
Obviously Orbis should not maintain RPC URLs for every EVM chain in existence (it's just too many of them), but instead each project would be required to add their own RPC URL in the context data (in the createContext/updateContext call). This would be required only for projects that want to use token gating, of course.