> ## Documentation Index > Fetch the complete documentation index at: https://docs.yieldseeker.xyz/llms.txt > Use this file to discover all available pages before exploring further. # Continuous Monitoring > How Yieldseeker continuously evaluates protocols, markets, and portfolio health. # Continuous Monitoring Portfolio management does not end once funds have been allocated. Markets evolve continuously. Yields change, liquidity fluctuates, incentives expire, and new opportunities emerge. Rather than making a single allocation decision at deposit, the Allocation Engine continuously reassesses both existing positions and alternative opportunities as market conditions evolve. Monitoring is continuous, but changes are only made when they improve portfolio quality or enhance user safety. *** ## Verify, Don't Trust Wherever practical, Yieldseeker reads protocol state directly from smart contracts rather than relying on third-party dashboards or protocol-reported statistics. This philosophy reduces dependence on external services and helps ensure allocation decisions are based on the current on-chain state of each supported protocol. *** ## What Is Monitored? The Allocation Engine continuously evaluates multiple aspects of supported protocols, candidate vaults, and existing portfolio positions. Examples include: * Total Value Locked (TVL) * withdrawable liquidity * available lending capacity * protocol interest rates * vault share prices * reward emissions * collateral composition * underlying asset quality * protocol-specific oracle data These inputs are evaluated alongside the user's own preferences, constraints, and investment profile before any portfolio changes are considered. *** ## Direct On-Chain Reads Whenever practical, Yieldseeker derives information directly from protocol smart contracts. Examples include: * TVL and available liquidity * maximum deposit capacity * collateral dependencies * vault accounting * lending rates * share prices This allows the protocol to verify conditions independently rather than relying solely on external APIs or protocol-reported metrics. *** ## Asset Quality Assessment Yieldseeker also evaluates the quality of collateral assets backing supported vaults. Rather than assuming an asset is suitable simply because it has been listed by another protocol, the Allocation Engine considers factors such as: * on-chain liquidity * trading volume * market depth * transaction activity Assets that fail internal quality requirements may become ineligible for future allocations. *** ## Continuous Portfolio Optimisation As market conditions evolve, the Allocation Engine determines whether rebalancing would improve expected long-term portfolio quality. When appropriate, Agents may: * move capital between supported protocols * rebalance portfolio allocations * compound earned rewards * convert reward tokens into the portfolio's base asset Execution only occurs when the expected benefit justifies the associated transaction costs and remains consistent with the user's configured investment profile, preferences, and constraints. *** ## Protocol Safety Parameters Not every monitoring parameter is configurable by users. In addition to market conditions and user-defined preferences, Yieldseeker maintains a small number of protocol safety parameters that protect the integrity of the allocation framework. These parameters are managed by the protocol and cannot be overridden by individual Agents. For example, if a supported vault or protocol is identified as presenting an unacceptable level of risk—such as a security incident, operational issue, or other material concern—it can be marked as ineligible for future allocations. Where appropriate, Agents may also be instructed to withdraw from affected positions as part of a coordinated protocol-wide safety response. This allows the protocol to respond quickly to changing conditions while preserving the normal allocation process for all other opportunities. *** ## Continuous Risk Assessment Monitoring is not limited to identifying better yield opportunities. The Allocation Engine continuously evaluates whether existing positions continue to satisfy the protocol's eligibility requirements and safety parameters. If an existing position no longer satisfies those requirements—or becomes subject to a protocol safety restriction—the Allocation Engine may reduce or remove exposure where appropriate. This allows portfolios to adapt as the ecosystem evolves rather than relying on static assumptions established at the time of deposit.