Cryptonite API - Revision history

Admin: added info on recent rpc changes

2014-09-03T11:39:35Z

added info on recent rpc changes

← Older revision		Revision as of 11:39, 3 September 2014
Line 15:		Line 15:
	* sendtoaddress,sendmany,sendfrom - The two comment fields have been replaced by a single message field that is actually included in the transaction		* sendtoaddress,sendmany,sendfrom - The two comment fields have been replaced by a single message field that is actually included in the transaction
	* signrawtransaction - Extra parameters allowed to help with signing of partially unsigned multisignature addresses		* signrawtransaction - Extra parameters allowed to help with signing of partially unsigned multisignature addresses
			* createrawtransaction - Added an optional parameter after all other arguments, used for setting message field like sendtoaddress
			* setaccount - Added an optional parameter after all other arguments, used to disable the automatic generation of new addresses

	===Restricted commands:===		===Restricted commands:===

Admin: changed coin value to 10 dec places

2014-07-25T03:58:54Z

changed coin value to 10 dec places

← Older revision		Revision as of 03:58, 25 July 2014
Line 32:		Line 32:
	Since Cryptonite uses 64-bit's worth of coin units, it is not safe to treat amounts as double precision floating point values unless they are smaller than about 32 million XCN. To prevent old code designed for use with bitcoin daemon from trying to parse Cryptonite amounts, all RPC calls use strings to represent amounts. We call this encoding the extended-precision encoding, or EP for short.		Since Cryptonite uses 64-bit's worth of coin units, it is not safe to treat amounts as double precision floating point values unless they are smaller than about 32 million XCN. To prevent old code designed for use with bitcoin daemon from trying to parse Cryptonite amounts, all RPC calls use strings to represent amounts. We call this encoding the extended-precision encoding, or EP for short.

	EP numbers are strings in JSON, and must always have 8 digits after the decimal point followed by "ep". An example of a valid RPC command using an ep number would be:		EP numbers are strings in JSON, and must always have 10 digits after the decimal point followed by "ep". An example of a valid RPC command using an ep number would be:
	<pre>./cryptonited sendtoaddress mvqH4czVQg2HdGpkV7PWVZJpRXVwLnMXpN "0.~~01000000ep~~"</pre>		<pre>./cryptonited sendtoaddress mvqH4czVQg2HdGpkV7PWVZJpRXVwLnMXpN "0.0100000000ep"</pre>

	All amounts returned in RPC results are also EP numbers, and you must take care to parse them, do not use floating point to represent them unless you are really sure of what you are doing.		All amounts returned in RPC results are also EP numbers, and you must take care to parse them, do not use floating point to represent them unless you are really sure of what you are doing.

Admin: small formatting fix

2014-07-24T15:10:17Z

small formatting fix

← Older revision		Revision as of 15:10, 24 July 2014
Line 1:		Line 1:
	__TOC__		__TOC__

	The [[Cryptonite]] API is similar to the [https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list Bitcoin API], containing a few additions and subtractions, some changed arguments, and some use restrictions. Almost all commands returning anything more than a hash will return different JSON objects as compared to bitcoin.		The [[Cryptonite]] API is similar to the [https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list Bitcoin API], containing a few additions and subtractions, some changed arguments, and some use restrictions. Almost all commands returning anything more than a hash will return different JSON objects as compared to bitcoin. You can use the help command to get more information about any command.

	===New commands:===		===New commands:===
Line 7:		Line 7:
	* addmultisigaddress - Generates a multisig destination address from a list of signers		* addmultisigaddress - Generates a multisig destination address from a list of signers
	* getblockheader - Gets header component of block only		* getblockheader - Gets header component of block only
	* setlimit - set withdrawal limit for an address		* setlimit - set [[Withdrawal_limits \| withdrawal limit]] for an address

	===Modified commands:===		===Modified commands:===
