Use this to get information about a user (AuthenticationInput or API key must be provided)

Get the partial pin challenge for the a user.

Submit the partial pin and if successful return the authentication tokens

Refresh the authentication tokens

Get the updated status of the transaction that has already been submitted (AuthenticationInput or API key must be provided)

Retrieves the request item associated with the given requestId (AuthenticationInput or API key must be provided)

Retrieve the transaction count for address and chainId as TrustVault sees it. Takes into account queued transactions. Contact Support to enable

Retrieves a list of all active vasps

create a subWallet for a given wallet

create an Ethereum Transaction specifying only the minimal attributes of the transaction and send the transaction to the TrustVault authorised signer(s) inbox for signing. Use the requestId to query the status of the transaction later.

create a Bitcoin Transaction specifying only the minimal attributes of the transaction and send the transaction to the TrustVault authorised signer(s) inbox for signing. Use the requestId to query the status of the transaction later. NOTE: returns null if an error occurred

create a change policy request of a wallet(s) (available via API key authentication only)

add public key & signature pairs for the given requestId (available via API key authentication only)

cancel the request item associated with the given requestId, optionally pass a reason for cancelling

Create a request to sign a given message using the private key of the given ethereum address

Create a request to sign with eth_signTypedData a message using the private key of the given ethereum address

Add new entry to address book

Users transactions in csv string, csv will be sent to a registered email, optionally can pass asset and walletId

Organisation audit log as csv string, csv will be sent to the registered email

Lightweight version of createEthereumTransaction which takes a raw transaction and its set of pre-signed signRequests. Returned is the signed rawTransactionBytes.

EIP1559 transactions

EIP2930 Transactions

Travel rule

Unique identifier for the address

asset if the address book references a known asset

Chain address

Chain the address belongs to

Name of the address

Label (optional)

Memo (optional), only supported for some chains

Information of the counterparty that should be used for travel rule if a transaction contains the address of interest (NOTE: only applicable if type contains TRAVEL_RULE)

Array with all the Address Book items

nextToken for pagination. Not used for now.

Whitelist flag

The current page of Address objects. This can be an empty array if there are no items on this page - (null for exchange wallets)

The token to use to get the next page of Address objects. If items is an empty array then this value should be null

Do not use for transactions, instead derive the address from the public key after verifying it with the trustVaultProvenanceSignature (null for exchange subWallets)

The sub-wallet's public key

The HD wallet path of the sub-wallet

The trustvault signature over SHA-256(DER(publicKey + path + walletId))

Bitcoin address type (only available on Bitcoin subWallets)

Big decimal in string format

could be the asset symbol or fiat currency

Timestamp represents how stale the data is NOTE: timestamp is either the timestamp when the amount of the asset is queried or if converted from another currency the timestamp of the convertion rate used

convert the value to another currency NOTE: currently only supports asset -> fiat / assets -> assets

The ticker symbol used to uniquely identify this asset within our systems. This will often match the publicly used ticker symbol, but may diverge where there are multiple matching assets.

The name of the asset

The location of a standardised icon for this asset

The asset type

The chain the asset belongs to (ETHEREUM / BITCOIN)

The ISO date that this asset was added to the catalog

The maximum number of decimal place for the asset

Public ticker symbol

The contract address of the asset (i.e. ERC20 tokens)

The email who will receive the auditLog

A unique identifier for this request

returns a list of all supported chains and information about them (only Ethereum supported for now)

returns the information about the chain requested, for EVM pass chain: ETHEREUM chainId: 0x12 if supported

Encrypted blob 3 tokens

Asset object

Amount of the asset - optional conversion in the currency given

The available to spend net of any fees (Support on certain exchanges only)

The current page of Asset objects. This can be an empty array if there are no items on this page - (null for exchange wallets)

The token to use to get the next page of Wallet objects. If items is an empty array then this value should be null

Unique identifier for the address.

The type (e.g. COMPATIBILITY) of the address generated as displayed in the 'id' field

The address usage type (e.g. CHANGE or RECEIVE)

Transactions were received into the given bitcoin address.

The address of the UTXO

