Raw transactions - Revision history

Pancyrus: Pancyrus moved page Raw Transactions to Raw transactions: It's not a proper noun, so it should be in sentence case.

2021-07-20T00:21:05Z

Pancyrus moved page Raw Transactions to Raw transactions: It's not a proper noun, so it should be in sentence case.

← Older revision		Revision as of 00:21, 20 July 2021
(No difference)

Belcher: /* See Also */ added coin analogy page link

2017-07-25T18:08:16Z

Posita: /* lockunspent unlock? [{"txid":txid,"vout":n},...] */

2014-06-02T20:21:20Z

lockunspent unlock? [{"txid":txid,"vout":n},...]

← Older revision		Revision as of 20:21, 2 June 2014
Line 7:		Line 7:
	Returns an array of unspent transaction outputs in the wallet that have between minconf and maxconf (inclusive) confirmations. Each output is a 5-element object with keys: txid, output, scriptPubKey, amount, confirmations. txid is the hexadecimal transaction id, output is which output of that transaction, scriptPubKey is the hexadecimal-encoded CScript for that output, amount is the value of that output and confirmations is the transaction's depth in the chain.		Returns an array of unspent transaction outputs in the wallet that have between minconf and maxconf (inclusive) confirmations. Each output is a 5-element object with keys: txid, output, scriptPubKey, amount, confirmations. txid is the hexadecimal transaction id, output is which output of that transaction, scriptPubKey is the hexadecimal-encoded CScript for that output, amount is the value of that output and confirmations is the transaction's depth in the chain.
	=== lockunspent unlock? [{"txid":txid,"vout":n},...] ===		=== lockunspent unlock? [{"txid":txid,"vout":n},...] ===
	Temporarily lock (~~true~~) or unlock (~~false~~) specified transaction outputs. A locked transaction output will not be chosen by automatic coin selection, when spending bitcoins. Locks are stored in memory only. Nodes start with zero locked outputs, and the locked output list is always cleared (by virtue of process exit) when a node stops or fails.		Temporarily lock (unlock=false) or unlock (unlock=true) specified transaction outputs. A locked transaction output will not be chosen by automatic coin selection, when spending bitcoins. Locks are stored in memory only. Nodes start with zero locked outputs, and the locked output list is always cleared (by virtue of process exit) when a node stops or fails.

	=== listlockunspent ===		=== listlockunspent ===

Jgarzik: /* lockunspent unlock? [{"txid":txid,"vout":n},...] */

2013-03-07T20:07:15Z

lockunspent unlock? [{"txid":txid,"vout":n},...]

← Older revision		Revision as of 20:07, 7 March 2013
Line 7:		Line 7:
	Returns an array of unspent transaction outputs in the wallet that have between minconf and maxconf (inclusive) confirmations. Each output is a 5-element object with keys: txid, output, scriptPubKey, amount, confirmations. txid is the hexadecimal transaction id, output is which output of that transaction, scriptPubKey is the hexadecimal-encoded CScript for that output, amount is the value of that output and confirmations is the transaction's depth in the chain.		Returns an array of unspent transaction outputs in the wallet that have between minconf and maxconf (inclusive) confirmations. Each output is a 5-element object with keys: txid, output, scriptPubKey, amount, confirmations. txid is the hexadecimal transaction id, output is which output of that transaction, scriptPubKey is the hexadecimal-encoded CScript for that output, amount is the value of that output and confirmations is the transaction's depth in the chain.
	=== lockunspent unlock? [{"txid":txid,"vout":n},...] ===		=== lockunspent unlock? [{"txid":txid,"vout":n},...] ===
	Temporarily ~~(until restart)~~ lock (true) or unlock (false) specified transaction outputs. A locked transaction output will not be chosen by automatic coin selection, when spending bitcoins.		Temporarily lock (true) or unlock (false) specified transaction outputs. A locked transaction output will not be chosen by automatic coin selection, when spending bitcoins. Locks are stored in memory only. Nodes start with zero locked outputs, and the locked output list is always cleared (by virtue of process exit) when a node stops or fails.

	=== listlockunspent ===		=== listlockunspent ===
	List all temporarily locked transaction outputs.		List all temporarily locked transaction outputs.

