No. TLAY provides machine-native technology and infrastructure. A machine account is a programmable account controlled by its owner, not a deposit account. Regulated payment and financial services are designed to be delivered through appropriate licensed partners.

TLAY — Economic Infrastructure for Autonomous Machines

Q: What is TLAY?

TLAY is the economic infrastructure for autonomous machines, and the trust layer for machine commerce. It gives robots and connected devices a programmable, owner-controlled account so they can work, earn, pay and build an operating history that anyone can verify and that payment, settlement and financial services can rely on.

Q: What is HashAnchor?

HashAnchor is TLAY's free, open-source verification infrastructure. It verifies machine-signed activity, links work to its payment events, batches records into a Merkle root and anchors that root on-chain, so any third party can independently verify the provenance and integrity of what a machine did — without trusting TLAY.

Q: What is the Machine Commerce Enabler?

It is TLAY's repeatable deployment pattern for turning an existing machine workflow into a pay to work to proof to settle loop. Built on BoAT and HashAnchor, it answers the same six decisions per scenario — the service, the unit, the pricing, the control path, the proof and the revenue routing. It is not a third product and not bespoke development from scratch.

Q: What is the machine commerce loop?

The loop is pay, work, proof, settle: a user pays in stablecoins, the machine is authorized on-chain and delivers physical work, BoAT signs proof of delivery, HashAnchor verifies it, and revenue is settled and distributed automatically. Every completed loop adds to the machine's verifiable operating history.

Q: How does TLAY make money if its core products are open source?

BoAT and HashAnchor are free and open source. TLAY does not depend on software license revenue: it earns from managed deployment, hosted verification and settlement, enterprise services, and the financial activity enabled through its network. It grows with the economic activity of the machines it connects.

01 Why TLAY

Machines can work. But they cannot yet participate economically.

Robots and connected machines can already sense, decide and act. But to receive payments, prove completed work and reach financial services they still depend on human accounts, cloud platforms and closed databases. What is missing is not a wallet — it is the full set of economic capabilities.

The machine works. The business belongs to someone else.

A machine becomes an economic participant when four questions have answers. For most fleets in the field, they don't —

Q·01

“Who controls this machine?”

Who owns it, who operates it, who may set its permissions. Today that answer lives in a platform account, not with the machine.

Q·02

“What is it authorized to do?”

How much it may spend, what it may buy, which jobs it may accept. Scoped economic authority is something almost no fleet system can express.

Q·03

“What work did it perform?”

It cannot demonstrate, to anyone who wasn't standing next to it, the work it delivered — or that this machine was the one that delivered it.

Q·04

“How does value move around it?”

Who pays, how revenue settles, how it splits between owner, operator and financier — and what record any of it leaves behind.

→ Identity · Authority · Proof · Transactions — the four capabilities an economic participant needs.

02 Core Products

Two open-source products. One economic foundation.

BoAT runs inside the machine. HashAnchor verifies what the machine did. Both are free and open source — device makers can embed them, operators can self-host them, and developers can extend them without asking permission.

◆ BoAT · inside the machine

Open-source economic runtime for machines

BoAT runs inside robots and connected devices, giving each machine a device-bound identity, owner-defined permissions, signing capability and payment authority. BoAT gives the machine controlled economic authority.

device-bound DIDon-device keyx402 · EIP-3009~58 KB

◆ HashAnchor · around the machine

Open-source verification infrastructure

HashAnchor verifies machine-signed activity, links work to its payment events, batches records into Merkle roots and issues receipts anyone can check. HashAnchor turns machine activity into verifiable economic records.

signature verificationMerkle anchoringportable receiptsdeclared trust tier

Core product · 01 Inside the Machine

BoAT — the Blockchain of AI Things.

A lightweight machine-economic runtime that embeds cryptographic and financial capabilities directly into the physical device — not a wallet app for humans, not a cloud API bridge. It is how a machine enters the on-chain economy natively, at the source.

It runs directly on IoT chips, robots and energy devices, written for resource-constrained hardware. The private key lives on the edge device, not on a central server — and the machine signs within the limits its owner sets.

