dethron 0.1.0__tar.gz

dethron-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

dethron-0.1.0/NOTICE

@@ -0,0 +1,9 @@
+Dethron
+Copyright 2026 Dethron contributors
+
+This product includes software developed as part of the Dethron project.
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file.
+
+Dethron builds on Reticulum (RNS) and LXMF, which are separate works under their
+own licenses. They are imported as dependencies, not derived from.

dethron-0.1.0/PKG-INFO

@@ -0,0 +1,162 @@
+Metadata-Version: 2.4
+Name: dethron
+Version: 0.1.0
+Summary: Verifiable message delivery over Reticulum and LXMF
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/elSilveira/dethron
+Project-URL: Evidence, https://github.com/elSilveira/dethron/tree/master/evidence
+Project-URL: Research, https://github.com/elSilveira/dethron-research
+Keywords: reticulum,lxmf,mesh,delay-tolerant,messaging,custody
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Communications
+Classifier: Topic :: System :: Networking
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: rns<2,>=1.5.4
+Requires-Dist: lxmf<2,>=1.1.1
+Requires-Dist: cryptography>=42
+Provides-Extra: serial
+Requires-Dist: pyserial>=3.5; extra == "serial"
+Dynamic: license-file
+
+# Dethron
+
+Verifiable message delivery over [Reticulum](https://reticulum.network/) and LXMF.
+
+**Guaranteed** delivery is impossible over intermittent contact: if the recipient never
+appears, nothing reaches them. What is possible is knowing, with cryptographic proof and
+without trusting the relay, which state a message is in.
+
+| State | Proof | Who signs it |
+| --- | --- | --- |
+| **Entered** | A custody attestation naming the message, the recipient, and the bytes actually stored | the relay |
+| **Pending** | A relay holding custody with no receipt: *awaiting contact* or *attested and not delivered* | derived, not claimed |
+| **Left** | A receipt over the exact reconstructed bytes, which reaches the sender through any relay carrying it | the recipient |
+
+A relay that attests and then discards the message is **named** by the absence of the
+recipient's receipt. That is the point: nothing here asks you to trust an intermediary.
+
+## Install
+
+```
+pip install dethron
+```
+
+Python 3.10 or newer. Reticulum and LXMF come with it. Exercised on Windows 11 with
+Python 3.10 and on Ubuntu 24.04 with Python 3.12, end-to-end test included.
+
+## Try it
+
+Three terminals, or one and some patience. Everything below is real: real Reticulum
+instances, real LXMF propagation, real signatures.
+
+```bash
+# 1. Mint three identities and note their contacts
+dethron identity ./relay
+dethron identity ./alice
+dethron identity ./bob
+
+# 2. Run a relay, which holds objects for recipients who are not here yet
+dethron relay ./relay --port 45810
+```
+
+With the relay running, and using the `contact` and `propagation` values it printed:
+
+```bash
+# 3. Alice hands an object to the relay and comes back with proof it was taken
+dethron send ./alice report.pdf \
+  --to <bob's contact> \
+  --relay 127.0.0.1:45810/<relay propagation> \
+  --relay-contact <relay's contact>
+
+# 4. Bob, who was not around for any of that, collects and reconstructs it
+dethron fetch ./bob \
+  --source <alice's contact> \
+  --relay 127.0.0.1:45810/<relay propagation> \
+  --receipt-to <alice's contact>
+
+# 5. Alice comes back later and picks up the receipt Bob signed
+dethron receipts ./alice --relay 127.0.0.1:45810/<relay propagation>
+
+# 6. Either of them recomputes every proof from the files on disk
+dethron verify ./alice
+```
+
+`verify` ends with both halves of the claim:
+
+```json
+{
+  "verdict": "pass",
+  "checks": [
+    { "check": "custody 10019ad5 is signed by the relay that was asked",
+      "passed": true, "proves": "entry", "stored_size": 18688 },
+    { "check": "receipt 02377a24 is signed by the recipient sent to",
+      "passed": true, "proves": "exit",
+      "digest": "02377a2438d3a5ab8f90f2bbc0cf67f16d8f1ce89da2d867dec1fc4ea2389070" }
+  ]
+}
+```
+
+Alice and Bob were never online at the same time.
+
+## As a library
+
+```python
+from dethron import Node
+
+with Node('./alice', peers=['relay.example:45810']) as node:
+    handoff = node.send(payload, to=bob_contact, via=relay_propagation)
+    proof = node.custody_of(handoff['transient_id'], relay=relay_contact)
+```
+
+Calls are synchronous: `send` returns once the relay has taken the object, `custody_of`
+returns the relay's signed attestation, `fetch` returns once the parts reconstruct. Each
+node writes an `events.jsonl` beside itself — not a log for humans, but the record an
+audit reads afterwards.
+
+## What is proved, and what is not
+
+The claims come with artifacts, in [`evidence/`](evidence/README.md), and with documents
+stating the controls that had to fail: see [`docs/`](docs/).
+
+Proved, within a declared scope:
+
+- Custody, pendency and receipt return ([V1](docs/V1_CUSTODY.md), [receipt](docs/V1_RECEIPT_RETURN.md)).
+- Reproduction on an independent machine following the document alone ([V2](docs/V2_REPRODUCTION.md)).
+- An object crossing between two distinct machines over a link carrying **no IP**,
+  with the recipient proved to hold no IP interface ([V3c](docs/V3C_BENCH.md)).
+
+Not proved, and not claimed:
+
+- **Scale.** One message, one relay, one recipient. No numbers for many peers or a queue.
+- **Key exchange and discovery.** Contacts are exchanged out of band, by you.
+- **A hostile relay in the wild.** The refusals are tested; the adversary is simulated.
+- **Long offline periods.** The sessions in the evidence are disjoint by seconds, not days.
+- **Anything beyond two platforms.** Windows and Linux are exercised; Android, macOS and
+  the BSDs are not. The milestone evidence below was produced on Windows, and says so.
+- Everything the milestone documents list under "Limits", which is where to look first.
+
+## Contributing
+
+Bug reports and reproductions are the most useful thing you can send. See
+[CONTRIBUTING.md](CONTRIBUTING.md). The house rule is that a claim arrives with the
+control that would have caught it being wrong.
+
+## Where the evidence came from
+
+The bench that produced it — generations of nodes, cut media, two-machine schedules, the
+auditors — lives in [dethron-research](https://github.com/elSilveira/dethron-research),
+along with the deliberation and the runs that failed. This repository is the part that is
+meant to be used; that one is the part that is meant to be checked.
+
+## Licence
+
+[Apache 2.0](LICENSE). Reticulum and LXMF are dependencies under their own licences; this
+work imports them, it does not derive from them.

dethron-0.1.0/README.md

@@ -0,0 +1,134 @@
+# Dethron
+
+Verifiable message delivery over [Reticulum](https://reticulum.network/) and LXMF.
+
+**Guaranteed** delivery is impossible over intermittent contact: if the recipient never
+appears, nothing reaches them. What is possible is knowing, with cryptographic proof and
+without trusting the relay, which state a message is in.
+
+| State | Proof | Who signs it |
+| --- | --- | --- |
+| **Entered** | A custody attestation naming the message, the recipient, and the bytes actually stored | the relay |
+| **Pending** | A relay holding custody with no receipt: *awaiting contact* or *attested and not delivered* | derived, not claimed |
+| **Left** | A receipt over the exact reconstructed bytes, which reaches the sender through any relay carrying it | the recipient |
+
+A relay that attests and then discards the message is **named** by the absence of the
+recipient's receipt. That is the point: nothing here asks you to trust an intermediary.
+
+## Install
+
+```
+pip install dethron
+```
+
+Python 3.10 or newer. Reticulum and LXMF come with it. Exercised on Windows 11 with
+Python 3.10 and on Ubuntu 24.04 with Python 3.12, end-to-end test included.
+
+## Try it
+
+Three terminals, or one and some patience. Everything below is real: real Reticulum
+instances, real LXMF propagation, real signatures.
+
+```bash
+# 1. Mint three identities and note their contacts
+dethron identity ./relay
+dethron identity ./alice
+dethron identity ./bob
+
+# 2. Run a relay, which holds objects for recipients who are not here yet
+dethron relay ./relay --port 45810
+```
+
+With the relay running, and using the `contact` and `propagation` values it printed:
+
+```bash
+# 3. Alice hands an object to the relay and comes back with proof it was taken
+dethron send ./alice report.pdf \
+  --to <bob's contact> \
+  --relay 127.0.0.1:45810/<relay propagation> \
+  --relay-contact <relay's contact>
+
+# 4. Bob, who was not around for any of that, collects and reconstructs it
+dethron fetch ./bob \
+  --source <alice's contact> \
+  --relay 127.0.0.1:45810/<relay propagation> \
+  --receipt-to <alice's contact>
+
+# 5. Alice comes back later and picks up the receipt Bob signed
+dethron receipts ./alice --relay 127.0.0.1:45810/<relay propagation>
+
+# 6. Either of them recomputes every proof from the files on disk
+dethron verify ./alice
+```
+
+`verify` ends with both halves of the claim:
+
+```json
+{
+  "verdict": "pass",
+  "checks": [
+    { "check": "custody 10019ad5 is signed by the relay that was asked",
+      "passed": true, "proves": "entry", "stored_size": 18688 },
+    { "check": "receipt 02377a24 is signed by the recipient sent to",
+      "passed": true, "proves": "exit",
+      "digest": "02377a2438d3a5ab8f90f2bbc0cf67f16d8f1ce89da2d867dec1fc4ea2389070" }
+  ]
+}
+```
+
+Alice and Bob were never online at the same time.
+
+## As a library
+
+```python
+from dethron import Node
+
+with Node('./alice', peers=['relay.example:45810']) as node:
+    handoff = node.send(payload, to=bob_contact, via=relay_propagation)
+    proof = node.custody_of(handoff['transient_id'], relay=relay_contact)
+```
+
+Calls are synchronous: `send` returns once the relay has taken the object, `custody_of`
+returns the relay's signed attestation, `fetch` returns once the parts reconstruct. Each
+node writes an `events.jsonl` beside itself — not a log for humans, but the record an
+audit reads afterwards.
+
+## What is proved, and what is not
+
+The claims come with artifacts, in [`evidence/`](evidence/README.md), and with documents
+stating the controls that had to fail: see [`docs/`](docs/).
+
+Proved, within a declared scope:
+
+- Custody, pendency and receipt return ([V1](docs/V1_CUSTODY.md), [receipt](docs/V1_RECEIPT_RETURN.md)).
+- Reproduction on an independent machine following the document alone ([V2](docs/V2_REPRODUCTION.md)).
+- An object crossing between two distinct machines over a link carrying **no IP**,
+  with the recipient proved to hold no IP interface ([V3c](docs/V3C_BENCH.md)).
+
+Not proved, and not claimed:
+
+- **Scale.** One message, one relay, one recipient. No numbers for many peers or a queue.
+- **Key exchange and discovery.** Contacts are exchanged out of band, by you.
+- **A hostile relay in the wild.** The refusals are tested; the adversary is simulated.
+- **Long offline periods.** The sessions in the evidence are disjoint by seconds, not days.
+- **Anything beyond two platforms.** Windows and Linux are exercised; Android, macOS and
+  the BSDs are not. The milestone evidence below was produced on Windows, and says so.
+- Everything the milestone documents list under "Limits", which is where to look first.
+
+## Contributing
+
+Bug reports and reproductions are the most useful thing you can send. See
+[CONTRIBUTING.md](CONTRIBUTING.md). The house rule is that a claim arrives with the
+control that would have caught it being wrong.
+
+## Where the evidence came from
+
+The bench that produced it — generations of nodes, cut media, two-machine schedules, the
+auditors — lives in [dethron-research](https://github.com/elSilveira/dethron-research),
+along with the deliberation and the runs that failed. This repository is the part that is
+meant to be used; that one is the part that is meant to be checked.
+
+## Licence
+
+[Apache 2.0](LICENSE). Reticulum and LXMF are dependencies under their own licences; this
+work imports them, it does not derive from them.

dethron-0.1.0/pyproject.toml

@@ -0,0 +1,44 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "dethron"
+version = "0.1.0"
+description = "Verifiable message delivery over Reticulum and LXMF"
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "Apache-2.0" }
+keywords = ["reticulum", "lxmf", "mesh", "delay-tolerant", "messaging", "custody"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Intended Audience :: Developers",
+  "License :: OSI Approved :: Apache Software License",
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Topic :: Communications",
+  "Topic :: System :: Networking",
+]
+dependencies = [
+  "rns>=1.5.4,<2",
+  "lxmf>=1.1.1,<2",
+  "cryptography>=42",
+]
+
+[project.optional-dependencies]
+serial = ["pyserial>=3.5"]
+
+[project.scripts]
+dethron = "dethron.cli:main"
+
+[project.urls]
+Homepage = "https://github.com/elSilveira/dethron"
+Evidence = "https://github.com/elSilveira/dethron/tree/master/evidence"
+Research = "https://github.com/elSilveira/dethron-research"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

dethron-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

dethron-0.1.0/src/dethron/__init__.py

@@ -0,0 +1,28 @@
+"""Verifiable message delivery over Reticulum and LXMF.
+
+Guaranteed delivery is impossible over intermittent contact: if the recipient never
+appears, nothing reaches them. What is possible is knowing, with cryptographic proof and
+without trusting the relay, which state a message is in — it entered the network, it is
+pending at a named relay, or the recipient signed for it.
+
+    from dethron import Node
+
+    with Node('./alice', peers=['relay.example:45810']) as node:
+        handoff = node.send(payload, to=recipient, via=relay_propagation)
+        proof = node.custody_of(handoff['transient_id'], relay=relay_contact)
+
+`proof` is the relay's signature over the message it is holding, for that recipient. It
+proves entry, not delivery: only the recipient's receipt proves exit, and a relay that
+attests and then discards is named by the absence of that receipt.
+"""
+from . import custody
+from .audit import verify_directory
+from .endpoint import Endpoint
+from .node import Node, parse_contact, parse_relay
+from .protocol import data_envelope, decode, encode, receipt_envelope
+from .wire import authenticate, declared_expiry
+
+__version__ = '0.1.0'
+__all__ = ['Endpoint', 'Node', 'authenticate', 'custody', 'data_envelope', 'decode',
+           'declared_expiry', 'encode', 'parse_contact', 'parse_relay', 'receipt_envelope',
+           'verify_directory']

dethron-0.1.0/src/dethron/adapter.py

@@ -0,0 +1,75 @@
+"""LXMF direct delivery adapter. pump() is explicit; no simulated network fallback."""
+import threading
+import time
+
+import LXMF
+import RNS
+
+from .protocol import APPLICATION, encode
+from .wire import authenticate
+
+
+class Adapter:
+    def __init__(self, router, source, mailbox, emit):
+        self.router, self.source, self.mailbox, self.emit = router, source, mailbox, emit
+        self.active = set()
+        self.lock = threading.RLock()
+        router.register_delivery_callback(self.receive)
+
+    def receive(self, message):
+        try:
+            identity = RNS.Identity.recall(message.source_hash)
+            if identity is None:
+                raise ValueError("unknown source identity")
+            obj = authenticate(message.packed, identity.get_public_key(), self.source.hash.hex(), time.time())
+            fresh = self.mailbox.accept_verified(obj, message.packed, time.time())
+            self.emit("confirmed" if obj["kind"] == "receipt" else "received",
+                      id=obj["id"], fresh=fresh, digest=obj["digest"])
+        except Exception as exc:
+            self.emit("rejected", error=repr(exc))
+
+    def transmit(self, destination, body, callback=None, failed=None):
+        dest_hash = bytes.fromhex(destination)
+        identity = RNS.Identity.recall(dest_hash)
+        if identity is None:
+            RNS.Transport.request_path(dest_hash)
+            return False
+        target = RNS.Destination(identity, RNS.Destination.OUT, RNS.Destination.SINGLE, "lxmf", "delivery")
+        message = LXMF.LXMessage(target, self.source, body, APPLICATION, desired_method=LXMF.LXMessage.DIRECT)
+        if callback:
+            message.register_delivery_callback(callback)
+        if failed:
+            message.register_failed_callback(failed)
+        self.router.handle_outbound(message)
+        return True
+
+    def _complete(self, key, message_id, succeeded):
+        with self.lock:
+            if succeeded:
+                self.mailbox.handoff(key)
+            self.active.discard(key)
+        self.emit("handoff" if succeeded else "attempt_failed", id=message_id)
+
+    def pump(self):
+        with self.lock:
+            for item in self.mailbox.pending(time.time()):
+                key, obj = item["key"], item["envelope"]
+                if key in self.active:
+                    continue
+                dest_hash = bytes.fromhex(obj["destination"])
+                # Native LXMF can reuse a backchannel even without a cached route.
+                if RNS.Identity.recall(dest_hash) is None:
+                    RNS.Transport.request_path(dest_hash)
+                    self.emit("no_path", id=obj["id"])
+                    continue
+                self.mailbox.begin_attempt(key, time.time())
+                self.active.add(key)
+                success = lambda m, k=key, i=obj["id"]: self._complete(k, i, True)
+                failure = lambda m, k=key, i=obj["id"]: self._complete(k, i, False)
+                try:
+                    sent = self.transmit(obj["destination"], encode(obj), success, failure)
+                    if not sent:
+                        self.active.discard(key)
+                except Exception:
+                    self.active.discard(key)
+                    raise