The hash of the transaction that generated the UTXO

The specific output in the referenced transaction id above

public key + signature over the hash of the transaction

Indicates if the transaction is final. Max value indicates finality (0xFFFFFFFF)

The amount of satoshi in the UTXO

The provenance signature data for the address of the utxo

IMPORTANT: This should only be used to verify that the digest you created from the transaction input is correct. NEVER sign this digest without verifying!

The address of the transaction recipient

The amount of satoshi to be sent

The provenance signature data for the change address. (Only the change output will have it)

The sub-wallet's public key

The HD wallet path of the sub-wallet

The trustvault signature over SHA-256(DER(publicKey + path + walletId))

Do not use for transactions, instead derive the address from the public key after verifying it with the trustVaultProvenanceSignature

Bitcoin address type

The raw bitcoin transaction

The provenance signature data for the change address

The UTXOs to be spent

The recipient(s) of the transaction - including the change address

Block height or timestamp when transaction is final

The signature type for the transaction

Wallet Information for this SubWallet

Convenience property showing the current address. For enhanced security, generate on the address on the client from the subWallet public key after verifying the signature

name of the subWallet

Creation time stamp (ISO 8601 UTC time)

Modified time stamp (ISO 8601 UTC time)

Wallet Type

The public key of the subWallet - used to generate the address on the client side

The chain of the subWallet

The TrustVault signature over the public key

Bitcoin Addresses associated with this subWallet, addressType defaults to RECEIVE

Transaction connection

assetId: NATIVE, or contract address chainId: For EVM only, specify hex

List of token assets with balances associated with the subWallet (ETH + ERC20 if Ethereum else BTC on Bitcoin) NOTE: pagination is not implemented yet - limit and nextToken are currently ignored

⚠️ DEPRECATED

use balance field

The total value of all the tokens associated with the subWallet

The exchange the transaction is sent from

The exchange the transaction is sent to

The amount of the transferred asset

Status of the transaction

Timestamp the transaction was created at (ISO 8601 UTC date time):

Timestamp the transaction was last updated (ISO 8601 UTC date time):

The transaction cost paid to the network for processing the transaction

the unique identifier of the transaction

the direction the transaction was sent

Chain specific raw transaction

the name of the chain (ETHEREUM, BITCOIN, etc..)

the native token symbol belonging to the chain (ETH, BTC, BNB, etc...)

the fee price at a specific speed (FAST, MEDIUM, SLOW are supported on all chains)

all the possible feePrices for a given chain (a minimum of 3 items)

The amount in wei that was transferred in the transaction (hex string)

The address for which the transaction is destined

The address for which the transaction is destined

The height of the block where this transaction is in

The r value of the ECDSA signature

The s value of the ECDSA signature

The index position of the transaction in the block. (hex string - null when its pending)

The recovery id

The gas limit of the transaction (hex string)

The gas price per unit of gas of the transaction in wei (hex string)

The number of transactions made by the sender prior to this one (hex string)

The decoded input data sent along with the transaction

The decoded event logs of the transaction (could be empty if there are no events, unsupported events is not included)

Unique identifier for the change policy request

The policy change that describe the new delegate/recoverer schedules

The TrustVault signature over the recoverer schedule. Use this to verify the recoverer schedule did indeed came from TrustVault

Unique identifier for the wallet to which the change policy is going to be applied to

IMPORTANT: This digest data should only be used to verify that the digest you created from the policyTemplate is correct. NEVER sign this digest without verifying!

The list of change policy requests created

An array of all tokens

Pagination token

token information

The addresses that manage the contract

The transaction data to be signed

Bitcoin rate in desired currency

The transaction fee in satoshi

The max allowed to send in satoshi

The fee for the max send amount in satoshi

The current balance of the wallet in satoshi

Unique identifier for the transaction request

The transaction data to be signed

Bitcoin rate in desired currency

The transaction fee in satoshi

The max allowed to send in satoshi

The fee for the max send amount in satoshi

The current balance of the wallet in satoshi

The unique identifier for the ethereum personal sign request (null if sendToDevicesForSigning is false)

