Status and How to Verify Yourself

Exfer is an early but live open-source project. Technical maturity is at the high end among small PoW projects; commercial traction, ecosystem, and exchange integration are still at the beginning. This page lays out what's shipped and what isn't — and gives you a checklist for independently verifying every claim.

What has shipped, what hasn't

In summary: Exfer is neither a pure-narrative project nor mature infrastructure — it sits between the two, closer to the early end. Whether that reads as opportunity or risk is for the reader to decide.

How to verify without taking anyone's word for it

For technical projects, self-verification is the most reliable way in.

1. Read the spec

Read upstream EXFER.md. Every algorithm has a formal definition and test vectors. After reading, you can independently judge "does this design hold together?" — no interpreter needed.

2. Read the code

Full source at github.com/ahuman-exfer/exfer. MIT, Rust, with tests. You can read it line by line and run cargo test. The most direct way to assess an open-source project's quality.

3. Run a full node

Follow Install to compile and start a node. Sync from the genesis block. If the protocol contains internal inconsistencies or the implementation has bugs, the node will fail to sync. This is the most direct verification that the design corresponds to working code.

4. Mine on a CPU

Follow How Exfer mining works and Solo mine on a CPU. A laptop is enough. Zero financial barrier. Mining your first block proves: memory-hard PoW works on your hardware, rewards arrive in your wallet, coinbase maturity is 360 blocks.

5. Verify "no premine"

Read the genesis module in the source. The genesis block's coinbase output is public — anyone can see which address it locks to, and the amount. If there were a premine, it would be there. Read it; confirm there isn't.

6. Read SECURITY.md

One signal of project honesty: does the team publicly enumerate known security tradeoffs? Exfer's SECURITY.md lists:

• The RPC interface is unauthenticated (production deployments need a reverse proxy)
• The exact boundaries of "Replay PoW Verification"
• No third-party audit currently

A project willing to print its weaknesses on the front page is more trustworthy than one that hides them — but that doesn't mean "no problems," it means "the maintainers know and have told you."

7. Engage the community

• Bug reports: https://github.com/ahuman-exfer/exfer/issues
• Discussion: https://github.com/ahuman-exfer/exfer/discussions

File an issue, see how quickly and substantively it's handled. Look at how historical issues were resolved. That tells you whether the project is alive or a zombie.

A self-check before going deep

If you intend to engage seriously with Exfer, at minimum do these three:

• Synced a full node to the chain tip
• Mined at least one block on a CPU (or joined a pool and seen actual rewards)
• Read SECURITY.md and understood the limitations listed there

Decide on deeper involvement only after those three steps. Reading this page and committing without verification is not careful diligence.

Costs / boundaries

• Ecosystem is thin today. Tooling, wallets, third-party services are scarce. Early involvement means building a lot of wheels yourself
• The value hypothesis is unrealized. All the "machine economy infrastructure" narrative is potential; expect 2–3 years before it's clear whether the AI-agent economy actually arrives at scale
• No formal foundation as a fallback. When something goes wrong, no entity is on the hook. This is the standard pattern for permissionless open-source protocols — but worth being clear-eyed about

Further reading

• FAQ — short answers
• Contributing — if you want to contribute code
• Backup & recovery — managing larger amounts