Skip to content

Clarify NAV semantics: make navBalance optional in FYV#194

Draft
liobrasil wants to merge 1 commit intoloic/pkm-385-add-nav-based-balance-to-yield-vault-strategiesfrom
lionel/nav-balance-optional-nil
Draft

Clarify NAV semantics: make navBalance optional in FYV#194
liobrasil wants to merge 1 commit intoloic/pkm-385-add-nav-based-balance-to-yield-vault-strategiesfrom
lionel/nav-balance-optional-nil

Conversation

@liobrasil
Copy link
Contributor

@liobrasil liobrasil commented Mar 2, 2026

Summary

  • make Strategy.navBalance return UFix64? and default to nil instead of falling back to availableBalance
  • make YieldVault.getNAVBalance return UFix64?
  • update PMStrategiesV1 NAV overrides/helpers to return optional values
  • in _navBalanceFor, return nil on missing ERC4626 config/call data instead of panicking in read path

Why

availableBalance is a withdrawable/health-constrained metric, not mark-to-market NAV. This keeps semantics explicit while preserving backward compatibility for non-ERC4626 strategies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant