RPOW (Reusable Proofs of Work)
E696524
RPOW (Reusable Proofs of Work) was an early digital cash system proposed by Hal Finney that aimed to make proof-of-work tokens transferable and reusable, serving as a conceptual precursor to modern cryptocurrencies.
Observed surface forms (1)
| Surface form | Occurrences |
|---|---|
| RPOW | 0 |
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
cryptographic protocol
ⓘ
digital cash system ⓘ proof-of-work system ⓘ |
| aimedToSolve |
double-spending of proof-of-work tokens
ⓘ
non-transferability of basic proof-of-work stamps ⓘ |
| basedOn | proof-of-work ⓘ |
| countryOfOrigin |
United States of America
ⓘ
surface form:
United States
|
| creator | Hal Finney NERFINISHED ⓘ |
| describedIn | RPOW: Reusable Proofs of Work NERFINISHED ⓘ |
| designedBy | Hal Finney NERFINISHED ⓘ |
| field |
computer security
ⓘ
cryptography ⓘ digital currency ⓘ |
| hasFeature |
prevents token duplication
ⓘ
publicly auditable server code ⓘ server issues new tokens in exchange ⓘ server validates incoming proof-of-work tokens ⓘ stateless client usage ⓘ |
| hasGoal |
enable transferable proof-of-work tokens
ⓘ
make proof-of-work tokens reusable ⓘ prevent double-spending of proof-of-work tokens ⓘ |
| hasProperty |
centralized server design
ⓘ
does not use a blockchain ⓘ experimental prototype ⓘ non-anonymous by default ⓘ openly published design ⓘ |
| hasWebsite | http://rpow.net/ ⓘ |
| influenced | Bitcoin community discussions ⓘ |
| inspiredBy | Hashcash NERFINISHED ⓘ |
| language | English ⓘ |
| notableFor |
conceptual precursor to modern cryptocurrencies
ⓘ
early reusable proof-of-work design ⓘ use of trusted computing for digital cash ⓘ |
| operatingModel | server issues and redeems tokens ⓘ |
| predecessorOf | cryptocurrency concepts ⓘ |
| publicationYear | 2004 ⓘ |
| relatedTo |
Bitcoin
NERFINISHED
ⓘ
Hashcash NERFINISHED ⓘ digital cash ⓘ proof-of-work tokens ⓘ |
| securityModel |
relies on public verification of server state
ⓘ
relies on tamper-resistant hardware ⓘ |
| status | inactive ⓘ |
| usesConcept |
one-time proof-of-work tokens
ⓘ
reissuance of tokens ⓘ remote attestation ⓘ secure server ⓘ tokenization of proof-of-work ⓘ trusted hardware ⓘ |
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.