Open Transactions: Difference between revisions
Jump to navigation
Jump to search
Create article for Open Transactions. |
m Use a list instead of code section. |
||
| Line 4: | Line 4: | ||
Featuring: | Featuring: | ||
* Untraceable Digital Cash (real blinded tokens) | |||
* Anyone An Issuer (Ricardian-style Contracts) | |||
* Bearer-only, Fully-Anonymous (when used cash-only) | |||
* Pseudonymous User Accounts (user account == PGP key) | |||
* No Account History (asset account == the last receipt) | |||
* Many Financial Instruments (cheques, cash, vouchers, invoices...) | |||
* Basket Currencies (10 "baskets" == 5 gold, 3 silver) | |||
* Markets with Trades (stop, fill-or-kill, limit orders...) | |||
* Payment Plans | |||
Includes an API, server and client. | Includes an API, server and client. | ||
Revision as of 21:56, 24 April 2011
A financial crypto and digital cash software library. The software's author likens it to "PGP for money".
Open Transactions (a centralized transaction system) is complementary to Bitcoin in that it provides some features that Bitcoin cannot, such as anonymous (versus pseudonymous) transactions, no latency (no double spending risk) and more.
Featuring:
- Untraceable Digital Cash (real blinded tokens)
- Anyone An Issuer (Ricardian-style Contracts)
- Bearer-only, Fully-Anonymous (when used cash-only)
- Pseudonymous User Accounts (user account == PGP key)
- No Account History (asset account == the last receipt)
- Many Financial Instruments (cheques, cash, vouchers, invoices...)
- Basket Currencies (10 "baskets" == 5 gold, 3 silver)
- Markets with Trades (stop, fill-or-kill, limit orders...)
- Payment Plans
Includes an API, server and client.
External Links
- Open Transactions project on GitHub
- Readme