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
  • Purpose
  • Permissions
  • Configuration
  • Timing Rules
  • Modifiers
Edit on GitHub
  1. Managing a Node

Rebalance Window & Cooldown

The Node implements a time-based control system that determines when rebalancing operations can occur:

uint64 public rebalanceCooldown = 23 hours;  // Default
uint64 public rebalanceWindow = 1 hours;     // Default
uint64 public lastRebalance;

Purpose

  • Enables Node owners to optimize transaction costs by batching investment and withdrawal transactions

  • Window provides predictable timeframe for operations

  • Rebalancer has discretion on when to start new window

  • Owner can adjust periods based on strategy needs

Permissions

  • The Node Owner has exclusive permission to set rebalance cooldown & duration

  • Whitelisted Rebalancers have exclusive rights to call startRebalance()

Configuration

// Only owner can modify
function setRebalanceCooldown(uint64 newRebalanceCooldown)
function setRebalanceWindow(uint64 newRebalanceWindow)

Timing Rules

  • Must wait rebalanceCooldown between rebalance windows

  • Rebalancing actions only valid for rebalanceWindow duration

  • Window starts when rebalancer calls startRebalance()

Modifiers

modifier onlyWhenRebalancing()     // Must be within window
modifier onlyWhenNotRebalancing()  // Must be outside window

PreviousUpdating Component AllocationsNextRebalancing a Node

Last updated 2 months ago