Jgarzik: /* JSON-RPC API */ add [list]lockunspent

2013-03-07T20:05:26Z

JSON-RPC API: add [list]lockunspent

← Older revision		Revision as of 20:05, 7 March 2013
Line 6:		Line 6:
	=== listunspent [minconf=1] [maxconf=999999] ===		=== listunspent [minconf=1] [maxconf=999999] ===
	Returns an array of unspent transaction outputs in the wallet that have between minconf and maxconf (inclusive) confirmations. Each output is a 5-element object with keys: txid, output, scriptPubKey, amount, confirmations. txid is the hexadecimal transaction id, output is which output of that transaction, scriptPubKey is the hexadecimal-encoded CScript for that output, amount is the value of that output and confirmations is the transaction's depth in the chain.		Returns an array of unspent transaction outputs in the wallet that have between minconf and maxconf (inclusive) confirmations. Each output is a 5-element object with keys: txid, output, scriptPubKey, amount, confirmations. txid is the hexadecimal transaction id, output is which output of that transaction, scriptPubKey is the hexadecimal-encoded CScript for that output, amount is the value of that output and confirmations is the transaction's depth in the chain.
			=== lockunspent unlock? [{"txid":txid,"vout":n},...] ===
			Temporarily (until restart) lock (true) or unlock (false) specified transaction outputs. A locked transaction output will not be chosen by automatic coin selection, when spending bitcoins.
			=== listlockunspent ===
			List all temporarily locked transaction outputs.
	=== createrawtransaction [{"txid":txid,"vout":n},...] {address:amount,...} ===		=== createrawtransaction [{"txid":txid,"vout":n},...] {address:amount,...} ===
	Create a transaction spending given inputs (array of objects containing transaction outputs to spend), sending to given address(es). Returns the hex-encoded transaction in a string. Note that the transaction's inputs are not signed, and it is not stored in the wallet or transmitted to the network.		Create a transaction spending given inputs (array of objects containing transaction outputs to spend), sending to given address(es). Returns the hex-encoded transaction in a string. Note that the transaction's inputs are not signed, and it is not stored in the wallet or transmitted to the network.

Smtp: /* Overview */

2013-01-05T19:48:42Z

Overview