The details of message data to be signed

The unique identifier for the ethereum personal sign request (null if sendToDevicesForSigning is false)

The details of message data to be signed

Data needed to sign a transaction

Ethereum rate in desired currency

Token rate in desired currency

The unique identifier for the ethereum transaction request

Data needed to sign a transaction

Ethereum rate in desired currency

Token rate in desired currency

Data needed to sign a transaction

Raw transaction bytes of signed transaction

The unique identifier for the ethereum transaction request

Data needed to sign a transaction

Ethereum rate in desired currency

Token rate in desired currency

NOTE: deprecated by trustVaultTransactionId

The Trustvault transaction id

Unique id for the subWallet

The receive address details of the newly created subWallet

The unique identifier for the ethereum transaction request

Data needed to sign a transaction

Ethereum rate in desired currency

Token rate in desired currency

The digest of the message input

The DER encoded transaction digest and the wallet path

The SHA3-256 digest of the signData

Hex - From address

Hex - To address

Hex - The value of ETH to send with this transaction

Hex - The chainId e.g. 1 for mainnet or 17000 for Holesky

Hex - The number of transactions a user has already sent (plus 1 for this transaction)

Hex - Limit of gas used for the transaction execution (wei)

Hex - compiled contract code for the transaction

Hex - Maximum fee per gas (wei)

Hex - Maximum priority fee per gas (wei)

Access list

The r value of the signature (optional as it will not exist if tx is not signed)

The s value of the signature (optional as it will not exist if tx is not signed)

The recovery Id of the Ethereum chain (optional as it will not exist if tx is not signed)

Hex - From address

Hex - To address

Hex - The value of ETH to send with this transaction

Hex - The chainId e.g. 1 for mainnet or 17000 for Holesky

Hex - A counter for the number of transactions sent by the account

Hex - Limit of gas used for the transaction execution (wei)

Hex - compiled contract code for the transaction

Access list

Hex - Gas price per unit consumed (wei)

The r value of the signature (optional as it will not exist if tx is not signed)

The s value of the signature (optional as it will not exist if tx is not signed)

The recovery Id of the Ethereum chain (optional as it will not exist if tx is not signed)

The parameter name of the decoded input array, only available on the top level params in EthDecodedMethodData

The solidity type of the input parameter (bytes, uint, address etc..)

The value of the input parameter

The keccak hash of method signature in hex string 4 bytes for decodedInput ("0x" + 8 hex strings) 32 bytes for decodedEvents ("0x" + 64 hex strings)

The signature of the method the transaction invoked (i.e. transfer(address to, uint256 amount))

The decoded parameters of the method

The parameter name of the decoded input, only available on the top level params in EthDecodedMethodData

The solidity type of the input parameter (bytes, uint, address etc..)

The value of the input parameter

The message and address from which the message is signed from

The HD wallet path within the BIP32 Wallet

The digest of the message

The message and address from which the message is signed from

The HD wallet path within the BIP32 Wallet

The digest of the message

An Ethereum Transaction

The HD wallet path within the BIP32 Wallet

IMPORTANT: This should only be used to verify that the digest you created from the transaction is correct. NEVER sign this digest without verifying!

The address to send this transaction is directed to

The value of ETH to send with this transaction

The chainId e.g. 1 for mainnet or 17000 for Holesky

The number of transactions a user has already sent (plus 1 for this transaction)

Int (as String) of the gas provided for the transaction execution.

Int (as String) of the gasPrice used for each paid gas

The address the transaction is sent from

The r value of the signature (optional as it will not exist if tx is not signed)

The s value of the signature (optional as it will not exist if tx is not signed)

The recovery Id of the Ethereum chain (optional as it will not exist if tx is not signed)

The compiled code of a contract OR the hash of the invoked method signature and encoded parameters.

0x prefixed hex

Only present for certain known EVM chains

An Ethereum Transaction

The HD wallet path within the BIP32 Wallet

IMPORTANT: This should only be used to verify that the digest you created from the transaction is correct. NEVER sign this digest without verifying!

wallet info

subWallet address

Unique id for the subWallet. String format of the subWalletId (id/type/index)

