xrpl-x402-core
Shared XRPL support for the x402 v2 stack. Version 0.2.0 pins x402==2.21.0.
This package re-exports official x402 schemas such as PaymentRequired,
PaymentRequirements, PaymentPayload, VerifyRequest, VerifyResponse,
SettleRequest, SettleResponse, and supported-kind models. It does not define
parallel wire schemas.
Local public types are XRPL-specific:
ExactXRPLPayloadwithsignedTxBlobExactXRPLExtraXRPLSettlementState- default asset, network, invoice hashing, transaction hash, and fingerprint helpers
XRPL assets are represented canonically: XRP is XRP with drops, while IOUs
use the currency code plus extra.issuer. find_default_asset(asset, network)
recognizes the official RLUSD entries.
Metadata
Release files for xrpl-x402-core 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| xrpl_x402_core-0.2.0.tar.gz | 8.1 kB | With provenance | Details for xrpl_x402_core-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| xrpl_x402_core-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for xrpl_x402_core-0.2.0-py3-none-any.whl |
Total release size: 18.2 kB
Release files / xrpl_x402_core-0.2.0.tar.gz
| Download URL | xrpl_x402_core-0.2.0.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17348ab8c4025b6348e667bb48f09cc3d4597b69a47a30ecda440a7ba419260f
|
|
BLAKE2b-256 checksum How to use checksums |
fcb9e1db5f723af024dab1e1d949b266efd8750169a091d655b30cff6a196ced
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logRelease files / xrpl_x402_core-0.2.0-py3-none-any.whl
| Download URL | xrpl_x402_core-0.2.0-py3-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bfce8ae022b771d5bebb2fed27072369b9f1fce5e90b48aa38d2cb940af93629
|
|
BLAKE2b-256 checksum How to use checksums |
59159dc3d0c76629e7ff9655cc21d38b68bd52227c28988bd58f3ca11348fd1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logSecurity for xrpl-x402-core 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for xrpl_x402_core-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.