Clear answers.
Less guesswork.

Talnet is an experimental proof-of-work cryptocurrency using PoWTaL, a UTXO ledger and hybrid ECDSA + SPHINCS+ transaction authorization. The desktop application combines a wallet, full node and GPU miner.

The V1 cap is 10,512,000 TAL. Alpha has no subsidy. Rewarded blocks start at height 1 with 10 TAL, halving every 525,600 rewarded blocks. Integer rounding can leave scheduled issuance slightly below the cap. This is not a live circulating-supply reading.

No. The full node selects a fully validated branch with strictly greater cumulative work. Peer count and reported height are discovery hints. Competing blocks, temporary forks and reorganizations can still happen.

Use the download page for the Windows archive, Android wallet APK and precompiled Linux x86-64 node archive. The Linux package needs compatible runtime libraries, not build tools; follow its included README. Check the package's compatibility first; the site does not claim that an unverified archive contains the current V1 build.

An incoming payment needs 6 confirmations. While only in the mempool it has no mined confirmations. Mining rewards follow a separate 200-confirmation maturity rule. Time estimates are approximate because block intervals vary.

A transaction may consume a larger UTXO and return the remainder to its authenticated owner. V1 exempts eligible same-owner change from incoming-payment maturity, including eligible mempool change. This is not permission to spend arbitrary unconfirmed payments from other people.

Subtract the amount sent and the actual fee from the available starting balance, assuming no other wallet activity. For example: 200 − 100 − 0.00102 = 99.99898 TAL. Eligible sender change should not be relabeled as a newly received payment awaiting six confirmations.

Immature outputs are not spendable. A transaction is also limited to 1000 inputs and 10 MiB, and it must pay its fee. If your balance is spread across more outputs, one MAX transaction may not sweep every UTXO.

No. A lost response does not prove the network rejected the transaction. Check its transaction ID, activity history and chain status before retrying. Sending a new transaction without checking can cause an unintended duplicate payment.

New wallets generate a 24-word recovery phrase. Store it privately offline and keep a separate protected backup of the wallet file and required credentials. Close the application before copying active wallet files. Never enter your phrase on this website or send it to support.

No. The Android project is a light wallet that uses reachable, compatible gateways and lightweight chain checks. It does not run all full-node validation, and a cached balance does not prove it is currently connected.

The bits-adaptive V1 mining profile starts at 2048 MiB and 1024 sequential RAM-walk steps, using SHA3 and BLAKE3 mixing. It is capped at 14746 MiB and 14746 steps. The supplied miner holds the dataset in system RAM; GPU mining also needs an OpenCL driver and a dataset copy in VRAM, plus overhead in both. A nominal 2 GB card is not guaranteed to fit even the base profile.

Yes. The current rules derive the dataset size and sequential step count from the block's difficulty bits. At 0x1d00ffff the profile is 3466 MiB / 2556 steps; at 0x1c00ffff it is 4885 MiB / 4089 steps. Small changes may stay within one integer threshold; falling difficulty can lower requirements back toward the base. There is no automatic growth when bits stay unchanged. See the profile examples and limits.

No. A received block already has a nonce. The low-memory CPU verifier derives the touched entries on demand and repeats the bits-derived number of walk steps. It does not mine the block again or allocate the full RAM/VRAM dataset. Larger walk counts still increase verification work.

No. Mining rewards go to the miner of an accepted block. Running a wallet or relay by itself does not earn a universal reward. No UBI distribution or guaranteed income is implemented by the features described here.

The network target is 300 seconds, with a configured difficulty adjustment interval of 2,016 blocks. Actual discovery times vary, and your own mining success depends on your work relative to the network.

Its rules are shared: the V1 model definition and initial-state hash are committed by Alpha. Nodes independently derive state from their accepted chain and exchange bounded checkpoints. A peer's checkpoint is checked against deterministic replay rather than adopted merely because it claims to be better.

Yes. The first V1 training update is at height 200, followed by an update every 200 accepted blocks. Its learned state evolves; the Alpha-bound V1 rules remain the same. The output is advisory, not a decision to accept or reject transactions or ordinary blocks.

Anyone can modify their own copy. That does not make compatible nodes accept invalid signatures or different consensus rules. A change to the chain identity or consensus parameters produces incompatible behavior; open source itself is not a security guarantee.

No. Talnet requires both ECDSA and SPHINCS+-SHAKE-256f-simple authorization, but a stolen recovery phrase, compromised device or implementation flaw can still put funds at risk. The project does not claim to be unbreakable or formally audited.