How noya-ai/noya-jul-2025-audit-scope works
Project type and purpose
• This is a suite of on-chain smart contracts written in Solidity (“noya-vault-contracts”).
• Purpose: Manage user deposits into vaults (minting shares), interact with external DeFi protocols, compute valuations, and support cross-chain operations via bridges and swaps.
File structure
• Top-level “contracts” directory subdivides into:
• accountingManager — the core Vault Manager
• connectors — protocol adapters (Aave, Curve, Uniswap, etc.)
• external — interface definitions & protocol library code
• governance — (on-chain governance entry points)
• helpers — omnichain handlers, swap handlers, oracles, and mocks
• interface — shared contract interfaces for accounting, swapping, oracles
• Build/config files: foundry.toml, hardhat.config.ts, tsconfig.json
• Tests: testFoundry utilities and mocks (excluded from audit scope)
Key insights from README
• Core modules in scope:
a. Accounting Manager (mint/burn ERC-20 shares, track deposits/withdrawals)
b. Connectors (deposit/withdraw assets to external protocols)
c. Omnichain Handler (LayerZero bridging & cross-chain messaging)
d. Noya Value Oracle (price/position valuation)
e. Noya Bridge & Swap Handler (LiFi-powered bridging, generic swap interface)
• External directories (externals, interfaces, mock) and LiFiImplementation.sol are out of audit scope.
Components
a. Users (EOAs or front-end)
b. Accounting Manager (Vault core)
c. ERC-20 Vault Token (shares)
d. Connectors (one per protocol)
e. External Protocols: Aave, Curve, Uniswap V3, Balancer, etc.
f. Noya Value Oracle
g. Swap Handler & Bridge Handler (LiFi abstraction)
h. Omnichain Handler (LayerZero endpoints)
i. Governance Module (if on-chain proposals exist)
j. External Services: LayerZero, LiFi, Price feeds (Chainlink or other oracles)
Relationships & data flows
• User → Accounting Manager: deposit(base token) → mint Vault Token
• Connectors ↔ External Protocol: call protocol contracts for asset management
• Connectors report positions/asset balances to Accounting Manager
• Accounting Manager queries Noya Value Oracle for valuations → computes share price
• Swap & Bridge Handler consulted when moving assets across chains or swapping tokens
• Omnichain Handler uses LayerZero to relay cross-chain instructions to connectors on remote chains
• Governance Module may call Administrative functions on Accounting Manager or Connectors
• All cross-chain calls pass through Omnichain Handler → LayerZero → target chain contracts
Architectural patterns & design principles
• Modular connectors (one adapter per DeFi protocol) for pluggability
• Single Vault core separating accounting logic from asset handling
• Oracle abstraction for on-chain valuation
• LayerZero-based omnichain messaging pattern for cross-chain operations
• Swap/Bridge abstraction (LiFi-agnostic) for future extensibility
Essential details to capture
• Vault token minting/burning flow
• Connector abstraction for each protocol
• Oracle valuation path back into accounting
• Cross-chain call chain: Accounting Manager → Omnichain Handler → LayerZero → Remote Connector
• Swap/bridge flow: Connector ↔ SwapHandler → LiFi → target DEX or chain