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
  • Request ID
  • Supported Integrations
  • Ethereum Mainnet
  • Arbitrum One
Edit on GitHub
  1. Routers

ERC-7540 Router

PreviousERC-4626 RouterNextRouter Tolerance

Last updated 19 days ago

The ERC7540 Router enables Nodes to interact with asynchronous yield-bearing vaults that implement the ERC7540 interface. This includes protocols with delayed withdrawals, request-claim patterns, and multi-step operations.

Key Features

  • Manages async deposit/withdrawal flows

  • Handles request and claim operations

  • Tracks pending and claimable amounts

  • Coordinates multi-step transactions

Request ID

The ERC7540Router expects that async deposits and redemptions returns a request ID of 0, otherwise the functionality reverts. However, some ERC-7540 vaults may return a non-zero request ID, according to future EIPS. In the case of NashPoint, the router contract purely uses the controller to the request state.

Supported Integrations

Ethereum Mainnet

Component Name
Protocol
Address

[Component Name]

[Protocol Name]

0x...

Arbitrum One

Component Name
Protocol
Address

[Component Name]

[Protocol Name]

0x...

discriminate