Rigoblock Documentation
  • Welcome
  • Introduction to RigoBlock
  • Contracts
    • Protocol
      • RigoblockPoolExtended
      • Core
        • constants
        • immutables
        • storage
        • actions
        • owner actions
        • abstract
        • fallback
        • initializer
        • state
        • storage accessible
      • Deps
        • Authority
          • authority docs
        • PoolRegistry
          • pool registry docs
      • Extensions
        • AGovernance
          • Solidity API
        • AMulticall
          • aMulticall docs
        • AStaking
          • aStaking docs
        • AUniswap
          • aUniswap docs
        • EUpgrade
          • eUpgrade docs
        • EWhitelist
          • eWhitelist docs
      • Proxies
        • proxy
          • proxy docs
        • proxy factory
          • proxyFactory docs
    • GRG Token
      • RigoToken
        • rigoToken docs
      • Inflation
        • inflation docs
      • ProofOfPerformance
        • pop docs
    • GRG Staking
      • GrgVault
        • grgVault docs
      • StakingProxy
        • stakingProxy docs
      • Staking
        • staking docs
    • Governance
      • Solidity API
  • Deployments
    • deployed contracts - V4
    • deployed contracts
    • v1.5.0
    • v1.4.2
    • v1.4.1
    • v1.3.0
    • v1.1.1
    • v1.1.0
  • Governance
    • Rigoblock Governance
    • Supported Applications
    • Token Whitelists
    • Supported Methods
      • Selectors - V4
      • Selectors - V3
  • Bug Bounty
    • Known Issues
  • Oracles and Price Feeds
Powered by GitBook
On this page
  1. Contracts
  2. GRG Staking

StakingProxy

PreviousgrgVault docsNextstakingProxy docs

Last updated 2 years ago

The staking proxy implements a minimal set of methods used to manage the proxy itself. All methods related to staking are implemented in the staking contract, therefore all non-implemented calls are forwarded to the staking implementation with a delegatecall. Before upgrading the implementation, the RigoBlock Governance must check that those new variables added to the staking implementation storage are placed after the existing variables and that the order of declaration is preserved, otherwise, a storage clash is possible.

Credits: UML diagram generated with
SOL2UML