Overview
This report provides a summary of all the events that have taken place on your account during the specified time frame. Events include significant changes such as created transactions, new wallets, or updates to wallet policies. You can find a detailed list of all recorded events below.
We have been tracking events in our system since the beginning, but please note that the download tool only includes events from December 16, 2022, onward.
Export Events
The events logged in the system can be exported in CSV format, containing the following information:
- Event timestamp (UTC)
- Description
An example of a downloaded event would be:
Alice Bob <alice.bob@bitpanda.com> has requested the creation of a Subwallet named "test" (subWalletId: d955ea0e-2edf-56gb-9e80-db8cb3df2cd4/ETH/15)
Event Date / Time
This indicates the actual date and time when the event occurred.
Description
This gives a user-friendly overview of the event, detailing who took action, what action was taken, and any relevant additional information.
The "who" will reflect various user types within the system. Below is a table outlining the types you might encounter.
| User Type | Example | Description |
| ApiKey | API Key ****1a3aS6 | The action was performed using an API key, showing the last 6 digits for identification. |
| User | Alice Bob <alex.bob@bitpanda.com> | A user who authenticated with their credentials (email/PIN). |
| User (via email authentication) | alex.bob@bitpanda.com <alex.bob@bitpanda.com> | A user who performed an action by clicking a link in an email. |
| Internal User | Bitpanda Custody Support <support@bitpandacustody.com> | The action was taken by Bitpanda Custody Support on your behalf. |
| Workflow User | Bitpanda Custody Workflow | This action was executed by a backend Bitpanda system, not as a direct result of user action. For example, a transaction will be signed by Bitpanda Custody Workflow after a backend process is completed. |
From the example above, we can see that user Alice Bob <alice.bob@bitpanda.com> performed the action in question, authenticating via email/PIN rather than through an email link, as indicated by their name.
Event Names and Their Descriptions
Below is a list of all possible recorded events.
| Num | Event Name | Description |
| 1 | DelegateSigned | A user has signed a transaction. |
| 2 | TransactionInitiated | A transaction has been initiated. |
| 3 | TransactionSigned | A transaction has been signed by our HSMs with the correct keys, meaning the wallet policy was satisfied. |
| 4 | TransactionSubmitted | A transaction has been submitted by TrustVault to the relevant chain. |
| 5 | TransactionCancelled | A transaction was cancelled. |
| 6 | WalletUpdateInitiated | A wallet change has been initiated (change of wallet policy). |
| 7 | WalletUpdateCompleted | A wallet change has been completed (change of wallet policy). |
| 8 | WalletUpdateCancelled | A wallet change has been cancelled. |
| 9 | UserPinReset | A user has (re)-set their PIN, indicating a new user account is now active. |
| 10 | UserRemovedFromOrg | A user has been removed from your organization and can no longer access the account. |
| 11 | UserAddedToOrg | A user has been added to your organization and may be able to access the account. |
| 12 | AddressBookEntryCreateInitiated | A request has been made to create an address book entry. |
| 13 | AddressBookEntryCreateCompleted | A request to create an address book entry has been completed. |
| 14 | AddressBookEntryDeleteInitiated | A request to delete an address book entry has been initiated. |
| 15 | AddressBookEntryDeleteCompleted | A request to delete an address book entry has been completed. |
| 16 | SubwalletCreateInitiated | A request to create a sub-wallet has been initiated. |
| 17 | SubwalletCreateCompleted | A request to create a sub-wallet has been completed. |
| 18 | CreateWalletInitiated | A request to create a wallet has been initiated. |
| 19 | CreateWalletCompleted | A request to create a wallet has been completed, and the wallet is now available for use. |
| 20 | CreateWalletCancelled | A request to create a wallet has been cancelled. |
| 21 | UserPermissionCreateCompleted | A request to add a permission to a user has been completed. |
| 22 | UserPermissionDeleteCompleted | A request to delete a permission from a user has been completed. |
Referring back to our example, we can see that user Alice Bob requested the creation of a Subwallet called "test" (SubwalletCreateInitiated).
Initiated vs Completed
For many events in the system, they can be initiated before they are completed. This typically happens when an approval is needed or if there is a delay between the request and approval. In some cases, the request and completion may occur simultaneously.
Process
To export a CSV of transactions, simply click the Export button and select Audit. You can find this button in the top right corner of the TrustVault Web Wallets section.
When you click "Export Audit History," you'll be prompted to choose the date range.
The options available are:
- 31 days back from today
- Custom Range
- Select any date after December 16, 2022
- Maximum of 31 days
Clicking "Request" will initiate the process, and you will receive an email with the results.
Tip: This report may contain a large amount of data and could take some time to generate. If you encounter a failure, please try again or select a smaller date range. If issues continue, feel free to reach out to us for assistance.