Loading ForensicBlock
Preparing your blockchain forensics platform...
Preparing your blockchain forensics platform...
Digital assets is broader than crypto. The firm encounters NFTs (high-value collectibles in divorce; rug-pull collections), identity / soulbound tokens (regulatory credentials, KYB attestations), and registry entries (ENS, .sol domains). We index them as first-class typed assets — cross-matter correlation just works.
5 classes: fungible / nft / identity / registry / other. Each carries the right field set (NFT has token_id + preview; identity has subject_address; registry has the domain string).
Indexed by (chain, contract, token_id). When two matters touch the same NFT or ENS, the conflict check + cross-matter search surface it (within privilege scope).
first_observed_at + first_observed_via (investigation / screening / manual / api). The asset record carries its own origin story.
/organizations/[id]/digital-assets — card grid, filterable by class.
Class-aware dialog. NFTs get a preview URL field; identities get subject address.
Unique constraint enforces correlation surface. Two matters touching the same asset surface in conflict check.
When an NFT is the subject of a matter, promote-to-exhibit allocates a Bates-style exhibit number for the matter.
Sealed reports carry digital_asset_links — every report cites the assets it touched, with provenance.
Honesty rail
We don't pretend to own a label database for every NFT collection on Ethereum. We index what your firm touches. Cross-matter correlation surfaces because YOUR matters share the asset, not because we attribute it independently.
Book a demo and bring a closed matter (or a hypothetical one).