Paymail BEEF Transaction
Last updated
Was this helpful?
Last updated
Was this helpful?
Deggen (deggen@kschw.com)
We specify a paymail capability extension which supports the passing of BEEF Transactions between hosts. The procedure for service discovery and requesting outputs is not detailed, rather this proposal contains only a recommendation to replace hex data with hex data.
We propose that functionality between hosts to include the data required for the counterparty to run SPV on the transaction.
A random ID was generated in order to avoid label collisions in the capability document of a paymail server.
We specify that an endpoint for delivery of transaction data ought to be added to the capabilities object in the .well-known response of a paymail service with the label: 5c55a7fdb7bb
.
The sender must replace the {alias}
and {domain.tld}
placeholders in the URI template provided by capabilities.5c55a7fdb7bb
with a valid Paymail handle. The client must then perform a POST HTTP request with the following body:
The server must validate the transaction and respond with the accepted transaction ID and an optional human-readable note.
A swimlanes diagram is included here for further clarification: https://swimlanes.io/u/6J2q8QCEb
BEEF transaction hex is a string encoding of the binary format detailed in .