Status and FAQ
Configurable is not the same as verified end to end. This page says which is which.
Payments#
| Device-side payment integration | Status |
|---|---|
| EIP-3009 / x402 on EVM, micro-USDC | Shipped — built into the buyer and seller profiles; the only path exercised on hardware |
| Lightning, HashKey Multi-Pay | In the codebase as additional modules; HashKey is host-side only |
| MPP | Planned — needs a new engine or a versioned wire |
| Solana Pay / PayAI, Coinbase x402, Lightning L402, Visa, PayPal | Candidate directions, not shipped |
The direction is provider-neutral: the device produces signed evidence, and which network carries it is an integration choice. Today, identity and unpaid attestation carry no chain binding; the v1 payment wire does, and has no scheme field to configure.
Known gaps#
- No CI. Maintainers run the host suite and the ESP-IDF profile builds before each release, not on every push.
- No declared ESP-IDF minimum and no component-registry package. Developed against 5.5.x; reference it by git tag.
boat_mer.his not a complete umbrella. The nanopayment and BLE engine headers must be included directly.- Per-profile code-size figures are stale until re-measured on current builds.
FAQ#
Is BoAT MER a wallet?#
No. It holds the device's own keys and produces signed attestations and signed payment authorizations. It holds no one else's keys, runs no wallet backend, and takes custody of no funds.
Does the device talk to the blockchain?#
No. The device signs; an off-device settlement service verifies the signature and submits it. That keeps the device free of gas, nodes and chain connectivity, and lets one settlement call carry many device-signed payments.
Can it prove a sensor reading is true?#
It proves that this device signed this reading and that it has not changed since. Whether the reading was accurate depends on the sensor, its calibration and the device's security.
How is it related to the earlier BoAT IoT SDK?#
It is a new runtime rather than an update. The earlier SDK connected devices directly to chains and is no longer maintained. BoAT MER is written for ESP32-class hardware, where the device signs and an off-device service submits.
Where does a signed record go to be verified by others?#
To HashAnchor, which batches records into a Merkle tree, anchors the root on a public chain and returns a receipt anyone can check.