waveygist
created:
by spalen0

Infinifi Shorttimelock - 11/08/2026 10:04 - LOW

Summary

Adds RWAEscrowRouterFarm as type-2 farm to FarmRegistry. Routine permissioned addition, no parameter changes or fund movements.

Call Flow

From: 0x4B174afbeD7b98BA01F50E36109EEE5e6d327c32

  1. addFarms(uint256,address[]) on 0xF5f2718708f471e43968271956CC01aaA8c46119 (FarmRegistry)

Analysis

What each call does and why

The transaction executes a single call on the FarmRegistry:

  • addFarms(uint256 _type, address[] _list)
    _type = 2, _list = [0x79e1B8e45932A7C802eA3dAb3844e5DEa68d971f]

This function registers one or more farm contracts under a given “type” category within the protocol’s farm registry. Only accounts holding the CoreRoles.PROTOCOL_PARAMETERS role can call it (as enforced by the onlyCoreRole modifier). The parameter _type = 2 indicates the farm category — likely a specific class of farm, such as RWA-backed escrow router farms. The newly added address is the RWAEscrowRouterFarm contract.

Parameter values and significance

  • _type = 2: no prior value available for comparison; this is the type being assigned to the new farm. The registry likely stores mappings from type to a list of farm addresses, enabling the protocol to query farms by category.
  • _list = [RWAEscrowRouterFarm]: only one address is added. The contract source indicates that _list can be an array of arbitrary length, so this is a minimal addition.

Asset/token flow changes

No tokens or ETH are moved by this transaction. The function only updates internal storage.

State changes

  • The FarmRegistry contract will append the RWAEscrowRouterFarm address to the list of farms for type 2. This is a single storage write.
  • No other state variables are affected. No balances, allowances, or governance parameters are altered.

Risk assessment

Risk: LOW

  • Permission control: The function is gated by a core role, meaning only authorized protocol operators can register farms. This reduces the likelihood of rogue additions.
  • No fund movement: No assets are transferred, approved, or locked. The transaction solely extends the registry’s list.
  • No parameter changes: Fee rates, thresholds, or any operational parameters remain untouched.
  • Dependency on the added contract: The risk level assumes the RWAEscrowRouterFarm contract itself is non‑malicious and correctly implemented. If that contract contained exploitable logic, it could affect users after they interact with it, but the registration action alone does not introduce that risk — it only makes the farm discoverable by the protocol. The monitoring team should verify the deployed bytecode of the RWAEscrowRouterFarm against its source (if available) to rule out any hidden functionality.

Observations

  • The transaction is straightforward and follows the standard pattern for adding a new farm to the registry.
  • No batch processing or edge‑case handling (e.g., duplicate address checks are presumably handled inside the contract).
  • The call does not emit any critical events beyond the standard FarmAdded event (if implemented); the monitoring team can confirm the event signature upon execution.