> For the complete documentation index, see [llms.txt](https://nashpoint.gitbook.io/nashpoint/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nashpoint.gitbook.io/nashpoint/routers.md).

# Routers

### Overview

Routers are specialized contracts that enable Nodes to interact with different types of yield-bearing vaults and DeFi protocols. They abstract away the complexity of various asset interfaces, providing a standardized way for Nodes to manage different types of assets while maintaining security and consistency.

### Adding New Routers to the Protocol

1. **Registry Owner Actions**
   * Deploy the new Router implementation
   * Add Router address to NodeRegistry using `setRegistryType`
   * Whitelist initial supported components using `batchSetWhitelistStatus`
   * Set appropriate tolerance values for the Router
2. **Node Owner Actions**
   * Add Router to Node using `addRouter`
   * Add desired components using `addComponent`
   * Configure component allocations and parameters
   * Update liquidation queue if necessary

### Adding New Components to Routers

1. **Security Review**
   * Verify component contract code and security
   * Ensure component implements required interfaces (ERC4626/ERC7540)
   * Validate component's risk parameters and behavior
2. **Registry Owner Actions**
   * Review component for protocol compatibility
   * Whitelist component on appropriate Router using `setWhitelistStatus`
   * Set any component-specific parameters
3. **Node Owner Actions**
   * Add component to Node using `addComponent`
   * Set target allocation and maximum delta
   * Specify Router for component interaction
   * Update liquidation queue position if needed