FortisX asset management

On-chain asset management for staking

FortisX provides an analytical and allocation layer for staking inside individual networks. The engine monitors validators, pools, and on-chain metrics, maintains target allocations, and revisits positions without cross-network auto-rebalancing.

Learn More Open App

How asset management works

From network data to executed allocations

FortisX continuously ingests on-chain data across validators, pools, and networks: participation, commissions, performance, concentration, and protocol events. This stream of metrics is the foundation for every allocation and risk decision in the system.

Based on these metrics, the engine maintains target allocations inside each network, reflecting risk policies, diversification limits, and validator selection rules. Policies are explicit, and the same datasets are available via API for transparency.

When the data changes enough to justify action, FortisX adjusts staking positions across validators and providers within the network. Internal liquidity pools are used to reduce downtime during these changes, keeping capital productive while native positions are moving.

Allocations, risks, and liquidity usage are monitored over time, with periodic reviews by the engine. Asset managers see the resulting positions, historical decisions, and current exposures, so on-chain staking fits into their broader portfolio and risk processes.

Operational liquidity layer

Liquidity layer for staking portfolios

FortisX internal liquidity pools form an operational layer on top of staking and risk policies. This layer buffers the difference between slow blockchain mechanics and faster portfolio requirements, so allocations, entries, exits, and payouts can follow predictable rules while native positions in the network move in the background.

Fast entry into staking

New allocations can enter staking from supported assets without waiting for slow operational cycles in the network. The engine uses internal liquidity to route these allocations into native staking positions under the current policies.

Instant-unstake within the network

Participants can exit staking under predefined conditions while native unbonding continues in the background. Liquidity from the pools covers the early exit, and once unbonding completes, native funds return to the pool according to its rules.

Rebalancing without downtime

When allocations are moved between validators or strategies, internal liquidity is used so that capital remains productive during the transition. Native positions can be closed and reopened under the hood while portfolios keep their target exposures.

Smoothed reward payouts

Native rewards arrive according to the network’s own schedule, which is not always regular. Liquidity pools help transform these flows into more predictable payout patterns, aligning reward schedules with portfolio and reporting needs.

Working with supported assets

Strategies can be funded, maintained, and exited using supported assets that differ from the underlying staking token in the same network. The liquidity layer handles the necessary conversions and timing gaps under the engine’s policies.

Infrastructure yield for LP

Liquidity providers share in the economics of the liquidity layer: swap fees and spreads, premiums for fast exits, compensation for covering rebalancing flows, and staking or LST yield on the portion of pool liquidity placed in native positions.

Network coverage

Asset management across major networks

FortisX runs its analytical and allocation engine per network, covering Ethereum, Solana, Polkadot, Avalanche, Cosmos and others. Each network has its own metrics, policies, and liquidity settings, while the interface brings these positions and risks into a single view.

FAQ

Frequently Asked Questions

It means that the analytics and allocation engine operates separately for each network: capital distribution is reviewed across validators, pools, and strategies inside a specific chain. Decisions about how much capital to allocate to a given network as a whole sit outside this layer and are defined on the user side or by external processes.

The engine relies on on-chain metrics for validators, pools, and the network itself: participation, fee parameters, performance, stake concentration, network events, and other observable indicators. These inputs are used both to compute target allocations and to decide when positions inside each network should be revisited.

Reviews are not tied to a rigid calendar schedule. The engine reacts to changes in the data and to thresholds set in the policies. The focus is on responding to meaningful shifts in metrics while avoiding unnecessary reshuffling. As a result, adjustments happen when changes in the network accumulate to a significant level, not on every minor fluctuation.

The liquidity layer creates a buffer between blockchain speed and portfolio requirements. It allows entering and exiting staking under more predictable rules (including instant-unstake) while native unbonding continues in the background. The availability of faster operations depends on how much liquidity is in the pools and on how its usage is configured, which needs to be taken into account when planning.

Native rewards arrive into the pool according to the network’s own logic, which can be uneven and not perfectly predictable. The liquidity layer uses these inflows as a source for payouts on the chosen schedule and, where configured, in selected payout assets. The time lag between when rewards hit the pool and when they are paid out becomes part of the liquidity pool’s economics.