@ -231,7 +237,7 @@ When they fail, some of these functions return only a key-value `err_msg`.
* Returns: `err_msg: String`*OR*`retVal: String`
* Returns: `err_msg: String`*OR*`retVal: String`
**`decodeRct`**
**`decodeRct`, `decodeRctSimple`**
* Args: `i: UInt32String`, `sk: String`, `rv: DecodeRCT_RV` where
* Args: `i: UInt32String`, `sk: String`, `rv: DecodeRCT_RV` where
@ -263,6 +269,18 @@ Useful for displaying an estimated fee – To obtain exact fees, see "Creating a
* Returns: `retVal: UInt64String`
* Returns: `retVal: UInt64String`
**`estimate_rct_tx_size`**
* Args:
* `n_inputs: UInt32String`
* `mixin: UInt32String`
* `n_outputs: UInt32String`
* `extra_size: UInt32String`
* `bulletproof: BoolString`
* Returns: `retVal: UInt32String`
#### Creating and Sending Transactions
#### Creating and Sending Transactions
As mentioned, implementing the Send procedure without making use of one of our existing libraries or examples involves two bridge calls surrounded by server API calls, and mandatory reconstruction logic, and is simplified by various opportunities to pass values directly between the steps.
As mentioned, implementing the Send procedure without making use of one of our existing libraries or examples involves two bridge calls surrounded by server API calls, and mandatory reconstruction logic, and is simplified by various opportunities to pass values directly between the steps.