Skip to content

Troya

Verifies that a physical asset exists and is in the declared condition, then certifies it tamper-proof.

Vertical: Business management and finance Solid base

What it is for

Certify in a tamper-proof way that a physical asset — a building, a machine, a shipment — exists and is in the condition declared, so it can be financed or tokenised with confidence.

What it does

Verifies asset condition by combining several sources, issues a cryptographically signed opinion, records it on a blockchain and automatically applies the legal rules of the jurisdiction it is operated from.

Sector

Fintech, real-world asset tokenisation and regulatory compliance.

What it improves

The main obstacle to real-world asset tokenisation is that nobody can check the digital asset corresponds to something real and in good condition. It also replaces manual allow-lists with automatic per-jurisdiction rules.

Target client

Tokenised investment platforms, asset financing, insurers and operators in crypto-regulated jurisdictions.

Status and maturity

Three components with their own test suites: an operational verification engine, compiled smart contracts and a live public API with usage billing and an integration kit.

Differentiator

Connects the verified physical world with programmable compliance; most projects solve only one of the two halves.

Commercial fit

Charged per verification and per volume through the API plus protocol participation. High potential and high regulatory risk: requires a licensed partner.

Architecture

Layered architecture

Three layers connecting the verified physical world with programmable compliance: a verdict engine that queries sources in parallel, a blockchain layer that anchors the verdict, and a public interface so other protocols can consume it.

  1. 01

    Verdict engine

    Queries all available providers in parallel — cadastral, valuation, physical condition, technical, legal, compliance, zone risk and geolocation — computes a weighted integrity score and emits a signed verdict with a deterministic fingerprint.

  2. 02

    Auditable log

    An append-only chained log that later proves a specific verdict was issued, verifiable from the chain itself.

  3. 03

    Blockchain layer

    Contracts for a verdict registry, asset-bound non-fungible token, per-jurisdiction restriction registry and regulated security issuance, with a proprietary bridge to publish and listen to events.

  4. 04

    Programmable compliance

    Jurisdictional restrictions execute in the contract, not on a central server: it replaces the manual allow-list with automatic rules.

  5. 05

    Public interface

    Service with per-client keys, per-tier limits, signed notifications to external systems and a documented integration kit.

Inventory

Status per component

A real inventory of the asset’s components with their declared status. We publish capability, never code or internal figures.

Built and testedFunctional with declared debtDesigned, not implementedWired; depends on a third party
  • Verdict engine and signing

    Built and tested

    Operational, with graceful degradation: if a provider fails the component is marked unavailable and the verdict is issued with reduced coverage, never invented.

  • Chained verdict log

    Built and tested

    Verifiable proof of issuance, the basis of trust in the protocol.

  • Smart contracts

    Built and tested

    A set of compiled, deployable contracts including the regulated securities standard.

  • Public interface with usage billing

    Built and tested

    Live, with key authentication, per-tier limits and signed notifications.

  • Per-jurisdiction data providers

    Wired; depends on a third party

    The interfaces assume no jurisdiction: each country is a concrete implementation of the same contract. Adding a country means adding a provider.

  • Public network deployment

    Designed, not implemented

    Ready for compatible networks; real production requires a licensed partner in the target jurisdiction.

  • Regulatory fit

    Functional with declared debt

    The asset’s main declared risk: high potential and high regulatory exposure. Not sold as solved.

This profile describes capabilities and status, not implementation. Code, architecture documentation and internal figures are shared under a confidentiality agreement during due diligence.