<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/82a8aaba9cdf4cd5b70290927a456589&quot; frameborder=&quot;0&quot; width=&quot;3360&quot; height=&quot;2520&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2520</height><width>3360</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2520</thumbnail_height><thumbnail_width>3360</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/82a8aaba9cdf4cd5b70290927a456589-de38868a67cd3b1c.gif</thumbnail_url><duration>131.266667</duration><title>Karma Verifiable Execution for BNB Agents</title><description>This Loom explains how Karma provides cryptographic proof of agent work for verifiable agentic commerce on the BNB chain. It addresses the gap in Urk 8,183’s optimistic policy, noting there is no proof without agent silence means approve, and describes generating tool receipts with a SHA-256 hash of inputs and outputs that are self-consistent. Receipts are bundled into a “Miracle Verifiable Evidence Package,” encoded as evidence bytes for router dot settle after the provider submits and the BNB verifier fetches deliverable downloads and runs the Karma runtime. Integration requires one import and three lines of code, with an evaluator that is fully typed and tested using 399 tests, validated for create job and set budget on the BSC testnet, and PR 33 open at github.com slash bnb chain slash vaginth SDK for review or a live demo request.</description></oembed>