Difference between revisions of "About"

From Open Transactions
Jump to navigation Jump to search
m (Radio Interviews: fixed agoristradio text)
(Video Walkthrough: Removed desktop video walkthru as well, since it contains footage showing the Monetas OT iPhone client. (Will post a new replacement video soon.))
 
(27 intermediate revisions by 2 users not shown)
Line 18: Line 18:
  
 
* Open-Transactions is an [[Use Cases|easy-to-use]], financial crypto, [[Sample Cash|digital cash]] and transaction [[List of Classes|library]].
 
* Open-Transactions is an [[Use Cases|easy-to-use]], financial crypto, [[Sample Cash|digital cash]] and transaction [[List of Classes|library]].
* Open-Transactions includes a [[API|client API]], a working [[Otserver|server]], a [[TestGUI|GUI test wallet]] (in Java) and a [[opentxs|command-line]] wallet utility.
+
* Open-Transactions is open-source.
 +
* Open-Transactions includes a [[API|client API]], a working [[Otserver|server]], a cross-platform [https://github.com/Open-Transactions/Moneychanger GUI] and a [[opentxs|command-line]] wallet utility.
 
* Open-Transactions features: a large variety of financial instruments, markets, basket currencies, unforgeable account balances, digital cash, destruction of account history, [http://iang.org/papers/ricardian_contract.html Ricardian contracts], Smart Contracts (scriptable clauses), and more.
 
* Open-Transactions features: a large variety of financial instruments, markets, basket currencies, unforgeable account balances, digital cash, destruction of account history, [http://iang.org/papers/ricardian_contract.html Ricardian contracts], Smart Contracts (scriptable clauses), and more.
  
Line 27: Line 28:
 
* Any issuer can sign and distribute new [[Sample Currency Contract|currency contracts]] in order to create new digital asset types.
 
* Any issuer can sign and distribute new [[Sample Currency Contract|currency contracts]] in order to create new digital asset types.
 
* Users may create many ''pseudonyms'' (public keys), each of which may own ''asset accounts'' of various types, on OT servers.
 
* Users may create many ''pseudonyms'' (public keys), each of which may own ''asset accounts'' of various types, on OT servers.
* Users can operate '''"cash-only"''' ''(without accounts)'' for maximum anonymity, using '''[[Sample Cash|unlinkable digital cash]]'''.
+
* Users can operate '''"cash-only"''' for maximum anonymity, using '''[[Sample Cash|untraceable digital cash]]'''.
  
  
Line 49: Line 50:
 
* Without the special mechanism that makes this possible, ''all parties would otherwise be forced to store all receipts forever''.
 
* Without the special mechanism that makes this possible, ''all parties would otherwise be forced to store all receipts forever''.
 
* Nyms and Asset Types have consistent IDs across all OT servers, since the ID is formed by hashing the relevant contract or public key.
 
* Nyms and Asset Types have consistent IDs across all OT servers, since the ID is formed by hashing the relevant contract or public key.
 +
 +
 +
<big>'''Is Open-Transactions [[CENTRALIZED|centralized]]?'''</big>
 +
* No—quite the opposite. Open-Transactions is highly '''decentralized'''.
 +
* Typical centralized servers have power over their users, but in OT, '''no server has power over the clients it serves''', because:
 +
# An OT server does not control user transactions—it merely notarizes them.
 +
# Anyone can operate an OT server, and users can go to any OT server to notarize transactions. Thus OT servers compete with each other to attract users to use their notary services.
 +
# Anyone can download an OT client, and use it to execute transactions on any OT server, or any group of OT servers.
 +
# OT uses triple-signed receipts, so transaction parties have independent cryptographic proof of transactions and balances.
 +
# OT servers do not store user assets. Rather, cryptocurrencies are stored in voting pools so the server can't steal them.
 +
 +
In every way, '''the user is in control, not the server'''—even when you're using servers you do not trust. These characteristics generate a '''federated''' network architecture—similar to the internet, and it has the same virtues as the internet—openness, decentralization, resilience, censorship-resistance, and user control.
 +
 +
The community behind OT is strongly committed to developing systems that give users full control over their own assets and information.
  
 
</div>
 
</div>
Line 55: Line 70:
 
<div style="float:right; max-width: 300px; margin: -20px 10px 0 20px;">
 
<div style="float:right; max-width: 300px; margin: -20px 10px 0 20px;">
  
 +
== White Paper ==
 +
 +
[http://www.opentransactions.org/open-transactions.pdf OT White Paper]
 +
 
 
== Diagrams ==
 
== Diagrams ==
  
[http://billstclair.com/ot/ot-diagram.jpg Architecture Overview]
+
[[Voting_Pool_Deposit_Process|Voting Pools]]
 +
 
 +
[http://i.imgur.com/HTyAJjg.png Architecture Overview (new)]
  
[http://billstclair.com/ot/OT-Anon-CashOnly.jpg Fully-Anonymous (cash only)]
+
[http://billstclair.com/ot/ot-diagram.jpg Architecture Overview (old)]
  
[http://billstclair.com/ot/OT-Pseudonym-Instruments.jpg Pseudo-Anonymous (using accounts)]
+
[http://billstclair.com/ot/OT-Pseudonym-Instruments.jpg Financial Instruments]
 
 
 
 
 +
 
== Radio Interviews ==
 
== Radio Interviews ==
  
Line 77: Line 99:
 
== Video Walkthrough ==
 
== Video Walkthrough ==
  
[http://goo.gl/Ea6rzq Desktop video 1 - Introduction]
+
[http://localhost:3000/img/iphone-app.png iPhone App screenshot]
 
 
[http://goo.gl/i0J3AF Desktop video 2 - Advanced]
 
 
 
[http://goo.gl/8Dxak1 iPhone video 1 - Introduction]
 
 
 
[http://goo.gl/u6xqHc iPhone video 2 - Advanced]
 
 
 
[http://vimeo.com/28141679 java testclient video 1]
 
 
 
[http://vimeo.com/28142096 java testclient video 2]
 
 
 
[http://open-transactions.github.io/tv/ Official video archive (more videos)]
 
  
 
-----
 
-----
 
Bitcoin donation address: 1NtTPVVjDsUfDWybS4BwvHpG2pdS9RnYyQ
 
 
'''IRC:''' #opentransactions at irc.freenode.net
 
 
Mailing list: [email protected]
 
 
[http://opentransactions.org/mailman/listinfo/ot-dev_opentransactions.org Subscribe to mailing list]
 
  
 
[[Components and GNU Licensing]]
 
[[Components and GNU Licensing]]
 
-----
 
 
Is Open-Transactions '''[[CENTRALIZED|centralized]]?'''
 
 
The vision is not of a central server that you must trust. Rather, the vision is of federated servers you don't have to trust.
 
 
-----
 
  
 
[[Vulnerabilities|Potential vulnerabilities]] of Open-Transactions
 
[[Vulnerabilities|Potential vulnerabilities]] of Open-Transactions
Line 116: Line 110:
  
 
[http://bitcoin.org/ Bitcoin] - A censorship-resistant global ledger
 
[http://bitcoin.org/ Bitcoin] - A censorship-resistant global ledger
 +
 +
[[Stash]] - Enterprise platform based on OT.
 +
 +
[[Monetas]] - Transaction platform inspired by OT.
  
 
[https://loom.cc/help Loom] - Asset issuance and transactions
 
[https://loom.cc/help Loom] - Asset issuance and transactions
Line 132: Line 130:
  
 
[https://ripple.com/ Ripple] - Consensus-based debt ledger
 
[https://ripple.com/ Ripple] - Consensus-based debt ledger
 +
 +
[https://www.stellar.org/ Stellar] - Ripple-based
  
 
[http://truledger.com/ Truledger] - Destruction of account history
 
[http://truledger.com/ Truledger] - Destruction of account history
Line 152: Line 152:
 
* It's like '''PGP FOR MONEY'''. The idea is to have many cash algorithms, not just Lucre. I’d like to add Chaum’s version, Brands’ version, etc. So that, just like PGP, the software should support as many of the top algorithms as possible, and make it easy to swap them out when necessary.
 
* It's like '''PGP FOR MONEY'''. The idea is to have many cash algorithms, not just Lucre. I’d like to add Chaum’s version, Brands’ version, etc. So that, just like PGP, the software should support as many of the top algorithms as possible, and make it easy to swap them out when necessary.
 
* User accounts are '''pseudonymous'''. '''A user account is a public key'''. (This is like [http://pktp.co.cc/ PKTP] by Andrew McMeikan.) You can open as many user accounts as you want. ''Full anonymity'' is possible only for "cash-only" transactions (where users only perform token exchanges, and do not open accounts), whereas ''pseudonymity'' means that transactions can be linked to the key that signed them. (While the real life identity of the owner is hidden, continuity of reputation becomes possible.) ''See full-color diagrams linked above''.
 
* User accounts are '''pseudonymous'''. '''A user account is a public key'''. (This is like [http://pktp.co.cc/ PKTP] by Andrew McMeikan.) You can open as many user accounts as you want. ''Full anonymity'' is possible only for "cash-only" transactions (where users only perform token exchanges, and do not open accounts), whereas ''pseudonymity'' means that transactions can be linked to the key that signed them. (While the real life identity of the owner is hidden, continuity of reputation becomes possible.) ''See full-color diagrams linked above''.
* '''Any user can issue new digital currencies''' and digital asset types, by uploading the new [currency contract] to the server. (This functionality is comparable to [http://www.systemics.com/docs/sox/overview.html Ricardo] by [http://financialcryptography.com/ Ian Grigg].)
+
* '''Any user can issue new digital currencies''' and digital asset types, by uploading the new [[Sample Currency Contract|currency contract]] to the server. (This functionality is comparable to [http://www.systemics.com/docs/sox/overview.html Ricardo] by [http://financialcryptography.com/ Ian Grigg].)
 
* '''Users can open asset accounts of any type.''' You can have as many as you want, associated with each user account. (See [http://loom.cc/ Loom] by Patrick Chkoreff.)
 
* '''Users can open asset accounts of any type.''' You can have as many as you want, associated with each user account. (See [http://loom.cc/ Loom] by Patrick Chkoreff.)
 
* [[Triple-Signed Receipts|Triple Signed Receipts / No Account History]]. On OT, entities are able to conduct transactions, verify instruments, ''and'' provably agree on current holdings via ''signed receipts'', all without the need to store any transaction history.'' An ''asset account'' on OT is not according to the traditional sense of the word (an account normally being thought of as, "a list of transactions, with a balance, used in double-entry bookkeeping.") While the word "account" makes things easy to understand, an ''asset account'' on OT exists only in the mind of the account holder himself. He simply asks the server to agree with him that it exists, and to provide him with a signed receipt to that effect. In the user interface, OT is able to mimic the ''account metaphor'', making usage intuitive, even though ''no actual account exists, or need be stored on either side, other than the signed receipt itself!'' (See Bill St. Clair's excellent [http://truledger.com/ Truledger] for an [http://truledger.com/doc/plain-english.html example of this concept].)
 
* [[Triple-Signed Receipts|Triple Signed Receipts / No Account History]]. On OT, entities are able to conduct transactions, verify instruments, ''and'' provably agree on current holdings via ''signed receipts'', all without the need to store any transaction history.'' An ''asset account'' on OT is not according to the traditional sense of the word (an account normally being thought of as, "a list of transactions, with a balance, used in double-entry bookkeeping.") While the word "account" makes things easy to understand, an ''asset account'' on OT exists only in the mind of the account holder himself. He simply asks the server to agree with him that it exists, and to provide him with a signed receipt to that effect. In the user interface, OT is able to mimic the ''account metaphor'', making usage intuitive, even though ''no actual account exists, or need be stored on either side, other than the signed receipt itself!'' (See Bill St. Clair's excellent [http://truledger.com/ Truledger] for an [http://truledger.com/doc/plain-english.html example of this concept].)

Latest revision as of 05:55, 5 December 2015