Guide for Asset Managers
Nashpoint is a smart-contract protocol enabling asset managers to create, manage, and upgrade on-chain diversified investment products integrating RWAs and DeFi.
The core smart contract on Nashpoint is the Node. Each Node is an ERC-20-compliant independent onchain investment fund structure that can be created instantly and operated independently by its creator. Once deployed, it can be upgraded and reconfigured by the asset manager over time as needed.
Each Node accepts user funds and issues share tokens to depositors, following the standard ERC-4626 interface. At regular intervals—defined in the contract by the asset manager—our automation services allocate user funds to the selected strategies.
Nodes can be configured to allocate capital across both DeFi and RWA investments. Today, any ERC-4626 or ERC-7540 vault can be integrated into a Node. Over time, more integrations will be added—such as Merkl, DEX strategies, and additional RWA protocols.
Deploying a Node
Nashpoint provides a Factory contract that enables permissionless creation of a fund (Node contract), similar to creating an LP pair on a permissionless DEX like Uniswap. Upon deployment, the asset manager defines the key rules that govern performance and behaviour.
This includes:
- The deposit asset (e.g., USDC)
- The strategies to invest in and their relative weights
- The amount of liquid asset to hold in reserve
- Fees
- Rebalance frequency
The manager (node Owner) must also grant permission to a rebalancer account, enabling our offchain services to execute the strategy.
Once set, only the manager account can update these parameters. The Node contract itself is immutable; the logic cannot be altered in any way, except via configuration changes by the manager.
Operating a Node
Once deployed, a correctly configured Node operates autonomously. A manager can update the strategy frequently (e.g., several times per day) or take a more passive approach (e.g., monthly or quarterly). In either case, the automation will continue to execute the defined strategy.
Nashpoint’s automation service will detect any new Node and begin allocating funds according to the manager’s configuration. User withdrawals are also handled by the automation system. Withdrawals operate using an order book-like system: users request to redeem shares, and during the next rebalance window, funds are processed—first from the reserve, then from underlying investments if needed.
Managers can configure the order in which underlying investments are withdrawn. The intended behaviour is to prioritize the most liquid assets first. This protects depositors from unnecessary execution costs. Only once liquid reserves are exhausted will the automation begin to redeem less liquid positions, such as RWAs requiring offchain settlement. If a delay is required, redemption requests will be processed on a FIFO (first in, first out) basis.
Managing a Node
Managers can continuously update a Node’s behaviour and strategy. For example, they may adjust fees, rebalancing frequency, allocation weights, or add/remove components. These updates are picked up by the automation service, which rebalances accordingly. All parameters defined during deployment can be updated later by the manager.
Upgrading a Node
The Node contract handles core accounting and rules, but it does not directly contain logic for interacting with other protocols. Instead, Nashpoint is designed as a modular system, where functionality can be extended over time.
Managers can add Router contracts to integrate with new protocols, or Quoter contracts to support complex pricing mechanisms like swing pricing. These modules are always optional and controlled by the manager. The system design ensures no forced upgrades are possible at the smart contract level.
To discuss creating a fund on Nashpoint reach our to our team
Try It Now, Earn Rewards
Nashpoint’s RWAFI Fund is live on Arbitrum One. Depositors in the fund will earn points toward a future token airdrop.