The name of the subWallet

Creation time stamp (ISO 8601 UTC date time):

Modified time stamp (ISO 8601 UTC date time):

Wallet Type

Transaction connection

Name of the exchange if its an exchange subWallet

status of the exchange subWallet

assetId: NATIVE, or contract address chainId: For EVM only, specify hex

List of token assets with balances associated with the subWallet (ETH + ERC20 if Ethereum else BTC on Bitcoin) NOTE: pagination is not implemented yet - limit and nextToken are currently ignored

⚠️ DEPRECATED

use balance field

All the wallets that this wallet can send to for each supported asset.

The exchange the transaction is sent from

The exchange the transaction is sent to

The amount of the transferred asset

Status of the transaction

Timestamp the transaction was created at (ISO 8601 UTC date time):

Timestamp the transaction was last updated (ISO 8601 UTC date time):

the optional tip or priority fee that can be added in most networks. Same unit as price

the name of the fee price, typical values are slow, medium and fast.

price in the unit specified

unit of the prices given. e.g. wei or satoshi per byte or other chain specific units

estimated wait time (in seconds) for the transaction to be included in a block at this price

The exchange the transaction is sent from from.id can be set to empty string if not present for outbound bitcoin transaction, from.id is the subwallet ID

The exchange the transaction is sent to

The amount of the transferred asset

Status of the transaction

Reason the Transaction was cancelled

Timestamp the transaction was created at (ISO 8601 UTC date time):

Timestamp the transaction was last updated (ISO 8601 UTC date time):

Free text field describing the chain

may be empty until transfers are known

Unique identifier for the transaction

Indicates if the transactions was created and signed from our systems

Array of transactions on this page

Token used for querying on the next page

Number of transactions for provided address on provided chainId

Purpose is a constant set to 44' (or 0x8000002C) following the BIP43 recommendation. It indicates that the subtree of this node is used according to this specification

Coin type is a constant, set for each cryptocoin

This level splits the key space into independent user identities, so the wallet never mixes the coins across different accounts.

Constant 0 is used for external chain(e.g. for receiving payments) and constant 1 for internal chain (also known as change addresses)

Addresses are numbered from index 0 in sequentially increasing manner. This number is used as child index in BIP32 derivation.

The message string to be signed

The address of the public key pair from which the message will be signed from

The trustId

The Organisation Name

Indicates whether the Organisation often acts as an intermediary for transfers on behalf of their customers

Indicates whether the Organisation can act as an intermediary or can only make direct transfers

The walletId associated with this policy

Schedule describing the recoverers policy

Schedule describing the delegates policy

Creation time stamp (unix timestamp)

Deadline for the creation to policy (unix timestamp) - security feature

Public key of the HSM

The version of the policy

The epoch timestamp the policy change request is valid until

The schedule that describes which public keys and how many of it is needed to access wallet funds

The schedule that describes which public keys and how many of it is needed to change the wallet policy

The total value of all the assets under the portfolio

The asset balance summaries of each of the coins (ETH/BTC) The balance summaries of each of the asset (i.e. ETH, BTC..)

The timestamp of the portfolio values (ISO 8601 UTC time)

The current page of Portfolio objects. There will be a portfolio item for each time Period specified in the query

The token to use to get the next page of Portfolio objects. If items is an empty array then this value should be null

CSV portfolio in string format. columns (trustId, subWalletId, asset, value, Value, timestamp)

email if user, empty if API Key

Description of the principal

Device Public Key

Unique identifier for the change policy request

The unique identifier for the request

The status of the request

The type of the request - RECOVERY CREATION ETHTRANSACTION EXTERNALETHTRANSACTION BTCTRANSACTION EXCHANGETRANSFER, ETHPERSONALSIGN ETHTYPEDDATASIGN

Unique identifier of the transaction in the blockchain. (only available on BTC_TRANSACTION request type)

The signatures for the request

Raw transaction bytes of the transaction

Defines the minimum number of public keys needed to sign to satisfy the schedule

The list of public keys that can sign for the wallet

The DER encoded transaction digest and the wallet path

