Difference between revisions of "Main Page"

From Open Transactions
Jump to navigation Jump to search
m (Documentation: clarification)
m (Documentation: re-arrange)
Line 24: Line 24:
  
 
* [http://opentransactions.org/docs/class_o_t_made_easy.html High-level API (all other languages)]
 
* [http://opentransactions.org/docs/class_o_t_made_easy.html High-level API (all other languages)]
 +
 +
The general rule of thumb is: Always prefer the high-level API.
 +
 +
(Only use the low-level functions in cases where no high-level function is available.)
  
 
* [http://opentransactions.org/docs/class_o_t_a_p_i___wrap.html Low-level API (C++)]
 
* [http://opentransactions.org/docs/class_o_t_a_p_i___wrap.html Low-level API (C++)]
  
 
* [http://opentransactions.org/docs/class_o_t_a_p_i___basic.html Low-level API (all other languages)]
 
* [http://opentransactions.org/docs/class_o_t_a_p_i___basic.html Low-level API (all other languages)]
 
The general rule of thumb is: Always prefer the high-level API.
 
 
(Only use the low-level functions in cases where no high-level function is available.)
 

Revision as of 21:04, 12 June 2013

Open-Transactions

The Open-Transactions project is a collaborative effort to develop a robust, commercial-grade, fully-featured, free-software toolkit implementing the OTX protocol as well as a full-strength financial cryptography library, API, CLI, and prototype server. The project is managed by a worldwide community of volunteers that use the Internet to communicate, plan, and develop the Open-Transactions toolkit and its related documentation.

Open-Transactions democratizes financial and monetary actions. You can use it for issuing currencies/stock, paying dividends, creating asset accounts, sending/receiving digital cash, writing/depositing cheques, cashier's cheques, creating basket currencies, trading on markets, scripting custom agreements, recurring payments, escrow, etc.

Open-Transactions uses strong crypto. The balances are unchangeable (even by a malicious server.) The receipts are destructible and redundant. The transactions are unforgeable. The cash is untraceable. The cheques are non-repudiable. Etc.

This product includes software developed by Ben Laurie for use in the Lucre project.

Source code

You can view the code on github.

Documentation

The general rule of thumb is: Always prefer the high-level API.

(Only use the low-level functions in cases where no high-level function is available.)