private key · on-device

FootprintA lightweight runtime for resource-constrained hardware — IoT chips, robots, energy devices.

NeutralChain-neutral and hardware-neutral by design — it doesn't pick your stack for you.

AuthorityThe private key lives on the edge device, not a central server — and the machine signs within owner-defined policies.

Inside BoAT — value accrues, tier by tier~58KB fully loaded

TIER 0

Crypto

~40 KB

TIER 1

Identity

+2 KB · Ed25519 · DID

TIER 2

Attestation

+4 KB · SHA-256 · Merkle

TIER 3

Payment

+12 KB · x402 · EIP-3009

Core product · 02 Verification Infrastructure

HashAnchor — machine activity anyone can verify.

BoAT signs activity at the source. HashAnchor turns it into an economic record a stranger can check — signature verified, work linked to its payment event, batched into a Merkle root and anchored on-chain. Verifiable provenance and integrity, not blind trust.

01

Signed at the source

The machine signs what it did — at the source, with its own key, alongside the payment event it belongs to.

02

Verified, not assumed

Every signature is checked against the machine's registered identity before it is accepted. An invalid one is rejected.

03

Anchored on-chain

Records are batched into a Merkle root and written to the chain — permanent, public, ordered in time.

04

Independently checkable

Anyone can verify the receipt without trusting TLAY — and settlement, audit and financing can read the same record.

Verifiable by construction

Any third party can independently confirm four things from a single receipt, and needs to trust no one to do it. What a receipt establishes is provenance and integrity — where a record came from and that it has not been altered. It does not, on its own, make a sensor's reading true; that is what the trust tier below is for.

Merkle proof valid root anchored on-chain device signature valid key-custody trust tier

03 The Machine Commerce Enabler

From a connected machine to a working commerce loop.

Machine Commerce Enabler is how TLAY puts BoAT and HashAnchor to work in a real business. It is not a third product, and not bespoke development from scratch — it is a repeatable deployment pattern: the same six decisions, answered per scenario, connecting pricing, payment, machine control, proof of service and settlement into one deployable system.

01

Define the service

What the machine actually sells — energy, a session, a delivery, a job, a stream of data.

02

Set the unit

What one paid unit is: a use, a minute, a kWh, a kilometre, a completed task.

03

Configure pricing

Fixed, dynamic, or a live market price the machine reads at the moment of sale.

04

Connect control

What a payment is authorised to switch on, for how long, and how that authority is revoked.

05

Define proof

What evidence shows the work was delivered, who signs it, and at which trust tier.

06

Route revenue

How income settles and splits between owner, operator, maintainer and financier.

→ Answer the six and the machine has a business — the runtime, the verification and the settlement are already built.

04 How It Works

Pay → work → proof → settle.

Every time the machine does something worth money, the same four steps run. A user, a business or another machine pays; BoAT authorises and the machine works; BoAT signs and HashAnchor verifies; the Commerce Enabler settles and routes the revenue.

One loop is a transaction. Thousands become a track record.

Every loop builds a verifiable operating history — revenue and operating performance that can be attributed to an individual machine or fleet, not just to the company that owns it.

05 The Open Economic Network

Open products. An expanding economic network.

BoAT and HashAnchor are free and open source. Device makers can embed them, operators can self-host them, and developers can extend them without asking permission. TLAY connects the machine activity they produce to managed payment, settlement and financial services.

Free and open source

Network and services

BoAT brings device makers and fleets onto the network.

Machine accounts and payment connectivity.

HashAnchor standardises what an economic record looks like.

Hosted verification and settlement.

The Commerce Enabler turns deployments into real transactions.

Enterprise operations and financial services.

Developers extend it to new devices and new scenarios.

Payment, financing and insurance partners.

Open-source the economic infrastructure. Monetise the financial flow.

TLAY does not depend on software license revenue — it grows with the economic activity of the machines it connects.

More machines create more verifiable activity; better records attract more payment and capital providers; better services bring more machines onto the network. The network is designed to compound as more machines and service providers participate.