The SHA3-256 digest of the signData

DER formatted signature

r + s signature

v + r + s signature

The current page of SubWallet objects. This can be an empty array if there are no items on this page

The token to use to get the next page of SubWallet objects. If items is an empty array then this value should be null

The HD wallet id

The subwallet type

The HD wallet index of the subwallet

Type of subWallet

Number of deleted subWallets

Number of SubWallets

Array of transactions on this page

Token used for querying on the next page

CSV in string format.

The date timestamp (ISO 8601 UTC time) to be inputted in the subsequent call to get the truncated transactions.

Amount of rows was truncated.

The transaction digest of the input

The DER encoded transaction digest and the wallet path

The SHA3-256 digest of the signData

from.id can be empty string if not present from.id is subWalletId for outbound Bitcoin

RECEIVED" | "SENT" | "SELF"

Whether the transfer has been previously submitted

space here for additional props, e.g. total etc in future

Whether the update was successful

User's secure tokens

User's first name

User's last name

User's email

Organisation details

Get the portfolio summary for the user - startDate / endDate is ISO 8601 UTC timestamp

Get the portfolio summary broken down by assets for each subWallet a user has in csv string format - startDate / endDate is ISO 8601 UTC timestamp, currency defaults to GBP NOTE: currently only supports ONEMONTHDAILY timePeriod and could fail to get the most recent time point if the endDate timestamp is within the last 30 minutes of the current hour

ONLY the subWallet details (name, address etc...) and Transactions is supported.

optional parameter to get the subWallet for the given subWalletId

defaults to GBP

pagination limit

pagination next token

optional parameter to get the wallets matching the given searchName

Get Wallets along with associated subwallet summaries NOTE: pagination is not implemented yet - limit and nextToken are currently ignored

optional parameter to include deleted Wallets

optional parameter to include each Wallet's policy

pagination limit

pagination next token

Optional parameter to set number of results per page, max 50

pagination next token

The hmac for secure intercom from iOS

The hmac for secure intercom from web

id of the vasp

name of the vasp

id of the vasp

name of the vasp

The VASP type

Unique identifier for the wallet

Name of wallet

Wallet's signing policy

Wallet's provenance signature

Summary of SubWallets in Wallet

Is this wallet deleted

Cluster information for this wallet

List of all publicKeys used in the Policy

The current page of Wallet objects. This can be an empty array if there are no items on this page

The token to use to get the next page of Wallet objects. If items is an empty array then this value should be null

Unique identifier for default wallet

The signature to be added for the requestId

Unique identifier for the request to which the signatures will be added

If not set it will be defaulted to [RECIPIENT]

The authentication tokens for the user

Only COMPATABILITY IS SUPPORTED

 Only Receive is supported

The unique identifier for the subWallet you wish to send this transaction from

The authentication tokens for the user. Optional for API key authentication

The create bitcoin transaction parameters

A text field identifying where the request to sign came from - your application name should go here

Request that when the transaction is signed by the authorised signer(s), TrustVault will send it directly to the network

The currency to return the assets in. See docs for supported currencies. defaults to GBP

If the transaction should be submitted for devices for signing. Set to false to allow reviewing transaction data. Set to true when you want to send a transaction to devices to sign. Defaults to true.

The unique identifier for the subWallet you wish to send this transaction from

The address this transaction is directed to

The value of BTC to send with this transation in satoshis

The speed at which you want the network to accept the transaction. This a dynamic value for the gasPrice and helps determine the fee. The fee is charged by the network in satoshi. This value is included in the total amount of the transaction. Defaults to MEDIUM

The amount of satoshi you are willing to pay per byte of the transaction

The schedule that describes which public keys and how many of it is needed to access wallet funds. (Only supports 1 of 1 schedule currently)

Unique identifier for the wallet which the new delegate schedule is going to apply to If not specified the new delegate schedule will going to be applied to ALL the wallets associated with the user

The authentication tokens for the user

The EthereumTransaction to be signed

A text field identifying where the request to sign came from - your application name should go here

Request that when the transaction is signed by the authorised signer(s), TrustVault will send it directly to the network