Line 28:		Line 28:
	* listlockedunspent		* listlockedunspent

	~~You can use the help command to get more information about any command.~~		==A note about EP amounts==

	==A note about EP amounts:==

	Since Cryptonite uses 64-bit's worth of coin units, it is not safe to treat amounts as double precision floating point values unless they are smaller than about 32 million XCN. To prevent old code designed for use with bitcoin daemon from trying to parse Cryptonite amounts, all RPC calls use strings to represent amounts. We call this encoding the extended-precision encoding, or EP for short.		Since Cryptonite uses 64-bit's worth of coin units, it is not safe to treat amounts as double precision floating point values unless they are smaller than about 32 million XCN. To prevent old code designed for use with bitcoin daemon from trying to parse Cryptonite amounts, all RPC calls use strings to represent amounts. We call this encoding the extended-precision encoding, or EP for short.

Admin: small visual fix

2014-07-20T17:37:46Z

small visual fix

← Older revision		Revision as of 17:37, 20 July 2014
Line 34:		Line 34:
	Since Cryptonite uses 64-bit's worth of coin units, it is not safe to treat amounts as double precision floating point values unless they are smaller than about 32 million XCN. To prevent old code designed for use with bitcoin daemon from trying to parse Cryptonite amounts, all RPC calls use strings to represent amounts. We call this encoding the extended-precision encoding, or EP for short.		Since Cryptonite uses 64-bit's worth of coin units, it is not safe to treat amounts as double precision floating point values unless they are smaller than about 32 million XCN. To prevent old code designed for use with bitcoin daemon from trying to parse Cryptonite amounts, all RPC calls use strings to represent amounts. We call this encoding the extended-precision encoding, or EP for short.

	EP numbers are strings in JSON, and must always have 8 digits after the decimal point followed by "ep". An example of a valid RPC command using an ep number would be:~~<br><br>~~		EP numbers are strings in JSON, and must always have 8 digits after the decimal point followed by "ep". An example of a valid RPC command using an ep number would be:
	<~~code~~>./cryptonited sendtoaddress mvqH4czVQg2HdGpkV7PWVZJpRXVwLnMXpN "0.01000000ep"</~~code~~>		<pre>./cryptonited sendtoaddress mvqH4czVQg2HdGpkV7PWVZJpRXVwLnMXpN "0.01000000ep"</pre>

	All amounts returned in RPC results are also EP numbers, and you must take care to parse them, do not use floating point to represent them unless you are really sure of what you are doing.		All amounts returned in RPC results are also EP numbers, and you must take care to parse them, do not use floating point to represent them unless you are really sure of what you are doing.

Admin: added stuff from catia

2014-07-20T17:35:56Z

added stuff from catia

@@ Line 1: / Line 1: @@
-The [[Cryptonite]] API call list is essentially the same as the [https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list Bitcoin API call list] with a few small changes.
+__TOC__
-listunspent is now listbalances and we have a new command: setlimit<br>
+The [[Cryptonite]] API is similar to the [https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list Bitcoin API], containing a few additions and subtractions, some changed arguments, and some use restrictions. Almost all commands returning anything more than a hash will return different JSON objects as compared to bitcoin.
-The following API commands have been removed:<br>
+===New commands:===
-All coin values should include all 8 decimal places, end with ep, and be encapsulated in quotes like so:<br>
+* addmultisigaddress - Generates a multisig destination address from a list of signers
 <code>./cryptonited sendtoaddress mvqH4czVQg2HdGpkV7PWVZJpRXVwLnMXpN "0.01000000ep"</code>

Admin: Added page to wiki

2014-07-16T06:31:10Z

Added page to wiki

New page

The [[Cryptonite]] API call list is essentially the same as the [https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list Bitcoin API call list] with a few small changes.

listunspent is now listbalances and we have a new command: setlimit<br>
You can use the help command to get information about setlimit or anything else.

The following API commands have been removed:<br>
getrawchangeaddress,decodescript,lockunspent,listlockedunspent

All coin values should include all 8 decimal places, end with ep, and be encapsulated in quotes like so:<br>
<code>./cryptonited sendtoaddress mvqH4czVQg2HdGpkV7PWVZJpRXVwLnMXpN "0.01000000ep"</code>