AFISCNT coin emblem
Development Network Active

AFISCNT

Australian Freedom Independence Scarcity Computing Network Transparency

A proof-of-work cryptocurrency being built from the protocol upward: deterministic monetary rules, verifiable ownership, independent nodes, persistent state, peer networking and transparent consensus.

What AFISCNT stands for

Built around seven principles.

AAustralian
FFreedom
IIndependence
SScarcity
CComputing
NNetwork
TTransparency
Development status: AFISCNT is currently a development / pre-mainnet project. Core protocol functionality and multi-node networking are operational in the development environment, but the protocol remains subject to testing, security review and further changes before any public mainnet launch.

Monetary Policy

Finite supply. Public allocation.

AFISCNT's monetary policy is designed to be understandable without hidden minting authority or an open-ended supply.

21,000,000
Maximum AFISCNT supply
87%
18,270,000 AFISCNT mining allocation
8%
1,680,000 AFISCNT treasury / ecosystem
5%
1,050,000 AFISCNT founder allocation
87% Mining
8%
5%

Mining schedule

AFISCNT targets one block approximately every 60 seconds. Mining issuance is designed to distribute the mining allocation over roughly 34.8 years. Consensus difficulty automatically adjusts as network hash power changes.

Founder vesting

The 5% founder allocation is locked for the first 12 months following mainnet launch, then vests linearly over the following 36 months. Full vesting therefore occurs four years after mainnet launch.

Protocol & Network

Working components, not just a whitepaper.

Proof of Work

AFISCNT uses proof-of-work mining with per-block difficulty and accumulated-work chain selection.

Dynamic difficulty

The development implementation targets 60-second blocks and retargets difficulty every 60 blocks when production moves substantially away from the target.

UTXO accounting

Ownership and spending are enforced through a UTXO model with signed transactions and exact atomic-unit accounting.

Encrypted wallets

Persistent secp256k1 wallets can be encrypted at rest, reloaded after restart and used to sign transactions locally.

Peer networking

Nodes can remember peers, discover additional peers, propagate blocks and transactions, and synchronize after being offline.

Fork resolution

Competing valid branches are compared using accumulated proof of work. Nodes can reorganise onto the stronger chain and rebuild derived state.

Development Progress

End-to-end functionality now demonstrated.

The development network has moved beyond isolated unit tests. Core workflows have been exercised from wallet creation through live node operation, transaction confirmation and recovery after restart.

✓

Live CLI node operational

AFISCNT can run as a long-lived node process, expose live status, manage peers, shut down cleanly and recover its chain on restart.

✓

Live transaction flow verified

Encrypted wallet → signed transaction → running-node mempool → mined block → recipient balance has been demonstrated end to end.

✓

Persistent mempool recovery

Pending transactions survive a clean node restart, are revalidated, and return to the mempool without being prematurely credited.

✓

Confirmed transaction cleanup

Once a recovered transaction is mined, it is removed from persistent mempool state and does not reappear after another restart.

✓

Replay protection verified

Confirmed transactions cannot simply be resubmitted to duplicate a payment because their original spendable outputs have already been consumed.

✓

Offline catch-up synchronization

A node can return after missing blocks, download the missing chain data in batches and converge on the same valid tip and balances.

✓

Automatic fork recovery

Divergent nodes can reconnect and automatically adopt the stronger valid branch, including removal of rewards that only existed on the losing fork.

✓

Automatic network maintenance

The node can periodically discover peers, attempt catch-up synchronization and invoke accumulated-work fork resolution without manual intervention.

✓

Network hardening

Request-size limits, malformed payload rejection, basic rate limiting, peer validation and bounded mempool behavior have been implemented.

✓

Persistent blockchain state

Blocks, reorganised chain state and dynamic difficulty data survive shutdown and restart while retaining independent validity checks.

These milestones describe the current development implementation and testing completed to date. They are not a claim that AFISCNT is production-ready, audited, listed, or operating a public mainnet.

Roadmap

From protocol to public network.

Phase 01

Protocol Foundation

Blocks, transactions, wallets, UTXOs, monetary policy, persistence and validation.

Core implemented
Phase 02

Node Networking

Propagation, peer persistence, discovery, synchronization, forks and maintenance.

Development implementation
Phase 03

Operational Hardening

Configuration, logging, packaging, broader regression testing and deployment tooling.

Current focus
Phase 04

Public Testnet

Multi-machine testing under real network conditions, failure testing and security review.

Planned
Phase 05

Mainnet

Mainnet only after protocol stabilization, testing and launch-readiness review.

Future

Transparency

No need to pretend it is finished.

Development-first disclosure

AFISCNT is openly described as pre-mainnet. Features may change while consensus rules, networking, security and deployment procedures are tested.

Technical enforcement over promises

Monetary policy, ownership rules and allocation restrictions are intended to be enforced by protocol logic wherever practical rather than relying solely on public statements.