How to report issues and bugs

TABLE OF CONTENTS

• Check for new Releases
• Submitting a Report
• Discharge of Responsibility

At Tatum, we appreciate your efforts in helping us improve our products.

Should you come across issues or bugs with the Tatum API, KMS, or SDKs, you can reach out to us.

Check for new Releases

We update the core API, KMS, and our SDKs regularly. 

We recommend testing with the available latest update release to see if the issue persists.

Submitting a Report

1. Create a Ticket: Submit a ticket to our support team with a brief subject line naming the issue or bug.
2. Provide Detailed Information: In your ticket, please provide the following information:
   • Problem Statement: A brief description of the issue and or Use Case you have in mind. Include:
     • Environment: Testnet or Mainnet
     • Timestamp: When the issue or bug happened.
       E.g., 2023.01.12 - 15:00 GMT (YYYY.MM.DD)
   • Expected Outcome: A clear explanation of what the expected behavior should have been.
   • Steps to Reproduce: Detailed instructions, including a list of cURLs with Headers, Payloads, and its Response Bodies, that show all the steps required to reproduce the issue from start to finish.
3. Add Relevant Screenshots or Videos: If possible, include screenshots or videos that demonstrate the issue you are encountering. This will help us understand and resolve the issue more quickly.

As of the writing of this article, Tatum does not have an active bug bounty program. Should this change, our documentation will be revised accordingly.

Discharge of Responsibility

It is imperative that you keep your privateKey(s) and mnemonics/seed phrases confidential and secure at all times. Sharing this information with anyone can result in serious consequences such as the loss of your funds. Your private keys and mnemonics give full access to your funds, and once they are shared, you lose control over your assets. 

No legitimate Tatum staff member will ever ask for your private keys or mnemonics. If you are asked for this information, it is most likely a scam attempt and you should immediately report it. Your security is of the utmost importance, and we highly encourage you to never share your private keys or mnemonics with anyone, under any circumstances.

It is your responsibility to safeguard your Private Keys and mnemonics/seed phrases and protect them from unauthorized access.