plumb-xrpl 0.1.0__tar.gz

plumb_xrpl-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2026 McDavid Charleston
+
+   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.

plumb_xrpl-0.1.0/NOTICE

@@ -0,0 +1,5 @@
+plumb-xrpl
+Copyright 2026 Plumb Data
+
+Extracted from Plumb (verified-reads), the payment-proof layer of the Plumb Data Exchange.
+Licensed under the Apache License, Version 2.0.

plumb_xrpl-0.1.0/PKG-INFO

@@ -0,0 +1,149 @@
+Metadata-Version: 2.4
+Name: plumb-xrpl
+Version: 0.1.0
+Summary: XRP Ledger transactions and payments proven without trusting any server: pinned validator list -> quorum-signed ledger -> hash links -> rebuilt transaction tree.
+Author: Plumb Data
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/Mlcharle518/plumb-xrpl
+Project-URL: Issues, https://github.com/Mlcharle518/plumb-xrpl/issues
+Keywords: xrpl,xrp,rlusd,payments,proof,verification,x402,agents,light-client
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security :: Cryptography
+Classifier: Topic :: Office/Business :: Financial
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: xrpl-py>=5.2
+Requires-Dist: coincurve>=20
+Requires-Dist: cryptography>=42
+Requires-Dist: websockets>=13
+Provides-Extra: mcp
+Requires-Dist: mcp>=1.20; extra == "mcp"
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Dynamic: license-file
+
+# plumb-xrpl
+
+XRP Ledger transactions and payments **proven without trusting any server**. Servers are only a source of bytes;
+every link of the chain of trust is checked on your machine:
+
+1. **Ripple's validator list** (vl.ripple.com): the publisher's manifest must be signed by the pinned publisher master
+   key, the list by the publisher's signing key, and every validator's manifest by its own master key. An expired list
+   is refused. Validators that rotated their signing key are refreshed with a newer manifest signed by the same master key.
+2. **A ledger signed by a quorum (80%)** of those validators: each validation's signature is checked against the
+   validator's current signing key, over the validation's own bytes.
+3. **Hash links** from that ledger back to the transaction's ledger: every header carries its parent's hash, and each
+   header's hash is recomputed here (SHA-512Half over `LWR\0` + header).
+4. **The ledger's transaction tree**, rebuilt from every transaction and its metadata (SHAMap) and compared with the
+   header's transaction root.
+5. **The payment itself**, from those proven bytes: a successful Payment, to the payee, of the right currency (issuer
+   included), the *delivered* amount (never the requested `Amount`) at least the minimum, optionally from one payer and
+   carrying one InvoiceID.
+
+A lie at any link is caught by the tests (`tests/test_prover.py`): wrong publisher key, forged validation, broken
+hash link, tampered transaction, wrong recipient, underpayment, partial payment, wrong invoice.
+
+This is the XRPL prover of the [Plumb Data Exchange](https://numba2witcheese.tail7d8d44.ts.net:10000/llms.txt), where
+it has proven live RLUSD, XRP, payment-channel, escrow and batch payments on mainnet since October 2026. It is published
+so any seller, agent or wallet can hold a payment to the same standard.
+
+## Install
+
+```
+pip install plumb-xrpl            # library + CLI
+pip install "plumb-xrpl[mcp]"     # + the MCP server for agents
+```
+
+Python 3.11+. Dependencies: `xrpl-py` (byte codecs only; every hash and signature is checked here), `coincurve`
+(secp256k1), `cryptography` (ed25519), `websockets`.
+
+## Command line
+
+```
+plumb-xrpl tx  71100808DD3DF3EA693471FA...                       # any transaction, proven: fields + metadata
+plumb-xrpl pay 71100808... r9Y5...P2d --token RLUSD --min 50000   # was at least 0.05 RLUSD delivered to this account?
+plumb-xrpl pay 3A3915B2... rXXX --invoice C08EC114...             # ...and does the payment carry this InvoiceID?
+plumb-xrpl record                                                 # keep quorum proofs (see "How old can a payment be?")
+plumb-xrpl serve                                                  # MCP server over stdio (extra: plumb-xrpl[mcp])
+```
+
+Output is JSON in one envelope shape:
+
+```json
+{"verified": true,
+ "value": {"verdict": "paid", "paid_raw": "50000", "reason": "...",
+           "tx": {"tx_hash": "...", "block_number": 100000000, "block_hash": "...", "final": true, "...": "..."},
+           "xrpl": {"level": "unl_quorum", "validators": 28, "of": 35, "quorum": 28, "proof_ledger": 100000120,
+                    "walked": 120, "from_archive": false, "delivered": "...", "invoice_id": "..."}},
+ "anchor": {"root": "<hash of the quorum-signed ledger>", "source": "XRPL validator list (vl.ripple.com seq N, pinned publisher ...): 28/35 validator signatures on ledger ..., 120 hash links back"}}
+```
+
+`verified: false` always comes with a `reason` and never a guess. A transaction the servers do not yet report in a
+validated ledger is `verdict: pending_validation` with `retry_after_s`.
+
+Amounts are raw integers: XRP in **drops**, issued currencies (RLUSD, ...) in **millionths** (value x 10^6, rounded
+down). Tokens: `XRP` (default), `RLUSD`, or `CURRENCY.rIssuer`.
+
+## Library
+
+```python
+from plumb_xrpl import XrplHistory, envelope
+
+h = XrplHistory()
+proof = h.verify_payment(tx_hash, recipient="r9Y5...P2d", token="RLUSD", min_raw=50_000, invoice=None)
+# proof["verdict"] in {"paid", "not_paid", "underpaid", "failed_transaction", ...}; proof["xrpl"]["validators"] etc.
+
+tx = h.transaction(tx_hash)          # any transaction type, decoded fields + metadata, proven
+out = envelope(lambda: h.transaction(tx_hash))   # the CLI's {"verified": ..., "value": ..., "anchor": ...} shape
+```
+
+What a proven *transaction* gives you beyond payments: the metadata's `AffectedNodes` carry the final fields of every
+ledger object the transaction created or changed, so the state **as of that transaction** is proven too: account
+balances after it, a trust line, an escrow or payment channel it created, a credential it issued.
+
+## MCP server
+
+`plumb-xrpl serve` exposes two tools over stdio: `get_transaction(tx_hash)` and
+`verify_payment(tx_hash, recipient, token="", min_amount_raw="0", payer="", invoice="")`. Same envelope as the CLI.
+
+## How old can a payment be?
+
+Validator signatures exist only live; rippled servers do not keep them. So a quorum proof comes from one of two places:
+
+- **the live stream**: for a fresh payment, walk back from a ledger being validated now (up to `MAX_WALK` ledgers);
+- **the proof archive**: `plumb-xrpl record` keeps one quorum-signed ledger per 256 ledgers (about every 16 minutes)
+  in `~/.verified-reads/xrpl-proofs.jsonl` (override with `VR_XRPL_ARCHIVE`). Any older payment is then proven by hash
+  links from the nearest archived proof. Run it as a service if you need to prove payments older than a few hours.
+
+A payment older than both is reported **unverifiable**, never guessed. The validator list is cached at
+`~/.verified-reads/xrpl-unl.json` (`VR_XRPL_UNL_CACHE`) and refreshed hourly.
+
+## What this does not do
+
+- It proves **transactions**, not the current state tree. "Current balance of account X" needs the full account-state
+  SHAMap, which no public server proves. Balances are proven as of a transaction (see Library).
+- It does not submit or sign anything. Keys never enter this package.
+- It trusts Ripple's **validator list publisher key**, pinned in the source, and the 80% quorum rule of the XRP Ledger.
+  That is the same trust assumption as a rippled node you run yourself, without running one.
+
+## Development
+
+```
+pip install -e ".[test,mcp]"
+python -m pytest -q
+```
+
+Fixtures are real mainnet bytes recorded with `tests/record_fixtures.py`; the tests replay them through a fake source
+and then tamper with each link.
+
+## License
+
+Apache-2.0. See `LICENSE` and `NOTICE`.

plumb_xrpl-0.1.0/README.md

@@ -0,0 +1,117 @@
+# plumb-xrpl
+
+XRP Ledger transactions and payments **proven without trusting any server**. Servers are only a source of bytes;
+every link of the chain of trust is checked on your machine:
+
+1. **Ripple's validator list** (vl.ripple.com): the publisher's manifest must be signed by the pinned publisher master
+   key, the list by the publisher's signing key, and every validator's manifest by its own master key. An expired list
+   is refused. Validators that rotated their signing key are refreshed with a newer manifest signed by the same master key.
+2. **A ledger signed by a quorum (80%)** of those validators: each validation's signature is checked against the
+   validator's current signing key, over the validation's own bytes.
+3. **Hash links** from that ledger back to the transaction's ledger: every header carries its parent's hash, and each
+   header's hash is recomputed here (SHA-512Half over `LWR\0` + header).
+4. **The ledger's transaction tree**, rebuilt from every transaction and its metadata (SHAMap) and compared with the
+   header's transaction root.
+5. **The payment itself**, from those proven bytes: a successful Payment, to the payee, of the right currency (issuer
+   included), the *delivered* amount (never the requested `Amount`) at least the minimum, optionally from one payer and
+   carrying one InvoiceID.
+
+A lie at any link is caught by the tests (`tests/test_prover.py`): wrong publisher key, forged validation, broken
+hash link, tampered transaction, wrong recipient, underpayment, partial payment, wrong invoice.
+
+This is the XRPL prover of the [Plumb Data Exchange](https://numba2witcheese.tail7d8d44.ts.net:10000/llms.txt), where
+it has proven live RLUSD, XRP, payment-channel, escrow and batch payments on mainnet since October 2026. It is published
+so any seller, agent or wallet can hold a payment to the same standard.
+
+## Install
+
+```
+pip install plumb-xrpl            # library + CLI
+pip install "plumb-xrpl[mcp]"     # + the MCP server for agents
+```
+
+Python 3.11+. Dependencies: `xrpl-py` (byte codecs only; every hash and signature is checked here), `coincurve`
+(secp256k1), `cryptography` (ed25519), `websockets`.
+
+## Command line
+
+```
+plumb-xrpl tx  71100808DD3DF3EA693471FA...                       # any transaction, proven: fields + metadata
+plumb-xrpl pay 71100808... r9Y5...P2d --token RLUSD --min 50000   # was at least 0.05 RLUSD delivered to this account?
+plumb-xrpl pay 3A3915B2... rXXX --invoice C08EC114...             # ...and does the payment carry this InvoiceID?
+plumb-xrpl record                                                 # keep quorum proofs (see "How old can a payment be?")
+plumb-xrpl serve                                                  # MCP server over stdio (extra: plumb-xrpl[mcp])
+```
+
+Output is JSON in one envelope shape:
+
+```json
+{"verified": true,
+ "value": {"verdict": "paid", "paid_raw": "50000", "reason": "...",
+           "tx": {"tx_hash": "...", "block_number": 100000000, "block_hash": "...", "final": true, "...": "..."},
+           "xrpl": {"level": "unl_quorum", "validators": 28, "of": 35, "quorum": 28, "proof_ledger": 100000120,
+                    "walked": 120, "from_archive": false, "delivered": "...", "invoice_id": "..."}},
+ "anchor": {"root": "<hash of the quorum-signed ledger>", "source": "XRPL validator list (vl.ripple.com seq N, pinned publisher ...): 28/35 validator signatures on ledger ..., 120 hash links back"}}
+```
+
+`verified: false` always comes with a `reason` and never a guess. A transaction the servers do not yet report in a
+validated ledger is `verdict: pending_validation` with `retry_after_s`.
+
+Amounts are raw integers: XRP in **drops**, issued currencies (RLUSD, ...) in **millionths** (value x 10^6, rounded
+down). Tokens: `XRP` (default), `RLUSD`, or `CURRENCY.rIssuer`.
+
+## Library
+
+```python
+from plumb_xrpl import XrplHistory, envelope
+
+h = XrplHistory()
+proof = h.verify_payment(tx_hash, recipient="r9Y5...P2d", token="RLUSD", min_raw=50_000, invoice=None)
+# proof["verdict"] in {"paid", "not_paid", "underpaid", "failed_transaction", ...}; proof["xrpl"]["validators"] etc.
+
+tx = h.transaction(tx_hash)          # any transaction type, decoded fields + metadata, proven
+out = envelope(lambda: h.transaction(tx_hash))   # the CLI's {"verified": ..., "value": ..., "anchor": ...} shape
+```
+
+What a proven *transaction* gives you beyond payments: the metadata's `AffectedNodes` carry the final fields of every
+ledger object the transaction created or changed, so the state **as of that transaction** is proven too: account
+balances after it, a trust line, an escrow or payment channel it created, a credential it issued.
+
+## MCP server
+
+`plumb-xrpl serve` exposes two tools over stdio: `get_transaction(tx_hash)` and
+`verify_payment(tx_hash, recipient, token="", min_amount_raw="0", payer="", invoice="")`. Same envelope as the CLI.
+
+## How old can a payment be?
+
+Validator signatures exist only live; rippled servers do not keep them. So a quorum proof comes from one of two places:
+
+- **the live stream**: for a fresh payment, walk back from a ledger being validated now (up to `MAX_WALK` ledgers);
+- **the proof archive**: `plumb-xrpl record` keeps one quorum-signed ledger per 256 ledgers (about every 16 minutes)
+  in `~/.verified-reads/xrpl-proofs.jsonl` (override with `VR_XRPL_ARCHIVE`). Any older payment is then proven by hash
+  links from the nearest archived proof. Run it as a service if you need to prove payments older than a few hours.
+
+A payment older than both is reported **unverifiable**, never guessed. The validator list is cached at
+`~/.verified-reads/xrpl-unl.json` (`VR_XRPL_UNL_CACHE`) and refreshed hourly.
+
+## What this does not do
+
+- It proves **transactions**, not the current state tree. "Current balance of account X" needs the full account-state
+  SHAMap, which no public server proves. Balances are proven as of a transaction (see Library).
+- It does not submit or sign anything. Keys never enter this package.
+- It trusts Ripple's **validator list publisher key**, pinned in the source, and the 80% quorum rule of the XRP Ledger.
+  That is the same trust assumption as a rippled node you run yourself, without running one.
+
+## Development
+
+```
+pip install -e ".[test,mcp]"
+python -m pytest -q
+```
+
+Fixtures are real mainnet bytes recorded with `tests/record_fixtures.py`; the tests replay them through a fake source
+and then tamper with each link.
+
+## License
+
+Apache-2.0. See `LICENSE` and `NOTICE`.

plumb_xrpl-0.1.0/plumb_xrpl/__init__.py

@@ -0,0 +1,12 @@
+"""plumb-xrpl: XRP Ledger transactions and payments proven without trusting any server.
+
+Servers are only a source of bytes. Every link is checked here: Ripple's validator list against the pinned publisher
+key, a ledger signed by 80% of those validators, hash links back to the payment's ledger, the ledger's rebuilt
+transaction tree, and the payment itself from those proven bytes. See `plumb_xrpl.prover`.
+"""
+from .prover import (Archive, HistoryError, PendingValidation, Source, XrplError, XrplHistory, envelope, judge,
+                     parse_token, record)
+
+__version__ = "0.1.0"
+__all__ = ["Archive", "HistoryError", "PendingValidation", "Source", "XrplError", "XrplHistory", "envelope", "judge",
+           "parse_token", "record", "__version__"]

plumb_xrpl-0.1.0/plumb_xrpl/__main__.py

@@ -0,0 +1,3 @@
+from .cli import main
+
+main()

plumb_xrpl-0.1.0/plumb_xrpl/cli.py

@@ -0,0 +1,65 @@
+"""Command line: `plumb-xrpl tx|pay|record|serve`. Output is JSON in Plumb's envelope shape:
+{"verified": true, "value": ..., "anchor": {...}} or {"verified": false, "reason": "..."}."""
+from __future__ import annotations
+
+import argparse
+import json
+import sys
+
+from . import __version__
+from . import prover as X
+
+
+def _print(o: object) -> None:
+    print(json.dumps(o, indent=2, default=str))
+
+
+def cmd_tx(a: argparse.Namespace) -> None:
+    _print(X.envelope(lambda: X.XrplHistory().transaction(a.hash)))
+
+
+def cmd_pay(a: argparse.Namespace) -> None:
+    _print(X.envelope(lambda: X.XrplHistory().verify_payment(a.hash, a.recipient, a.token, a.min, a.payer or None,
+                                                             a.invoice or None)))
+
+
+def cmd_record(a: argparse.Namespace) -> None:
+    print(f"recording XRPL validator-quorum proofs every {a.every} ledgers to {X.Archive().path} (Ctrl+C to stop)",
+          flush=True)
+    X.record(every=a.every)
+
+
+def cmd_serve(_a: argparse.Namespace) -> None:
+    try:
+        from .server import main as serve
+    except ImportError as e:  # the MCP server is an extra
+        sys.exit(f"the MCP server needs the extra: pip install plumb-xrpl[mcp] ({e})")
+    serve()
+
+
+def main(argv: list[str] | None = None) -> None:
+    ap = argparse.ArgumentParser(prog="plumb-xrpl",
+                                 description="XRP Ledger transactions and payments proven without trusting any server.")
+    ap.add_argument("--version", action="version", version=f"plumb-xrpl {__version__}")
+    sub = ap.add_subparsers(dest="cmd", required=True)
+    p = sub.add_parser("tx", help="any transaction, proven: full fields + metadata")
+    p.add_argument("hash")
+    p.set_defaults(fn=cmd_tx)
+    p = sub.add_parser("pay", help="was this payment made? verdict bound to recipient, token, minimum, payer, invoice")
+    p.add_argument("hash")
+    p.add_argument("recipient")
+    p.add_argument("--token", default="", help="XRP (default), RLUSD, or CURRENCY.rIssuer")
+    p.add_argument("--min", type=int, default=0, help="minimum delivered amount: XRP drops or issued millionths")
+    p.add_argument("--from", dest="payer", default="", help="count only a payment from this account")
+    p.add_argument("--invoice", default="", help="the payment InvoiceID must equal this (64 hex)")
+    p.set_defaults(fn=cmd_pay)
+    p = sub.add_parser("record", help="keep validator-quorum proofs so payments older than the live stream stay provable")
+    p.add_argument("--every", type=int, default=X.ARCHIVE_EVERY)
+    p.set_defaults(fn=cmd_record)
+    sub.add_parser("serve", help="MCP server over stdio (extra: plumb-xrpl[mcp])").set_defaults(fn=cmd_serve)
+    a = ap.parse_args(argv)
+    a.fn(a)
+
+
+if __name__ == "__main__":
+    main()