NashPoint
NashPoint
  • Introduction
    • Introduction To Nashpoint
    • Current Features & Capabilities
    • Post Launch Roadmap
  • User Documentation
    • Node Contract Overview
    • Node Owner & Rebalancer Roles
    • Portfolio Management
    • Rebalancing & Strategy Execution
    • User Deposits & Shares
    • Asynchronous Redemptions
      • Two Step Process
    • Swing Pricing
    • Processing User Redemptions
    • Management & Execution Fees
  • Developer Documentation
    • Overview
    • Role-Based Access Control
    • Smart Contract Architecture
  • Routers
    • ERC-4626 Router
    • ERC-7540 Router
    • Router Tolerance
  • Creating A Node
  • Asynchronous Redemptions
  • Managing a Node
    • Adding & Removing Components
    • Updating Component Allocations
    • Rebalance Window & Cooldown
    • Rebalancing a Node
    • Managing Rebalancers
    • Processing User Redemptions
      • Reserve vs Component Fulfillment
    • Reserve Management
    • Fees Configuration
    • Liquidation Queue Configuration
    • Max Deposit Limits
    • Operator Permissions
    • Emergency Controls
  • Upgrading a Node
    • Adding Quoters & Routers
    • Custom Router Development
    • Multi-Tier Permissioning
  • Cached Data & Gas Efficiency
  • Swing Pricing Calculations
  • Adding Routers and Components - Step by Step Guide
  • Node Execute Function
  • Resources
    • FAQ
    • Glossary
    • Supported Networks & Protocols
    • Deployments
    • Audits
    • GitHub
    • Telegram
    • NashPoint
  • Node Strategies
    • Test Node A
Powered by GitBook
On this page
  • Security Checks
  • Example Usage
  • Important Notes
Edit on GitHub
  1. Managing a Node

Updating Component Allocations

Node owners can modify a component's target allocation, maximum deviation, and router using the updateComponentAllocation function.

function updateComponentAllocation(
    address component,
    uint64 targetWeight,
    uint64 maxDelta,
    address router
) external onlyOwner onlyWhenNotRebalancing

Security Checks

  1. Component must:

    • Be an existing component

    • Be whitelisted in new router (if router changes)

  2. Router must:

    • Be whitelisted in Node

    • Be whitelisted in Registry

  3. Timing:

    • Cannot update during rebalance window

Example Usage

// Update allocation and parameters
node.updateComponentAllocation(
    vaultAddress,     // Existing component
    0.3e18,          // New target: 30%
    0.02e18,         // New max delta: 2%
    routerAddress    // Can be same or new router
);

Important Notes

  • New allocations must still sum to 100% with other components and reserve

  • Changes take effect at next rebalance

  • Consider impact on reserve ratio when changing allocations

  • Router changes require component to be whitelisted in new router

PreviousAdding & Removing ComponentsNextRebalance Window & Cooldown

Last updated 2 months ago