Search results

Jump to navigation Jump to search

Create the page "OT Messages" on this wiki! See also the search results found.

  • Bailment
    [[Category:OT Messages]]
    25 bytes (3 words) - 08:20, 22 May 2014
  • Payment Protocol (voting pools)
    ...d arrive at the customer’s device through the OT inbox. At this point the OT client can validate the deposit address and signatures against the voting p ...>PaymentRequest</code> wrapper includes OT-specific values that enable the OT client to validate the deposit address as valid for the specified voting po
    2 KB (241 words) - 11:14, 23 May 2014
  • Notary (voting pools)
    The Notary must keep track of all blockchain-denominated balances via OT receipts. In addition to the separate account(s) for each customer, the ser ...the application account back to the the appropriate purchasing customer’s OT account. Any trade fees that the exchange earns would be sent to the servic
    2 KB (328 words) - 12:59, 12 November 2014
  • Auditor (voting pools)
    ...stream which carries regular OT transaction information also contains the OT receipts for Bitcoin withdrawal requests from the pool. The auditor initiat ...n server. It also tracks withdrawals from the time at which it receives an OT receipt, containing a withdrawal request, until the corresponding Bitcoin t
    2 KB (221 words) - 06:12, 8 October 2014
  • Messaging
    ...you can transport that string using whatever form of transport you wish. (OT operates on Request / Response model.) See this article on the [[OTX|OTX pr The OT Server, Test Client, and API were written using the OT Library. ''These'' pieces ''do'' implement transport, via a callback functi
    7 KB (1,083 words) - 23:40, 18 September 2013
  • Data models
    ...acceptance by the recipient.) The NYMBOX is a LEDGER. (Used for receiving MESSAGES and for receiving NEW TRANSACTION NUMBERS, which must be signed for.) Ledger objects are also used inside the OT messages, whenever you need to signal acceptance or rejection of specific transactio
    5 KB (900 words) - 13:53, 12 June 2013
  • OTX
    For using OT in your own application, see the [[API|article on the high-level API.]] For more details on how these messages work, see the [[Messaging|article on messaging.]]
    4 KB (528 words) - 05:23, 16 December 2015
  • Test Wallet commands
    ...is much more easy to use, and basically automates all of the complexity of OT. Whereas the low-level CLI described on this page, similar to the [[API | l ...The below notes are not relevant to you unless you plan on doing low-level OT work! Otherwise use the high-level command-line interface, [[Opentxs | open
    12 KB (2,069 words) - 16:11, 12 June 2013
  • Sample Currency Contract
    ...endezvous points may be described in the contract. Whenever the user sends messages to the entity listed on the contract, he has pretty good confidence that on ...ry. Most objects in the library are derived, somehow, from OTContract. The messages are contracts. The datafiles are contracts. The ledgers are contracts. The
    10 KB (1,556 words) - 17:02, 11 June 2013
  • Voting Pool Withdrawal Process
    ...hen the service receives such a request, it notifies the OT client via the OT client API function: <code>[[outBailment]]</code>. When the OT client receives notice of a user desire to withdraw funds from a voting poo
    6 KB (987 words) - 16:11, 29 September 2014
  • Low level Use Cases
    '''SERVER MESSAGES''' ...c and everything works perfectly. But if the number goes out of sync, your messages will all fail! Just call <code>OT_API_getRequest()</code> to put it back in
    24 KB (3,836 words) - 16:47, 12 June 2013
  • About
    ...ublic keys), each of which may own ''asset accounts'' of various types, on OT servers. * '''Even an OT server cannot change balances, or forge transactions--since it cannot forge
    15 KB (2,168 words) - 05:55, 5 December 2015
  • List of Classes
    ...API,'' as used from C++. Used for sending messages back and forth with an OT server. ...ts of request numbers and transaction numbers for that identity on various OT servers. A pseudonym may own many asset accounts.
    20 KB (3,232 words) - 23:41, 18 September 2013
  • Triple-Signed Receipts
    Here's how OT solves this problem: All transactions must be accompanied by a valid transa ...because cheque 7 has cleared, does ''not'' mean that 5 and 6 have cleared! OT thus does ''not'' have the same guarantee of sequential processing that Tru
    15 KB (2,501 words) - 17:35, 11 June 2013
  • Release Notes
    See Open-Transactions/scripts/util/adjust_usage.ot 0.84a--- OT now creates ALL data files it needs.
    26 KB (3,847 words) - 13:10, 12 June 2013
  • API
    ...high-level API version is available. If you are writing software that uses OT, and you need to copy some sample code, just get it from [https://github.co * OT's high-level API is also available in OT [https://github.com/FellowTraveler/Open-Transactions/wiki/Client-side-scrip
    35 KB (4,910 words) - 22:53, 8 July 2015
  • Use Cases
    ...numbers, or comparing inbox hashes, or downloading your nymbox, or dropped messages, or timeouts, or retries, etc! Instead, you use simple functions like '''se '''USE CASES for the OT API, described on this page:'''
    34 KB (4,780 words) - 22:47, 8 July 2015
  • FAQ
    ...fers, payment plans, markets with trades, etc. ([http://billstclair.com/ot/OT-Pseudonym-Instruments.jpg See the diagram]) ...r.com/ot/OT-Anon-CashOnly.jpg diagram] of the fully-anonymous operation of OT.
    44 KB (7,441 words) - 01:04, 16 January 2016
  • Transactions
    If you haven't first read the [[Messaging|article on basic messages,]] start there. (It continues to this article.) As you can see, the ledger above is just another contract. In OT, you can have contracts nested inside contracts. Inside this ledger you can
    26 KB (4,160 words) - 23:41, 18 September 2013
Retrieved from "http://opentransactions.org/wiki/Special:Search"