06 Financial Access

From verifiable activity to financial access.

Financial services are a consequence of the loop, not the top of the stack. Once machines produce records that hold up to inspection, the people who finance and insure them can price the risk on what the machines actually did. It runs in three steps.

STEP 01

Verifiable operating history

Every loop adds delivered work, utilisation, revenue and settlement to a record attributable to a specific machine or fleet — signed at the source, independently verifiable, and declared at a known trust tier.

STEP 02

Better risk assessment

With the owner's authorisation, financing and insurance providers can read that record to judge utilisation, revenue stability, operating risk and asset quality — instead of underwriting the parent company and inferring the rest.

STEP 03

Access to financial services

Owners and operators reach equipment financing, fleet finance, leasing, insurance, cash-flow financing and RWA capital through partners — priced against what their machines demonstrably did.

A machine's operating record stops being an internal log and becomes something capital can underwrite.

This does not eliminate risk — it makes risk visible. Machine performance, trust tier and cash flow, evaluated in the open. Financing and insurance partners still perform their own underwriting, and regulated services are designed to be delivered through licensed partners where required.

07 Trust You Can Grade

Not every record carries the same assurance.

Not every machine in the field can hold a key yet — so every HashAnchor receipt declares how the data was signed and where the key was held. A fleet can climb the ladder over time.

◌ Tier 1 · platform-custodied

Platform-signed

A platform or trusted gateway signs on the machine's behalf — a bridge for firmware that cannot yet hold a key.

◑ Tier 2 · device-bound

Device-bound

The key is bound to the specific device or its gateway, so every record ties back to real hardware.

◆ Tier 3 · device-resident

Device-resident

BoAT's edge signature: the machine holds its own key and signs at the source. The highest assurance available.

higher-assurance records → stronger underwriting → more efficient risk pricing. A fleet can climb the trust ladder over time, with no disruptive cut-over.

08 One Loop, Any Machine Business

One loop, wherever machines already do measurable work.

The unit of service, the pricing logic and the control adapter are configured per scenario — so a new machine business is assembled from the same core, not forked from it. What changes between verticals is what is sold and how it is proved.

◆ Robotics & Logistics

Robots that bill for the task they completed

A cleaning, inspection, delivery or handling robot sells a task. Payment authorises the run, the robot signs completion and custody at each hop, and revenue splits between the fleet operator and whoever financed the hardware.

unit: task · minute · deliveryproof: proof of taskresult: fleet revenue and cost record

◆ Energy & Charging

Energy agents that sell their own output

AI-managed solar, storage and charging assets export power, sign each kilowatt-hour at the source, and settle revenue automatically — assets that pay for themselves and can be financed against what they delivered.

unit: kWh · minuteproof: energy delivery attestationresult: PayGo settlement, asset financing

◆ Autonomous Compute

Compute fleets with a verifiable work record

Machines that prove the compute they performed and what it earned build an operating history at machine granularity — the basis for financing a fleet against what it delivers rather than what its owner promises.

unit: job · GPU-hourproof: compute delivery proofresult: micro-payments, fleet finance

◆ Commercial IoT & Machine Data

Machines and agents that sell usage by the unit

Dispensers, meters and instrumented equipment sell a use, a cycle or a reading. Physical-world data is attested at the source and priced per call, so AI agents and protocols can buy it directly through an open interface.

unit: litre · cycle · callproof: service completion · MCP + x402result: recurring revenue, operating credit

Reference implementation

eCandle — machine-native PayGo for energy devices

The first full deployment of the pattern, and the proof that the Machine Commerce Enabler is a way of building rather than a slide. A device is funded through an on-chain capital pool; a stablecoin payment activates it; BoAT signs the energy it delivers; HashAnchor verifies the record; revenue settles and splits automatically between the operator, the asset owner and the capital that financed it.

payment activates the device → energy is delivered → BoAT signs the service → HashAnchor verifies the record → revenue settles and distributes

09 The End State

Stand back, and TLAY's layers line up cleanly.

