Independent Singapore VCC guidance
Direct answer
Treat a digital-asset fork as an event requiring separate ownership, control, security, quantity, recognition, valuation and disposition decisions. Freeze the pre-event position and wallet evidence, identify which chain and asset the VCC can actually control, and prevent unapproved claiming, signing or transfer. Ask the administrator and valuation owner to document whether a supportable value can enter NAV, with uncertainty and liquidity visible. The manager should compare hold, claim, transfer, sell or decline-support options, record conflicts and authority, and keep investors informed through the fund's existing disclosure framework without promising value or access.
At a glance
- A protocol event does not prove that the VCC controls a new asset.
- Protect keys and operations before attempting to claim economic value.
- Separate ownership, recognition, valuation and disposition approvals.
- Keep unsupported or inaccessible assets visible as exceptions, not hidden gains.
Who this is for
- Digital-asset VCCs and sub-funds exposed to a chain split, forked token or closely related protocol distribution.
Important exclusions
- Tax, legal or accounting advice on a specific asset, or a recommendation to support, claim, trade or ignore a fork.
Open an event file before taking action
Create one event record containing the affected asset, chain, expected activation point, authoritative technical information, custodian or wallet-provider position, pre-event holdings, wallet addresses, delegated staking or lending status, restrictions and relevant VCC or sub-fund. Preserve the data and system state used to establish the pre-event position. Name the investment, operations, technology, security, compliance, administrator and valuation owners. No one should claim, sign, broadcast or transfer a forked asset merely to test access. First determine whether that action could expose keys, replay transactions, breach provider terms, interrupt custody support or create an uncontrolled record that the administrator cannot reconcile.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority- Pre-event position and wallet evidence are frozen by VCC and sub-fund.
- Authoritative protocol and provider information is separated from market commentary.
- Custody, staking, lending and smart-contract dependencies are identified.
- Signing, claiming, transfer and communication authority is documented before action.
- Administrator and valuation owners know how the event will enter their exception process.
Related guidance: VCC directors and fund-manager roles
Decide whether the VCC controls the asset
Economic expectation is not the same as control. Establish the chain state, entitlement basis, quantity logic, wallet or custodian support, access conditions and restrictions. If assets sit with a custodian, obtain evidence of the provider's support policy, allocation method and operational timeline. If the VCC controls wallets directly or through another arrangement, verify that approved signers and secure procedures can access the new chain without exposing the original asset. Account for balances committed to staking, lending, bridges or smart contracts separately because the protocol event may treat them differently. Keep uncertain quantities outside an approved ledger balance until the evidence and accounting conclusion are sufficient.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of Singapore- Ownership is supportedProceed to control and quantity tests while preserving the legal and operational evidence.
- Provider allocates laterRecord a monitored contingent event and do not assume timing, quantity or accessibility.
- Wallet access is unsafePrioritise protection of existing assets and evaluate a controlled alternative or no-claim route.
- Entitlement is disputedEscalate for appropriate advice and keep the event outside an unsupported NAV gain.
- Asset is controlledMove to recognition, valuation and disposition decisions under separate approved authorities with recorded evidence.
Protect keys, providers and operating continuity
A fork can create operational threats even if the new asset has little expected value. Review software provenance, replay protection, node or wallet compatibility, signer access, hardware support, provider dependencies, chain monitoring and incident response. Use segregated testing and controlled data. Do not introduce unreviewed software into the production wallet environment. Ask the custodian or technology provider how it will protect the original asset, prove balances, manage chain identifiers, isolate transactions and communicate incidents. Plan for degraded service if deposits, withdrawals or valuation feeds pause. The VCC's decision should reflect end-to-end fund continuity, not only whether a wallet interface shows a new balance.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore| Risk | Evidence request | Stop condition |
|---|---|---|
| Key exposure | Approved signing design and environment separation | Claim requires unreviewed software or uncontrolled key use |
| Replay or chain confusion | Provider and technical control explanation | Original-asset movement cannot be isolated safely |
| Provider dependency | Support policy, allocation method and incident route | Provider cannot explain custody or balance treatment |
| Data integrity | Chain identifiers, wallet mapping and quantity proof | Administrator cannot reconcile the event to fund ownership |
| Service disruption | Withdrawal, pricing and recovery plan | Critical fund operation cannot continue within approved tolerance |
Related guidance: digital-asset wallet recovery drill
Separate recognition from valuation
The fund may have evidence of an entitlement before it has secure access, reliable quantity data, an approved accounting conclusion or a supportable value. Keep these decisions separate. The administrator should record the evidence and proposed treatment, while the valuation owner assesses available markets, transferability, liquidity, price quality, concentration, restrictions and the cost or risk of realisation. A displayed exchange quote does not prove that the VCC can deposit, sell or settle the asset. Compare independent sources and challenge thin, fragmented or self-referential markets. If value cannot be supported, document the uncertainty and approved NAV treatment without implying that the asset is worthless or certain to become realisable later.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore| Decision | Question | Evidence |
|---|---|---|
| Entitlement | Does the event allocate an asset to the VCC or sub-fund? | Pre-event position and protocol or provider allocation |
| Control | Can authorised arrangements access and protect the asset? | Wallet, custody, signing and restriction evidence |
| Quantity | Can the amount be reproduced and reconciled? | Chain, wallet, provider and administrator records |
| Recognition | What approved accounting treatment follows from the facts? | Administrator paper and responsible approval |
| Valuation | Is a supportable value available for the fund's NAV process? | Market, liquidity, transfer and valuation analysis |
Related guidance: staking-reward reconciliation before NAV · asset valuation override decision
Compare claim, hold, transfer and disposal options
Prepare a decision paper that compares not claiming, monitoring, claiming to secure control, holding, transferring to a supported provider or disposing under the investment mandate. For each option, show security exposure, operational dependency, liquidity, valuation uncertainty, transaction authority, conflicts, service-provider capability, cost and investor impact. Confirm that the manager's mandate and the VCC's governance support the chosen action, and obtain specialist advice where the documents or asset treatment are uncertain. Do not let the expected token value dominate the risk comparison. A low-value asset may create disproportionate key and provider risk, while declining immediate support may preserve assets but require ongoing monitoring and disclosure.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority| Option | Potential benefit | Decision risk |
|---|---|---|
| Monitor without claiming | Avoids immediate signing and software risk | Access or evidence may become harder later |
| Claim under controlled process | Secures supported ownership and quantity evidence | Introduces key, software and transaction risk |
| Hold with provider | Reduces immediate transfer complexity | Creates provider, liquidity and valuation dependency |
| Transfer to supported custody | May improve operational control and reporting | Requires safe transfer and complete successor acceptance |
| Dispose under mandate | May remove an unsupported operational asset | Needs valuation, liquidity, authority and execution evidence |
Related guidance: VCC investment-rule system test
Frequently asked questions
Does a hard fork automatically create a VCC asset?
No. The event may create an expected entitlement, but the fund still needs evidence of ownership, control, quantity and an approved accounting conclusion. Custody terms, wallet state, protocol treatment and restrictions can affect whether the asset is accessible and supportable.
Should the VCC claim every forked token?
Not automatically. Compare expected benefit with key, software, provider, liquidity, valuation and mandate risks. A decision not to claim immediately should still be documented, monitored and revisited if evidence or operational support changes.
Can an exchange quote be used directly in NAV?
A quote is one input, not a complete valuation conclusion. Assess whether the market is reliable, accessible to the VCC, sufficiently liquid, transferable through approved arrangements and consistent across independent sources. Record restrictions and execution uncertainty.
What if the custodian supports the fork later?
Keep the event open with the provider policy, expected allocation method and review trigger. When support arrives, authenticate the allocation, reconcile quantity and control, and route recognition and valuation decisions again rather than backdating an unsupported balance.
How should inaccessible forked assets be reported internally?
Use an exception register that identifies the affected sub-fund, evidence, estimated exposure range if supportable, access barrier, provider dependency, decision owner and next review trigger. Avoid treating absence from the ledger as absence of operational risk.
Official sources and further reading
- Risk Management Practices for Fund Management Companies (Monetary Authority of Singapore)
- Governance and Management of Variable Capital Companies (Monetary Authority of Singapore)
- Operational Resilience for Financial Institutions in Singapore (Monetary Authority of Singapore)
- VCC Features, Eligibility and Requirements (Accounting and Corporate Regulatory Authority)
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.