Independent digital‑asset verification and security assessment.

Last updated: 17 October 2026

A token’s name, symbol and logo establish nothing. They are strings an issuer chose. ACV answers a narrower and more useful question: is this contract the asset you think it is, and what can whoever controls it still do to you?

ACV is Violet Sky Security’s digital‑asset verification service for exchanges, custodians, financial institutions and real‑world‑asset infrastructure. It resolves asset identity on‑chain, evaluates security‑relevant properties (issuer controls, contract privileges, upgradeability, transfer restrictions) and issues a cryptographically signed verdict with the evidence attached, so the recipient can re‑check the conclusion rather than take our word for it.

ACV
Verify the asset.
SPT‑Txn
Authorize the transaction.

The two are independent. ACV is a commercial subscription product, licensed separately; it is not a component of the SPT‑Txn open‑source framework and is not covered by its Apache‑2.0 licence. It is independently deployable and does not require SPT‑Txn.

The problem

Two contracts can present the same name, the same symbol and the same decimals. Only one of them is the asset your desk thinks it is trading. Identity is the first problem, and it is the easy one.

The harder problem is that identity is not a permanent property. A contract that was safe at listing can change afterwards. An upgrade authority can be transferred. A pause, freeze or blacklist capability can be introduced or exercised. An issuer can acquire control over transfers it did not previously have. A one‑time smart‑contract audit describes a snapshot; it does not tell an operator that the snapshot stopped being true last Tuesday.

What ACV does not claim. ACV verifies on‑chain facts and the evidence behind them. It does not verify off‑chain ownership, legal enforceability, reserve adequacy, or that a real‑world asset exists. Where an asset declares backing, ACV records what is declared and where it is declared, not whether the declaration is true.

What ACV verifies

Evidence and assurance

Every assessment is a signed artifact, not a dashboard reading. A verdict carries the evidence it was derived from, the sources it was derived from, and the time it was derived, so a counterparty, an auditor or a regulator can re‑run the check and disagree with the conclusion on the merits.

Verdicts are graded, and a missing answer is not a pass

PASS REVIEW HOLD FAIL BLOCK

ACV distinguishes this is fine from this needs a human from we could not establish this to the standard required. That distinction is the product. A verification service that returns a pass when it cannot see clearly is worse than no service at all, because it launders uncertainty into confidence.

Fail‑closed, by construction

An explicit limitation, stated up front. An identity PASS is not a statement about transfer eligibility. ACV establishing that a contract is the asset it claims to be says nothing about whether a specific transfer between two specific parties is permitted. Those are different questions and ACV answers only the first.

Institutional use cases

Current status

Stated plainly, because the difference between what runs and what is planned is the thing a technical reader most needs and most often cannot get.

CapabilityStatus
EVM verification (Ethereum, Base)Implemented
Signed verdicts and evidence artifactsImplemented
Signed asset registry, versioned and expiringImplemented
Further EVM networksShort‑dated; the adapter pattern is shared
HederaImplemented, capped below PASS pending verified source assurance
SolanaSpecified and hostile‑reviewed; implementation in progress
Algorand, XRPLResearched; not built
Maturity, without varnish. ACV is pre‑production. It has not been externally audited, it has no production deployments, and it is offered for evaluation and design‑partner engagement rather than as a generally available service. Any verdict or coverage claim on this page is subject to that.

Commercial model

ACV is an enterprise digital‑asset verification and security assessment platform, available independently or as an optional integration with SPT‑Txn. Contact Violet Sky Security to discuss institutional use cases and commercial access.

This is a deliberate departure from SPT‑Txn, and worth being precise about so nobody infers the wrong thing from the rest of this site. SPT‑Txn’s verifier, decision core, adapters and token formats are open source under Apache‑2.0 and always will be; what is paid there is operating a fleet of enforcement points and proving compliance with them. ACV is not part of that open‑source boundary. It is independently licensed, commercially, and its verification service is not free.

Engagements run as self‑hosted evaluation under NDA, shadow mode first: ACV renders verdicts alongside an existing process without gating anything, so a prospective operator can see what it would have refused before anything depends on it.

Two independent products, one complementary trust model

ACV establishes evidence about the asset. SPT‑Txn determines whether a transaction is authorized. Each is useful on its own and neither requires the other.

ACV and SPT-Txn as two independent products with an optional integration ACV establishes evidence about an asset and issues a signed assessment. SPT-Txn decides whether a specific transaction is authorized and issues a signed receipt. Each is independently deployable. Optionally, SPT-Txn can take a current ACV assessment as one additional authorization condition; in ACV-REQUIRED mode anything other than a current verifiable PASS fails closed. ACV Verify the asset Establishes evidence about the asset: identity, issuer controls, privileges. OUTPUT: SIGNED ASSESSMENT SPT-TXN Authorize the transaction Decides whether this transaction was authorized, and proves it offline. OUTPUT: SIGNED RECEIPT OPTIONAL INDEPENDENTLY DEPLOYABLE INDEPENDENTLY DEPLOYABLE When integrated SPT-Txn can take a current ACV assessment as one additional authorization condition. In ACV-REQUIRED mode, anything other than a current, verifiable PASS fails closed.

The integration is a condition, not a pipeline. An institution can run ACV with no SPT‑Txn deployment at all, or run SPT‑Txn against its own policy with no ACV. Where both are deployed, an authorization can be made to depend on a current, signed assessment of the asset being moved, and each half stays independently verifiable.

SPT‑Txn framework →
rudi@violetskysecurity.com