Lexe Python SDK
The Lexe Python SDK provides a Python interface for developers to control self-custodial, always-online Lexe Lightning nodes.
pip install lexe-sdk
Create a wallet
from lexe import Credentials, LexeWallet, RootSeed, WalletConfig
# Configure `mainnet()` or `testnet3()`
config = WalletConfig.mainnet()
# Sample a new seed and write it to ~/.lexe/seedphrase.txt
seed = RootSeed.generate()
seed.write(config)
# Create wallet and register with Lexe (data stored in ~/.lexe)
creds = Credentials.from_root_seed(seed)
wallet = LexeWallet.fresh(config, creds)
wallet.signup(root_seed=seed, partner_pk=None)
# Create a Lightning invoice
invoice = wallet.create_invoice(
expiration_secs=3600,
amount_sats=1000,
description="Initial deposit",
)
print(f"Invoice: {invoice.invoice}")
# Wait for payment
payment = wallet.wait_for_payment(index=invoice.index, timeout_secs=300)
print(f"Payment received: {payment.amount_sats} sats")
Load an existing wallet
from lexe import Credentials, LexeWallet, RootSeed, WalletConfig
# Load existing wallet from ~/.lexe
config = WalletConfig.mainnet()
seed = RootSeed.read(config)
creds = Credentials.from_root_seed(seed)
wallet = LexeWallet.load(config, creds)
# Update to the latest node software
wallet.provision(creds)
# Pay a Lightning invoice
payment = wallet.pay_invoice(
invoice="lnbc...",
fallback_amount_sats=None,
personal_note="Paying for coffee",
)
payment = wallet.wait_for_payment(index=payment.index, timeout_secs=15)
print(f"Payment: {payment.status}")
Metadata
Release files for lexe-sdk 0.1.21
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 |
|---|---|---|---|---|
| lexe_sdk-0.1.21.tar.gz | 644.1 kB | With provenance | Details for lexe_sdk-0.1.21.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| lexe_sdk-0.1.21-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for lexe_sdk-0.1.21-py3-none-win_amd64.whl |
| lexe_sdk-0.1.21-py3-none-manylinux_2_28_aarch64.whl | Python 3 | none | Linux glibc 2.28+ ARM64 | Details for lexe_sdk-0.1.21-py3-none-manylinux_2_28_aarch64.whl |
| lexe_sdk-0.1.21-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details for lexe_sdk-0.1.21-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| lexe_sdk-0.1.21-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for lexe_sdk-0.1.21-py3-none-macosx_11_0_arm64.whl |
Total release size: 25.8 MB
Release files / lexe_sdk-0.1.21.tar.gz
| Download URL | lexe_sdk-0.1.21.tar.gz |
|---|---|
| Size | 644.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5382f0f8fc8fdaa9bc50747734a710edd830696c97d970b9a0c2c0007ef0e11a
|
|
BLAKE2b-256 checksum How to use checksums |
a6eb3b81fdc66c0595ca0e792334d52a5e03b47f403ed989e9d49434bdf11539
|
| 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 Oct 2, 2026.
Transparency logRelease files / lexe_sdk-0.1.21-py3-none-win_amd64.whl
| Download URL | lexe_sdk-0.1.21-py3-none-win_amd64.whl |
|---|---|
| Size | 5.8 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
4fe79eae6dc18887e40d392f4a26f5d3bdf60646de42d2e3dfaac3135182b359
|
|
BLAKE2b-256 checksum How to use checksums |
6f9446e168fee0b4d184416aabdbbb563c02e9cc8dd7965ed337a8cd8d50e65a
|
| 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 Oct 2, 2026.
Transparency logRelease files / lexe_sdk-0.1.21-py3-none-manylinux_2_28_aarch64.whl
| Download URL | lexe_sdk-0.1.21-py3-none-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 6.7 MB |
| Tags | Linux glibc 2.28+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
6d5c22dc5b45c4256ab53251f0615b310d54a61215aa5de05219750dc53ad74a
|
|
BLAKE2b-256 checksum How to use checksums |
035c8ecb22f83ce0a2e4ca08eacdbcb83dd1d72b5f368bf18625586373663301
|
| 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 Oct 2, 2026.
Transparency logRelease files / lexe_sdk-0.1.21-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | lexe_sdk-0.1.21-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
c5c112d2e4551f9e817bc343bdf8661a52787c052d62db86629961f044aa2e5e
|
|
BLAKE2b-256 checksum How to use checksums |
c01de131b264b2aa9eaac673bd5b81f3e1def2ddc5a5758dc1cb7edbba22270c
|
| 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 Oct 2, 2026.
Transparency logRelease files / lexe_sdk-0.1.21-py3-none-macosx_11_0_arm64.whl
| Download URL | lexe_sdk-0.1.21-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
103cd80aa02134ad9d8b55ce9e6146ebef1ad67e01463935bc63d98d172b4884
|
|
BLAKE2b-256 checksum How to use checksums |
1a2c5f1d34a99a01ee297f7bcf8b84aecffef738b1746cab7014de8eb77412a2
|
| 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 Oct 2, 2026.
Transparency logSecurity for lexe-sdk 0.1.21
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 5 files in this release have been uploaded with provenance metadata.
Attestation for lexe_sdk-0.1.21.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 Oct 2, 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.
