In GRVT, each user is required to register both Web2 and Web3 credentials, with SecureKeys serving as their Web3 credentials.
Web2 Credentials (Emails)
Users sign up with their email by setting a password or using Google/Microsoft OAuth. This access enables non-trading features, including completing KYC, participating in referrals, viewing portfolios, and checking positions.
Web3 Credentials (SecureKey)
For trading features, users must register a SecureKey, which functions as their self custodial credential on GRVT. SecureKeys are Ethereum public/private key pairs, where only the user has access to the private keys. Any action that could alter asset ownership requires a signature from the SecureKey, adding an essential layer of security and self-custody.
Credential Type | Identifier | Secret | Use case |
web 2.0 |
| password/oauth | Read + Write
No Trading features
|
web 3.0
SecureKey | Ethereum public key | private key | Own
Sign trades and messages that can lead to change in the ownership of your funds
|
GRVT SecureKey vs using an external wallet as a SecureKey
You can use an external wallet like MetaMask as your SecureKey specifically for signing messages with the private key stored in the Metamask browser extension. Note that signing transactions in GRVT does not require gas fees, except for bridging assets.
If you prefer not to use MetaMask or another external wallet for signing transactions, GRVT offers a built-in SecureKey secured by Dfns — a biometric wallet that enables transaction signing with passkeys. If you use this option, you do not have to manage private keys. You can simply onboard one or more devices, and sign trades using passkeys. Learn more.