LapseCoin
Peer-to-peer electronic cash, secured by a Verifiable Delay Function instead of proof-of-work mining, with quantum-resistant signatures.
Recommended: use a pre-built release. Building from source requires native libraries (liboqs, chiavdf) that involve complex C/C++ compilation and can produce DLL or shared library errors depending on your platform. The release binaries on the downloads page are self-contained and require no dependencies.
Join the Discord for discussions, news, and trades with other coins.
Quick start
Grab a binary from the downloads page, self-contained with no dependencies.
# Linux # Windows
chmod +x lapsecoin lapsecoin.msi
./lapsecoin
You'll be prompted for a signing passphrase, then the wallet is at http://localhost:8335 and the block explorer at http://localhost:8333.
For headless environments (Docker/systemd/CI, no GUI), set the passphrase non-interactively and pass --no-gui:
export LAPSECOIN_PASSPHRASE="your passphrase"
./lapsecoin --no-gui
Your wallet
The first start creates a wallet and shows its recovery phrase (12 words) once, in the window or the terminal. Write it down: it restores every address of the wallet on any machine. It is kept in lapsecoin_wallet.json, encrypted under your passphrase.
- More addresses. The Addresses page adds one, names them and shows each balance (
--new-addressdoes the same from the terminal). Each address is its own account. The node mines and builds as the one it started with (--account N, default 0; a name you gave the address works too); Send and the board let you pick which address signs, and remember the last one you used. - A key for another machine. On a box that should mine without holding your recovery phrase, run it with one address's key only: Addresses > Export a key, or
./lapsecoin --export 1. Give a name instead (./lapsecoin --export rig1) and the address is created on the spot if you have none by that name, sorig1andrig2each get their own key to paste on their own machine, and you watch them all from here. It prints about 120 characters (lc1-...) sealed under a new passphrase. On that machine use it as--keyor$LAPSECOIN_KEY(withLAPSECOIN_PASSPHRASE). It never holds the phrase, so losing the machine exposes that one address and nothing else. Nothing is written to disk there. - Restoring. In an empty folder,
./lapsecoin --restoreasks for the phrase (hidden input, or piped in) and a passphrase. When the node has synced it finds the other addresses the phrase has used. - Upgrading an older node. A node that still has
lapsecoin_key.jsonmoves to a recovery phrase at its next start: it creates the wallet under the same passphrase, shows the phrase once and runs as the new address. Once synced it sends the old address's funds to it in one ordinary transaction and deletes the old key. Without a terminal or window (Docker, systemd) the phrase is printed once to the program's output, never to the log file.
The phrase follows the convention on the wallet integration page, so other wallets that follow it restore the same addresses. FALCON key generation from a seed is not in liboqs, so a small library built from the same PQClean sources (native/falcon_seeded) provides it; the install scripts and releases include it, and a source checkout builds it with make -C native/falcon_seeded.
Fee requests
Fees in the wallet gets you gas on another chain: pick the network and what you want to do, sign with the wallet that holds the address, and burn 10 LAPSE (returned only if no node offers). To serve requests, fund the Base address on Send. A node helps while that wallet holds enough, and does nothing otherwise.
Exchanges
No LAPSE exchange listings yet.
In the meantime, the Discord is the place to trade directly with other members.
Support the project: BTC bc1q8qxvr5zuws78650wz9rgzpqxfx7dqzl38rdtsw
1 maintainer
Metadata
1 maintainer
Release files for lapsecoin 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lapsecoin-1.1.1.tar.gz | 732.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lapsecoin-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 MB
Release files / lapsecoin-1.1.1.tar.gz
| Download URL | lapsecoin-1.1.1.tar.gz |
|---|---|
| Size | 732.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e1eb348a53b8922de1301011128d8497e02fe5ddf2cde2ee9581cd739b35ef6
|
|
BLAKE2b-256 checksum How to use checksums |
c16721fb6d9ef9555b51534f6547e2893b7d7e4d8d87196e4f28b9427d1f9f51
|
| 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 16, 2026.
Transparency logRelease files / lapsecoin-1.1.1-py3-none-any.whl
| Download URL | lapsecoin-1.1.1-py3-none-any.whl |
|---|---|
| Size | 580.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f4d49af2b96d1592731d099d78a9d6e744c6f27e19be7423de5b578af976ab1
|
|
BLAKE2b-256 checksum How to use checksums |
8a103c25b8f44ec912561cb1130b0da86929ae0f86a8be0ae3762ce5968598eb
|
| 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 16, 2026.
Transparency log
