# Lokiwiki - Flokicoin Knowledge Source > Technical guides for Flokicoin, Lokichain, and the Lokihub ecosystem. This file contains all documentation content in a single document following the llmstxt.org standard. ## Economy import EconomyNow from '@site/src/components/EconomyNow'; // eslint-disable-line no-unused-vars import Amount from '@site/src/components/Amount'; // eslint-disable-line no-unused-vars import rewardOverTimeImage from './reward_over_time.webp'; import supplyOverTimeImage from './supply_over_time.webp'; import inflationRateImage from './inflation_rate_over_10_years.webp'; ## How the Money Works Flokicoin's monetary policy is hard-coded. Every number on this page is verifiable on-chain — no surprises, no changes behind closed doors. ## Key Numbers - **Block time** — 1 minute. - **Halving** — Every 210,000 blocks (~5 months). - **Starting reward** — FLC per block. - **Tail emission** — A permanent FLC per block once halvings finish. - **Coinbase maturity** — 300 blocks (~5 hours before you can spend mined coins). ## How the Block Reward Changes Over Time The reward starts high and halves on a fixed schedule. Once it would drop below , it stays there forever. That's the tail emission — a permanent security budget that keeps miners incentivized indefinitely. :::important[Why tail emission matters] Most chains with a hard cap will eventually rely only on transaction fees to pay miners. Flokicoin avoids that gamble with a small, constant block reward that never stops. ::: ## Reward Schedule | Blocks | Reward | Approx. Halving Date | Cumulative Supply (million FLC) | |---------------------|------------------------------:|-----------------------|--------------------------------:| | → 210,000 | | 2025-11-26 | 210.00 | | 210,000 → 420,000 | | 2026-04-20 | 315.00 | | 420,000 → 630,000 | | 2026-09-13 | 367.50 | | 630,000 → 840,000 | | 2027-02-06 | 393.75 | | 840,000 → 1,050,000 | | 2027-07-02 | 406.88 | | 1,050,000 → 1,260,000 | | 2027-11-25 | 413.44 | | 1,260,000+ | (fixed) | — | - | ## Long-Term Inflation Once tail emission kicks in, new coins are minted at a fixed rate of FLC per year. Because the total supply keeps growing, the inflation rate drops every year: ### Definitions - Annual issuance E = R × B, where R is the per‑block reward () and B is blocks per year (525,600). - Annual inflation (%) = (E ÷ total supply at year start) × 100. :::note Projections assume the average block interval stays close to 1 minute. Real‑world issuance varies with network conditions. ::: | Year | Total Supply(million FLC) | Annual Inflation Rate(%) | |-----:|-------------------------------:|-----------------------------:| | 1 | 424.48 | 2.67 | | 2 | 435.51 | 2.60 | | 3 | 446.55 | 2.53 | | 4 | 457.59 | 2.47 | | 5 | 468.63 | 2.41 | | 6 | 479.67 | 2.36 | | 7 | 490.70 | 2.30 | | 8 | 501.74 | 2.25 | | 9 | 512.78 | 2.20 | | 10 | 523.82 | 2.15 | ## Live Metrics Real-time numbers from the Flokicoin network: --- ## Lokiwiki — Flokicoin Documentation & Guides import heroImage from './hero.webp'; import Link from '@docusaurus/Link'; // eslint-disable-line no-unused-vars import Heading from '@theme/Heading'; // eslint-disable-line no-unused-vars import { Wallet, Zap, Pickaxe, Code, TrendingUp, Server } from 'lucide-react'; Such Wiki Practical docs for the Flokicoin ecosystem. Get a Wallet Run a Node Explore Lokihub How to Participate Pick a path and get started. {/* --- Wallets Path --- */} Wallets Secure your assets. Find the perfect wallet for your needs, including the recommended tWallet with Lightning support. {/* --- Lokihub Path --- */} Lokihub Run your Lightning node. Manage funds, channels, and apps from a single dashboard. {/* --- Miner Path --- */} Mining Start earning rewards. Help secure the network with GPU or ASIC mining and join community pools. {/* --- Developer Path --- */} Builders Build the future. Explore RPC parameters, FIPs, and the core reference implementation for Lokichain. {/* --- Economy Path --- */} Economy Understand scarcity. Track the issuance schedule, halving cadence, and the long-term tail emission model. {/* --- WoF Path --- */} Web of Fun Explore apps. Build and use everyday services powered by the Nostr protocol and decentralized work.
Looking for AI Context files? We publish llms.txt and llms-full.txt static files containing the full docs in a streamlined Markdown-style format optimized for AI.
--- ## FIP-05: Difficulty Adjustment Author: Thiniboy Status: Final Created: 2025-07-18 ## Summary Adopt a per-block, Digishield-style difficulty retarget using an exponential moving average (EMA) toward the one-minute target spacing. The algorithm improves responsiveness to hashrate shocks while damping oscillations and reducing variance. ## Motivation Long retarget windows allow exploitable oscillations and long periods of off-target difficulty. A per-block EMA responds quickly to changes while preserving stability. ## Specification - Target spacing T = 60 seconds. - At each block n, update an EMA of observed spacings with amplitude divisor 8 (effectively an 8-sample EWMA). - Apply bounded damping on each step to limit the effective spacing influence to the range [0.75·T, 1.5·T]. - Compute the next target by scaling the previous target by the ratio of clamped spacing to T, subject to consensus limits. - Allow minimum-difficulty blocks when the observed spacing exceeds a chain-parameterized threshold (where enabled). :::important **Activation (mainnet):** block 115,000. ::: ## Rationale Per-block EMA reduces lag compared to long-window retargets while the clamp prevents over-reaction to outliers. Similar approaches were proven in other UTXO chains under the “Digishield” family. ## Reference Implementation Implemented in `go-flokicoin` and enabled via chain parameters. See release [0.25.7-beta](/lokichain/releases/0.25.7-beta) and consensus changes therein. ```text Inputs: T := 60 seconds (target spacing) Divisor := DigishieldAmplitudeDivisor (8 in Flokicoin) ClampMin := 0.75 × T ClampMax := 1.50 × T prevTarget := last difficulty target (integer) actualSpan := timestamp_n - timestamp_{n-1} Algorithm: 1. modulatedSpan ← T + (actualSpan - T) / Divisor 2. modulatedSpan ← clamp(modulatedSpan, ClampMin, ClampMax) 3. nextTarget ← prevTarget × modulatedSpan / T 4. nextTarget ← min(nextTarget, PowLimit) Result: Convert nextTarget back to compact bits for the header. Note: when ReduceMinDifficulty is enabled, a separate rule mints a minimum-difficulty block if actualSpan exceeds DigishieldLateBlockMultiple × T. That shortcut is orthogonal to the per-block EMA above. ``` --- ## FIP-06: Merge Mining Author: Izimmerma <izimer@ohstr.com> Status: Final Created: 2025-08-15 ## Abstract Lokichain adopts Auxiliary Proof-of-Work (AuxPoW) so miners can reuse work found on a parent proof-of-work chain. The AuxPoW envelope supplies the parent header, coinbase commitment, and merkle proofs needed to show that the Lokichain block header was embedded in the parent block’s work. ## Motivation Merge mining allows Lokichain to inherit a larger network’s hashrate without demanding miners split their effort. Following established AuxPoW conventions reduces the integration burden for mining pools while preserving consensus clarity. ## Terminology - **Parent blockchain:** The network whose valid block header and proof-of-work are reused by Lokichain (e.g., any scrypt-family PoW chain). - **Auxiliary blockchain:** Lokichain, which validates AuxPoW data and accepts the parent work as its own. - **AuxPoW block:** A Lokichain block that may not satisfy the child difficulty target on its own but includes proofs that the parent block’s work does. - **Aux work merkle tree:** The commitment structure rooted in the parent coinbase that yields both the coinbase branch (into the parent merkle root) and the chain branch (down to the Lokichain header commitment), enabling multiple auxiliary chains to share a single parent block. ## Specification Lokichain marks a header as AuxPoW-enabled by setting bit 8 of the version field (`VersionAuxPow`) and writing the six-bit chain identifier into bits [16..21]. When this flag is present the node appends the following payload immediately after the 80-byte base header and before the transaction vector: | Field | Type | Purpose | | --- | --- | --- | | `aux_version` | 1 byte | AuxPoW payload version. Lokichain uses `0x00`. | | `parent_coinbase_tx` | Serialized transaction | Full parent coinbase transaction containing the merge-mining commitment. | | `coinbase_branch` | Merkle branch (`var_int` length, 32-byte hashes, 32-bit side mask) | Proves the coinbase transaction is included in the parent merkle root. | | `chain_branch` | Merkle branch (optional) | Proves the Lokichain commitment within the Aux work merkle tree; empty when the parent block services only Lokichain. | | `parent_header` | 80-byte serialized header | Parent chain header whose proof-of-work will be validated against Lokichain’s requirement. | ### Aux proof-of-work block Fields serialize in the table order above. `aux_version` is fixed at `0x00`; `coinbase_branch` must have a side mask of `0` because the coinbase resides at index 0; `chain_branch` may be length zero when Lokichain is the only auxiliary chain. Lokichain omits the legacy standalone `block_hash` element—nodes recompute it from the provided header and merkle data. ### Parent coinbase commitment Miners place the merged-mining marker `0xfa 0xbe 'm' 'm'` in the `scriptSig` of `parent_coinbase_tx`, immediately followed by: 1. `chain_root` — the double-SHA256 root obtained by folding `chain_branch` over the current Lokichain block hash, encoded little-endian in the script. 2. `tree_size` — a little-endian `uint32` that must equal `1 << chain_branch.Size()`. 3. `merkle_nonce` — a little-endian `uint32` mixed with the AuxPoW `chain_id` to pick Lokichain’s deterministic slot in the Aux work tree. :::tip Lokichain uses `0x21` as its AuxPoW `chain_id`. ::: When only Lokichain participates, `chain_branch` is length zero and `chain_root` is just the current Lokichain block hash. With multiple auxiliary chains, miners supply the branch proving Lokichain’s leaf inside the shared Aux work tree. ### Validation rules Lokichain consensus validates AuxPoW blocks as follows: - Require the AuxPoW header bit and correct `ChainID` encoding for the current network parameters. - Hash `parent_header` and ensure the resulting proof-of-work meets or exceeds the Lokichain difficulty target for the block height. - Recalculate the parent merkle root using `parent_coinbase_tx` and `coinbase_branch`, ensuring it matches the root in `parent_header`. - Verify `coinbase_branch.SideMask` is zero and the coinbase transaction size stays within consensus limits. - Combine the current Lokichain block hash with `chain_branch` (if present) to derive `chain_root`, and verify the little-endian bytes appear in the parent coinbase exactly after the merged-mining marker. - Check that `tree_size` equals `1 << chain_branch.Size()` and that the `SideMask` from `chain_branch` matches the deterministic index `getExpectedIndex(merkle_nonce, chain_id, branch_size)`. - Confirm standard Lokichain consensus rules on the current block header (previous-hash linkage, difficulty bits, median time, and contextual checks). - Reject AuxPoW payloads that include the deprecated `block_hash` field or otherwise mismatch the expected serialization. :::important **Activation (mainnet):** block 115,840. ::: ## Rationale Reusing the long-standing merged-mining structure keeps BIP-compliant semantics while the omission of the redundant `block_hash` field delivers a modest bandwidth and storage optimisation. The structure is compatible with existing pool software that already supports AuxPoW networks. ## Reference Implementation Implemented in `go-flokicoin` (wire + consensus). See release [0.25.7-beta](/lokichain/releases/0.25.7-beta) for activation parameters and wire structs. ### RPC Support AuxPoW mining is exposed over the standard RPC interface: ``` createauxblock ``` Returns an object containing: - `hash` — identifier miners must hash in the parent chain coinbase. - `chainid` — Lokichain’s chain identifier (decimal `33`, hex `0x21`). - `previousblockhash`, `height`, `bits`, `target` — child-chain context and work target. - `coinbasevalue` — child-chain coinbase payout in atomic units. Example response: ``` { "hash": "0c63598bf66646ee9bf80797a40d607d12db9a6bc97fd4b98da70c904dd250c8", "chainid": 33, "previousblockhash": "94f1f588f620713ef99dfb1b2f3079a0f4545d4e15035e8227c5534dea965f33", "coinbasevalue": 100000000000, "bits": "202f725e", "height": 13, "target": "2f725e0000000000000000000000000000000000000000000000000000000000" } ``` Miners call: ``` submitauxblock ``` Where `auxpow_hex` is the serialized AuxPoW payload built from the parent block template. --- ## FIPs Flokicoin Improvement Proposals (FIPs) are design documents providing information to the Flokicoin community, or describing new features, their rationale, and technical specifications. Current proposals: - [FIP-06: Merge Mining](/lokichain/fips/FIP-06) - [FIP-05: Difficulty Adjustment](/lokichain/fips/FIP-05) --- ## Lokichain import Link from '@docusaurus/Link'; import { Rocket } from 'lucide-react'; Lokichain is the blockchain behind Flokicoin. It validates every transaction, enforces the consensus rules, and keeps everything decentralized. If you want to understand the engine under the hood, you're in the right place. :::release **Latest release**: Flokicoin Core [v0.25.12-alpha](/lokichain/releases/0.25.12-alpha) — our current reference implementation. ::: ## Run a Node Running a full node is the most direct way to support the network. Your node verifies the entire chain independently and serves RPCs for wallets, miners, and apps. :::tip[Quick option] Want a simpler setup? Try the community plug‑and‑play node at [myfloki.com/fullnode](https://myfloki.com/fullnode). ::: ## Build on Lokichain Whether you're building a wallet, an explorer, or something new — here's where to start: - **FIPs** — See how the protocol evolves via [Flokicoin Improvement Proposals](/lokichain/fips). - **Releases** — Track every [software version](/lokichain/releases). - **Source code** — Browse and contribute to [go-flokicoin](https://github.com/flokiorg/go-flokicoin). ## Deploy to Lokihub The Lokihub App Store is the central hub for community applications. If you've built a Lightning-enabled app, you can deploy it directly to the ecosystem via our open-source store. Ready to Launch? Learn how to submit your application to the Lokihub App Store and reach thousands of node operators instantly. Submit Your App ## Mine Miners provide the hashpower that makes the chain immutable. You'll need the latest node software and a Scrypt ASIC or GPU. - **Get started** — [Mining setup guide](/mining). ## How It Works Lokichain is a peer-to-peer network. Every node enforces the same rules, so there's no single point of failure. The consensus rules are updated through FIPs — think of them as the "laws" of the network. ## Get Help - **Discord** — Join the conversation in [#dev](https://flokicoin.org/discord). - **GitHub** — Report bugs or suggest features via [Issues](https://github.com/flokiorg/go-flokicoin/issues). --- ## 0.25.1-beta Please report bugs using the issue tracker at GitHub: https://github.com/flokiorg/go-flokicoin/issues GitHub release tag: [v0.25.1-beta](https://github.com/flokiorg/go-flokicoin/releases/tag/v0.25.1-beta) ## Notes - This is a pre-release for testing and feedback. - Developers and early adopters are encouraged to report issues. --- ## 0.25.10-beta GitHub Please report bugs using the issue tracker at GitHub: https://github.com/flokiorg/go-flokicoin/issues This release tightens RPC correctness, improves sync heuristics, refreshes checkpoints, and renames the daemon/CLI binaries. Upgrade to stay aligned with the network and to adopt the new `lokid`/`lokid-cli` names. ## Upgrade notes - Daemon and CLI renamed to `lokid` and `lokid-cli` (previously `flokicoind`/`flokicoind-cli`). Update service files, scripts, and container entrypoints accordingly. ## Highlights - Consensus and checkpoints - Refreshed mainnet checkpoints through height 209,771 to speed up initial sync. - Networking and sync - Improved outbound peer group tracking and ensured peers answer `getblocks`, reducing stalls near tip. - Tightened download scheduling when already current to avoid redundant fetches. - Refined block header/message serialization for sturdier I/O paths. - RPC - `getblockchaininfo` now derives verification progress from best peer headers; `getblock` exposes richer block details. - `getrawtransaction` response types and help text now match payloads; `createrawtransaction` enforces stricter amount validation. - Added block statistics aggregation powering `getblockstats` (fee/size percentiles, UTXO deltas). - `getinfo` reports the correct P2P protocol version and fills missing fields. - Mempool and validation - Switched value bounds to full `int64` range and guarded dust checks against overflow when computing `MaxLoki`/fee policy. - Validation errors now emit properly cast `MaxLoki` values to avoid misleading messages. - Tooling and tests - Added deterministic block dataset generator (`make testexport`) and refreshed fixtures for CI stability. - Strengthened difficulty/statistics and outbound group accounting test coverage. ## Notable commits (chronological) - Tooling/fixtures refresh and `testexport` helper ([`31eff16`](https://github.com/flokiorg/go-flokicoin/commit/31eff16), [`0e5dcd3`](https://github.com/flokiorg/go-flokicoin/commit/0e5dcd3)). - RPC/build fixes for protocol/version reporting and banners ([`651a453`](https://github.com/flokiorg/go-flokicoin/commit/651a453), [`2e92497`](https://github.com/flokiorg/go-flokicoin/commit/2e92497)). - Policy safety for `MaxLoki` range and dust overflow guards ([`9d9eef1`](https://github.com/flokiorg/go-flokicoin/commit/9d9eef1), [`5b583c0`](https://github.com/flokiorg/go-flokicoin/commit/5b583c0)). - RPC correctness updates and block stats package ([`4483bfa`](https://github.com/flokiorg/go-flokicoin/commit/4483bfa), [`ed3f11b`](https://github.com/flokiorg/go-flokicoin/commit/ed3f11b), [`04bfa8b`](https://github.com/flokiorg/go-flokicoin/commit/04bfa8b)). - Daemon rename, checkpoints, sync/p2p/rpc refinements leading to 0.25.10-beta ([`66a4658`](https://github.com/flokiorg/go-flokicoin/commit/66a4658), [`037c55c`](https://github.com/flokiorg/go-flokicoin/commit/037c55c), [`9f457dd`](https://github.com/flokiorg/go-flokicoin/commit/9f457dd), [`3388ec1`](https://github.com/flokiorg/go-flokicoin/commit/3388ec1), [`3d115e4`](https://github.com/flokiorg/go-flokicoin/commit/3d115e4), [`5eadc7b`](https://github.com/flokiorg/go-flokicoin/commit/5eadc7b), [`91a004e`](https://github.com/flokiorg/go-flokicoin/commit/91a004e), [`fbbef28`](https://github.com/flokiorg/go-flokicoin/commit/fbbef28)). ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.10-beta/lokid-darwin-arm64-v0.25.10-beta.tar.gz | | macOS (Intel) | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.10-beta/lokid-darwin-amd64-v0.25.10-beta.tar.gz | | Linux x86_64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.10-beta/lokid-linux-amd64-v0.25.10-beta.tar.gz | | Linux arm64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.10-beta/lokid-linux-arm64-v0.25.10-beta.tar.gz | | Windows x86_64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.10-beta/lokid-windows-amd64-v0.25.10-beta.zip | | Windows 32-bit | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.10-beta/lokid-windows-386-v0.25.10-beta.zip | Additional builds (ppc64, mips, *BSD, illumos/solaris) are available on the [GitHub release page](https://github.com/flokiorg/go-flokicoin/releases/tag/v0.25.10-beta). --- ## 0.25.12-alpha GitHub Please report bugs using the issue tracker at GitHub: https://github.com/flokiorg/go-flokicoin/issues This release introduces significant improvements to fee estimation logic, including atomic persistence to disk, better history tracking, and smarter handling of removal reasons. ## Upgrade notes - Fee estimator snapshots now live on disk as `fee_estimates.dat` under the data dir (atomic write/read). Ensure the daemon can write there on shutdown; stale files older than ~60h are ignored on startup. ## Highlights - **Fee estimation** - Tracks up to 1008 blocks of history and caps long-horizon queries instead of rejecting them, aligning with Bitcoin Core behavior (`mempool/estimatefee.go`). - Records mempool removal reasons so unconfirmed drops (conflicts, reorgs, evictions, rejects) clear estimator state and reduce stale observations (`mempool` plumbing, `netsync/manager.go`, `rpcserver.go`). - `estimatesmartfee` accepts `economical` or `conservative` modes (defaults conservative) and reports invalid modes cleanly; result now includes an explicit `errors` field (`rpcserver.go`). - **Persistence** - Fee estimator state is saved atomically to disk on shutdown and restored on startup when fresh; stale data surfaces an error and is skipped. Helpers and tests cover the binary format and max-age enforcement (`mempool/fee_persist*.go`, `server.go`). ## Notable commits (planned batch) - mempool: track removal reasons in fee estimation; widen history to 1008 blocks and cap queries. - mempool: persist fee estimator to disk with atomic writes and staleness checks. - Added aggregated nonce signing flow for MuSig2, including updated context handling and comprehensive tests. ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.12-alpha/lokid-darwin-arm64-v0.25.12-alpha.tar.gz | | macOS (Intel) | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.12-alpha/lokid-darwin-amd64-v0.25.12-alpha.tar.gz | | Linux x86_64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.12-alpha/lokid-linux-amd64-v0.25.12-alpha.tar.gz | | Linux arm64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.12-alpha/lokid-linux-arm64-v0.25.12-alpha.tar.gz | | Windows x86_64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.12-alpha/lokid-windows-amd64-v0.25.12-alpha.zip | | Windows 32-bit | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.12-alpha/lokid-windows-386-v0.25.12-alpha.zip | Additional builds (ppc64, mips, *BSD, illumos/solaris) are available on the [GitHub release page](https://github.com/flokiorg/go-flokicoin/releases/tag/v0.25.12-alpha). --- ## 0.25.5-beta Please report bugs using the issue tracker at GitHub: https://github.com/flokiorg/go-flokicoin/issues ## Notable changes - Added new blockchain checkpoints, including at block 0 and later heights. - Enhanced PSBT handling: support for extended public keys (XPubs) and path validation. - Added PSBT test coverage for BIP32 path serialization/deserialization. - Improved validation of PSBT path minimum length. - Improved block header timestamp validation. - Updated mempool, txscript, and wallet to use `maps.Copy` for safer and cleaner map handling. - Fixed typo: corrected PSBT constant from `XpubType` to `XPubType`. - Fixed minor issues in PSBT encoding/decoding and comments. - Renamed `flokicoin-cli` to `flokicoind-cli` across all binaries, config paths, and documentation. ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.5-beta/flokicoind-darwin-arm64-v0.25.5-beta.tar.gz | | macOS (Intel) | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.5-beta/flokicoind-darwin-amd64-v0.25.5-beta.tar.gz | | Linux x86_64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.5-beta/flokicoind-linux-amd64-v0.25.5-beta.tar.gz | | Linux arm64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.5-beta/flokicoind-linux-arm64-v0.25.5-beta.tar.gz | | Windows x86_64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.5-beta/flokicoind-windows-amd64-v0.25.5-beta.zip | --- ## 0.25.6-beta Please report bugs using the issue tracker at GitHub: https://github.com/flokiorg/go-flokicoin/issues ## Notable changes - Update testnet3 and regression chain parameters. - Adjust difficulty logic for testnet4. - Restore default PoW limits for regression network. - Update version bits deployment thresholds and timings. - Remove legacy difficulty calculation fallback. - Clean up block version test formatting. ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.6-beta/flokicoind-darwin-arm64-v0.25.6-beta.tar.gz | | macOS (Intel) | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.6-beta/flokicoind-darwin-amd64-v0.25.6-beta.tar.gz | | Linux x86_64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.6-beta/flokicoind-linux-amd64-v0.25.6-beta.tar.gz | | Linux arm64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.6-beta/flokicoind-linux-arm64-v0.25.6-beta.tar.gz | | Windows x86_64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.6-beta/flokicoind-windows-amd64-v0.25.6-beta.zip | --- ## 0.25.7-beta Please report bugs using the issue tracker at GitHub: https://github.com/flokiorg/go-flokicoin/issues This is a minor beta release of Flokicoin Core with a new per-block difficulty retarget algorithm (Digishield-style), AuxPoW header and consensus support, testnet feature updates, RPC corrections, and build/test improvements. This release schedules `MAINNET ACTIVATION` for both Digishield and AuxPoW via chain parameters. All mainnet nodes must upgrade before the activation heights below to avoid chain splits. ## Notable changes - Consensus: Digishield difficulty retarget - Introduces a per-block exponential moving average retarget toward the target spacing with amplitude divisor 8. - Applies bounded damping each step (min 0.75x, max 1.5x of target spacing influence) to reduce volatility. - Supports min-difficulty on late blocks where enabled by chain parameters. - Integrates into validation and mining (next-required-bits, block template target) and expands unit/full-block tests. - P2P/Wire: AuxPoW header support - Adds AuxPoW structures (coinbase, merkle branches, parent header) and serialization helpers. - Extends `BlockHeader` with AuxPoW flag and ChainID utilities plus optional AuxPoW payload encode/decode. - Updates `MsgBlock` decoding to parse AuxPoW payloads when present; adds coverage for read/write paths. - Consensus: AuxPoW is activated on mainnet at the height listed below. - Testnet/regtest updates - Enables SegWit and Taproot features on testnet where configured. - Tunes `MinHighPriority` and increases the `MaxLoki` bound used in RPC amount validation. - RPC fixes and improvements - Aligns reported P2P protocol version with `wire.ProtocolVersion` and fills `getinfo` fields (subversion, localservices, connections_in/out, localaddresses) from live server state. - Tooling and tests - Adds `make testexport` target and a deterministic test-data exporter. - Unifies block dataset loader with mandatory network-magic validation; refactors call sites. - Adds an end-to-end difficulty validation over curated datasets and emits steady-state tuning metrics. - Build and configuration - Drops local `replace` override for `flokicoin-neutrino` to avoid developer-only paths. - Prints a single startup banner with semantic version during config load; refactors ASCII-art constants. ## Compatibility - Mainnet will activate Digishield and AuxPoW at fixed heights (below). These are consensus changes and constitute a hard fork at activation. All miners, validators, and services must upgrade before those heights. - AuxPoW wire support remains backward compatible for non-AuxPoW headers until activation height. - No database format changes are introduced. ## Activation schedule (mainnet) - Digishield difficulty retarget: activates at height 115,000 (`DigishieldActivationHeight` in `chaincfg/params.go`). - AuxPoW consensus: activates at height 115,840 (`AuxpowHeightEffective` in `chaincfg/params.go`). These activations are parameterized in `repos/flokiorg/go-flokicoin/chaincfg/params.go` under `MainNetParams`. ## Upgrade notices - Mainnet node operators: upgrade to 0.25.7-beta before heights 115,000 (Digishield) and 115,840 (AuxPoW) to remain on the canonical chain. - Testnet/regtest operators should upgrade to participate in the updated difficulty and feature policies. - Application developers should re-vendor/update to pick up RPC schema fixes and wire additions related to AuxPoW. ## RPC changes - `getinfo` now reports accurate `subversion`, `localservices`, `localservicesnames`, `connections_in`, `connections_out`, and `localaddresses`. - Reported max protocol version aligns with `wire.ProtocolVersion` (70016). ## Build system and tooling - New `make testexport` target to export block datasets for deterministic tests. - Removed local `replace` for `flokicoin-neutrino` to produce clean module graphs in builds. ## Tests and QA - Unified block loader enforces network magic and uses buffered, full-length reads. - Added E2E difficulty validation with metrics output for steady-state analysis. - Curated, smaller test datasets improve determinism and CI time. ## Changelog since [v0.25.6-beta](/lokichain/releases/0.25.6-beta) - b4f439e consensus: add Digishield difficulty retarget - dec0948 wire: integrate AuxPoW header support - 31eff16 chore: repo updates for rpc/db, tests, fixtures - e2ac6e7 tests: validate difficulty dataset and expose tuning metrics - 735410f tests: unify block loader to enforce network magic; refactor call sites - 0e5dcd3 make: add testexport target for exporting block datasets - 651a453 rpc: report correct p2p protocol and fill getinfo fields - bea6a7a build: drop local replace for flokicoin-neutrino - 2e92497 config: print startup banner with version; refactor art constants - b24e870 wire: remove stale TODO comment in protocol.go - 60460f8 enable segiwit/taproot for testnet - f9bf3ae increase maxloki const - 712355d update MinHighPriority const - fa96bbd bump version 0.25.7-dev - 4523b79 version: bump to 0.25.7-beta ## Credits Thanks to everyone who directly contributed to this release: - naliyi - izimmerma - mechion - repins - nanovex - liarpo11 - arowqo - thiniboy ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.7-beta/flokicoind-darwin-arm64-v0.25.7-beta.tar.gz | | macOS (Intel) | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.7-beta/flokicoind-darwin-amd64-v0.25.7-beta.tar.gz | | Linux x86_64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.7-beta/flokicoind-linux-amd64-v0.25.7-beta.tar.gz | | Linux arm64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.7-beta/flokicoind-linux-arm64-v0.25.7-beta.tar.gz | | Windows x86_64 | https://github.com/flokiorg/go-flokicoin/releases/download/v0.25.7-beta/flokicoind-windows-amd64-v0.25.7-beta.zip | --- ## Release Notes Flokicoin Core is the reference full node for the Lokichain. It validates blocks and transactions, enforces consensus, and exposes RPCs for wallets and services. Please report bugs on GitHub: https://github.com/flokiorg/go-flokicoin/issues ## Releases - [0.25.12-alpha](/lokichain/releases/0.25.12-alpha) - [0.25.10-beta](/lokichain/releases/0.25.10-beta) - [0.25.7-beta](/lokichain/releases/0.25.7-beta) - [0.25.6-beta](/lokichain/releases/0.25.6-beta) - [0.25.5-beta](/lokichain/releases/0.25.5-beta) - [0.25.1-beta](/lokichain/releases/0.25.1-beta) --- ## Downloads Download the latest Lokihub release for your operating system. :::release Latest Release: **v0.1.2-alpha** — [View on GitHub](https://github.com/flokiorg/lokihub/releases/tag/v0.1.2-alpha) ::: ## Download Assets ### Desktop | Platform | Download Link | | --- | --- | | Linux (RPM aarch64) | [lokihub-desktop-linux-aarch64-v0.1.2-alpha.rpm](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-desktop-linux-aarch64-v0.1.2-alpha.rpm) | | Linux (AppImage amd64) | [lokihub-desktop-linux-amd64-v0.1.2-alpha.AppImage](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-desktop-linux-amd64-v0.1.2-alpha.AppImage) | | Linux (Deb amd64) | [lokihub-desktop-linux-amd64-v0.1.2-alpha.deb](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-desktop-linux-amd64-v0.1.2-alpha.deb) | | Linux (AppImage arm64) | [lokihub-desktop-linux-arm64-v0.1.2-alpha.AppImage](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-desktop-linux-arm64-v0.1.2-alpha.AppImage) | | Linux (Deb arm64) | [lokihub-desktop-linux-arm64-v0.1.2-alpha.deb](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-desktop-linux-arm64-v0.1.2-alpha.deb) | | Linux (RPM x86_64) | [lokihub-desktop-linux-x86_64-v0.1.2-alpha.rpm](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-desktop-linux-x86_64-v0.1.2-alpha.rpm) | | macOS (Universal) | [lokihub-desktop-macos-v0.1.2-alpha.dmg](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-desktop-macos-v0.1.2-alpha.dmg) | | Windows (x86_64) | [lokihub-desktop-windows-v0.1.2-alpha.zip](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-desktop-windows-v0.1.2-alpha.zip) | ### Server | Platform | Download Link | | --- | --- | | Linux (amd64) | [lokihub-server-linux-amd64-v0.1.2-alpha.tar.gz](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-server-linux-amd64-v0.1.2-alpha.tar.gz) | | Linux (arm64) | [lokihub-server-linux-arm64-v0.1.2-alpha.tar.gz](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-server-linux-arm64-v0.1.2-alpha.tar.gz) | | macOS (Universal) | [lokihub-server-macos-v0.1.2-alpha.zip](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-server-macos-v0.1.2-alpha.zip) | | Windows (x86_64) | [lokihub-server-windows-v0.1.2-alpha.zip](https://github.com/flokiorg/lokihub/releases/download/v0.1.2-alpha/lokihub-server-windows-v0.1.2-alpha.zip) | ## Installation & Usage :::tip If your OS flags the binary as unverified, you may need to explicitly allow it in your security settings. ::: ### Desktop (GUI) **macOS** 1. Open the downloaded `.dmg` file. 2. Drag **Lokihub** to your Applications folder. **Windows** 1. Extract the downloaded `.zip` file. 2. Run `lokihub.exe`. **Linux** - **AppImage**: ```bash chmod +x lokihub-*.AppImage ./lokihub-*.AppImage ``` - **Debian/Ubuntu**: ```bash sudo dpkg -i lokihub-*.deb ``` - **Fedora/RHEL**: ```bash sudo rpm -i lokihub-*.rpm ``` ### Server (HTTP) The server version runs as a background process and serves the web interface via HTTP. 1. **Extract the archive**: ```bash tar -xvf lokihub-server-*.tar.gz # Linux # Or unzip on Windows/macOS ``` 2. **Run the binary**: ```bash ./lokihub ``` 3. **Open in Browser**: Navigate to `http://localhost:1610` (default port). ## Next Steps After installation, follow the [Setup Guide](/lokihub/setup) to connect Lokihub to your FLND node. ## Verify Downloads All releases are published on GitHub with checksums. Visit the [releases page](https://github.com/flokiorg/lokihub/releases) to verify download integrity. --- ## Features Lokihub provides everything you need to run a self-custodial Lightning node. ## Lightning Wallet Send and receive funds through Lightning channels and on-chain transactions. **Capabilities:** - **Send & Receive** — Create Lightning invoices and pay others - **On-Chain** — Regular Flokicoin transactions - **Sub-Wallets** — Separate wallets for different uses - **History** — View all on-chain and Lightning transactions :::tip Lokihub's default currency unit is **Loki**. `1 FLC = 100,000,000 Loki`. ::: ## Channel Management Lightning channels let you send and receive instant payments. Lokihub helps you manage them. **Features:** - **Open Channels** — Connect to other nodes to enable routing - **Close Channels** — Shut down channels and return funds on-chain - **Manual Control** — Open/close channels to specific peers - **Liquidity Visualization** — See how much you can send (outbound) vs receive (inbound) ## Peer Management View and manage your connections to the Lightning Network. - See connected peers - Add new peers manually - Disconnect from peers you no longer need - Update node alias ## App Connections (NWC) Connect external apps to your Lightning node using [**Nostr WalletConnect**](https://nwc.dev) (NWC). NWC is an open standard that lets apps request payments from your wallet without holding your keys. You grant permissions and can revoke access anytime. **How it works:** 1. Open an app that supports NWC 2. In Lokihub, generate a connection string 3. Scan the QR code or paste the connection string in the app 4. Grant permissions (read-only, send up to X amount, etc.) 5. Use the app—it can now request payments from your node **Examples of what you can connect:** - Social apps that need zapping/tipping - Services that need payment authorization - Any NWC-compatible application Learn more about the NWC standard at [nwc.dev](https://nwc.dev). ## Service Freedom Lokihub is community-driven by design. Users can submit PRs to add their own services. You choose. **Configurable Services:** - **LSP** — Lightning Service Provider for inbound liquidity - **Nostr Relay** — Message routing for NWC connections - **Block Explorer** — Transaction lookup and monitoring Switch providers anytime in the Services settings. [Learn more →](/lokihub/services) --- ## Lokihub import Link from '@docusaurus/Link'; # Master Your Lightning Node **Lokihub** gives you complete financial sovereignty over your Lightning node. Beyond just a manager, it's your gateway to the decentralized web—integrated with [tWallet](/wallets/twallet) to help you manage sub-wallets, handle channels, and connect apps via NWC. :::caution[CRITICAL: BACKUP RISK] **Lightning channel funds are NOT stored on the blockchain.** A 24-word seed phrase only recovers your on-chain balance. To avoid total loss of channel funds, you must back up your **Static Channel Backups (SCB)**. [Learn how to protect your node →](/wallets/twallet/v1#critical-lightning-backups) ::: Latest: v0.1.2-alpha Download Setup Guide ## Getting Started ### 1. Download & Install Get Lokihub for your platform and install the binary. [Downloads →](/lokihub/downloads) ### 2. Connect Your Node Connect Lokihub to the FLND node integrated within [tWallet](/wallets/twallet). [Setup Guide →](/lokihub/setup) ### 3. Start Using Manage wallets, open channels, connect apps. [Features →](/lokihub/features) import { Zap, Droplet } from 'lucide-react'; ## What Lokihub Does For You Instant Payments, Zero Middlemen Leverage the Lightning Network for fast, secure, and low-fee transactions. Create dedicated sub-wallets to organize your liquidity for different apps or personal budgets. Full Sovereignty Over Your Liquidity Take direct control of your Lightning channels. Open, close, and manage your inbound and outbound capacity with full manual transparency. Connect Apps Connect external applications to your node using NWC. Grant specific permissions and revoke access when needed. Browse App Store → Choose Services Self-custody means you choose your own providers. Configure your LSP, Nostr relay, block explorer, and messageboards. View Services → ## Documentation - **[Downloads](/lokihub/downloads)** — Get the latest release - **[Setup](/lokihub/setup)** — Connect to your node - **[Features](/lokihub/features)** — Wallet, channels, NWC - **[App Store](/lokihub/store)** — Connect external apps - **[Services](/lokihub/services)** — LSP, relay, explorer - **[Resources](/lokihub/resources)** — Explorers, faucets, tools Need help? Join [Discord](https://flokicoin.org/discord) #lokihub --- ## Resources import resourcesImage from './resources.webp'; import Link from '@docusaurus/Link'; // eslint-disable-line no-unused-vars import Heading from '@theme/Heading'; // eslint-disable-line no-unused-vars import { Telescope, Gamepad2, Pickaxe, Sparkles, Zap } from 'lucide-react';
Community Ecosystem • Maintained & Supported Lokichain Resources Browse community explorers, faucets, mining pools, and helper tooling. Every link here is maintained by trusted operators to keep your nodes, tests, and monitoring on track. Suggest via Discord Open a pull request
Network Explorers Track blocks, transactions, and address balances on mainnet and testnet. flokichain • Mainnet lokichain • Mainnet testnet.flokichain.info • Testnet
Faucet & Mini-Game Collect testnet coins by playing a short community mini-game. lokirace.com
Mining Pool Community pools for Lokichain mining. fpool.net • Mining has never been so easy 🐟 viaflc.com • More Coins Same Power hash2.cash • Where every share counts.
Lokiapps Community-built apps and bundles for Lokichain ecosystem. myfloki.com • Full node + Electrum bundle lokimap.com • Live node map
Electrum Servers Community hosted endpoints for your wallets.
myfloki.com electrum@myfloki.com SSL electrum.myfloki.com:50002 TCP electrum.myfloki.com:50001 WSS electrum.myfloki.com:50004
hashboard.space listing@hashboard.space SSL electrum-flc.hashboard.space:50002 TCP electrum-flc.hashboard.space:50001 WSS electrum-flc.hashboard.space:50004
Keep the list fresh Run a new explorer, tooling bundle, or pool? Open a pull request or drop a link in #builders on Discord and we’ll review it.
--- ## Services # Lokihub Services Lokihub uses external services for Lightning operations, [NWC](https://nwc.dev) communication, and blockchain lookups. You can choose from community defaults or configure your own. ## Service Types ### LSP (Lightning Service Provider) **Optional** — Provides inbound liquidity for receiving payments. When you open a Lightning channel, you can only send the funds you put in. To receive payments, you need inbound liquidity—either from natural channel balancing or from an LSP opening a channel to you. **What LSPs offer:** - Open channels to your node - Provide inbound liquidity - Just-in-time (JIT) channel creation **In Lokihub:** Select from community LSPs or add your own. Lokihub LSPs use the **LSPS specifications** ([LSPS0 to LSPS5](https://github.com/lightning/blips)) for standardized liquidity. ### Nostr Relay Routes [NWC](https://nwc.dev) connection messages between your node and connected apps. When you connect an app via NWC, your node and the app communicate through a Nostr relay. The relay doesn't see payment data—just encrypted connection messages. **In Lokihub:** Choose a public relay or run your own. You can select as many relays as you want to ensure strong communication fallbacks and reliability. ### Block Explorer Looks up on-chain transaction details, blockchain information, and Lightning node statistics. **In Lokihub:** Point to any Flokicoin-compatible block explorer. ### Widget Messageboard Interactive chat widgets where community members can post messages with zaps. Collected funds can be used for community airdrops or other purposes. Configure multiple widgets for different channels. **In Lokihub:** Choose from community messageboards or configure your own. ### Swap Service **Optional** — Swap funds between your on-chain wallet and Lightning channels. Useful when you need to move funds from your on-chain balance to Lightning (loop in) or from Lightning to on-chain (loop out). **In Lokihub:** Use the built-in swap interface powered by your chosen swap provider. ## For Service Providers: Submit Your Service The Services directory is open-source and community-maintained. ### Repository Structure Service configurations live at: [flokiorg/lokihub-services](https://github.com/flokiorg/lokihub-services) ``` lokihub-services/ ├── services.json # LSPs, relays, explorers ├── rates.json # Exchange rates ├── currencies.json # Supported currencies └── info.json # General info and MOTD ``` ### Adding a Service **1. Fork the Repository** Fork [flokiorg/lokihub-services](https://github.com/flokiorg/lokihub-services) on GitHub. **2. Edit `services.json`** Add your service to the appropriate section. #### Adding an LSP Add to the `lsp` array: ```json { "name": "My LSP", "uri": "pubkey@host:port", "description": "Supports JIT Channels & Inbound Liquidity" } ``` **Fields:** - `name` — Display name of your LSP - `uri` — Connection string (`pubkey@host:port`) - `description` — Brief description of services offered #### Adding a Nostr Relay Add to the `relay` array: ```json { "name": "My Relay", "url": "wss://relay.example.com", "description": "Fast Nostr relay for NWC" } ``` **Fields:** - `name` — Display name - `url` — WebSocket URL - `description` — Brief description #### Adding a Block Explorer Add to the `explorer` array: ```json { "name": "My Explorer", "url": "https://explorer.example.com", "description": "Flokicoin blockchain explorer" } ``` **Fields:** - `name` — Display name - `url` — HTTPS URL - `description` — Brief description #### Adding a Widget Messageboard Add to the `widget` array: ```json { "name": "Community Board", "url": "nostr+walletconnect://b889...4f1?relay=wss://relay.example.com/v1&secret=79...a1", "description": "Funds collected in this messageboard are destined for airdrop sessions and game payouts" } ``` **Fields:** - `name` — Display name - `url` — NWC connection string (`nostr+walletconnect://...`) - `description` — Brief description **3. Create Pull Request** Submit your changes for review. ### Review Process Pull requests are reviewed for: - Valid JSON structure - Working service endpoints - Accurate service information - Reliability and uptime (for community defaults) ## File Descriptions ### `services.json` Directory of recommended community services: - **LSPs** — Lightning Service Providers - **Relays** — Nostr relays for NWC - **Explorers** — Block explorers - **Widgets** — Chat messageboards with zaps - **Swap Services** — On-chain/off-chain fund swaps ### `rates.json` Current exchange rates for FLC (Flokicoin) against fiat currencies. ### `currencies.json` List of supported fiat currencies and their symbols. ### `info.json` General information and message of the day (MOTD) for Lokihub users. ## Questions? - Repository: [flokiorg/lokihub-services](https://github.com/flokiorg/lokihub-services) - Issues: [GitHub Issues](https://github.com/flokiorg/lokihub-services/issues) - Community: [Discord](https://flokicoin.org/discord) #lokihub --- ## Setup Guide import Heading from '@theme/Heading'; import setupFlndImage from './setup-flnd.png'; # Setup Guide Connect Lokihub to your node and start managing your Lightning liquidity in minutes. ## Before you start To use Lokihub, you'll need: - **Lokihub App**: [Download it here](/lokihub/downloads). - **tWallet v1**: Your Lightning node (FLND) must be running. If you haven't set it up yet, follow the [tWallet guide](/wallets/twallet). :::tip If you're running **tWallet v1** on the same computer, Lokihub will find it for you automatically. Use the [Automated Connection](#automated-connection) option! ::: ## First Launch 1. Open Lokihub. 2. Follow the setup wizard to get started. ## Step-by-Step Setup ### 1. Create a Password Set a strong password to protect your data. This password encrypts your connection details and app settings. > **Important**: We cannot recover this password for you. Please write it down and keep it safe. ### 2. Choose Your Services Lokihub uses specific services to interact with the network: - **Nostr Relay**: Connects your node to external apps. - **Block Explorer**: Shows you transaction details. - **Optional**: You can also add Liquidity (LSP) or Swap services later. ### 3. Connect to tWallet Lokihub connects to the Lightning node built into **tWallet v1**. Option A: Automated Connection (Recommended) If tWallet is running on the **same machine**: 1. Choose **"Local Node"** during the setup wizard. 2. Lokihub will automatically link with your tWallet credentials. 3. You're ready to go! #### Option B: Custom tWallet configuration (Advanced) If you're running [tWallet](/wallets/twallet) on another machine (VPS, Raspberry Pi, etc.): 1. Select "Advanced Mode" 2. Enter connection details: - **gRPC Address**: IP and port (example: `127.0.0.1:10005`) - **Macaroon**: Paste `admin.macaroon` hex content - **TLS Certificate**: Paste `tls.cert` hex content (Optional) 3. Click "Connect" :::tip[How to find these credentials] In tWallet, press CTRL + N to open the Lightning configuration window. This displays your **gRPC Address**, **Macaroon Hex**, and **TLS Certificate Hex**. Simply copy and paste them into Lokihub. ::: ## Troubleshooting **Can't connect to local tWallet?** - Make sure tWallet is running - Check that ports aren't blocked by firewall **Remote connection fails?** - Verify the gRPC address is correct - Ensure your node is accessible from your network - Check that macaroon and TLS cert hex strings are correct **Need help?** Join the community on [Discord](https://flokicoin.org/discord) in #lokihub ## Next Steps ### 1. Secure Your Sovereignty (Required) Before you open your first channel, you must establish a reliable recovery plan. Unlike traditional on-chain funds, Lightning liquidity needs active protection. :::important[CHANNEL BACKUPS ARE NOT AUTOMATIC] Your 24-word seed phrase **ONLY** recovers funds on the blockchain. To protect your channel liquidity from system failures, you MUST maintain a copy of your `channel.backup` file. ::: 1. **Locate**: On Linux, this is typically in `~/.flnd/data/chain/flokicoin/mainnet/channel.backup`. 2. **Backup**: Copy this file to a separate device (USB, Cloud, etc.) every time you open or close a channel. 3. **Learn More**: Read the full [Lightning Backup Guide](/wallets/twallet/v1#critical-lightning-backups). ### 2. Further Reading Once connected, you can: - [Manage your wallet and channels](/lokihub/features) - [Connect external apps via NWC](/lokihub/store) - [Configure service providers](/lokihub/services) --- ## App Store import Heading from '@theme/Heading'; # Lokihub App Store The Lokihub App Store is a community-maintained directory of applications that work with your Lightning node through [NWC (Nostr WalletConnect)](https://nwc.dev). ## How Apps Connect Apps listed in the store connect to your Lokihub node using NWC. This means: 1. **No Installation** — Apps don't install on Lokihub itself 2. **Permission-Based** — You grant specific permissions (read balance, send up to X amount, etc.) 3. **Revocable** — Remove app access anytime ## Using Apps from the Store 1. Browse available apps in Lokihub 2. Click an app to view details 3. Click "Connect" 4. Review and grant permissions 5. Scan the QR code or copy the connection string into the app ## App Categories The store organizes apps into categories: - **Wallet Interfaces** — Alternative wallet UIs - **Social Media** — Nostr clients, tipping platforms - **Merchant Tools** — Point-of-sale, invoicing - **Payment Tools** — Budgeting, accounting - **Shopping** — E-commerce integrations - **Nostr Tools** — Nostr-specific utilities - **Games** — Lightning-enabled games - **AI** — AI services with Lightning payments - **Music** — Streaming, tipping artists - **Blogging** — Content platforms - **Misc** — Other applications For Developers: Submit Your App The App Store is open-source and community-driven. Anyone can submit an app. ### Repository Structure The store data lives at: [flokiorg/lokihub-store](https://github.com/flokiorg/lokihub-store) ``` lokihub-store/ ├── apps.json # All app metadata └── logos/ # App logos (PNG/SVG) ``` ### Submission Steps **1. Fork the Repository** Fork [flokiorg/lokihub-store](https://github.com/flokiorg/lokihub-store) on GitHub. **2. Add Your App Logo** - Place a high-quality logo in the `logos/` directory - Format: PNG or SVG - Recommended size: 512x512 pixels - Filename: `your-app-id.png` (e.g., `my-lightning-app.png`) **3. Edit `apps.json`** Add your app entry to the array: ```json { "id": "my-app", "title": "My App", "description": "Short description (max 100 chars)", "extendedDescription": "Longer description explaining the integration", "webLink": "https://myapp.com", "playLink": "https://play.google.com/store/apps/details?id=com.myapp", "appleLink": "https://apps.apple.com/us/app/my-app/id123456", "categories": ["social-media"], "logo": "my-app.png", "installGuide": "How to install/setup the app", "finalizeGuide": "How to connect to Lokihub (where to paste NWC string)", "version": "1.0.0", "createdAt": 1709251200, "updatedAt": 1709251200 } ``` **Required Fields:** - `id` — Unique identifier (lowercase, dashes only) - `title` — Display name - `description` — Short tagline - `version` — Semantic version (e.g., `1.0.0`) - `createdAt` — Unix timestamp (seconds) - `updatedAt` — Unix timestamp (seconds) **Optional Fields:** - `extendedDescription` — Detailed explanation - `webLink` — App website - `playLink` — Google Play Store URL - `appleLink` — Apple App Store URL - `logo` — Filename from `logos/` directory - `installGuide` — Setup instructions before connecting - `finalizeGuide` — Connection instructions (where to paste NWC secret) - `categories` — Array of categories (see list above) **4. Create Pull Request** Submit your changes for review. The maintainers will review and merge if everything looks good. ### Review Process Pull requests are reviewed for: - Valid JSON structure - Logo quality and file size - Accurate app information - Working NWC implementation Once merged, your app appears in all Lokihub instances automatically. ## Questions? - Repository: [flokiorg/lokihub-store](https://github.com/flokiorg/lokihub-store) - Issues: [GitHub Issues](https://github.com/flokiorg/lokihub-store/issues) - Community: [Discord](https://flokicoin.org/discord) #lokihub --- ## Gminer :::warning[CPU miner notice] Gminer is a CPU miner. CPU mining is only practical on test networks; on mainnet it is not competitive. Use GPU or scrypt ASIC for mainnet. ::: This guide walks you through downloading, configuring, and running Gminer. By the end, you'll have a working CPU miner connected to a Flokicoin testnet pool. - [Download and Installation](#download-and-installation): Guide to download and install `gminer` - [Configuration](#configuration): Instructions for configuring `gminer.conf`. - [How to Run](#how-to-run): Guide to start mining Flokicoin. - [Monitoring](#monitoring): Monitor mining performance and status information - [Troubleshooting and recommendations](#troubleshooting-and-recommendations): Common issues and their solutions - [Support](#support) --- import Heading from '@theme/Heading'; Download and Installation Download the latest miner release: - Go to the [releases](https://github.com/flokiorg/grpc-miner/releases/tag/v0.1.1-beta) page. - Download the version suitable for your operating system and architecture. gminer is available on: - Mac - Linux - Windows ### Install `gminer` on Mac #### **Mac with apple silicon** Download [gminer-darwin-arm64-v0.1.1-beta.tar.gz](https://github.com/flokiorg/grpc-miner/releases/download/v0.1.1-beta/gminer-darwin-arm64-v0.1.1-beta.tar.gz) then extract the archive: ```bash tar -xvf gminer-darwin-arm64-v0.1.1-beta.tar.gz chmod +x gminer ``` #### **Mac with Intel chip** Download [gminer-darwin-amd64-v0.1.1-beta.tar.gz](https://github.com/flokiorg/grpc-miner/releases/download/v0.1.1-beta/gminer-darwin-amd64-v0.1.1-beta.tar.gz) then extract the archive: ```bash tar -xvf gminer-darwin-amd64-v0.1.1-beta.tar.gz chmod +x gminer ```   ### Install on Linux Download [gminer-linux-amd64-v0.1.1-beta.tar.gz ](https://github.com/flokiorg/grpc-miner/releases/download/v0.1.1-beta/gminer-linux-amd64-v0.1.1-beta.tar.gz) then extract the archive: ```bash tar -xvf gminer-linux-amd64-v0.1.1-beta.tar.gz chmod +x gminer ```   ### Install on Windows Download [gminer-windows-386-v0.1.1-beta.zip](https://github.com/flokiorg/grpc-miner/releases/download/v0.1.1-beta/gminer-windows-386-v0.1.1-beta.zip) then extract the archive.   Configuration Before running the miner, ensure a configuration file (`gminer.conf`) exists in the same directory as the `gminer` executable file. You can download a [sample config file](https://raw.githubusercontent.com/flokiorg/grpc-miner/refs/heads/main/sample-gminer.conf) from grpc-miner repository. You need to update the following parameters: **Mining pool endpoint** ```ini pool = solo.example.com:5055 ``` Find below the list of community-known pools: | Author | Dev fee | Pool | Port | | --- | --- | --- | --- | | myf | - | gpool.myfloki.com | 5055 | You’re encouraged to create your own pool, set a developer fee if desired, and share it with the Flokicoin community in **#Mining** channel on [Discord](https://flokicoin.org/discord). **Mining addresses** You can specify one or more mining addresses: ```ini miningaddr = YOUR_FLOKICOIN_ADDRESS_1 miningaddr = YOUR_FLOKICOIN_ADDRESS_2 ``` **Threads** Set the number of CPU threads to dedicate for mining. By default, if unspecified, gminer uses all available threads. ```ini threads = 16 ```   import { Lightbulb } from 'lucide-react'; How to run **On Mac and Linux:** Navigate to the directory containing the extracted binary and run: ```bash ./gminer ``` On macOS, authorize gminer by navigating to System Settings → Privacy & Security → General and click “Open Anyway” to trust the developer. **On Windows:** Navigate to the directory containing the extracted `gminer.exe` and double-click it or run it from the command line: ```bash gminer.exe ``` If Windows Defender or another antivirus blocks gminer.exe, you might need to explicitly allow or unblock it.   Monitoring You can monitor the mining performance and status directly in the terminal. The information includes: - Hashrate - Blocks found - Possible errors   Troubleshooting and recommendations - Verify that your `gminer.conf` file is in the correct directory and that pool addresses, mining addresses, and ports match your intended configuration. - On macOS, authorize `gminer` in System Settings and mark the developer as trusted. - Verify the server address and port in `gminer.conf`. - Ensure your internet connection is active. - Regularly update the `gminer` from the releases page.   Support For further assistance, join the `#mining` channel in the [Flokicoin Discord Community](https://flokicoin.org/discord). --- ## Mining import { Rocket, Users, User, Handshake, FlaskConical } from 'lucide-react'; ## Start Earning Flokicoin Mining is how you help secure the network and earn coins doing it. Flokicoin uses the **Scrypt** algorithm, which means you can mine it alongside Litecoin and Dogecoin. ### Why Mine Flokicoin? - **Scrypt algorithm** — Join a globally recognized mining ecosystem used by LTC and DOGE. - **Support the network** — Every miner helps keep Flokicoin decentralized and resilient. - **AuxPoW (Merge Mining)** — Earn Flokicoin "for free" while mining other Scrypt coins. :::warning[Safety First] Mining uses a lot of hardware resources. Keep your mining rig separate from personal data, make sure it stays cool, and only download software from trusted sources. ::: ## 3-Step Quick Start 1. **Pick your hardware** — Scrypt ASIC for serious mining, GPU if you're a hobbyist. 2. **Join a pool** — Steady payouts instead of waiting weeks for a solo block. [Explore pools](/mining/pools). 3. **Point and earn** — Set your pool's stratum address and your FLC wallet as the username. ## Hardware Guide | Setup | Difficulty | Best For | | :--- | :--- | :--- | | **ASIC** | Easy | **Maximum Rewards** | | **GPU** | Moderate | **Hobbyist Mining** | | **CPU** | Easy | **Testnet/Learning only** | ## Network Basics - **Algorithm**: Scrypt - **Block Time**: 1 Minute - **Merge Mining**: Supported (earn coins for free while mining LTC/DOGE) ## Ways to Mine ### Join a Pool (Recommended) Work together with others to find blocks. You get a share of the rewards based on your contribution. [Check out the pools](/mining/pools). ### Solo Mining (Advanced) Mine on your own. You keep the full reward for every block you find, but payouts can be rare. ### Merge Mining (AuxPoW) If your pool supports it, you can mine Flokicoin *at the same time* as Litecoin or Dogecoin without using any extra electricity. ## Mining Apps - **NVIDIA GPU**: [ccminer](https://github.com/tpruvot/ccminer) - **AMD/NVIDIA GPU**: [nevermore](https://github.com/brian112358/nevermore-miner) - **ASIC Support**: [CGMiner](https://github.com/ckolivas/cgminer) or [BFGMiner](https://github.com/luke-jr/bfgminer) ### Try it on Testnet If you're just learning, try mining with your CPU on our testnet: - [Gminer](/mining/gminer) — A simple CPU mining tool for practice. ## Support Join the [#mining](https://flokicoin.org/discord) channel on Discord for help. --- ## Pools :::danger[Disclaimer] Pools and miners listed here are third‑party. Verify binaries and configs yourself and prefer sandboxed testing before production use. ::: import { Fish } from 'lucide-react'; ## Pools - [fpool.net](https://fpool.net) Mining has never been so easy (solo, PPLNS) - [viaflc.com](https://viaflc.com) More Coins Same Power (PPLNS, merge-mining) ### Notes - Mainnet: use GPU or scrypt ASIC. CPU mining is not competitive; reserve cpuminer for testnet or experimentation. - AuxPoW: If the pool supports merge mining with a scrypt‑family parent and forwards AuxPoW to Flokicoin, follow the pool’s specific instructions. Details vary by pool. ## Stratum Basics - URL: `stratum+tcp://POOL_HOST:PORT` - Username: your Flokicoin payout address (or pool account) - Password: often `x` or pool‑specific token ## Support Join the [#mining](https://flokicoin.org/discord) channel on Discord for help. --- ## flnd import Link from '@docusaurus/Link'; import { Terminal, Cpu, Zap, Shield, ArrowRight, Download, Play, Unlock, Info } from 'lucide-react'; **flnd** is the engine that powers the Flokicoin Lightning Network. It is a full-featured daemon that acts as both a Flokicoin wallet and a Lightning Network node. If you are a developer, a node operator, or a power user who prefers automation and a powerful command-line interface, **flnd** is your choice. High Performance Written in Go, designed for stability and 24/7 operation. Lightning Ready Supports instant payments and smart-contract channels natively. Fully Scriptable Every feature is accessible via the `flncli` tool or a robust gRPC/REST API. ## Quick Installation **flnd** is distributed as a pair of binaries: `flnd` (the daemon) and `flncli` (the controller). 1. **Download**: Go to the [flnd Releases](https://github.com/flokiorg/flnd/releases) page and grab the version for your system. 2. **Extract**: Unpack the archives and move the binaries to your path (e.g., `/usr/local/bin` or `C:\Windows`). 3. **Verify**: ```bash flnd --version flncli --version ``` ## The Onboarding Lifecycle Operating **flnd** follows a standard lifecycle: **Start Daemon → Create/Unlock Wallet → Sync → Operate**. ### 2. Starting the Daemon Before you can interact with your wallet, the **flnd** daemon must be running. By default, it will use DNS seeds to find peers and connect to the network using Neutrino. Simply run: ```bash flnd ``` **What to look for in the logs:** ```text [INF] LTND: Waiting for wallet encryption password. Use flncli create to create a wallet or flncli unlock to unlock an existing wallet. ``` ### 2. Creating Your Wallet Open a second terminal window and run the initialization command: ```bash flncli create ``` You will be guided through several critical security steps: 1. **Wallet Password**: Enter a password (min 8 characters). This password encrypts your local `wallet.db` file. You will need it every time you start the daemon. 2. **Cipher Seed**: You will be asked if you have an existing seed to import. For a new wallet, choose **No** (`n`). 3. **Seed Passphrase (Optional)**: You can add an extra "25th word" for additional security. If you don't want one, simply press **Enter**. 4. **The 24-Word Seed**: The terminal will display your unique 24-word recovery phrase. :::danger[Security Protocol] * **Write it down**: Use physical paper. * **Offline only**: Never take a screenshot, photo, or store it in a digital file. * **Ultimate Backup**: This seed (and your optional passphrase) is the **only way** to recover your on-chain funds. ::: ### 3. Static Channel Backup (SCB) While the 24-word seed restores your Flokicoin balance, it **does not** automatically restore your Lightning channels. * **File**: `channel.backup` * **Location**: Inside your data directory (e.g., `chain/flokicoin/mainnet/`). * **Action**: Every time you open or close a channel, this file updates. You should back this file up to a separate device or cloud storage to ensure you can recover Lightning funds. ### 4. Unlocking the Wallet Every time you restart the **flnd** daemon, you must provide your wallet password to decrypt the local keys: ```bash flncli unlock ``` #### Pro Tip: Auto-Unlocking To allow the daemon to start and unlock automatically (useful for servers), you can use a password file: 1. Create a file containing only your wallet password (e.g., `~/.flnd/pwd.txt`). 2. Start the daemon with the flag: `--wallet-unlock-password-file=/path/to/pwd.txt`. ## Network & Connectivity To be a healthy part of the network, your node needs to talk to others. ### Port Forwarding If you are running **flnd** behind a home router, you should forward these ports to your node's local IP to allow external connectivity: * **5521 (TCP)**: The standard port for Lightning Network peer-to-peer communication. * **10005 (TCP)**: The gRPC port used by `flncli` and external dashboards like Lokihub. * **5050 (TCP)**: The REST API port for web-based integrations. ### Data Directory By default, all data (logs, database, macaroons) is stored in: - **Linux**: `~/.flnd/` - **macOS**: `~/Library/Application Support/Flnd/` - **Windows**: `%LOCALAPPDATA%\Flnd\` You can move this to an external drive using the `--lnddir=/path/to/data` flag. ## Basic Operations Once unlocked, the daemon will begin syncing with the Flokicoin network. Use these commands to manage your funds: **Check Sync Status:** ```bash flncli getinfo ``` **Generate a SegWit Address:** ```bash flncli newaddress p2wkh ``` **Check Balances:** ```bash flncli walletbalance # On-chain Flokicoin flncli channelbalance # Lightning Network liquidity ``` **Send Flokicoin:** ```bash flncli sendcoins --addr=[ADDRESS] --amt=[AMOUNT_IN_LOKI] ``` ## External Access (Macaroons) **flnd** uses "Macaroons" for authentication. These are credential files that grant specific permissions to external apps. * `admin.macaroon`: Full access (keep this secret). * `readonly.macaroon`: Only allows viewing balances and info. * `invoice.macaroon`: Only allows creating and viewing invoices. When connecting apps like **Zeus** or **Lokihub**, you will often need to provide the hex-encoded string of your `admin.macaroon`. ## Advanced: Lightning Network **flnd** is a full Lightning Network implementation. Once you have on-chain funds, you can open channels to start sending instant, near-free payments. 1. **Find a peer**: Ask for a node's public key on the [Flokicoin Discord](https://flokicoin.org/discord). 2. **Connect**: `flncli connect [pubkey]@[host]:[port]` 3. **Open Channel**: `flncli openchannel [pubkey] [amount_in_Loki]` ## Next Steps - **Node Operators**: Learn how to [connect Lokihub](/lokihub) to manage your node from a web dashboard. - **Developers**: **flnd** is fully compatible with the LND API. Refer to the [gRPC Documentation](https://api.lightning.community) or the [REST API Reference](https://lightning.engineering/api-docs/api/lnd/rest-endpoints/) for integration guides. - **Community**: Join the [#builders](https://flokicoin.org/discord) channel on Discord. --- ## Wallets import Link from '@docusaurus/Link'; # Flokicoin Wallets To interact with the Flokicoin network, you need a safe place to manage your keys. Whether you're a power user who needs Lightning support or a beginner looking for a simple interface, we have an option for you. {/* --- tWallet Card --- */} tWallet The Power User's Choice. A fast, terminal-based wallet (TUI) with a built-in Lightning node. Ideal for users who want total control and privacy without the bloat. Integrated Lightning Network Privacy-focused (Neutrino) Fast, light, and low-resource Get tWallet {/* --- flnd Card --- */} flnd (Daemon) The Node Operator's Choice. A high-performance Lightning Network and wallet daemon. It's the engine for automation and robust node operations. Full Daemon & CLI experience Robust gRPC/REST API Ideal for 24/7 server nodes Explore flnd {/* --- Komodo Card --- */} Komodo Wallet The User-Friendly Choice. A multi-coin wallet with a traditional graphic interface (GUI). Perfect for everyday users on desktop or mobile. Graphic User Interface Supports F-addresses & Segwit Mobile, Desktop, and Web Get Komodo ## Quick Comparison | Feature | tWallet | flnd | Komodo Wallet | | :--- | :--- | :--- | :--- | | **Interface** | Terminal (TUI) | Command Line (CLI) | Graphic (GUI) | | **Lightning** | Yes (Built-in) | Yes (Natively) | No | | **Experience** | Intermediate | Advanced | Beginner | | **Best For** | Desktop privacy | Node operators | Everyday users | :::tip[Running Lokihub?] If you plan on using **Lokihub**, we highly recommend starting with **tWallet v1**, as it provides the necessary Lightning backend for node operations. ::: --- ## Komodo Wallet import Link from '@docusaurus/Link'; import { Monitor, Smartphone, Globe, ArrowRight, MousePointer2, Layers, Repeat } from 'lucide-react'; **Komodo Wallet** (formerly AtomicDEX) is a multi-coin, cross-platform wallet with a clean graphic interface. If you prefer a visual experience over terminal commands, this is your wallet. Visual Interface No terminal needed. See your balance and transactions in a familiar app. Multi-coin Manage Flokicoin alongside dozens of other assets in one secure place. Segwit Ready Lower fees and faster confirmations out of the box with `fc1` addresses. ## Choose Your Platform Pick the version that fits your workflow. All versions use the same secure technology. Desktop Best for daily management on Windows, macOS, or Linux. Full feature set Local private key storage Hardware wallet support Download Desktop Mobile Best for sending and receiving Flokicoin on the go. iOS & Android support Biometric security (FaceID/Fingerprint) Scan QR codes to pay Get Mobile App Web Best for quick access from any browser without installation. No installation required Access from any device Simple, fast interface Open Web Wallet ## Quick Setup Guide Getting started takes about 5 minutes. Follow these simple steps: 1. **Get the App**: Download or open the version for your preferred platform above. 2. **Create New Wallet**: Choose "Create New Wallet" and write down your **seed phrase**. 3. **Backup Your Keys**: Store your seed phrase on physical paper in a safe place. 4. **Enable Flokicoin**: Search for **Flokicoin** in the assets list and enable it to get your address. :::warning[Security First] Your seed phrase is your *only* backup. If you lose it, you lose your coins. Never store it digitally, never share it, and never take a screenshot of it. ::: ## About Addresses (F vs fc1) By default, Komodo Wallet generates an address starting with **F** (Legacy). It also fully supports **fc1** (Segwit) addresses. * **Legacy (F)**: Maximum compatibility with older services. * **Segwit (fc1)**: Recommended for everyday use. It results in **lower network fees** and is supported by most modern services. You can toggle between these formats in the wallet settings. Both formats work on the same Flokicoin network. ## Support & Links - **Komodo Docs**: [Official documentation](https://docs.komodoplatform.com/) for deep technical help. - **Discord**: Join the [Flokicoin Discord](https://flokicoin.org/discord) for community support. - **Next Steps**: Learn how [Flokicoin issuance works](/economy) or [start mining](/mining/pools). --- ## tWallet — Flokicoin Terminal Wallet import Link from '@docusaurus/Link'; import { Shield, Zap, Eye, ArrowRight, Terminal, Server } from 'lucide-react'; A fast, lightweight terminal wallet that gives you direct access to the Flokicoin network. No bloat, no tracking, full control. Fast Syncs with the network in seconds, not hours. Private No tracking. No third-party servers required. Your Keys Full control over your coins and recovery phrase. ## Which Version Is Right for You? Most users should start with **v1**. It's newer, more private, and comes with Lightning payments built in. Recommended v1 — Neutrino Best for new users and anyone who wants Lightning payments. Talks directly to the blockchain — no middleman Send instant, near-free payments with Lightning Supports modern address formats (SegWit, Taproot) Recovery phrase uses the latest security standard Get Started with v1 v0 — Electrum Best for users with an existing BIP39 seed or who need an external server. Loads your full transaction history instantly Works with any industry-standard recovery phrase Get Started with v0 :::tip[Using Lokihub?] If you plan to manage a Lightning node from a dashboard, start with **v1** and then [set up Lokihub](/lokihub/setup). ::: ## Getting Started Once you've picked a version, the setup takes about 5 minutes: 1. **Download** the version for your operating system. 2. **Back up** your recovery phrase. Write it down and **never share it**. 3. **Sync** — let the wallet catch up with the network (a few minutes at most). 4. **Receive** — generate an address and get your first coins. ## Community & Support Got questions? The community is active and welcoming. - **Discord**: Join the [#tWallet channel](https://flokicoin.org/discord) for real-time help. - **GitHub**: [Browse the code or report issues](https://github.com/flokiorg/twallet). --- ## 0.1.0-alpha - This is a **pre-release** for testing and feedback. ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/tWallet/releases/download/v0.1.0-alpha/twallet-darwin-arm64-v0.1.0-alpha.tar.gz | | macOS (Intel) | https://github.com/flokiorg/tWallet/releases/download/v0.1.0-alpha/twallet-darwin-amd64-v0.1.0-alpha.tar.gz | | Linux x86_64 | https://github.com/flokiorg/tWallet/releases/download/v0.1.0-alpha/twallet-linux-amd64-v0.1.0-alpha.tar.gz | | Linux arm64 | https://github.com/flokiorg/tWallet/releases/download/v0.1.0-alpha/twallet-linux-arm64-v0.1.0-alpha.tar.gz | | Windows x86_64 | https://github.com/flokiorg/tWallet/releases/download/v0.1.0-alpha/twallet-windows-amd64-v0.1.0-alpha.zip | --- ## 0.1.1-alpha - This is a **pre-release** for testing and feedback. - Developers and early adopters are encouraged to **report issues**. - Fee configuration options: `feeslow`, `feemedium`, `feefast` - Renamed app data directory from `flcwallet` to `twallet` ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/tWallet/releases/download/v0.1.1-alpha/twallet-darwin-arm64-v0.1.1-alpha.tar.gz | | macOS (Intel) | https://github.com/flokiorg/tWallet/releases/download/v0.1.1-alpha/twallet-darwin-amd64-v0.1.1-alpha.tar.gz | | Linux x86_64 | https://github.com/flokiorg/tWallet/releases/download/v0.1.1-alpha/twallet-linux-amd64-v0.1.1-alpha.tar.gz | | Linux arm64 | https://github.com/flokiorg/tWallet/releases/download/v0.1.1-alpha/twallet-linux-arm64-v0.1.1-alpha.tar.gz | | Windows x86_64 | https://github.com/flokiorg/tWallet/releases/download/v0.1.1-alpha/twallet-windows-amd64-v0.1.1-alpha.zip | --- ## tWallet v0 (Electrum) import Link from '@docusaurus/Link'; import { History } from 'lucide-react'; v0 is the legacy tWallet line. It connects to an Electrum server that indexes the blockchain and serves wallet queries. ## Electrum - Electrum is a light-client protocol: the server maintains an index; clients query balances, history, and broadcast transactions. - Simplicity: Quick to get started, minimal sync. - Trade-offs: You trust the server’s view of the chain. Public servers also see your query patterns. ### Electrum Setup :::note[Not a technical user or don’t want to deal with setup?] Check out the community plug-and-play option: https://myfloki.com/operator ::: :::tip Need help or want a ready-made Electrum endpoint? Join the **Flokicoin Discord**; community members may share public Electrum instances. 👉 [Join Discord](https://flokicoin.org/discord) ::: To use **tWallet v0**, you must run your own Electrum-compatible server. For Flokicoin, the reference implementation is [`flokicoin-electrs`](https://github.com/flokiorg/flokicoin-electrs), a fork of `electrs` that indexes the chain and serves both Electrum and [Esplora APIs](https://github.com/Blockstream/esplora/blob/master/API.md). #### Requirements - A **fully synced Flokicoin full node daemon** (`lokid`) - RPC credentials for your node (`rpcuser` / `rpcpassword`) - Disk space for the Electrum index database (`--db-dir`) #### Example run command ```bash electrs -vvv \ --network mainnet \ --db-dir /data \ --jsonrpc-import \ --daemon-rpc-addr :15213 \ --electrum-rpc-addr 0.0.0.0:50001 \ --http-addr 0.0.0.0:3000 \ --cookie : \ --enable-json-rpc-logging \ --index-unspendables ``` Replace: - `` → hostname or IP of your `lokid` - `` / `` → your daemon RPC credentials Once running, point `twallet.conf` to your server: ```ini title="twallet.conf (example)" electserver = 127.0.0.1:50001 ``` ## tWallet Limitations v0 vs v1 - Addresses: legacy Flokicoin address format only (no segwit/taproot generation). - No built‑in Lightning daemon (FLND is not included). - Seed format: [BIP39](https://bips.dev/39/) mnemonic (different from v1’s aezeed). :::tip Restoring an existing [BIP39](https://bips.dev/39/) seed? Use v0. v1 (aezeed) is not compatible with [BIP39](https://bips.dev/39/). ::: **Status:** Public Electrum endpoints previously listed are deprecated. Prefer your own server or a trusted community provider. ## Install Latest known v0 build: 0.1.1-alpha | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/tWallet/releases/download/v0.1.1-alpha/twallet-darwin-arm64-v0.1.1-alpha.tar.gz | | macOS (Intel) | https://github.com/flokiorg/tWallet/releases/download/v0.1.1-alpha/twallet-darwin-amd64-v0.1.1-alpha.tar.gz | | Linux x86_64 | https://github.com/flokiorg/tWallet/releases/download/v0.1.1-alpha/twallet-linux-amd64-v0.1.1-alpha.tar.gz | | Linux arm64 (Raspberry Pi) | https://github.com/flokiorg/tWallet/releases/download/v0.1.1-alpha/twallet-linux-arm64-v0.1.1-alpha.tar.gz | | Windows x86_64 | https://github.com/flokiorg/tWallet/releases/download/v0.1.1-alpha/twallet-windows-amd64-v0.1.1-alpha.zip | Extract and make the binary executable where applicable: ```bash tar -xvf twallet-*.tar.gz chmod +x twallet ``` ## Configure Create a `twallet.conf` next to the binary and point it to your Electrum server: ```ini title="twallet.conf (v0 minimal)" electserver = electrum.example.com:50001 # timeout = 10s ```
Full sample (v0) — Click to expand ```ini title="Full sample (v0)" ; Directory for the wallet database ; walletdir = /private/link/flc/db ; Network settings (only one can be true) ; If both regtest and testnet are false, mainnet will be used by default. ; Use the regression test network ; regtest = false ; Use the test network ; testnet = false ; Database connection timeout (in seconds) timeout = 10s ; Electrum server configuration (host:port) electserver = electrum.example.com:50001 # Fee for slow transactions (in loki/vB) # feeslow = 1 # Fee for medium transactions (in loki/vB) # feemedium = 2 # Fee for fast transactions (in loki/vB) # available on v0.1.1 # feefast = 3 ```
## Run On macOS/Linux: ```bash ./twallet ``` On Windows: ```powershell twallet.exe ``` If your OS flags the binary, allow it explicitly. Legacy Release History Access full technical notes and cross-platform binary assets for all historical tWallet v0 (Electrum) versions. View Archive ## Security - Back up your seed phrase (24 words recommended) and test recovery. - Set a spending passphrase and lock your wallet when idle. - Keep tWallet up to date: https://github.com/flokiorg/tWallet/releases --- ## Release History import Link from '@docusaurus/Link'; import { History, ExternalLink } from 'lucide-react'; # tWallet v0 Release History This page tracks the history of **tWallet v0 (Electrum)**. The v0 branch is maintained for users who require **BIP39 seed restoration** or prefer using public Flokicoin Electrum servers. | Version | Focus | | :--- | :--- | | [**0.1.1-alpha**](/wallets/twallet/v0/0.1.1-alpha) | Added multi-server failover and improved wallet synchronization logic. | | [**0.1.0-alpha**](/wallets/twallet/v0/0.1.0-alpha) | First public alpha for the terminal interface with Electrum support. | --- :::important[Looking for v1?] If you don't need to restore an existing BIP39 seed, we recommend checking out [**tWallet v1**](/wallets/twallet/v1) for the best performance and privacy (Neutrino). ::: --- ## 1.0.1-alpha This is a **pre-release** for testing and feedback. Developers and early adopters are encouraged to **report issues**. ## Changes - Registered the WalletKit gRPC service (`walletrpc.WalletKit`) so WalletKit endpoints are now available. ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/tWallet/releases/download/v1.0.1-alpha/twallet-darwin-arm64-v1.0.1-alpha.tar.gz | | macOS (Intel) | https://github.com/flokiorg/tWallet/releases/download/v1.0.1-alpha/twallet-darwin-amd64-v1.0.1-alpha.tar.gz | | Linux x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.1-alpha/twallet-linux-amd64-v1.0.1-alpha.tar.gz | | Linux arm64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.1-alpha/twallet-linux-arm64-v1.0.1-alpha.tar.gz | | Windows x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.1-alpha/twallet-windows-amd64-v1.0.1-alpha.zip | --- ## 1.0.2-alpha - This is a **pre-release** for testing and feedback. - Developers and early adopters are encouraged to **report issues**. ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/tWallet/releases/download/v1.0.2-alpha/twallet-darwin-arm64-v1.0.2-alpha.tar.gz | | macOS (Intel) | https://github.com/flokiorg/tWallet/releases/download/v1.0.2-alpha/twallet-darwin-amd64-v1.0.2-alpha.tar.gz | | Linux x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.2-alpha/twallet-linux-amd64-v1.0.2-alpha.tar.gz | | Linux arm64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.2-alpha/twallet-linux-arm64-v1.0.2-alpha.tar.gz | | Windows x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.2-alpha/twallet-windows-amd64-v1.0.2-alpha.zip | --- ## 1.0.3-alpha This is a **pre-release** for testing and feedback. Developers and early adopters are encouraged to **report issues**. ## Changelog - Migrated backend from **Electrum** to **Neutrino** - Integrated **Flokicoin Lightning Node (LN)** with full LN stack support - Enables **native Lightning development** on the Flokicoin network - Added configurable address types: `segwit`, `nested-segwit`, `taproot` - Introduced secure wallet locking/unlocking and password change UI - Improved transaction builder with live fee estimation - Enhanced **balance display** with confirmed and unconfirmed amounts - Enhanced terminal UI with sync status, LN health, and live updates - Major internal refactor for modular config, stability, and future expansion ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/tWallet/releases/download/v1.0.3-alpha/twallet-darwin-arm64-v1.0.3-alpha.tar.gz | | macOS (Intel) | https://github.com/flokiorg/tWallet/releases/download/v1.0.3-alpha/twallet-darwin-amd64-v1.0.3-alpha.tar.gz | | Linux x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.3-alpha/twallet-linux-amd64-v1.0.3-alpha.tar.gz | | Linux arm64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.3-alpha/twallet-linux-arm64-v1.0.3-alpha.tar.gz | | Windows x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.3-alpha/twallet-windows-amd64-v1.0.3-alpha.zip | --- ## 1.0.4-beta Please report bugs using the issue tracker on GitHub: https://github.com/flokiorg/tWallet/issues ## Changes ### Dependencies - Updated `go-flokicoin` → **[v0.25.7-beta](/lokichain/releases/0.25.7-beta)** - Updated `flokicoin-neutrino` → **v0.16.2-beta** - Updated `walletd` → **v0.1.3-beta** ### Fixes - General bug fixes and stability improvements - Improved reliability of status handling during sync/init ## Notes - This release aligns with the latest upstream library updates - Users are encouraged to upgrade for better stability and compatibility ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/tWallet/releases/download/v1.0.4-beta/twallet-darwin-arm64-v1.0.4-beta.tar.gz | | macOS (Intel) | https://github.com/flokiorg/tWallet/releases/download/v1.0.4-beta/twallet-darwin-amd64-v1.0.4-beta.tar.gz | | Linux x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.4-beta/twallet-linux-amd64-v1.0.4-beta.tar.gz | | Linux arm64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.4-beta/twallet-linux-arm64-v1.0.4-beta.tar.gz | | Windows x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.4-beta/twallet-windows-amd64-v1.0.4-beta.zip | --- ## 1.0.5-beta Please report bugs using the issue tracker on GitHub: https://github.com/flokiorg/tWallet/issues ## Changes ### Dependencies - Updated `flokicoin-neutrino` → **v0.16.3-beta** ### Fixes - Depends on neutrino with params‑sourced filter checkpoints. ## Notes - This release aligns with the latest upstream library updates - Users are encouraged to upgrade for better stability and compatibility ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/tWallet/releases/download/v1.0.5-beta/twallet-darwin-arm64-v1.0.5-beta.tar.gz | | macOS (Intel) | https://github.com/flokiorg/tWallet/releases/download/v1.0.5-beta/twallet-darwin-amd64-v1.0.5-beta.tar.gz | | Linux x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.5-beta/twallet-linux-amd64-v1.0.5-beta.tar.gz | | Linux arm64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.5-beta/twallet-linux-arm64-v1.0.5-beta.tar.gz | | Windows x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.5-beta/twallet-windows-amd64-v1.0.5-beta.zip | --- ## 1.0.8-beta GitHub :::info[Hotfix Update: v1.0.8-beta.2] **Released Dec 19, 2025** A hotfix has been pushed to address specific issues on **Windows** and update core dependencies. * **Windows Fixes**: Resolved keyboard input and window resizing issues (via `tcell` upgrade). * **UI Stability**: Removed the TUI resize guard for smoother rendering. * **Dependencies**: Bumped `flnd` and `tcell` versions. We recommend all Windows users upgrade to **beta.2** immediately. The download links below have been updated to this version. ::: Please report bugs using the issue tracker on GitHub: https://github.com/flokiorg/tWallet/issues This beta focuses on smoother startup/recovery flows, clearer onboarding, UI refinements, stronger caching, and refreshed dependencies. ## Changes ### Startup and recovery - Added a guided recovery path that clears Neutrino cache files and restarts the wallet service when boot fails (press R on the splash screen). - Startup now blocks until the service reports a healthy state; down/EOF conditions surface clear instructions to recover or exit. ### Restore and onboarding - Restore flow monitors recovery progress, shows toast updates, and waits for RPC readiness before entering the main app. - Seed create/restore transitions avoid premature navigation by tracking restore state and waiting for wallet availability. ### Wallet UI - Switches/buttons gained configurable colors and keep active styling in sync with state. - Copying the cipher now confirms via toast; receive flow messaging is clearer. - TUI skips draws when the terminal reports zero dimensions and clears the screen after a valid size returns, preventing resize panics and stale frames. - Balance header always shows unconfirmed funds even when locked funds are present to keep pending exposure consistent. ### Configuration and defaults - Sample config documents `transactiondisplaylimit`, clarifying it caps the number of transactions shown (not fetched). - CLI defaults now set a transaction display limit and clarify fee URL guidance; sample config documents the expected fee API response. ### Stability, caching, and monitoring - Load cache now tracks balances and chain tip height; notifications update the tip on new blocks/transactions. - Recovery monitoring retries until the wallet RPC is ready and reports recovery completion. ### Dependencies - Bumped to `flnd` **v0.1.8-beta** and `walletd` **v0.1.5-beta**. - VERSION set to **1.0.8-beta**. ## Config example ```ini title="twallet.conf snippet" ; Limit how many transactions are displayed (fetched set is unchanged) transactiondisplaylimit=50 ; Recommended fee endpoint format remains the same feeurl=https://flokichain.info/api/v1/fees/recommended ``` ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/tWallet/releases/download/v1.0.8-beta.2/twallet-darwin-arm64-v1.0.8-beta.2.tar.gz | | macOS (Intel) | https://github.com/flokiorg/tWallet/releases/download/v1.0.8-beta.2/twallet-darwin-amd64-v1.0.8-beta.2.tar.gz | | Linux x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.8-beta.2/twallet-linux-amd64-v1.0.8-beta.2.tar.gz | | Linux arm64 (Raspberry Pi) | https://github.com/flokiorg/tWallet/releases/download/v1.0.8-beta.2/twallet-linux-arm64-v1.0.8-beta.2.tar.gz | | Windows x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.8-beta.2/twallet-windows-amd64-v1.0.8-beta.2.zip | | Windows 32-bit | https://github.com/flokiorg/tWallet/releases/download/v1.0.8-beta.2/twallet-windows-386-v1.0.8-beta.2.zip | Additional builds (ppc64, mips, and *BSD) are available on the [GitHub release page](https://github.com/flokiorg/tWallet/releases/tag/v1.0.8-beta.2). --- ## 1.0.9-beta GitHub Please report bugs using the issue tracker at GitHub: https://github.com/flokiorg/tWallet/issues This release integrates a dedicated internal Lightning connector and adds a configuration view for node management. ## Notable Changes ### Internal Lightning Connector The wallet now implements an internal connector strategy. The connection management and service logic have been moved internally to `tWallet`, decoupling the application from the external `FLND` repository. This provides a stable, application-specific interface for all Lightning operations. ### Configuration Updates - Added mapping for additional `flnd` configuration options and synchronized default values to ensure consistency with the core Lightning implementation. ### New: Lightning Configuration Modal A new configuration modal is accessible via the `Ctrl+N` shortcut. - **Connection Details**: Displays RPC Address, Peer Address, and Identity PubKey. - **Credentials**: Exports Macaroon and TLS Certificate in hex format for configuring external tools like `LokiHub`, `flncli`, or web dashboards. - **Clipboard**: Implements a new cross-platform copy mechanism with robust fallback support (OSC 52, native OS commands) for seamless use in local and remote environments. ### First Run Auto-Unlock To support automated deployments and Ops workflows, a new `autounlock` configuration option has been added. - **Automated Startup**: When enabled alongside `defaultpassword`, the wallet silently unlocks on the initial application run without requiring user interaction. - **Stealth UI**: The unlock form is hidden during the automatic process, displaying only a status indicator. - **Security**: This behavior is restricted to the first run only; subsequent manual locking/unlocking operations retain the standard password prompt for security. ## Assets | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-darwin-arm64-v1.0.9-beta.tar.gz | | macOS (Intel) | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-darwin-amd64-v1.0.9-beta.tar.gz | | Linux x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-linux-amd64-v1.0.9-beta.tar.gz | | Linux arm64 (Raspberry Pi) | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-linux-arm64-v1.0.9-beta.tar.gz | | Windows x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-windows-amd64-v1.0.9-beta.zip | | Windows 32-bit | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-windows-386-v1.0.9-beta.zip | Additional builds (ppc64, mips, and *BSD) are available on the [GitHub release page](https://github.com/flokiorg/tWallet/releases/tag/v1.0.9-beta). --- ## tWallet v1 (Neutrino) import Link from '@docusaurus/Link'; import { History } from 'lucide-react'; import Heading from '@theme/Heading'; v1 is the recommended tWallet line. It uses the Neutrino light‑client protocol ([BIP157](https://bips.dev/157/)/[BIP158](https://bips.dev/158/)) to sync without relying on a third‑party Electrum server. ## Capabilities - Built‑in FLND (Flokicoin Lightning Network Daemon) for integrated Lightning operations. - Address types: segwit ([BIP173](https://bips.dev/173/)) and taproot ([BIP341](https://bips.dev/341/), [BIP342](https://bips.dev/342/)). - Seed format: aezeed (LND seed, new format) for backup and recovery. :::note Default address type is `segwit`. You can switch via `addresstype=segwit|nested-segwit|taproot` in `twallet.conf`. ::: :::important Seed compatibility: v1 uses aezeed and cannot import [BIP39](https://bips.dev/39/) mnemonics. To restore a [BIP39](https://bips.dev/39/) seed, use v0 (Electrum) instead. ::: Why Neutrino - Built-in: Neutrino is integrated directly into tWallet, no external server required. - Trust‑minimized: You verify headers and use compact block filters; no single server dictates your view of the chain. - Privacy: Queries are not centralized at an Electrum server. ## Install :::tip Install via [myFloki plug-and-play](https://myfloki.com): ```bash sh -c "$(curl -fsSL https://raw.githubusercontent.com/myfloki/community-tools/main/downloader.sh)" ``` After installation, run `twallet`. See [myfloki.com](https://myfloki.com) for details on the bundled components. ::: Download the latest [1.0.9-beta release assets](https://github.com/flokiorg/tWallet/releases/tag/v1.0.9-beta) from GitHub and extract them. | OS/Arch | Asset | | --- | --- | | macOS (Apple Silicon) | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-darwin-arm64-v1.0.9-beta.tar.gz | | macOS (Intel) | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-darwin-amd64-v1.0.9-beta.tar.gz | | Linux x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-linux-amd64-v1.0.9-beta.tar.gz | | Linux arm64 (Raspberry Pi) | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-linux-arm64-v1.0.9-beta.tar.gz | | Windows x86_64 | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-windows-amd64-v1.0.9-beta.zip | | Windows 32-bit | https://github.com/flokiorg/tWallet/releases/download/v1.0.9-beta/twallet-windows-386-v1.0.9-beta.zip | Extract and make the binary executable where applicable: ```bash tar -xvf twallet-*.tar.gz chmod +x twallet ``` ## Configure You can run `twallet` without a config file; add one only when you need custom settings (for example, running a second wallet). Create a `twallet.conf` file next to the binary or in your app data directory. Minimal example: ```ini title="twallet.conf (v1 minimal)" # walletdir = ./loki # addresstype = segwit # segwit | nested-segwit | taproot # feeurl = https://lokichain.info/api/v1/fees/recommended # debuglevel = info # connectiontimeout = 50s # rpclisten = 127.0.0.1:10005 # RPC API # restlisten = 127.0.0.1:5050 # REST API # restcors = * # CORS for REST API # transactiondisplaylimit=121 ```
Full sample (annotated) — Click to expand ```ini title="Full sample (v1)" ; ============================================================================ ; General Application Options ; ============================================================================ ; Directory for the wallet database. ; walletdir=./loki ; Logging level for all subsystems {trace, debug, info, warn, error, critical}. ; Default is 'info'. ; debuglevel=info ; Logging level for the twallet application {trace, debug, info, warn, error, fatal, panic}. ; Default is 'info'. ; loglevel=info ; Use default passphrase for locking. ; This is required if 'autounlock' is set to true. ; defaultpassword=pass ; Automatically unlock the wallet on startup using defaultpassword. ; WARNING: This stores your password in plain text in this config file. ; Use with caution and only in secure environments. ; autounlock=false ; Maximum number of transactions to display. ; This does NOT affect how many transactions are fetched internally; ; it only limits how many are presented at once. ; transactiondisplaylimit=121 ; Reset wallet transactions on startup to trigger a full rescan. ; Use this if you suspect missing transactions. ; resetwallettransactions=false ; ============================================================================ ; Chain & On-Chain Configuration ; ============================================================================ ; Network settings (only one can be true). ; If both regtest and testnet are false, mainnet will be used by default. ; Use the regression test network. ; regtest=false ; Use the test network. ; testnet=false ; Address type to generate (taproot, segwit, or nested-segwit). ; Default is 'segwit'. ; addresstype=segwit ; Custom fee estimation API endpoint (optional). ; The URL below is only an example — you can replace it with your own fee provider. ; Expected response format: ; {"fastestFee":1,"halfHourFee":1,"hourFee":1,"economyFee":0,"minimumFee":0} ; feeurl=https://lokichain.info/api/v1/fees/recommended ; ============================================================================ ; Node Identity ; ============================================================================ ; The node alias (max 32 UTF-8 characters). ; This is how your node will appear to others on the network. ; Default is 'MyLokiNode'. ; alias=MyLokiNode ; The color of the node in hex format (e.g., '#da9526'). ; Used to customize node appearance in graph visualizations. ; Default is '#da9526'. ; color=#da9526 ; ============================================================================ ; P2P Network & Connectivity ; ============================================================================ ; The timeout value for network connections {ms, s, m, h}. ; Default is '50s'. ; connectiontimeout=50s ; Add an interface/port to listen for peer connections (incoming). ; One listen address per line. Example: listen=0.0.0.0:5521 ; listen=0.0.0.0:5521 ; Disable listening for incoming peer connections. ; Set to true if you want to run a private node (outgoing connections only). ; nolisten=false ; Connect only to the specified peers at startup (exclusive mode). ; connect=node.example.org ; Add peers to connect to at startup (in addition to any discovered peers). ; One peer per line. Format: hostname:port or ip:port ; Flokicoin default P2P port is 15212. ; addpeer=peer1.example.com:15212 ; addpeer=peer2.example.com:15212 ; If true, will apply a randomized staggering between 0s and 30s when ; reconnecting to persistent peers on startup. ; Helps reduce connection storms on node restart. ; stagger-initial-reconnect=false ; --- Tor Configuration --- ; Enable Tor for P2P connectivity. ; If enabled, the node will use Tor SOCKS proxy for outgoing connections ; and create a hidden service for incoming connections. ; tor.active=false ; The host:port that Tor's SOCKS proxy is listening on. ; Default is localhost:9050. ; tor.socks=localhost:9050 ; The DNS server as host:port that Tor will use for SRV queries. ; Note: Must have TCP resolution enabled. ; Default is ln.myfloki.com:53 ; tor.dns=ln.myfloki.com:53 ; The host:port that Tor is listening on for control connections. ; Required for creating hidden services (onion addresses). ; Default is localhost:9051 ; tor.control=localhost:9051 ; --- Public Announcement --- ; Add an ip:port to advertise to the network for incoming connections. ; Use this if you have a static public IP address. ; One IP per line. Example: externalip=55.10.16.10:5521 ; externalip= ; Add a hostname:port that should be periodically resolved to announce IPs. ; Use this if you have a dynamic IP with a DNS hostname (e.g., DynDNS, No-IP). ; FLND will automatically resolve the hostname and update your advertised IP. ; If port is not specified, the default (5521) will be used. ; One hostname per line. Example: externalhosts=mynode.ddns.net:5521 ; externalhosts= ; Toggle NAT traversal support (using either UPnP or NAT-PMP). ; Automatically advertise your external IP address to the network. ; Useful if you're behind a router and want to accept incoming connections. ; nat=false ; ============================================================================ ; RPC & REST API Configuration ; ============================================================================ ; Add an interface/port/socket to listen for RPC connections. ; One listen address per line. ; Example: rpclisten=127.0.0.1:10005 ; rpclisten=127.0.0.1:10005 ; Add an interface/port/socket to listen for REST connections. ; One listen address per line. ; Example: restlisten=127.0.0.1:5050 ; restlisten=127.0.0.1:5050 ; Add an ip:port or hostname to allow cross-origin access to the REST API. ; One entry per line. ; Examples: ; restcors=http://localhost:3000 ; restcors=https://mydomain.com ; restcors=http://localhost:3000 ; --- TLS Options --- ; Adds an extra IP to the generated certificate. One IP per line. ; tlsextraip=0.0.0.0 ; Adds an extra domain to the generated certificate. One domain per line. ; tlsextradomain=localhost ; Re-generate TLS certificate and key if the IPs or domains are changed. ; Enabled by default to ensure certificate validity when changing network settings. ; tlsautorefresh=true ; ============================================================================ ; Channel Configuration ; ============================================================================ ; The maximum number of incoming pending channels permitted per peer. ; Default is 1. Increase if you want to accept multiple channels from the same peer. ; maxpendingchannels=1 ; If true, the node will be configured to allow channels larger than 5 FLC. ; Use this option if you want to accept large channels (Wumbo). ; Default is false. ; wumbo-channels=false ; The largest channel size (in Loki) that we should accept. ; Incoming channels larger than this will be rejected. ; ; If wumbo-channels is false (default), the maximum allowed value is 500,000,000 Loki (5 FLC). ; If you want to accept larger channels (e.g. 210 FLC), you must set wumbo-channels=true above. ; ; Default is 500000000 Loki (5 FLC). ; maxchansize=500000000 ; The smallest channel size (in Loki) that we should accept. ; Incoming channels smaller than this will be rejected. ; Default is 20000 Loki (0.00020000 FLC). ; minchansize=20000 ; ============================================================================ ; Routing & Forwarding Configuration ; ============================================================================ ; If true, lnd will not forward any HTLCs that are meant as onward payments. ; Use this to run in wallet-only mode (no routing). ; rejecthtlc=false ; The smallest HTLC we will forward (in milli-Loki). ; Default is 1 milli-Loki. ; minhtlc=1 ; The base fee in milli-Loki we will charge for forwarding payments. ; This is a fixed fee added to every forwarded payment. ; Default is 1000 milli-Loki (1 Loki). ; basefee=1000 ; The fee rate used when forwarding payments (in millionths). ; Total fee = basefee + (amount × feerate / 1,000,000) ; Example: feerate=100 means 0.01% (100 ppm) ; Default is 100 (0.01%). ; feerate=100 ; The CLTV delta we will subtract from a forwarded HTLC's timelock value. ; This is the number of blocks you require for safety when forwarding. ; Default is 400 blocks. ; timelockdelta=400 ; The maximum number of blocks funds could be locked up for when forwarding payments. ; This is a safety limit to prevent funds being locked for too long. ; Default is 10080 blocks (7 days with 1-minute blocks). ; max-cltv-expiry=10080 ; Accept spontaneous payments through keysend (payments without invoices). ; Set to true to enable receiving keysend payments. ; accept-keysend=false ; Accept spontaneous payments through AMP (Atomic Multi-Path Payments). ; Set to true to enable receiving AMP payments. ; accept-amp=false ; ============================================================================ ; Network Graph & Gossip Configuration ; ============================================================================ ; The number of peers that we should receive new graph updates from. ; Higher values provide better network awareness but use more bandwidth. ; Default is 3. Recommended: 3-5 for routing nodes, 1-2 for wallet-only nodes. ; numgraphsyncpeers=3 ; The polling interval between historical graph sync attempts. ; Format: duration with unit (e.g., 20m, 1h, 30s) ; Default is 20 minutes. ; historicalsyncinterval=20m ; If true, will not reply with historical data that matches the range ; specified by a remote peer's gossip_timestamp_filter. ; Set to true to reduce bandwidth usage. ; ignore-historical-gossip-filters=false ; ============================================================================ ; Watchtower Configuration ; ============================================================================ ; Enable integrated watchtower to help protect your channels when offline. ; The watchtower monitors the blockchain for channel breaches. ; watchtower=false ; Directory for watchtower state. ; If not specified, uses a subdirectory in walletdir. ; watchtower.towerdir= ; ============================================================================ ; Protocol Options ; ============================================================================ ; Allow the node to accept and lend out (zero-conf) unconfirmed channels. ; This allows channels to be usable immediately after funding transaction broadcast, ; but comes with trust risks. ; protocol.option-zeroconf=true ; Allow the node to accept and provide SCID aliases for private channels. ; Useful for privacy and zero-conf channels. ; protocol.option-scid-alias=true ; ============================================================================ ; Performance & Tuning ; ============================================================================ ; Time in milliseconds between each release of announcements to the network. ; Lower values propagate gossip faster but use more bandwidth. ; Default is 9000 (9 seconds). ; trickledelay=9000 ; The polling interval between attempts to detect if an active channel has ; become inactive due to its peer going offline. ; Format: duration string (e.g. 1m, 30s). ; Default is 1m. ; chan-status-sample-interval=1m ; ============================================================================ ; Invoices ; ============================================================================ ; The number of blocks within which the invoice will remain in the accepted state ; before being canceled. ; Default is 0. ; hodl.expiry-delta=0 ```
## Run On macOS/Linux: ```bash ./twallet ``` On Windows: ```powershell twallet.exe ``` If your OS flags the binary, allow it explicitly. --- ## Managing with Lokihub While **tWallet** provides the core FLND node, most users prefer a dedicated interface for managing Lightning operations. **Lokihub** is the recommended companion app for this purpose. ### Quick Connection To connect Lokihub to your running tWallet node: 1. **Open Lokihub** on the same computer. 2. Choose **"Automated Connection"** (or select **"Local Node"**). 3. Lokihub will automatically retrieve the necessary credentials from your tWallet data directory. ### Manual Configuration If you are connecting from a different machine or the automated connection fails, you will need your node's credentials: - Press CTRL + N inside tWallet. - This opens a window displaying your **gRPC Address**, **Macaroon Hex**, and **TLS Certificate**. - Copy these into the Lokihub setup wizard. [View the Lokihub Setup Guide →](/lokihub/setup#automated-connection) --- Data Locations By default, **tWallet** stores its configuration, logs, and all underlying **FLND** node data (including channel databases and wallet files) in the application data directory of your operating system. | OS | Default Path | | :--- | :--- | | **Linux** | `~/.flnd/` | | **macOS** | `~/Library/Application Support/Flnd/` | | **Windows** | `%APPDATA%\Flnd\` | The `.flnd/` directory is the unified home for both your on-chain wallet and your Lightning node state. **Always back up the entire `.flnd/` directory before making system changes or migrations.** CRITICAL: Lightning Backups Unlike traditional wallets, **a 24-word seed phrase DOES NOT recover your Lightning channel funds.** The seed only recovers funds in your on-chain (on-chain) wallet. To protect your channel liquidity, you must understand the following: 1. **Static Channel Backups (SCB)**: Your node generates a `channel.backup` file (found in `.flnd/data/chain/flokicoin/mainnet/`). This file is required to recover funds from open channels in the event of hardware failure. 2. **Seed + SCB**: To fully restore a node, you need **both** your 24-word seed and your most recent `channel.backup` file. 3. **The channel.db Risk**: **NEVER** attempt to restore an old copy of your `channel.db` file. If you broadcast an outdated channel state to the network, your peers may trigger a "penalty transaction," which results in the **total loss of your funds** in that channel. :::danger[DATA LOSS RISK] Always ensure you have an automated or frequent backup of your `channel.backup` file. Without it, funds locked in Lightning channels cannot be recovered if your local data is lost. ::: ### Custom Data Location If you want to store your wallet on an external drive or a specific partition, use the `walletdir` flag or config option: ```bash ./twallet --walletdir /path/to/custom/folder ``` --- ## Advanced Usage ### Running Multiple Instances You can run multiple independent wallets on the same machine by specifying unique data directories and ports. 1. **Create a second directory**: `mkdir ~/twallet-alt` 2. **Launch with custom ports**: ```bash ./twallet --walletdir ~/twallet-alt --rpclisten 127.0.0.1:11005 --restlisten 127.0.0.1:6060 ``` 3. **Unique Identity**: Ensure each instance has a different `alias` in its respective `twallet.conf`. --- ## Uninstallation To cleanly remove tWallet from your system: 1. **Remove the Binary**: Delete the `twallet` (or `twallet.exe`) file. 2. **Purge Data**: Delete the default data directory (see [Data Locations](#data-locations) above). 3. **Clean Logs**: If you configured custom logging paths, ensure those files are also removed. :::warning[IRREVERSIBLE] Uninstalling and deleting the data directory will permanently remove your local encrypted database. Ensure you have your **24-word seed phrase** before doing this. ::: --- ## FAQ & Troubleshooting ### Why is the initial sync taking so long? tWallet v1 uses the **Neutrino protocol**. During the first run, it must download "Block Filters" to scan for your transactions. This is a one-time process. If it seems stuck: * Ensure your internet connection is stable. * Check `debuglevel=info` in your logs to see if it's still processing filters. ### "Permission Denied" on Linux/macOS If you cannot run the binary, you may need to grant execution permissions: ```bash chmod +x twallet ``` ### Can I use my tWallet v0 seed? **No.** v1 uses the `aezeed` format (compatible with LND), while v0 uses `BIP39`. To use your v0 funds, you must either: 1. Continue using [**tWallet v0**](/wallets/twallet/v0). 2. Send your funds from v0 to a new v1 address. --- Full Release History Access detailed technical notes, cryptographic checksums, and cross-platform installation assets for all historical tWallet v1 versions. View Archive ## Security - Back up your seed phrase (24 words recommended) and test recovery. - Set a spending passphrase and lock your wallet when idle. - Keep tWallet up to date: https://github.com/flokiorg/tWallet/releases --- ## Release History(V1) import Link from '@docusaurus/Link'; import { Download, History, ExternalLink } from 'lucide-react'; # tWallet v1 Release History This page tracks the evolution of **tWallet v1**. While we recommend always using the latest release for security and performance, you can find the full history of v1 pre-releases below. | Version | Date | Key Changes | | :--- | :--- | :--- | | [**1.0.9-beta**](/wallets/twallet/v1/1.0.9-beta) | Latest | Added Windows 32-bit assets and improved dependency management. | | [**1.0.8-beta**](/wallets/twallet/v1/1.0.8-beta) | - | Migrated from btcsuite's Neutrino to Flokiorg's fork for enhanced reliability. | | [**1.0.5-beta**](/wallets/twallet/v1/1.0.5-beta) | - | Critical fix for transaction scanning on low-memory devices. | | [**1.0.4-beta**](/wallets/twallet/v1/1.0.4-beta) | - | Optimized gRPC streaming for mobile-compatible dashboard clients. | | [**1.0.3-alpha**](/wallets/twallet/v1/1.0.3-alpha) | - | Initial Flokicoin Neutrino protocol implementation. | | [**1.0.2-alpha**](/wallets/twallet/v1/1.0.2-alpha) | - | Added Segwit and Taproot address support. | | [**1.0.1-alpha**](/wallets/twallet/v1/1.0.1-alpha) | - | First WalletKit gRPC service public test. | --- :::tip[Always Stay Updated] For the best experience and the latest security patches, we strongly recommend running the latest version from our [GitHub Releases](https://github.com/flokiorg/tWallet/releases). ::: --- ## Web of Fun — Reimagine Everyday Internet Services import wofBookImage from './wof_book.png'; import Heading from '@theme/Heading'; // eslint-disable-line no-unused-vars Overview
“You never change things by fighting the existing reality. To change something, build a new model that makes the existing model obsolete.” — Buckminster Fuller
The internet’s first age connected peers and shared static pages. Services followed, shaped by centralized interfaces that traded convenience for control over our data. Bitcoin reintroduced a public, decentralized mindset, yet the promise of Web3 tangled with speculation, token printing, and platforms that owned the experience. WoF is the movement to build the next web by redesigning everyday services so people decide how their data, identity, engagement, and contributions circulate in a work-based economy. If you believe the web can be cooperative, trustless, and permissionless, you belong here. :::warning[Asking about Flokicoin and WoF?] WoF stands on its own—no coin, no chain, a movement to reimagine the web through [FEPs](#what-is-a-fep). :::
The next web is transforming energy into shared value and returning ownership to its source.
## Web2, Web3… and the Next Web - **Web1** let us publish static pages, but expression was limited. - **Web2** layered rich interfaces, yet every login, review, and dataset collapsed into walled platforms hungry for our data. - **Bitcoin** showed a different path. Value could move without middlemen. - **Web3** made wallets and tokens mainstream but mostly printed assets around the same middlemen; everyday web engagements never changed. WoF is the reset button. We focus on everyday internet services—maps, messaging, media, commerce—and reimagine them with transparent economics, data ownership, sovereign identity, cohesive collaboration, and measurable engagement. The goal isn’t to decorate the old web; it’s to invent a humane one. ## Why Nostr + POW Are WoF’s Backbone Most people hear “[Nostr](https://jump.ohstr.com/)” and picture a decentralized social app popularized by Jack Dorsey. In reality, Nostr is a lightweight communication layer—think of it as HTTP for the next web: simple, open, and portable. Proof-of-work is the economic layer that keeps that next web honest. You either spend previously earned work-backed coins to access services, or you contribute fresh work that other people can rely on. Core principles WoF leans on: - **Proof-of-work**: offerings price access in energy-backed coins—people can spend previously mined work or pick up new work to earn their way in. - **Keys as identity**: public/private pairs replace platform-bound usernames, keeping reputation portable. - **Signed notes**: every interaction is an immutable, timestamped event any client can read, verify, or extend. - **Relay choice**: participants pick or run relays to route events, so no single intermediary controls communication. WoF builds on Nostr so every service speaks the same language from day one, and on proof-of-work so every economic promise traces back to real effort. Communication, coordination, and engagement travel through Nostr, while pricing, access, and governance lean on verifiable work. What is a FEP? **FEP** stands for **Fun Enhancement Possibility**. A FEP is WoF’s proposal blueprint. It lays out the experience issues you want to ease, the journey you’re inviting people into, and the economy that will support it. It’s not a feature request. It’s not a pump scheme. It’s a design challenge that invites anyone to remix the rules of the web. A clear FEP usually covers: - What’s happening today and what you want to redesign. - Who’s involved now and how their experience improves. - The economic design: how value circulates, what work backs it, and how participants stay aligned. - The Nostr primitives or new NIP drafts the service depends on. It isn’t a roadmap—it’s a launchpad. Submit your FEP and let’s buckle in. :::tip[Need a concrete example?] Check the [Sharenote manifesto](/wof/sharenote) for how one mining industry is taking shape. ::: ## Who WoF is For Builders Prototype services on top of the Nostr protocol, proof-of-work incentives, and expressive UX that hand ownership back to people. Marketers Craft narratives, campaigns, and rituals that onboard everyday users into decentralized services without losing their sense of wonder. Infrastructure Backers Spot teams and concepts worth funding early. Use FEPs to evaluate adoption models, work-based economies, and resilient infrastructure bets. Donors Fund experiments that create public goods, art, or education. Help teams cross the gap from idea to live prototype with mission-aligned resources. ## Why Build on Top, Not Against? We’re not here to torch the current web. The habits, networks, and tooling people rely on every day are the launch ramps for what comes next. WoF experiments extend what already works instead of forcing everyone to migrate overnight. We build on top because: - **Familiar entry points** let people try new experiences without abandoning their existing workflows. - **Incremental upgrades** allow teams to ship, measure, and iterate faster than a ground-up rewrite. - **Interoperability** keeps bridges open between legacy services. That is why WoF projects plug into today’s services, add transparent communication through Nostr, and weave in work-backed incentives. Evolution beats isolation. ## Ready to Submit Your First FEP? Start with a question: > *“Wouldn’t it be fun if…?”* Sketch the outline using the FEP checklist above, then publish it where the community already gathers. Use the discussion to refine the idea, gather feedback, and find collaborators who want to explore it with you. Because the only thing better than **thinking outside the box** is **turning the box into a game console**. :::note[Need a starting point?] Join the WoF Discord and drop into the discussion channels to swap notes and sharpen your concept. ::: ## WoF is Not a Feature. It’s a Philosophy. If you're here to speculate, that's okay. If you're here to innovate — welcome home. Let’s make the web courageous again. Let’s make online life resilient again. Let’s build with intention. **Let’s create Fun on Purpose.** - Join the #WoF Discord forum. Post a FEP. - Launch an experiment. - And above all—**don’t ask for permission. Ask: what’s the most meaningful move we could make right now?** --- ## Sharenote import ScratchReveal from '@site/src/components/ScratchReveal'; // eslint-disable-line no-unused-vars ## Abstract Sharenote is a miner-controlled proof-of-work note: every accepted share mints a signed sharenote, a bearer record of the work the miner resolved. Sharenotes can be spent on social engagements, resolving coin-mining blocks, buying intelligence, and more. Miners keep control of template selection and payout accounting. Learn more at [sharenote.xyz](https://sharenote.xyz). ## Motivation Even with hashpower growing, miners still rely on a handful of work-provider giants (Foundry USA · AntPool · F2Pool · ViaBTC). Two glaring issues stand out: **Opaque payouts** - Outside of solo mining, miners rarely know how their submitted shares translate into rewards. Payout logic lives inside proprietary dashboards. - Third-party tools estimate earnings, yet miners must trust that their shares were counted correctly, not reprioritized for another client. **Hidden block-template value** - Pools can embed auxiliary chains or custom policies into block templates without disclosing the additional rewards. - Miners have no channel to inspect or propose changes before work is assembled, even if extra value is minted using their hashpower. WoF aims to redesign everyday internet services around Nostr and work-backed incentives. Without transparent payouts and templates, miners stay dependent on centralized work providers, undermining WoF’s mission of participant-controlled engagement. ## Sharenote Concept Summary (Draft) Sharenote acts as the connective tissue between the Web of Fun (WoF) vision for playful, work-backed services and the daily routines of miners. Each accepted share becomes a signed receipt the miner can point to, redirect, or burn. The receipt is a sharenote: tangible proof that computational work happened and a programmable ticket that can be spent on social engagements, resolving coin-mining blocks, buying intelligence, and more. The lifecycle is intentionally simple: - **Mint** – The miner accepts a template from a work provider, performs the hashing work, and sees the resulting share captured as a sharenote. - **Record** – A sidecar app signs the sharenote and publishes it as a Notes and Other Stuff Transmitted by Relays (Nostr) event so anyone the miner authorizes can audit the stream. - **Spend** – The miner redeems the sharenote for social engagements, resolving coin-mining blocks, buying intelligence, and more; burns it; or keeps it as an auditable receipt for payouts. Sharenote keeps the miner, not the pool, in the driver’s seat. Miners can compare templates, track how many sharenotes each template minted, and decide which ones to support. Pool operators gain a channel to publish template changes, payout adjustments, and anomaly alerts without leaving the miner guessing. Observers—wallet builders, accounting tools, or community auditors—can follow the Nostr feed to build dashboards without depending on closed dashboards or web scraping. Because this Fun Enhancement Possibility (FEP) is still a draft, Sharenote sticks to a Without Breaking Existing Things (WBET) rollout. Stratum traffic keeps flowing, and the sidecar listens in, signs shares, and broadcasts them without interrupting the main client. That incremental path lets miners test Sharenote privately, pool by pool, before committing to public relays or template governance rituals. ## Status & Next Steps Sharenote is currently a draft FEP. Immediate work includes: - Finalizing the NIP references or creating a new NIP for Sharenote-specific events. - Building a prototype relay/client stack to test with a volunteer pool. - Following the WBET stage so Sharenote keeps working cleanly alongside existing mining workflows. If you want to participate, drop into the WoF Discord (#WoF) and look for the Sharenote thread. Learn more at [sharenote.xyz](https://sharenote.xyz).