← Older revision		Revision as of 19:48, 5 January 2013
Line 1:		Line 1:
	== Overview ==		== Overview ==

	The "raw transaction API" was introduced with Bitcoin-Qt/bitcoind version 0.7. It gives developers or very sophisticated end-users low-level access to transaction creation and broadcast.		The "raw transaction API" was introduced with [[Bitcoind# History of official bitcoind (and predecessor) releases \| Bitcoin-Qt/bitcoind version 0.7]]. It gives developers or very sophisticated end-users low-level access to transaction creation and broadcast.

	== JSON-RPC API ==		== JSON-RPC API ==

Kjj: Added example links

2012-11-21T18:23:47Z

Added example links

← Older revision		Revision as of 18:23, 21 November 2012
Line 68:		Line 68:

	* [[Original_Bitcoin_client/API_calls_list\|API calls list]]		* [[Original_Bitcoin_client/API_calls_list\|API calls list]]
			* https://people.xiph.org/~greg/signdemo.txt example of signing offline<BR>
			* https://people.xiph.org/~greg/escrowexample.txt example for escrow<BR>
			* https://gist.github.com/3966071 example for offline multisig (not supported as of 0.7.1)<BR>

	[[Category:Technical]]		[[Category:Technical]]
	[[Category:Developer]]		[[Category:Developer]]

Sgornick: Add See Also with an entry to the rest of the API.

2012-10-28T22:41:46Z

Add See Also with an entry to the rest of the API.

← Older revision		Revision as of 22:41, 28 October 2012
Line 64:		Line 64:
	=== Validate a transaction without broadcasting it ===		=== Validate a transaction without broadcasting it ===
	If you have a raw transaction and want to make sure all of its signatures are correct, you can use the signrawtransaction API call. Pass in the hex-encoded raw transaction, any inputs that bitcoind doesn't yet know about, and an empty array of private keys to use to sign the transaction. Passing an empty array of private keys will prevent signrawtransaction from doing any signing; if it returns "complete":1 then all of the existing signatures are valid and there are no signatures missing.		If you have a raw transaction and want to make sure all of its signatures are correct, you can use the signrawtransaction API call. Pass in the hex-encoded raw transaction, any inputs that bitcoind doesn't yet know about, and an empty array of private keys to use to sign the transaction. Passing an empty array of private keys will prevent signrawtransaction from doing any signing; if it returns "complete":1 then all of the existing signatures are valid and there are no signatures missing.

			==See Also==

			* [[Original_Bitcoin_client/API_calls_list\|API calls list]]

	[[Category:Technical]]		[[Category:Technical]]
	[[Category:Developer]]		[[Category:Developer]]

Gavinandresen at 11:17, 29 August 2012

2012-08-29T11:17:14Z

← Older revision		Revision as of 11:17, 29 August 2012
Line 6:		Line 6:
	=== listunspent [minconf=1] [maxconf=999999] ===		=== listunspent [minconf=1] [maxconf=999999] ===
	Returns an array of unspent transaction outputs in the wallet that have between minconf and maxconf (inclusive) confirmations. Each output is a 5-element object with keys: txid, output, scriptPubKey, amount, confirmations. txid is the hexadecimal transaction id, output is which output of that transaction, scriptPubKey is the hexadecimal-encoded CScript for that output, amount is the value of that output and confirmations is the transaction's depth in the chain.		Returns an array of unspent transaction outputs in the wallet that have between minconf and maxconf (inclusive) confirmations. Each output is a 5-element object with keys: txid, output, scriptPubKey, amount, confirmations. txid is the hexadecimal transaction id, output is which output of that transaction, scriptPubKey is the hexadecimal-encoded CScript for that output, amount is the value of that output and confirmations is the transaction's depth in the chain.
	=== createrawtransaction [{"txid":txid,"vout":n],...] {address:amount,...} ===		=== createrawtransaction [{"txid":txid,"vout":n},...] {address:amount,...} ===
	Create a transaction spending given inputs (array of objects containing transaction outputs to spend), sending to given address(es). Returns the hex-encoded transaction in a string. Note that the transaction's inputs are not signed, and it is not stored in the wallet or transmitted to the network.		Create a transaction spending given inputs (array of objects containing transaction outputs to spend), sending to given address(es). Returns the hex-encoded transaction in a string. Note that the transaction's inputs are not signed, and it is not stored in the wallet or transmitted to the network.

Tril: /* Validate a transaction without broadcasting it */ it's -> its

2012-08-27T06:04:10Z

Validate a transaction without broadcasting it: it's -> its

← Older revision		Revision as of 06:04, 27 August 2012
Line 63:		Line 63:

	=== Validate a transaction without broadcasting it ===		=== Validate a transaction without broadcasting it ===
	If you have a raw transaction and want to make sure all of ~~it's~~ signatures are correct, you can use the signrawtransaction API call. Pass in the hex-encoded raw transaction, any inputs that bitcoind doesn't yet know about, and an empty array of private keys to use to sign the transaction. Passing an empty array of private keys will prevent signrawtransaction from doing any signing; if it returns "complete":1 then all of the existing signatures are valid and there are no signatures missing.		If you have a raw transaction and want to make sure all of its signatures are correct, you can use the signrawtransaction API call. Pass in the hex-encoded raw transaction, any inputs that bitcoind doesn't yet know about, and an empty array of private keys to use to sign the transaction. Passing an empty array of private keys will prevent signrawtransaction from doing any signing; if it returns "complete":1 then all of the existing signatures are valid and there are no signatures missing.
	[[Category:Technical]]		[[Category:Technical]]
	[[Category:Developer]]		[[Category:Developer]]

← Older revision		Revision as of 18:08, 25 July 2017
Line 72:		Line 72:
	==See Also==		==See Also==

			* [[Coin analogy]]
	* [[Original_Bitcoin_client/API_calls_list\|API calls list]]		* [[Original_Bitcoin_client/API_calls_list\|API calls list]]
	* https://people.xiph.org/~greg/signdemo.txt example of signing offline<BR>		* https://people.xiph.org/~greg/signdemo.txt example of signing offline<BR>