TLAY Product Architecture

16. Getting Started

For embedded developers#

  1. Review the BoAT MER repository.
  2. Select a supported or portable hardware target.
  3. Choose buyer, seller, or full capability profile.
  4. Run identity and signing examples.
  5. Test an EIP-3009, x402, or BLE commerce workflow appropriate to the use case.
  6. Connect signed machine events to HashAnchor.

For application developers#

  1. Define the physical service and its commercial unit.
  2. Model the offer, acceptance, delivery, and completion events.
  3. Define economic permissions and risk limits.
  4. Integrate the HashAnchor client and API.
  5. Verify portable receipts independently.
  6. Add payment routing and link settlement references to the event chain.

For enterprises#

Start with one bounded workflow where cross-party trust or reconciliation is expensive. Good candidates have:

  • a measurable physical service;
  • repeat transactions;
  • more than one organization or system of record;
  • a need for automated payment or proof;
  • clear economic value from reducing manual coordination.

The first deployment should prove one complete commerce loop before expanding across a fleet or marketplace.