The currency to return the assets in. See docs for supported currencies. defaults to GBP

A non-authenticated Rpc Url of a node to submit transactions to

The authentication tokens for the user

The EthereumTransaction to be signed

A text field identifying where the request to sign came from - your application name should go here

Request that when the transaction is signed by the authorised signer(s), TrustVault will send it directly to the network

The currency to return the assets in. See docs for supported currencies. defaults to GBP

A non-authenticated Rpc Url of a node to submit transactions to

The authentication tokens for the user

The signPersonalMessage to be signed

A text field identifying where the request to sign came from - your application name should go here

If the transaction should be submitted for devices for signing. Set to false to allow reviewing transaction data. Set to true when you want to send a transaction to devices to sign. Defaults to true.

A public key of the caller used to encrypt the signature. Must be on the secp256k1 curve

The authentication tokens for the user

The EthSignTypeData to be signed

A text field identifying where the request to sign came from - your application name should go here

If the transaction should be submitted for devices for signing. Set to false to allow reviewing transaction data. Set to true when you want to send a transaction to devices to sign. Defaults to true.

A public key of the caller used to encrypt the signature. Must be on the secp256k1 curve

The authentication tokens for the user

The EthereumTransaction to be signed

A text field identifying where the request to sign came from - your application name should go here

Request that when the transaction is signed by the authorised signer(s), TrustVault will send it directly to the network

The currency to return the assets in. See docs for supported currencies. defaults to GBP

If the transaction should be submitted for devices for signing. Set to false to allow reviewing transaction data. Set to true when you want to send a transaction to devices to sign. Defaults to true.

A non-authenticated Rpc Url of a node to submit transactions to

The EthereumTransaction to be signed

A text field identifying where the request to sign came from - your application name should go here

The signatures which satisfy the wallet's policy

The digest the user signed (this should include the wallet path)

The HD wallet path within the BIP32 Wallet

The authentication tokens for the user

The ExchangeTransfer to be signed

A text field identifying where the request to sign came from - your application name should go here

The authentication tokens for the user

Unique id for the HD wallet

Name of the asset (i.e BTC / ETH)

Name of the subWallet (i.e BTC / ETH)

The address this transaction is directed to OR the ERC20 token recipient

This TrustVault supported asset you are trying to send. For Ether set this to ETH for ERC20 token, set this to the TrustVault token symbol. (See docs for supported tokens)

For ETH, the value of ETH to send with this transaction in WEI, for ERC20, the value in base unit. e.g. for a token with 6 decimal places, to send 1 token specify 1000000

The speed at which you want the network to accept the transaction. This a dynamic value for the gasPrice and helps determine the fee. The fee is charged by the network in ETH. This value is included in the total amount of the transaction. Defaults to MEDIUM (either speed or gasLimit + gasPrice must be given)

Int (as String) of the gas provided for the transaction execution (either speed or gasLimit + gasPrice must be given)

Int (as String) of the gasPrice used for each paid gas (either speed or gasLimit + gasPrice must be given)

The address the transaction is sent from (This must be owned by the user whose authentication tokens you are using)

The number of transactions made by the sender prior to this one (will be calculated automatically if not given)

The chainId e.g. 1 for mainnet or 17000 for Holesky (will be calculated automatically if not given)

The compiled code of a contract OR the hash of the invoked method signature and encoded parameters (will be calculated automatically if not given)

Hex - From address

Hex - To address

Hex - The value of ETH to send with this transaction

Hex - The chainId e.g. 1 for mainnet or 17000 for Holesky

Hex - The number of transactions a user has already sent (plus 1 for this transaction)

Hex - Limit of gas used for the transaction execution (wei)

Hex - compiled contract code for the transaction, valid values undefined, 0x, 0xdeadbeef etc

Hex - Maximum fee per gas (wei)

Hex - Maximum priority fee per gas (wei)

Access list

Hex - From address

Hex - To address

Hex - The value of ETH to send with this transaction

Hex - The chainId e.g. 1 for mainnet or 17000 for Holesky

Hex - A counter for the number of transactions sent by the account

