Welcome to the new dacs.io: same team, same address, new look. Spotted something off? Tell us

Verification of digital asset holdings

An independent statement of what an entity holds in digital assets — where it sits, who controls it and what it was worth on the day — prepared so an auditor can rely on it.


Independent verification of self-custody holdings, reported under ASRS 4400.

What a verification of holdings is

A self-managed super fund holds assets. Every one of them — property, shares, cash — has to be evidenced to the fund's auditor each year. Digital assets are no different. The problem is that the usual evidence (a statement from a bank or a registry) does not exist for a wallet or an exchange account.

A DACS verification fills that gap. We independently confirm the holdings against the exchange or the blockchain, price them on the reporting date, tie them to the entity, and put it all in one report.

Why we call it an attestation

To attest is to bear witness. An attestation is a formal, evidenced statement — the same root as testimony. A DACS attestation report is exactly that: a statement of fact about a holding, made by an independent party, from evidence that party collected itself. The customer-facing word is verification; the report you receive is an attestation report.

Why SMSFs need it

An SMSF gets concessional tax treatment because it submits to an annual independent audit. The audit has component parts an auditor must satisfy — existence, ownership, valuation and control of every asset. For digital assets, a DACS report is how those parts get satisfied.

Who we work with

Two ways DACS is used

What the report contains

A DACS attestation report is a standalone evidence file, structured the way an SMSF auditor works through an asset: what the fund holds, where each holding sits, which procedure tested it, what it was worth at the balance date — and, just as deliberately, what fell outside scope and what the findings do not assert.

Engagement frame

The ASRS 4400 basis, the DACS reference, the fund, trustee, accountant and auditor, the financial year, balance date and verification date.

Scope and method, platform by platform

Each wallet or exchange account, the procedure applied to it, and the assets it covers.

What was excluded, and why

Holdings the trustee disclosed that no procedure could test. Named, with the reason.

Methodology

How control was tested: cryptographic handshake, full-population on-chain scan, view-key ingestion, authenticated read-only exchange API.

Findings

A dated line for every procedure performed and what it evidenced.

Balances and valuation

Every holding by platform: quantity, DAVO™ VWAP price at the balance date, value and subtotals.

Caveats and evidence register

Numbered limitations cited where they apply, plus what DACS retained and how the auditor requests it.

Seal

A SHA-256 fingerprint and QR code. Alter one byte and verification fails.

What every report confirms

Ownership

The assets exist and belong to the entity — verified directly against exchanges and blockchains, not against statements the holder prepared.

Control

The entity controls the assets. Exchange-held balances are confirmed by read-only API pull from the venue; self-custodied wallets are confirmed on-chain from the public address.

Valuation

Holdings are priced by DAVO™, DACS's Digital Asset Valuation Oracle, using volume-weighted average prices from independent exchange sources at the reporting date.

Entity linkage

KYC and KYB procedures tie each holding to the entity itself — a super fund, a company, a trust — not to an individual personally. This is the link most audits cannot otherwise evidence.

Annotated sample DACS attestation report — cover page and sealed execution page, six numbered callouts

SAMPLE REPORT

See what your auditor receives

An annotated sample attestation report — the cover page and the sealed execution page, with six numbered callouts. The legend is below.

1 · Standards basis

Every report is an agreed-upon procedures engagement under ASRS 4400. It says so on the first line, so an auditor knows how to treat it before reading further.

2 · Reference, fund and dates

Our reference, the fund, trustee, accountant and auditor, the financial year, the balance date and the verification date — the frame the auditor files it under.

3 · Platforms and methods

Where the assets sit and which procedure was applied to each: cryptographic handshake, view-key scan, read-only exchange API, DAVO™ valuation.

4 · Scope statement

What was done, what was not, and which caveats apply. No opinion, no assurance conclusion — findings only.

5 · Signed by an authorised officer

Who signed, in what capacity, and when. The visible signature and an embedded digital signature.

6 · Seal and QR code

The seal ID is a SHA-256 fingerprint of the file. Scan the QR code or visit the URL, drop your copy of the PDF on the page, and it tells you whether a single byte has changed.

Why auditors ask for it

Auditors must obtain sufficient appropriate evidence under ASA 500 before signing off. For digital assets, that evidence has historically been thin:

  • Exchange screenshots
  • Wallet addresses without proof of control
  • Prices pulled from whichever website the holder chose

A DACS verification report replaces all of that with one document an auditor can rely on and independently check.

Get your holdings verified

Fixed price for straightforward holdings. Scoped in one conversation for everything else.