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

The node starts at once. Its wallet is at http://localhost:8335, which asks for your passphrase the first time you open it (that is what lets the node answer fee requests from its Base wallet), and the block explorer is at http://localhost:8333. The very first start, an old key file being moved, and a wallet whose recovery phrase was never confirmed ask for the passphrase in the window before starting, because they have a phrase to show.

For headless environments (Docker/systemd/CI, no GUI), pass --no-gui. With a terminal it prompts for the passphrase; without one it starts anyway and asks on the wallet page, or you can set it up front:

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-address does 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, so rig1 and rig2 each 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 --key or $LAPSECOIN_KEY (with LAPSECOIN_PASSPHRASE). It never holds the phrase, so losing the machine exposes that one address and nothing else. Nothing is written to disk there.
• A miner with no key at all. Give a machine just an address: ./lapsecoin --address tree.mention.pride... (or LAPSECOIN_ADDRESS). It builds blocks and the reward goes to that address; there is no passphrase, nothing to unlock, and nothing on the machine that can spend. It cannot send, post, vote or answer fee requests, and says so on those pages. The address can be pasted with dots, spaces, commas or line breaks between the words. Addresses have no checksum, so check the words before you start. Give each machine its own address (Addresses > New address); two machines on one address compute the same block.
• What wins when more than one is given. Each of --address, --key and --account says who the node is, so give at most one (two is an error that names them). --account N (or a name) runs as that address of the wallet file here and beats the environment. With none, LAPSECOIN_ADDRESS or LAPSECOIN_KEY (again at most one). With none, the wallet file, then an old key file to move, then a new wallet. The command line beats the environment, and either beats what is on disk; the log says what was passed over. If an address or a key turns out to be one of the wallet file's own addresses, the log says so and what you gave still runs (use --account N to run as it with signing). ./lapsecoin -h lists every option and variable, and Config > Decisions in the wallet shows what applied to this run and why: who it runs as, when it asks for a passphrase, its ports and peers, and what was passed over.
• Restoring. In an empty folder, ./lapsecoin --restore asks 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.json moves 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