Admin Guide
EVM access rules
Create self-service ERC-20, ERC-721 and ERC-1155 Discord access rules on Ethereum Mainnet and Robinhood Mainnet.
Supported EVM networks
- Ethereum Mainnet: Chain ID 1.
- Robinhood Mainnet: Chain ID 4663 (0x1237).
- Robinhood Testnet is not offered for new customer rule configuration.
Supported asset standards
- ERC-20: fungible-token balance gating.
- ERC-721: NFT ownership gating, optionally targeting a specific Token ID.
- ERC-1155: multi-token gating with a required Token ID.
Create an EVM rule
- 1Open your server → Access Control → Rules.
- 2Click Add a rule.
- 3Choose EVM.
- 4Select Ethereum Mainnet or Robinhood Mainnet.
- 5Enter a Rule Name.
- 6Choose ERC-20, ERC-721 or ERC-1155.
- 7Enter the EVM Contract Address.
- 8For ERC-721, optionally enter a Token ID to target one NFT; leave it empty to accept any NFT from the contract.
- 9For ERC-1155, enter the required Token ID.
- 10Enter Minimum Balance.
- 11Select the Discord Role controlled by the rule.
- 12Leave the rule enabled unless you intentionally want to save it inactive.
- 13Create the rule.
EVM rule setup is self-service
Server administrators can create and edit supported EVM rules directly from Access Control without asking the Medusa team to configure the contract manually.
Network identity matters
An EVM rule always evaluates the contract on the network selected for that rule. The same contract address or wallet address can exist on more than one EVM network, so Ethereum Mainnet and Robinhood Mainnet are treated as distinct rule contexts.
Balance and Token ID behavior
For ERC-20, Minimum Balance is evaluated against the configured token balance. For ERC-721, a blank Token ID means any NFT in the contract can qualify. ERC-1155 requires a Token ID because balances are token-ID specific.
Capacity accounting
EVM rules count toward the server rule allowance shown in Billing. EVM contracts also participate in the server asset-capacity model used by the Access Control interface.