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
  • A
  • C
  • D
  • E
  • M
  • N
  • O
  • R
  • S
  • T
Edit on GitHub
  1. Resources

Glossary

Important terminology you will find used across the NashPoint project

PreviousFAQNextSupported Networks & Protocols

Last updated 2 months ago

A

Asynchronous Asset: An asset that doesn't allow immediate withdrawals, typically managed using the ERC-7540 standard in NashPoint.

Asset Manager: An individual or entity responsible for creating and managing a Node within the NashPoint ecosystem.

Async Max Delta: The maximum allowable deviation for asynchronous assets from their target ratio in a Node.


C

Component: An individual asset or investment strategy to which a Node can allocate funds.

Centrifuge: A decentralized asset financing protocol that NashPoint integrates with for Real World Asset (RWA) investments.


D

Deposit Asset: The primary asset used for deposits into a Node, typically a stablecoin.


E

ERC-4626: A standard for tokenized vaults in Ethereum, used by NashPoint for handling deposits and synchronous asset interactions.

ERC-7540: An extension of ERC-4626 that supports asynchronous (delayed) deposits and withdrawals, implemented by NashPoint for managing illiquid assets.

Escrow: A unique contract create for each Node that holds shares and assets during asynchronous user withdrawals.


M

Max Delta: The maximum allowable deviation for synchronous assets from their target ratio in a Node.

Max Discount: The maximum discount the swing pricing mechanism can apply during withdrawals.


N

Node: The core unit of the NashPoint protocol, representing an individual investment strategy managed by an asset manager.

NodeFactory: A contract that allows for the permissionless creation of new Nodes.


O

Operator: An address approved by a controller (user) to execute specific actions on their behalf, particularly for asynchronous redemptions.


R

Rebalancer: An entity responsible for executing asset management functions across Nodes, including investing in assets and processing withdrawals.

Real World Asset (RWA): Tokenized representations of real-world assets that can be included in a Node's investment strategy.


S

Swing Pricing: A mechanism implemented in NashPoint to adjust the price of shares during deposits and withdrawals based on the current reserve ratio, aiming to protect the Node's liquidity.

Synchronous Asset: An asset that allows immediate withdrawals, typically managed using the ERC-4626 standard in NashPoint.


T

Target Reserve Ratio: The ideal percentage of a Node's total assets to be kept as liquid reserves.