Developer Guide
Welcome to Viction Wallet Developer Guide. This documentation contains guides for developers to get started developing on Viction Wallet Extension.
The easiest way to connect to Viction Wallet
Check if the provider is window.viction, if not, please replace it with the exclusive Viction Wallet provider window.viction.
For example, see below:
ChainID:
Hex | Decimal | Network | Hex | Decimal | Network |
0x58 | 88 | Viction | 0x64 | 100 | Gnosis Chain |
Use eth_chainId or net_version to returns the current network/chain ID
To detect Viction Wallet Extension
Notice Viction Testnet is under development and not available now
To connect Viction Wallet Extension
Access a user's accounts
We recommend providing a button to allow users to connect Viction Wallet to your dapp. Selecting this button should call eth_requestAccounts to access the user's accounts.
Handle accounts
Use the eth_accounts RPC method to handle user accounts. Listen to the accountsChanged provider event to be notified when the user changes accounts.
To check if Dapp connected
To disconnect Viction Wallet Extension
To disconnect Viction Extension, please use:
To experience functions
Once your account is connected, let's start experiencing more functions.
Account
How to get Current Account
return Promise<Array[String]>
If wallet can not be found, return [] instead of throw Error
Sign Transaction
Important
eth_signTypedData_v1, and eth_signTypedData_v3 are deprecated. We highly recommend user to use eth_signTypedData_v4 or personal_sign.
Personal_sign
personal_sign provides a simple means to request signatures that are human-readable and don't require efficient processing on-chain. It's commonly used for signature challenges authenticated on a web server.
Viction Wallet implements both personal_sign and eth_sign. You might need to check what method your supported signers use for a given implementation.
eth_signTypedData_v4
eth_signTypedData_v4 offers highly legible signatures that can be processed efficiently on-chain. Adheres to the EIP-712 standard, enabling users to sign sign typed structured data that can be confirmed on-chain.
Note:
Gas limit: is an optional parameter, since Viction Wallet automatically calculates a reasonable gas price.
chainid: The chain ID is derived from the user's current selected network at window.Viction.net_version.
personal_ecRecover
personal_ecRecover returns the address associated with the private key that was used to calculate a signature.
Transfer
This method requires that the user has granted permission to interact with their account first, so please make sure to call eth_requestAccounts or wallet_requestPermissions first.
eth_sendTransaction
return Promise<hash>
Decrypt & Encrypt
eth_decrypt
Requests that Viction Wallet decrypt the specified encrypted message.
The message must have been encrypted using the public encryption key of the specified Ethereum address.
return Promise<string>
eth_getEncryptionPublicKey
Requests that the user share their public encryption key. Returns a public encryption key, or rejects if the user denies the request.
return Promise<string>- The public encryption key of the Ethereum account whose encryption key should be retrived
Encrypt
List of events
Currently we only support some action event from wallet extension
Events | Trigger |
---|---|
accountsChanged | Receive when active account changed in Extension |
networkChanged | Receive when active network changed in Extension |
Method | Description |
---|---|
on(event, callback) | Add event listener |
off(event, callback) | Remove event listener |
Last updated