This article is for Operators only.
Concurrent transaction approval
It's possible to create multiple transaction requests in an account. Transactions are broadcasted only when all approvals have been collected from the necessary Operators. They can be approved in any order.
To allow this, two different balances will be displayed in the account:
- the total balance: the account's total balance at a given time.
- the available balance: the account's balance minus the total amount of pending transaction requests and the expected max fees. Put simply, this is the amount you can spend in your next transactions.
The available balance is calculated differently depending on the crypto asset.
|Crypto asset||Available balance|
Bitcoin and Bitcoin-like
Account total balance - (total pending transaction amounts + pending max fees in the account)
|Ethereum accounts that don't have children ERC20 accounts|
|Ethereum accounts that have children ERC20 accounts||
Account total balance - (total pending transaction amounts + pending max fees in the account + pending max fees in all children ERC20 accounts)
Account total balance - the account's total pending transactions
Transaction fees & speed
When creating a transaction, you first need to select a transaction speed: slow, medium (default), or fast. The selected speed will determine the total transaction fees.
At this stage, the exact amount is unknown as multiple factors must be taken into account such as the crypto asset, the size of the transaction, and the state of the network. For this reason, only the total max fees is displayed when creating transaction requests. That is the highest amount you will pay for the transaction to be approved. The fee can be lower but will never go above that amount.
The estimated total max fees are calculated when creating the transaction request and is calculated differently depending on the crypto asset. The final fees are calculated once the transaction is approved by the last Operator.
|speed||Network fees||Max fees|
|Slow||Fees to confirm in 6 blocks||+ 50%|
|Medium||Fees to confirm in 3 blocks||+ 50%|
|Fast||Fees to confirm in 1 blocks||+ 50%|
|speed||Network fees||Max fees|
|Slow||Fee amount when creating the transaction request - 25%||+ 50%|
|Medium||Fee amount when creating the transaction request||+ 50%|
|Fast||Fee amount when creating the transaction request + 25%||+ 50%|
Refer to the XRP ledger for additional information.
|speed||Network fees||Max fees|
|Slow||10 drops||+ 50%|
|Medium||10 drops + load cost||+ 50%|
|Fast||10 drops + (load cost + open ledger cost) *1.5||+ 50%|
It's possible to define the max fee you're willing to pay if you don't want to spend over a specific amount. You can do this by enabling the Custom toggle. Note that if the entered amount is too low, the transaction will take longer to confirm.
Once the last approval of the transaction request is collected, the transaction is created and immediately broadcasted. At that moment, the fees are calculated again and compared to the max fees. If the recalculated fees:
- are below than the total max fees, the transaction is broadcasted with the recalculated fees. The difference between the max fees and the actual fees are therefore available again for use in your account.
- are above the total max fees, the transaction is broadcasted with the max fees. You'll never pay more than the amount indicated when creating the request. Note that our calculation method is made to prevent this case from happening.
In case of issues, we will automatically retry to send the transaction three times. If it still fails, the transaction will the Failed to broadcast status.
In Bitcoin and Bitcoin-like blockchains, transactions are made of inputs and outputs:
- The output represents the amount sent to the recipient, and
- The input is the change that goes back in your wallet and that can be reused in another transaction.
Example: You would like to make an $8 transaction but you only have a $10 bill. You'll use this bill to pay and receive $2 in change.
UTXOs are therefore the collection of all the change (or input) that exist in the account and which, added together, equals to the total balance.
- We recommend consolidating UTXOs:
- When no transaction requests are pending in the account.
- When no transactions are supposed to be received in the account.
- We also recommend :
- Approving UTXO transaction requests as soon as possible after creation.
- Creating a single UTXO transaction request at a time and approving it before creating a new one.
When consolidating UTXOs, you aggregate the value of multiple UTXOs into one. You can see this as exchanging coins for a bill. This allows you to send larger amounts creating transactions and enables you to save money if you consolidate when network fees are low.
You can consolidate up to 100 UTXOs at a time by creating a transaction to yourself. UTXOs which have the smallest amounts will be selected. However, UTXOs which value falls below 546 satoshis are too small to be consolidated and will be ignored.
If your account contains over 100 UTXOs you'll be required to perform the consolidation multiple times. For more information, see Consolidate UTXOs.
The consolidation is always performed on the index 0 address of the account, that is the first-ever generated address in your account.
If the account for which you want to consolidate UTXOs uses whitelists only, make sure an Administrator either adds the address index 0 of that account to one the whitelists or creates a separate rule for this address. This is to ensure you can consolidate UTXOs in the account.
When creating a transaction you can select which UTXOs should be used among these three options:
- Merge outputs: To select UTXOs which have the lowest amounts. This strategy is used by default.
- Optimize size: To select UTXOs which have the highest amounts.
- Deep outputs first: To select UTXOs which have the highest amount of confirmations on the blockchain.
Transaction rules can vary from an account to the other. It'll affect how you create transactions as the amount per transaction can be limited as well as the possible list of allowed recipients. Additionally, a different approval workflow can be implemented.
To find out which rules have been defined in an account, go to Accounts > Account dashboard > and open the Rules section.
- The parent Ethereum account must be credited to allow paying the gas fees of ERC20 transactions.
- You're required to hold a minimum balance of XRP 20 at all time. You'll be prevented from creating a transaction if your account's total balance falls below that amount.
Transactions below XRP 20 sent to inactive XRP accounts aren't permitted by the network and will fail.
- You're required to hold a minimum balance of XLM 1 at all time. You'll be prevented from creating a transaction if your account's total balance falls below that amount.