Transactions - Revision history

FellowTraveler: unlinkable

2013-09-18T23:41:19Z

unlinkable

FellowTraveler: fixed smart contract link

2013-06-17T07:57:11Z

fixed smart contract link

FellowTraveler: minor fix

2013-06-17T07:55:36Z

minor fix

FellowTraveler: added link to messaging article

2013-06-17T07:54:47Z

added link to messaging article

FellowTraveler: formatting

2013-06-15T10:49:37Z

formatting

FellowTraveler: fixed contract link

2013-06-15T10:48:04Z

fixed contract link

FellowTraveler: fixed purse link

2013-06-15T10:46:53Z

fixed purse link

Cryptoman at 22:41, 10 June 2013

2013-06-10T22:41:14Z

Cryptoman at 22:40, 10 June 2013

2013-06-10T22:40:24Z

Cryptoman at 22:36, 10 June 2013

2013-06-10T22:36:47Z

@@ Line 234: / Line 234: @@
 '''Every transaction request must include a transaction number, and you may only use one that has been issued to you by the server.'''
-Some instruments may be written and signed offline, which means you will want to have a supply of transaction numbers in your wallet, in case you want to write a cheque or sign a payment plan, or whatever. (NOTE: these transaction numbers ''cannot'' be used to trace the digital cash transactions, since the cash tokens themselves are untraceable, and cannot be linked from withdrawal back to deposit again. But the withdrawal and deposit _will_ each have a transaction number attached to each message. This in no way violates the untraceability of the cash, FYI. That is, just because you used transaction#5 to withdraw some tokens, and just because I used transaction#9 to deposit those tokens, the tokens themselves are still untraceable, and the server still has no idea whether I got them from you.)
+Some instruments may be written and signed offline, which means you will want to have a supply of transaction numbers in your wallet, in case you want to write a cheque or sign a payment plan, or whatever. (NOTE: these transaction numbers ''cannot'' be used to trace the digital cash transactions, since the cash tokens themselves are unlinkable, and cannot be linked from withdrawal back to deposit again. But the withdrawal and deposit _will_ each have a transaction number attached to each message. This in no way violates the untraceability of the cash, FYI. That is, just because you used transaction#5 to withdraw some tokens, and just because I used transaction#9 to deposit those tokens, the tokens themselves are still unlinkable, and the server still has no idea whether I got them from you.)
 Transaction numbers are important because they are what make it possible to prove all balances and all closed transactions, ''without'' all parties being forced to store their entire transaction history forever. Instead, parties can prove their position in any dispute, simply by saving the ''last signed receipt.'' Nifty, eh? [[Triple-Signed Receipts | Read more about this]]
@@ Line 406: / Line 406: @@
 Later, a copy of the above transaction item will be included by the server as part of my withdrawal receipt.
-So... the above withdrawal item has an attachment on it -- what is it?  It’s an '''''OTPurse''''', containing the actual prototokens for the cash withdrawal. (The wallet must ''blind'' the tokens before sending them to the server, so that the server won't know their IDs when they are signed... that's how they stay untraceable: their token IDs are only unblinded after being returned to the user's wallet.)
+So... the above withdrawal item has an attachment on it -- what is it?  It’s an '''''OTPurse''''', containing the actual prototokens for the cash withdrawal. (The wallet must ''blind'' the tokens before sending them to the server, so that the server won't know their IDs when they are signed... that's how they stay unlinkable: their token IDs are only unblinded after being returned to the user's wallet.)
 In this case, only a single prototoken was necessary for this withdrawal, as you can see if you look inside the purse:
@@ Line 465: / Line 465: @@
 If you want to write a cheque for a strange amount, such as 1291, or 87622, it's no problem.
-But with ''cash'', the cash tokens come in specific denominations, such as 1, 5, 10, etc. (it's a part of what makes them untraceable. Exact denominations to be configurable in each [[Sample Currency Contract|currency contract]].)  Due to this, *you do not handle tokens directly, but instead, _purses full of tokens_.* This way you can have a purse worth 1291, or 87622, or any amount you wish.  That's why all messages involving cash use an OTPurse.
+But with ''cash'', the cash tokens come in specific denominations, such as 1, 5, 10, etc. (it's a part of what makes them unlinkable. Exact denominations to be configurable in each [[Sample Currency Contract|currency contract]].)  Due to this, *you do not handle tokens directly, but instead, _purses full of tokens_.* This way you can have a purse worth 1291, or 87622, or any amount you wish.  That's why all messages involving cash use an OTPurse.
 The token in the purse above cannot be base64-decoded since it was actually encrypted before it was encoded. (Tokens are stored in encrypted form.) As long as you have the right nym loaded, you can use 'opentxs decrypt' at the command line in order to view most encrypted contents. (They might be in binary form, depending on which OT data you are actually decrypting.)

@@ Line 472: / Line 472: @@
 [[Sample Purse | To see another sample purse, click here]].<br>
 [[Sample Mint | To read about the OTMint object, click here]].<br>
-[https://github.com/FellowTraveler/Open-Transactions/wiki/Smart-contracts To read about smart contracts, click here]<br>
+[[Smart contracts | To read about smart contracts, click here]]<br>
-[[Messaging | To go back to the basic article on OTMessage page]].<br>
+[[Messaging | To go back to the basic article on OTMessage, click here]].<br>

@@ Line 473: / Line 473: @@
 [[Sample Mint | To read about the OTMint object, click here]].<br>
 [https://github.com/FellowTraveler/Open-Transactions/wiki/Smart-contracts To read about smart contracts, click here]<br>
-[[Messaging | To go back to the OTMessage page, click here]].<br>
+[[Messaging | To go back to the basic article on OTMessage page]].<br>

← Older revision		Revision as of 07:54, 17 June 2013
Line 1:		Line 1:
		+	If you haven't first read the [[Messaging\|article on basic messages,]] start there. (It continues to this article.)
		+
	Let’s say I want to withdraw some cash. In that case, my OTMessage will have an ''OTLedger'' attached to it.		Let’s say I want to withdraw some cash. In that case, my OTMessage will have an ''OTLedger'' attached to it.

@@ Line 234: / Line 234: @@
 Some instruments may be written and signed offline, which means you will want to have a supply of transaction numbers in your wallet, in case you want to write a cheque or sign a payment plan, or whatever. (NOTE: these transaction numbers ''cannot'' be used to trace the digital cash transactions, since the cash tokens themselves are untraceable, and cannot be linked from withdrawal back to deposit again. But the withdrawal and deposit _will_ each have a transaction number attached to each message. This in no way violates the untraceability of the cash, FYI. That is, just because you used transaction#5 to withdraw some tokens, and just because I used transaction#9 to deposit those tokens, the tokens themselves are still untraceable, and the server still has no idea whether I got them from you.)
-'''Transaction numbers are important because they are what make it possible to prove all balances and all closed transactions, _without_ all parties being forced to store their entire transaction history forever. Instead, parties can prove their position in any dispute, simply by saving the _last signed receipt_.* Nifty, eh? [[Triple-Signed-Receipts | Read more about this]]
+Transaction numbers are important because they are what make it possible to prove all balances and all closed transactions, ''without'' all parties being forced to store their entire transaction history forever. Instead, parties can prove their position in any dispute, simply by saving the ''last signed receipt.'' Nifty, eh? [[Triple-Signed Receipts | Read more about this]]
 Here's the transaction:

@@ Line 467: / Line 467: @@
 The token in the purse above cannot be base64-decoded since it was actually encrypted before it was encoded. (Tokens are stored in encrypted form.) As long as you have the right nym loaded, you can use 'opentxs decrypt' at the command line in order to view most encrypted contents. (They might be in binary form, depending on which OT data you are actually decrypting.)
-[[To continue reading about cash tokens, click here|Sample Cash]].
+[[Sample Cash | To continue reading about cash tokens, click here]].
-[[To see another sample purse, click here|Sample purse]].
+[[Sample purse | To see another sample purse, click here]].
-[[To read about the OTMint object, click here|Sample Mint]].
+[[Sample Mint | To read about the OTMint object, click here]].
-"To read about smart contracts, click here":https://github.com/FellowTraveler/Open-Transactions/wiki/Smart-contracts
+[https://github.com/FellowTraveler/Open-Transactions/wiki/Smart-contracts To read about smart contracts, click here]
-[[To go back to the OTMessage page, click here|Messaging]].
+[[Messaging | To go back to the OTMessage page, click here]].