Skip to main content
LapseCoin logo

LapseCoin

Peer-to-peer electronic cash, secured by a Verifiable Delay Function instead of proof-of-work mining, with quantum-resistant signatures.

Release Live node Whitepaper Donate BTC Discord Reddit

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 releases 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 releases page, self-contained with no dependencies.

# Linux                    # Windows
chmod +x lapsecoin         lapsecoin.exe
./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
How consensus works

Most cumulative proven work wins, Bitcoin-style. Two blocks at the same height carry equal work, so that tie goes to the lower VDF output, not to whichever arrived first. A height stays open to a better sibling for a few seconds (LAPSECOIN_DRAW_WINDOW_SECONDS) so the comparison can happen; work on the next height never stops meanwhile.

Block timing is enforced by a VDF anchored to real elapsed time, believed to have a much smaller hardware-advantage gap than proof-of-work. Transactions are ordinary and plaintext, with sender-bid fees, much like Bitcoin's own. Signatures are FALCON-512 (quantum-resistant). Full spec in docs/whitepaper.md.

Running from source

Requires Python 3.11+.

Linux/macOS:

curl -fsSL https://raw.githubusercontent.com/Lapsecoin/core/main/scripts/install.sh | bash

Windows (PowerShell):

irm https://raw.githubusercontent.com/Lapsecoin/core/main/scripts/install.ps1 | iex

Then: lapsecoin. Installs build tools if missing, then the app; falls back to skipping libtorrent (with a starter peers list) only if that's what fails.

Building the binary yourself
pip install pyinstaller cairosvg Pillow miniupnpc
make linux    # on Linux
make windows  # on Windows

Produces a self-contained binary in dist/. Requires cmake, ninja, and a C compiler (on Windows, also liboqs and MSVC redistributables).

Updating, and when it isn't optional

A node too old to speak the current wire format is refused at the handshake, so it sits alone mining a chain nobody sees. Old formats aren't carried forever, so some updates are mandatory. The version number says which:

Change Example What it means
Third number 0.6.0 to 0.6.1 Fixes. Update when convenient
Second number 0.5.1 to 0.6.0 Required. Wire format changed, older nodes are dropped
First number 0.x to 1.x Consensus break. Required, expect a resync

Alone with no peers after everyone else updated? Check your version first.

Ports and passphrase
Port Interface Purpose
Public 8333 (--port) 0.0.0.0 Peer traffic (UDP) and the read-only node UI (TCP). Safe to expose. Send disabled.
Private port+2 (--private-port) 127.0.0.1 Wallet UI. Never expose. Full access, including Send.

port+3 is reserved for the DHT subsystem (libtorrent). Port 18334 is fixed and reserved across every node for same-network peer discovery (broadcast-based, finds other LapseCoin nodes on your LAN automatically regardless of their own port). Don't bind other services to either.

The passphrase is required to start the node. By default you're prompted via getpass (nothing touches shell history or ps). For Docker/systemd/CI, set it non-interactively instead:

export LAPSECOIN_PASSPHRASE="your passphrase"
python main.py

There is no --passphrase flag, since it was removed because it leaked into ps aux and shell history.

The peer port can be set the same way, which is often easier than a flag in a container or unit file:

export LAPSECOIN_PORT=8444
python main.py

--port still wins if you pass it, so the variable sets the default rather than overriding what you typed. The private port follows from it as usual unless you set --private-port.

The log level can be set the same way:

export LAPSECOIN_LOG_LEVEL=DEBUG
python main.py

--log-level still wins if you pass it.

Settings and environment variables

Node-local settings live on the private wallet UI under Settings, and each can also be set by environment variable. The environment wins, so a container or unit file can force a value for one launch without overwriting what's saved; a value set that way shows on the page as forced rather than editable.

Variable Default Meaning
LAPSECOIN_SWAP_CONFIRM_DEPTH 2 How many blocks must bury a LapseCoin payment before a swap treats it as settled
LAPSECOIN_SWAP_AUTO_ACCEPT_MIN_TRUST 0 Minimum counterparty trust score for a fill request to auto-accept

Upgrading from 0.6.2 or earlier with the privacy setting on? That version created a second key file, lapsecoin_key.json.privacy, and advertised its address for peers to pay. Nodes no longer advertise an address at all, so nothing creates or uses that file any more, but yours still exists and may hold what peers already sent it. Keep it, and back it up. It is an ordinary key file with its own salt, so the same passphrase opens it on its own whenever you want those funds.

All CLI options
Option Default Description
--host 0.0.0.0 Interface to bind for the public port
--port 8333 Public port for HTTP API and peer connections
--private-port port+2 Private port for wallet UI, always bound to 127.0.0.1
--keyfile lapsecoin_key.json Path to encrypted keypair
--db lapsecoin_chain.db Path to SQLite chain database
--peer host:port - Bootstrap peer (repeatable)
--max-peers 125 Hard cap on peer table size
--log-level INFO (or LAPSECOIN_LOG_LEVEL) Verbosity: DEBUG, INFO, WARNING, ERROR. DEBUG adds the HTTP access log
--no-gui off Headless. Implied when LAPSECOIN_PASSPHRASE is set
--no-update-check off Don't check for new releases
--update-check-url (project) Where to look for the current version
--releases-url (project) Where the update notice points people

Exchanges

No LAPSE exchange listings yet.

In the meantime, Discord allows direct trades with XLM, as well as the in-app Market (beta). Default rate is 1 XLM for 1000 LAPSE.

Support the project: BTC bc1q8qxvr5zuws78650wz9rgzpqxfx7dqzl38rdtsw

Metadata

Release files for lapsecoin 0.8.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lapsecoin 0.8.5
File Size Uploaded
lapsecoin-0.8.5.tar.gz 633.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for lapsecoin 0.8.5
File Interpreter ABI Platform
lapsecoin-0.8.5-py3-none-any.whl Python 3 none any Details

Total release size: 1.1 MB

Release files / lapsecoin-0.8.5.tar.gz

Download URL lapsecoin-0.8.5.tar.gz
Size 633.9 kB
Tags Source
SHA-256 checksum
How to use checksums
862759d17e52f81083f1b084af600c4a77cefde774e2a9c923bdf35f8e4142c6
BLAKE2b-256 checksum
How to use checksums
42b032b09871fcba575f35708626a65e7c956d44d335df200db3b9ba6ad0bb3e
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 27, 2026.

Transparency log

Release files / lapsecoin-0.8.5-py3-none-any.whl

Download URL lapsecoin-0.8.5-py3-none-any.whl
Size 482.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f5527b1eeeabc367b82c016c428d12d33f34d80496043d8ae2f786d28f2f8c6e
BLAKE2b-256 checksum
How to use checksums
0938d5c652b928d9f27e07bfd55dd4dc3dfca0a23fb4215d46da3eaafd67a26b
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 27, 2026.

Transparency log

Release history Release notifications | RSS feed

1.0.15

2 release files

1.0.14

2 release files

1.0.13

2 release files

1.0.12

2 release files

1.0.11

2 release files

1.0.10

2 release files

1.0.9

2 release files

1.0.8

2 release files

1.0.7

2 release files

1.0.6

2 release files

1.0.5

2 release files

1.0.4

2 release files

1.0.3

2 release files

1.0.2

2 release files

1.0.1

2 release files

1.0.0

2 release files

0.8.15

2 release files

0.8.14

2 release files

0.8.13

2 release files

0.8.12

2 release files

0.8.11

2 release files

0.8.10

2 release files

0.8.9

2 release files

0.8.8

2 release files

0.8.7

2 release files

0.8.6

2 release files

This release

0.8.5 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page