Independent Singapore VCC guidance
Direct answer
A digital-asset VCC should reconcile staking rewards from the protocol event to the controlled wallet, validator or custodian statement, administrator ledger and NAV. Record gross entitlement, actual receipt, validator or service deductions, slashing, lock-up status and the asset-owning sub-fund separately. Use approved valuation sources and cut-off rules for each token. A balance visible on-chain is not enough if ownership, availability, fees or pricing remain unclear. Unresolved differences should stay on an exception register and block unsupported income or asset recognition.
At a glance
- Separate entitlement, receipt, fees, restrictions and valuation.
- Map every wallet and staking account to one controlled sub-fund owner.
- Reconcile on-chain evidence with custodian, validator and administrator records.
- Escalate slashing, missing rewards and stale prices before NAV release.
Who this is for
- Digital-asset VCC strategies that stake tokens directly or through a custodian, exchange, validator or delegated service.
Important exclusions
- Tax advice, a recommendation to stake, or a conclusion about any token, protocol, provider or custody model.
Map the staking arrangement and ownership
Create a controlled inventory of the VCC sub-fund, token, wallet, custodian account, validator, protocol, delegation transaction and reward destination. Identify who controls keys or instructions, who can change the validator, where rewards land and whether they are automatically restaked. A wallet address is an identifier, not complete ownership evidence. Link it to board or mandate authority, custody records and the administrator security master. If one operational wallet services more than one strategy, the sub-ledger and transfer controls must preserve economic ownership. MAS governance, risk and valuation expectations remain relevant because staking combines delegated operations, asset safeguarding, data inputs and valuation judgments. Do not begin with a downloaded balance and infer the operating model afterward.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of Singapore| Element | Evidence | Control question |
|---|---|---|
| Sub-fund owner | Mandate and investment register | Which investor pool bears reward and risk? |
| Wallet or account | Custody record and approved address register | Who controls movement and changes? |
| Validator or provider | Executed terms and due diligence | How are rewards, fees and losses determined? |
| Reward destination | Protocol configuration and transaction evidence | Where should gross and net amounts appear? |
| Restrictions | Protocol and custody status | Are tokens transferable, bonded or pending release? |
Related guidance: digital-asset VCC operating risks
Define the reward event and cut-off
The policy should distinguish a reward that is estimated, earned under the protocol, claimable, received, restaked or still subject to reversal or slashing. Those states can occur at different times and may not support the same ledger treatment. Document the event used for recognition under the applicable accounting policy, the cut-off time, network source and confirmation standard. If the administrator uses a provider file, compare its event definition with on-chain or custodian evidence. Keep pending epochs or unfinalised events outside settled balances until the policy conditions are met. For an umbrella VCC, apply the same event logic consistently within the relevant sub-fund while keeping other sub-funds separate. Any policy change needs controlled approval and parallel testing before it affects NAV.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Singapore Statutes Online- Estimated onlyKeep an estimate distinct from recognised reward and record the uncertainty and source used.
- Protocol event completeTest the policy recognition point, ownership and confirmation standard before creating a ledger amount.
- Claimable but lockedRecord availability and restriction separately so the valuation and liquidity view remains accurate.
- Received or restakedTrace the exact wallet movement and update token quantity without duplicating the prior accrual.
- Reversed or slashedEscalate the loss, provider responsibility and valuation effect using current transaction evidence.
Reconcile gross rewards and provider deductions
Build the reconciliation gross-to-net. Start with the protocol or provider reward basis, then show validator commission, custody fee, exchange charge, network fee, withholding or another deduction only when supported. Avoid recording the net wallet increase as reward income if the same deductions are separately expensed, because that can double-count fees. Conversely, do not assume every difference is a fee; missed epochs, commission changes, slashing, timing and address errors require different treatment. Compare provider terms with actual deductions and investigate changes in rate or destination. Digital-asset administrators commonly support position, transaction and income categorisation, but the VCC and manager still need to challenge data lineage and ownership rather than outsourcing the conclusion.
Sources: NAV Fund Services · Monetary Authority of Singapore · Monetary Authority of Singapore| Line | Expected evidence | Exception to investigate |
|---|---|---|
| Gross reward entitlement | Protocol event or controlled provider calculation | Missing, duplicated or estimated event |
| Validator commission | Executed terms and event-level deduction | Unexpected rate or changed recipient |
| Custody or service fee | Contract, invoice or statement | Fee netted without supporting detail |
| Network movement | Transaction hash and wallet register | Wrong address or unsupported transfer |
| Net reward received | Controlled wallet or custody statement | Difference from calculated net amount |
| Restaked quantity | Delegation event and position record | Reward counted as both cash and staked asset |
Control pricing, restrictions and token quantities
Reward quantity and fair value require separate controls. First prove units by token and wallet. Then apply the approved price source, timestamp, market hierarchy and exception process. A token may be visible but not freely transferable because it is bonded, pending withdrawal, frozen or subject to provider controls. Record those restrictions for liquidity and valuation review rather than treating every unit as immediately available. Check token denomination, decimals, forks, wrappers and liquid-staking representations carefully; a symbol match is not enough. If the security master or price source changed, test historical continuity and approval. MAS valuation guidance supports reliable inputs, governance and independent challenge. Stale or unrepresentative prices should follow the established escalation process before NAV.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore- Reconcile native token units, wrapped tokens and staking representations as separate controlled instruments.
- Match wallet decimals and token identifiers to the approved security master before applying prices.
- Apply the authorised valuation source, timestamp and hierarchy for the relevant NAV cut-off.
- Record bonded, unbonding, claimable, frozen and freely transferable quantities separately.
- Escalate stale, missing or unrepresentative price inputs through independent valuation review.
Related guidance: VCC security-master change controls · stale-price escalation before VCC NAV
Frequently asked questions
Is an on-chain wallet balance enough for VCC NAV?
No. It shows a technical balance at an address, but the VCC must also prove ownership, sub-fund attribution, custody or key control, token identity, restrictions, fees, cut-off and valuation. Reconcile the balance with custodian, validator and administrator records, then resolve any difference before relying on it for NAV.
Should staking rewards be recorded gross or net of validator fees?
The controlled policy and provider terms determine presentation, but the reconciliation should expose both gross entitlement and every supported deduction. Recording only a net wallet increase can hide fee changes or missed rewards. It can also create double counting if the administrator separately posts the same validator or custody fee.
How should automatically restaked rewards be controlled?
Trace the reward event and the subsequent delegation or restaking event as connected but distinct records. Update the staked quantity only once, preserve the reward lineage, and confirm the wallet and validator destination. The administrator should not book both an income asset and another position increase without the approved accounting bridge.
What if a reward is claimable but locked?
Record the quantity and its status separately under the approved accounting and valuation policy. Claimable does not necessarily mean freely transferable. Provide the valuation and liquidity owners with the lock, unbonding or release evidence, and avoid presenting restricted units as immediately available cash or liquid inventory.
How should slashing appear in the control pack?
Identify the affected token quantity, protocol event, cause, provider responsibility, wallet and sub-fund. Reconcile the loss across on-chain, custodian, validator, administrator and valuation records. Escalate legal or recovery questions separately. Do not conceal slashing as a lower reward rate or unexplained price movement.
Official sources and further reading
- Variable Capital Companies Act 2018 (Singapore Statutes Online)
- IID 04/2025 Governance and Management of Variable Capital Companies (Monetary Authority of Singapore)
- Risk Management Practices for Fund Management Companies (Monetary Authority of Singapore)
- Valuation Practices for Fund Management Companies (Monetary Authority of Singapore)
- Digital Asset Fund Administration (NAV Fund Services)
Discuss a Singapore VCC structure
For help coordinating a Singapore VCC setup or corporate administration, contact Raffles Corporate Services.
General information only. This article is not legal, tax, regulatory or investment advice and does not imply affiliation with or endorsement by ACRA, MAS or IRAS.