Understand the protocol.

One ledger. Local validation.

Talnet uses unspent transaction outputs (UTXOs). A transaction consumes existing outputs and creates new ones. Every compatible full node validates the PoWTaL work, transaction authorization and ledger rules before accepting a branch.

Fork choice requires strictly greater cumulative work on a fully validated branch. Peer counts, advertised heights and AI predictions are not substitutes for this validation. Temporary competing blocks and reorganizations remain possible.

PoWTaL V1: bits-adaptive mining.

PoWTaL combines SHA3-256 and BLAKE3 mixing with a SipHash-indexed, sequential RAM walk. The block header commits to its state, difficulty bits, dataset size and walk count. Difficulty selects both the acceptable hash target and the mining resource profile.

The base is 2048 MiB with 1024 dependent reads per hash at 0x1e00ffff. A harder target can raise both to 14746 MiB and 14746 steps. The shared integer schedule uses the exponent and mantissa of bits, not elapsed time or the number of GPUs.

Example profiles

0x1e00ffff

2048 MiB / 1024 steps

0x1d00ffff

3466 MiB / 2556 steps

0x1c00ffff

4885 MiB / 4089 steps

0x1500ffff

14746 MiB / 14746 steps (caps reached)

Small difficulty changes can stay within the same integer threshold. Falling difficulty can reduce the profile, never below the base. Unchanged bits do not increase resources simply because another block was mined. These examples describe the configured formula, not today's live network difficulty.

PoWTaL targets ASIC resistance through a memory-intensive workload. Scaling is not proof of one physical PC per miner, does not forbid dataset sharing and is not a guarantee against specialized hardware or time-memory tradeoffs. More or faster hardware can still produce more work.

The current profile is BITS-ADAPTIVE-2048MB-1024-STEPS-MAX14746-V1. It is committed with the new Alpha identity. Memory checkpoints are not a zero-knowledge proof; the full node still validates blocks and transactions.

Sign once per owner.
Track each confirmation.

V1 groups the hybrid witness by authenticated input owner: ECDSA/secp256k1 plus SPHINCS+-SHAKE-256f-simple. Inputs from the same owner reference that witness instead of carrying duplicate post-quantum signatures. The SPHINCS+ component is 49,856 bytes per owner witness, before keys, classical signatures and transaction data.

Incoming payment

6 confirmations before it becomes spendable

Mining reward

200 confirmations before it becomes spendable

Authenticated sender change

Exempt from incoming-payment maturity, including eligible mempool change

New wallet backup

24-word recovery phrase

Precision

1 TAL = 1,000,000,000 Tallions

A mempool entry is not a mined confirmation. Pending sends reduce the amount available to spend by the transfer plus its fee; eligible change remains with the sender. The exemption applies to authenticated same-owner change, not any unconfirmed incoming payment.

The minimum fee is 20,000 Tallions per started 1,000 bytes. Wallet recommendations can be higher. MAX must also respect the 1000-input and 10 MiB transaction limits; it may not sweep an entire wallet in one transfer.

ChainGuard is shared.
Consensus stays proof of work.

ChainGuard V1 uses a fixed 8→16→8 model definition and deterministic integer arithmetic. Alpha commits the rules hash and initial-state hash. The first training update occurs at height 200, then after each batch of 200 accepted blocks.

1. Each node derives model features from its accepted chain.
2. Compatible peers exchange bounded, rate-limited checkpoints.
3. A received checkpoint is checked against independent canonical replay, not trusted because a peer advertises a newer version.
4. Chain changes require the shared model to follow the accepted branch.

The model is advisory: it predicts block-derived features. A lower training loss is not a calibrated attack-detection rate, and the AI does not accept or reject ordinary blocks or transactions.

V1 specifications.

Chain ID

TALNET-POWTAL-V1

Block wire version

1

Block interval target

300 seconds

Supply cap

10,512,000 TAL

First subsidized block

1; Alpha has no subsidy

Initial block subsidy

10 TAL

Halving interval

525,600 blocks

Difficulty adjustment interval

2,016 blocks

Incoming confirmations

6

Coinbase maturity

200

Base mining dataset / walk

2048 MiB / 1024 steps

Maximum mining dataset / walk

14746 MiB / 14746 steps

Memory scaling

Derived from each block's difficulty bits; integer thresholds, with base and caps

Maximum serialized block

16 MiB

Maximum transaction

10 MiB

Maximum transaction inputs / outputs

1000 / 1000

Minimum output

0.0001 TAL

Minimum size-based fee

20,000 Tallions per started 1,000 bytes

Five minutes is a target, not a deadline. Halvings occur by height, not calendar date. At the target rate, 525,600 blocks is approximately five years.

Identity from Block 0.

These anchors describe the current bits-adaptive source revision, not the live tip or a certification of the downloadable binaries. The earlier fixed-profile test chain is incompatible. Use matching builds; do not reuse its chain database as the new chain. Keep wallet backups separate.

Alpha mined (UTC)

13 September 2026 · 19:38:42 UTC

Timestamp (Unix seconds)

1789328322

Nonce

14885883

Initial bits

0x1e00ffff

The fixed AI commitments are embedded in Alpha's metadata and covered by its Merkle root, proof of work and consensus commitment. The model's learned state changes over time; its V1 rules are not replaced by arbitrary files from peers.

Changing the chain-defining rules creates an incompatible protocol. Open-source code can be edited, but an edit does not make existing compatible nodes accept different rules.

Before you run a node.

1. Check the package/source identity. Back up any existing wallet before replacing software.
2. On desktop, create or load your wallet. Record the 24-word recovery phrase privately and offline.
3. Let the node synchronize with compatible peers and inspect its connection and chain status.
4. For GPU mining, install a suitable OpenCL driver. Check that the current bits-derived dataset fits both system RAM and GPU VRAM, with overhead; a later difficulty increase may need more memory.
5. Choose the intended reward wallet before starting the miner. Mining has variable results and resource costs.

The Linux target TalnetNode is a headless full node built from the core, wallet, network and PoWTaL validation sources. It is not merely a relay, and it does not provide the Windows wallet GUI. A precompiled Linux x86-64 runtime archive is available. Extract it into a new folder and run ./install-dependencies.sh, then ./startnode.sh check and ./startnode.sh start. The dependency installer supports selected Ubuntu, Debian and Mint releases and reads requirements.txt; the exact MiniUPnPc ABI is bundled privately. No compilation is needed. See the included README and RUNTIME.txt. This headless package does not mine. Clean-machine Linux startup has not been tested here.

Hardware speeds and minimum system-memory/disk requirements have not been benchmarked here. Storage demand grows with the local blockchain.

Clear boundaries.

• Proof of work does not eliminate reorganizations, majority-hashpower attacks or network isolation.
• Hybrid signatures do not protect a stolen recovery phrase, compromised device or faulty implementation.
• Protocol size limits are not a guarantee against denial-of-service attacks.
• An Android light wallet depends on reachable, compatible gateways; it does not perform all full-node validation.
• PatchTal's local SHA-256 comparison is not independently verified publisher signing. Review update-source trust before installing.

Do not enter a recovery phrase on this website or send wallet/private-key files to support. Report suspected vulnerabilities privately through the maintainer's established contact channel.