RPOW (Reusable Proofs of Work)
RPOW (“Reusable Proofs of Work”) was a working prototype system built by Hal Finney (2004) to make proof-of-work tokens transferable and reusable. In the 21ideas framing, RPOW demonstrates how close pre-Bitcoin systems came — and why reliance on a central server remained a fatal limitation.
The problem RPOW tried to solve
Genesis Files Part V explains that Hashcash-style PoW tokens are expensive to produce but, by themselves, are not good “money” because the recipient cannot easily reuse them as payment.
RPOW’s purpose was to turn PoW into a token that could circulate.
How the system works (per the source)
In raw/Theory/history/genesis-files/genesis-5.md, the flow is:
- a user generates a valid PoW token (Hashcash-style),
- the user submits it to an RPOW server,
- the server returns a signed RPOW token,
- recipients can submit received tokens to the server to verify they weren’t spent before,
- the server marks the old token spent and issues a fresh one (so the token can circulate).
In other words, the system enforces “single-use” at each exchange step, while still allowing ongoing transfer by reissuing a fresh token.
Minimizing trust with remote attestation
The source emphasizes Finney’s attempt to minimize trust in the server operator by running the server on tamper-resistant hardware and using remote attestation so users could verify the exact software running.
In 21ideas terms, this is “trust-minimization” — but it is not “trust elimination.”
Why RPOW still falls short (per 21ideas)
Two key limitations are highlighted:
- Central point of failure: even if the server behaves honestly, it can be shut down or forced offline, instantly breaking the system.
- Inflation/declining cost over time: as computation gets cheaper, PoW becomes easier, impacting long-term “store of value” ambitions (Finney’s own framing is that it is not designed for savings).
Relationship to Bitcoin
Genesis Files frames Bitcoin’s breakthrough as removing the central server while keeping the useful parts of PoW, plus adding difficulty adjustment and a consensus rule that makes reversing history expensive.
See:
Sources
Related Terms
Glossary | Hashcash | Proof of Work | difficulty adjustment | third parties
Related Pages
- b-money — predecessor proposal; consensus gaps
- bit-gold — predecessor proposal; trust surfaces and fungibility issues
- hal-finney — RPOW’s creator and early Bitcoin contributor