Hex - Limit of gas used for the transaction execution (wei)

Hex - compiled contract code for the transaction, valid values undefined, 0x, 0xdeadbeef etc

Access list

Hex - Gas price per unit consumed (wei)

The Ethereum transaction envelope type, defaults to 0 (legacy) if not provided

The address this transaction is directed to OR the ERC20 token recipient

The value of ETH to send with this transactiona

Int (as String) of the gas provided for the transaction execution.

Int (as String) - wei

Int (as String) - wei

Int (as String) - wei

The address the transaction is sent from (This must be owned by the user whose authentication tokens you are using)

The number of transactions made by the sender prior to this one

The chainId e.g. 1 for mainnet or 17000 for Holesky

The compiled c code of a contract OR the hash of the invoked method signature and encoded parameters

The amount of the asset to be transferred, a decimal integer string in the base unit of the asset e.g. Satoshis for BTC or Wei for ETH

The asset to be transferred

The id of the wallet

The type of the exchange wallet, i.e. which exchange is it on

The 0-based index of the key within the same wallet. This allows us to have multiple exchange accounts of the same type within a single wallet. This isn't expected right now, but good to be future proof

The authentication tokens for the user (optional for API key users)

The chainId of the desired transaction count e.g. 1 for mainnet or 17000 for Holesky

Address from which to count the number of transaction

Internal Only. Temporarily used to determine whether queuing is turned on for that account/wallet

Purpose is a constant set to 44' (or 0x8000002C) following the BIP43 recommendation. It indicates that the subtree of this node is used according to this specification

Coin type is a constant, set for each cryptocoin

This level splits the key space into independent user identities, so the wallet never mixes the coins across different accounts.

Constant 0 is used for external chain(e.g. for receiving payments) and constant 1 for internal chain (also known as change addresses)

Addresses are numbered from index 0 in sequentially increasing manner. This number is used as child index in BIP32 derivation.

The message string to be signed

The address of the public key pair from which the message will be signed from

Version of the ethsignedtypeddata. defaults to "V3". format is currently "V3" or "V4"

The public key of the private key that was used to sign the digest

The signature generated when the digest was signed by the private key

The authentication tokens for the user (optional for API key users)

The end date from date in ISO format e.g. '2022-11-29T16:52:03.892Z'. Will default to now

The initial from date in ISO format e.g. '2022-11-29T16:52:03.892Z'. Will default to one month ago

The authentication tokens for the user (optional for API key users)

Defines the minimum number of public keys needed to sign to satisfy the schedule

The list of public keys that can sign for the wallet

The public key and signature pair over the digest

The HD wallet id

The subwallet type

The HD wallet index of the subwallet

The transfer ID ${transactionId}-${index} e.g. 1245-0

The beneficiary information

The originator information

Whether to submit the transfer for compliance review or not

The name of the originator

The account ID of the originator

The customer ID of the originator If value >= 1000 EUR, an additional identifier for customer is required

True means the Organisation is the originator/beneficiary (depending on transfer direction of SENT/RECEIVED respectively) False means that the originator/beneficiary is the User's Organisation is acting as an intermediary OR its an unrelated 3rd party. (depending on the transfer direction)

The VASP (virtual asset service provider) information

id of the vasp

name of the vasp if no id is provided

The VASP type

The amount in wei that was transferred in the transaction - hex string

The height of the block where this transaction is in

The transaction data to be signed

Bitcoin rate in desired currency

The transaction fee in satoshi

The max allowed to send in satoshi

The fee for the max send amount in satoshi

The current balance of the wallet in satoshi

Data needed to sign a transaction

Ethereum rate in desired currency

Token rate in desired currency

The parameter name of the decoded input array, only available on the top level params in EthDecodedMethodData

The solidity type of the input parameter (bytes, uint, address etc..)

The sub-wallet's public key

The HD wallet path of the sub-wallet

The trustvault signature over SHA-256(DER(publicKey + path + walletId))

Wallet Information for this SubWallet

subWallet address

Unique id for the subWallet. String format of the subWalletId (id/type/index)

name of the subWallet