Contracts
The Stargate staking system consists of two primary contracts that work together to manage VeChain protocol staking positions:
Stargate.sol:The main entry point and business logic contractStargateNFT.sol: The ERC721 token contract representing staking positions
These contracts implement a separation of concerns where the NFT contract handles: token ownership and details, metadata, boosting and managers. While the Stargate contract manages the staking mechanics, validator delegation and rewards logic.
Contracts are public and can be found at the following repository: https://github.com/vechain/stargate-contracts
StarGate
Not deployed yet
Stargate.sol
Stargate.solEntry point for all staking, delegation, and reward operations. Acts as the orchestrator between users, the StargateNFT contract, and the VeChain Protocol Staker contract.
Orchestrates staking, delegation, exits, and reward accounting.
Custodies VET during non-delegated phases; funds the on-chain validator delegation when active.
Computes and pays out VTHO rewards.
Coordinates state with the protocol (IProtocolStaker) and with the NFT contract.
Interactions with external protocol and tokens:
→
StargateNFT: Callsmint(),burn(),migrate(),boostOnBehalfOf()→ Protocol
Stakercontract: CallsaddDelegation(),withdrawDelegation(),signalDelegationExit()→
VTHOToken: Transfers rewards using SafeERC20
StargateNFT.sol
StargateNFT.solERC721 NFT contract representing staking positions. Manages token metadata, levels, maturity periods, and acts as a continuation of the legacy VechainNodes (X-Node/Eco Node) collection.
ERC721 that represents the staking position.
Stores token metadata required for protocol math (level, vetAmountStaked, maturity, rewardsMultiplier, etc.).
Manages levels, maturity periods, boosting, supply caps, and manager assignments.
Can only be minted/burned by
Stargate(not by users).
Security audits
StarGate smart contracts have undergone a comprehensive audit by Hacken.
ABIs
Interfaces
Last updated
Was this helpful?

