15. Frequently Asked Questions
Is TLAY a bank for robots?#
“A bank for robots” is a useful analogy because it helps a general audience understand that machines will need accounts, payments, and financial services. It should not be the precise category definition. TLAY is broader and more infrastructural: it provides identity, authority, transaction, and proof capabilities and does not necessarily custody funds or perform regulated banking activities.
The recommended framing is:
TLAY is economic infrastructure for autonomous machines—the account, payment, and proof layer for machine commerce.
Why use “economic infrastructure” instead of “financial infrastructure”?#
Financial infrastructure emphasizes money movement. Machine commerce also includes service definitions, operational permissions, physical delivery, data integrity, and cross-party coordination. “Economic infrastructure” describes the full system and gives TLAY room to support many payment and business models.
Does every machine need a blockchain wallet?#
Not necessarily. A machine needs a secure identity and a way to express economic authority. Depending on the architecture, it may sign blockchain-compatible authorizations, use an account managed by a fleet controller, interact through a payment channel, or delegate settlement to a gateway.
Must all machine data go onchain?#
No. Raw data should usually remain offchain. Critical events, state commitments, payment references, and business-process proofs can be anchored selectively. The principle is onchain-verifiable, not onchain-everything.
Why can’t an ordinary cloud database handle this?#
A cloud database works inside one trust domain. Machine commerce increasingly crosses companies, fleets, platforms, and jurisdictions. Portable cryptographic receipts reduce dependence on one platform’s database and make reconciliation and auditing easier.
What happens if the machine is offline?#
The deployment can define offline limits, local counters, delayed submission, channel-based payment, or gateway synchronization. Offline autonomy should be bounded by value, time, counterparty, and replay-protection policies.
Can TLAY support fiat payments?#
Yes, through integrated providers or account systems, provided the payment method can receive a valid machine authorization and return a settlement reference. TLAY’s core model is payment-rail agnostic, although current implementations focus on specific digital payment paths.
Who is legally responsible for a machine’s purchase?#
That depends on the legal and commercial arrangement. Typically, a person, company, fleet operator, or protocol owner delegates authority to the machine and remains accountable within the contract. TLAY supplies technical controls and evidence; it does not define legal personhood for machines.
Is the machine’s proof automatically true?#
The proof establishes integrity, origin, and ordering under the selected trust model. It does not guarantee that a compromised device or faulty sensor accurately represented the physical world. Secure hardware, calibration, redundancy, and operational governance remain essential.
Can developers use BoAT MER and HashAnchor separately?#
Yes. Each product creates standalone value. Their combined use creates a stronger end-to-end chain between machine identity, economic authorization, service delivery, and verifiable evidence.
What creates TLAY’s network effect?#
Every additional machine identity, accepted proof format, settlement integration, service provider, and developer application increases the number of possible economic relationships. Open products accelerate the edges of the network; managed coordination services capture value at scale.