.svg?alt=media&token=5f4690a3-d3e0-45f8-aa6b-ba353a5f4d02)
.svg?alt=media&token=712cfff9-4c4c-4d6b-ac9a-4ba99c77020b)
Receiving Royalty Tokens
Receiving Royalty Tokens On-Chain: Overview
Revelator is introducing a new way for payees (artists, songwriters, rights holders, etc.) to receive their royalties on-chain using Web3Auth (a password-less, email-based wallet creation service) or by connecting an existing, self-custody wallet (like MetaMask). This feature helps reduce friction for anyone looking to adopt web3 technology and simplifies how royalties are paid out on the blockchain.
Why This Matters
Payees can easily get started with royalty tokens using a simple email login (no complicated seed phrase management required).
Enterprises or “Parents” can now seamlessly add on-chain payments to their business without forcing payees to be blockchain experts from day one.
New business opportunities open up for customers (especially in emerging markets) who want to leverage on-chain royalties.
Flexible approach ensures that payees already familiar with web3 can still connect any external wallet of their choice.
How It Works: Step by Step
1. Adding a Payee to a Royalty Token Contract
When an enterprise (the “parent”) wants to give a payee a share of royalties on-chain, they’ll add that payee’s wallet address (0x address) to the Royalty Token contract.
If a payee already has a 0x address on file, great – that address is used automatically.
If a payee has no 0x address yet, a Payee Vault is created on-chain to temporarily hold their tokens until they create or connect a wallet.
Payee Vault is simply a special on-chain contract that stores any unclaimed tokens or funds for the payee until they’re ready.
2. Payee Receives an Email Notification
After the parent mints the royalty token:
The payee gets an email letting them know “You’ve got royalty tokens waiting!”
The email includes instructions on how to create or connect a wallet from the Payee Portal in order to claim those tokens.
3. Create or Connect a Wallet
In the Payee Portal, payees have two main options to set up their wallet:
Create a wallet using Web3Auth
With Web3Auth, payees sign in using just their email and a secure verification (2FA).
This approach is simpler than memorizing seed phrases, making it perfect for newcomers to web3.
Connect an existing self-custody wallet
If a payee already uses MetaMask or another wallet, they can connect it directly.
This is great for payees who are already comfortable managing their wallet keys.
Once the wallet is set up or connected, its 0x address is saved in the payee’s account details for all future on-chain royalty distributions.
4. Claiming Royalty Tokens from the Payee Vault
If a payee was added without a 0x address, any tokens or funds were put in their Payee Vault.
The payee simply clicks a “Claim” button in the portal (after they have a wallet) to move all unclaimed tokens from the Payee Vault into their chosen wallet address.
Extra Security: 2FA is used before the claim transaction goes through, requiring the payee to confirm via their email. This helps prevent unauthorized claims.
Once Claimed: All future royalty tokens and payments will be sent directly to the payee’s new 0x address, with no need for a vault.
Frequently Asked Questions
Benefits for Different Users
Payees
Simple On-Boarding: No need to learn complex crypto setups. Sign in with your email and start receiving tokens.
Advanced Users Welcome: If you already have a crypto wallet, connect it and manage your royalties in your favorite wallet app.
Enterprises / “Parents”
Reduced Friction: Easily add any payee to the Royalty Token contract. If they lack a wallet, the system automatically creates a Payee Vault so you don’t have to wait.
Future-Proof: Lays the groundwork for advanced on-chain royalty payments, including potential stablecoin payouts, token streaming, and more.
Safety Net: If a payee never claims their tokens, you can revert or redistribute the funds as needed.
Security and Recovery
2FA
To claim tokens, payees must verify themselves via email. This helps stop attackers from taking control of tokens even if they somehow guess or steal a payee’s Payee Portal login.
Unclaimed Funds
If a payee never claims their tokens (no wallet, never sets it up), the enterprise/parent can recover or revert the balance after a certain period.
Legal & Compliance
Revelator uses a 3rd-party service (Web3Auth) for wallet security, key storage, and password-less authentication. This helps us stay compliant and reduces our direct handling of sensitive private keys.
Next Steps and Future Releases
Mobile Wallet Improvements: We plan to add more robust wallet features in the Revelator mobile app so payees can view on-chain balances, send or receive tokens, and potentially convert funds to fiat if desired.
Advanced On-Chain Features: The ability to handle stablecoins, multi-split contracts, or further bridging solutions may come in future updates.
Enhanced Security Options: If payees or enterprises require more robust security, we’re exploring additional 2FA or verification workflows down the line.
Getting Started
If you’re an Enterprise:
Add Payees to your royalty token contract as you normally would – just enter their name and/or email.
If they don’t have a wallet address, a Payee Vault is automatically created.
Send them an email or rely on Revelator’s email flow to explain how they can create or connect their wallet.
If you’re a Payee:
Check Your Email for the invite from Revelator.
Click “Create or Connect My Wallet” in the Payee Portal.
Choose Web3Auth to quickly create a wallet with just your email & 2FA. Or connect your own existing wallet (e.g., MetaMask).
Click “Claim Tokens” to move the royalty tokens from your Payee Vault into your wallet address. Done!
Support and Maintenance
If you need help, contact [Support/Your Customer Success contact] for assistance with:
Troubleshooting wallet setup
Handling 2FA or email verification issues
Questions about token claiming and Payee Vaults
We hope this new feature helps you embrace web3 and get paid seamlessly on-chain. Happy royalty collecting!
Last updated