# Audits

## Security, Smart Contracts, and Audits

<mark style="color:red;">Please read this section in full before browsing our audit reports.</mark>

**Risks**

Although we have taken numerous steps to ensure that our smart contracts and wallet systems are secure, potential users of JetBolt should be aware that it is a new and experimental technology. The security model used in our wallet is new and untested, and despite third-party audits and extensive unit tests, we do not guarantee that our smart contracts and wallet are bug-free and safe. All users should exercise caution when interacting with the JetBolt ecosystem and only purchase JetBolt tokens with sums of money they are prepared to lose.

**Bug Reporting**

We take security very seriously. If you discover any bugs or vulnerabilities within our products, please immediately contact us at <support@jetbolt.io>. Be sure to include as much information as possible so that we can resolve any issues promptly.

**Contract Upgradability**

Due to the early stage and experimental nature of the JetBolt ecosystem, all of our smart contracts are upgradeable. This is necessary if we need to fix a bug or add new features. In addition to this, there are several privileged functions which the admin has control over. This is necessary for the business logic of our presale, which allows users to mint tokens immediately. However, these are in fact potential security risks that have been flagged in our audits. Users should keep these risks in mind when using the JetBolt ecosystem.

**Wallet Security Model**

Our wallet works by splitting a seed phrase into two components and storing them separately on the user’s device. One portion is stored in the browser’s local storage and the other portion is stored in a Personally Identifiable Information (PII) field in a WebAuthN credential. Due to the security standards of modern web browsers and based on the specifications of the WebAuthN protocol, our developers have deemed this security model to be safe. We have also conducted a third-party audit on the wallet which has passed successfully. However, this system is new and untested. We are using WebAuthN credentials in a way that was not initially intended by the developers of that protocol. As such we strongly advise all users to exercise caution and never to store any assets in a JetBolt wallet that they are not prepared to lose.

**Understanding Audits**

All readers should be aware that a successful audit does not guarantee that a product is bug-free and safe. We have done our best to ensure that JetBolt is safe and we have paid a trusted third party to audit our source code. However, there may still be bugs and vulnerabilities that were not detected by our developers and the audit team. In addition, blockchain technologies are themselves new. As such flaws may exist in the underlying blockchains, systems, software, and libraries that we have used to implement JetBolt. All JetBolt users should be aware of these risks and not treat an audit report as gospel.

**Smart Contract Addresses**

Below you can find the addresses of our deployed smart contract

Token: [0x579916a67b47d25Bea73c61f06690d180Ce2d9d5](https://honorable-steel-rasalhague.explorer.mainnet.skalenodes.com/address/0x579916a67b47d25Bea73c61f06690d180Ce2d9d5)

Friends: [0xC4af99537818d1fA0A5e235F4863c705c6A8F762](https://honorable-steel-rasalhague.explorer.mainnet.skalenodes.com/address/0xC4af99537818d1fA0A5e235F4863c705c6A8F762)

Logs: [0x9E1732234f1f670CC18f5B0b9988eE26d496282e](https://honorable-steel-rasalhague.explorer.mainnet.skalenodes.com/address/0x9E1732234f1f670CC18f5B0b9988eE26d496282e)

Sessions: [0xa757D3091d3afff44DF396c533C38A72217042fe](https://honorable-steel-rasalhague.explorer.mainnet.skalenodes.com/address/0xa757D3091d3afff44DF396c533C38A72217042fe)

\
**Independent Audits**

[Wallet Audit](https://jetbolt.io/wallet_audit.pdf)

[Smart Contract Audit](https://jetbolt.io/contract_audit.pdf)

[Smart Contract Unit Testing](https://jetbolt.io/unit_tests.pdf)

[**RETURN TO JETBOLT SITE**](https://jetbolt.io/)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://jetbolt.gitbook.io/jetbolt-terms-risks-and-privacy-policy/audits.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.