# Architecture

The following diagram presents the architecture of the tBTC SDK and its place in the ecosystem:

<figure><img src="/files/YMTE0DReM4y8cjJiCXOT" alt=""><figcaption></figcaption></figure>

As you can see, the SDK consists of several major parts:

* `TBTC` component
* Feature services
* Shared libraries

### `TBTC` component

The `TBTC` component is the main entry point to the SDK. It provides different ways to initialize the SDK that are supposed to address the common use cases (see [Initialize SDK](/app-development/tbtc-sdk/guides/initialize-sdk.md) guide to learn more). Moreover, the `TBTC` component gives access to the SDK core features through feature services as well as low-level direct access to the underlying tBTC smart contracts and Bitcoin network client.

### Feature services

The SDK feature services provide seamless access to the core features of the tBTC bridge. The most important features of the SDK are:

* **Deposits:** deposit and mint flow for BTC depositors
* **Redemptions:** unmint and redeem flow for TBTC redeemers&#x20;
* **Maintenance:** authorized maintenance actions for maintainers (e.g. optimistic minting guardians)

### Shared libraries

Shared libraries are reusable modules that provide cross-cutting concerns leveraged by multiple feature services and the `TBTC` component. The main shared libraries of the SDK are:

* **Bitcoin**: interfaces and utilities necessary to interact with the Bitcoin chain
* **Contracts**: chain-agnostic interfaces allowing interaction with tBTC smart contracts
* **Electrum**: Electrum-based implementation of the Bitcoin client
* **Ethereum**: implementations of tBTC smart contract interfaces for the Ethereum chain
* **Utils**: general utility functions


---

# 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://docs.threshold.network/app-development/tbtc-sdk/architecture.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.