2. Configuration
Components
vNFT: main contract of the integration, manages all the vNFT logic and vSuite interactions
MerkleVault: contract that will receive all the execution layer rewards generated by the underlying validators of the vNFTs. It uses a merkle tree mechanism to distribute the rewards, the merkle tree is computed off-chain and uploaded to IPFS and the hash and the root are then uploaded on this contract.
Roles
Role | Description |
---|---|
SYS_ADMIN | Can modify integrator address, integrator commission, operator commission, name, symbol and uri and can pause/unpause purchases. |
Deployment Parameters
Param | Type | Description |
---|---|---|
name | string | Name of the ERC721 token |
symbol | string | Symbol of the ERC721 token |
uriPrefix | string | The uri prefix to use for every token from which to pull the metadata |
extraData | string | The extra data to use upon validator deposits (can be used if managed by the operator) |
actors | address[4] |
|
commissions | uint256[2] |
|
soulboundMode | bool | Whether or not the soulbound mode is enabled |
Soulbound mode
A vNFT integration contract can be deployed with the soulbound mode. When the soulbound mode is enable, all the transfers functions of the ERC721 are disabled, becoming a non transferable NFT.
Last updated