Two open-source products, one deployment pattern, one network — and a long-term destination.

TLAYthe infrastructure

The economic infrastructure for autonomous machines — what a machine must be able to do to work, transact and build a record.

BoATinside the machine

Runs inside the machine — identity, owner-defined permissions, signing and payment authority, at the edge. Free and open source.

HashAnchoraround the machine

Verifies machine activity and turns it into portable economic records anyone can check. Free and open source.

Commerce Enablerthe deployment pattern

Combines the two products into deployable industry solutions — pricing, control, proof and settlement, answered once per scenario.

TLAY Networkpayments · settlement · capital

Connects machine activity to payment, settlement and financial services — the layer TLAY operates and monetises.

Together, these layers enable a Smart Open Machine Economy — machines that don't just work, but participate.

SOME · global · permissionless · machine-native · composable

10 FAQ

Quick answers.

What is TLAY?

TLAY is the economic infrastructure for autonomous machines, and the trust layer for machine commerce. It gives robots and connected devices a programmable, owner-controlled account so they can work, earn, pay and build an operating history that anyone can verify — and that payment, settlement and financial services can rely on.

What is BoAT (Blockchain of AI Things)?

BoAT is TLAY's free, open-source economic runtime, and it runs inside the machine. It embeds a device-bound DID identity, owner-defined permissions, data attestation and payment authorization directly into IoT chips, robots and energy devices — about 58 KB fully loaded. The private key lives on the edge device, not on a central server.

What is HashAnchor?

HashAnchor is TLAY's free, open-source verification infrastructure. It verifies machine-signed activity, links work to its payment events, batches records into a Merkle root and anchors that root on-chain — so any third party can independently verify the provenance and integrity of what a machine did, without trusting TLAY.

What is the Machine Commerce Enabler?

It is TLAY's repeatable deployment pattern for turning an existing machine workflow into a pay → work → proof → settle loop. Built on BoAT and HashAnchor, it answers the same six decisions per scenario: the service, the unit, the pricing, the control path, the proof and the revenue routing. It is not a third product, and not bespoke development from scratch.

What is the machine commerce loop?

The loop is pay → work → proof → settle: a user pays in stablecoins, the machine is authorized on-chain and delivers physical work, BoAT signs proof of delivery, HashAnchor verifies it, and revenue is settled and distributed automatically. Every completed loop adds to the machine's verifiable operating history.

Is TLAY a bank?

No. TLAY provides machine-native technology and infrastructure. A machine account is a programmable account controlled by its owner, not a deposit account, and a machine is an owner-authorised economic participant rather than an independent legal entity. Regulated payment and financial services are designed to be delivered through appropriate licensed partners.

How does TLAY make money if its core products are open source?

BoAT and HashAnchor are free and open source, and TLAY does not depend on software license revenue. It earns from managed deployment, hosted verification and settlement, enterprise services, and the financial activity enabled through its network — so it grows with the economic activity of the machines it connects.

What is eCandle?

eCandle is TLAY's first reference implementation: machine-native PayGo for energy devices. A device is funded through an on-chain capital pool, activated by stablecoin payments, signs proof of the service it delivers, and distributes revenue automatically to its stakeholders.

Which blockchains and currencies does TLAY support?

TLAY is chain-neutral by design — the settlement layer is a replaceable module. It currently runs across Polygon, Base, BNB Chain, HashKey Chain, Arc, Solana and Lightning, settling in stablecoins such as USDC and USDT as well as BTC. Supporting a settlement network is a technical integration, not a commercial partnership.

Does on-chain data make every machine a safe investment?

No. On-chain records do not eliminate risk — they make risk visible. Every receipt declares the trust tier it was produced under, so machine performance, key custody and cash flow can be evaluated transparently. Financing and insurance partners still perform their own underwriting.

Silicon & embedded platforms BoAT is built to run across

Connectivity, platform and industry ecosystem

These marks denote the hardware, connectivity and platform landscape the runtime targets. Inclusion indicates technical relevance or integration — not endorsement, and not a commercial partnership.

Supported settlement networks