Create Royal ID

The Royal Protocol provides flexible ways to create Royal IDs, accommodating both self-service users and platform-assisted registration. This flexibility ensures that both crypto-native users and those new to web3 can easily establish their digital identity.

This is for only creating Royal IDs

Registering a Royal ID can also be bundled with a delegation. This is a special function aimed at supporting UX for registrars. It allows for user registration and delegation (to the registrar) to happen with a single signature from the end user.

Core Approaches

Users can create Royal IDs in two primary ways:

• Direct Creation: Users with ETH can create their own Royal ID by sending a transaction directly. This approach gives users complete control over the process but requires them to have ETH for gas fees.
• Sponsored Creation: Platforms or registrars can create Royal IDs on behalf of users, with user approval via signature. This approach eliminates the need for users to hold ETH, making it ideal for onboarding new users.

Setup Requirements

Before creating a Royal ID, ensure:

• The user has access to a web3 wallet (like MetaMask or Coinbase Wallet)
• For direct creation, the user has ETH on Base for gas fees
• For sponsored creation, the platform handles gas fees

Direct Creation Flow

1. User connects their wallet to a Royal Protocol-enabled application
2. User provides their desired username and optional recovery address
3. Application calls IdGateway.register() with:
   • Username
   • Recovery address (if specified)
4. User approves the transaction in their wallet
5. IdGateway validates the request and forwards it to IdRegistry
6. IdRegistry creates the Royal ID and emits a Registered event

Sponsored Creation Flow

1. User connects their wallet to a Royal Protocol-enabled application
2. User provides their desired username and optional recovery address
3. User signs a message containing:
   • Their wallet address (future custody address)
   • Chosen username
   • Recovery address (if specified)
   • Request deadline
4. Platform submits the signed message via IdGateway.registerFor()
5. IdGateway verifies the signature and forwards the request to IdRegistry
6. IdRegistry creates the Royal ID and emits a Registered event

Success Verification

For both flows, successful creation is indicated by:

• The Registered event being emitted
• The new Royal ID being queryable via IdRegistry
• The user’s address being associated with the new Royal ID