> For the complete documentation index, see [llms.txt](https://bcts-1.gitbook.io/swissdlt/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bcts-1.gitbook.io/swissdlt/general/architecture.md).

# Architecture

SwissDTL  is oriented around providing the simplest possible experience for end-users, who may have no familiarity with Blockchain or Cryptocurrencies.

### A Full-Stack Approach[​](https://docs.celo.org/learn/celo-stack#a-full-stack-approach) <a href="#a-full-stack-approach" id="a-full-stack-approach"></a>

To achieve this, SwissDLT takes a full-stack approach, where each layer of the stack is designed with the end-user in mind while considering other stakeholders (e.g. operators of nodes in the network) involved in enabling the end-user experience.

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

### SwissDLT Blockchain[​](https://docs.celo.org/learn/celo-stack#celo-blockchain) <a href="#celo-blockchain" id="celo-blockchain"></a>

An open cryptographic protocol that allows applications to make transactions with and run smart contracts in a secure and decentralized fashion. The SwissDL blockchain code is using  with[ Ethereum](https://www.ethereum.org/) Clients and maintains full EVM compatibility for smart contracts. However, it uses the POA Clique Consensus Algorithm.

### SwissDLT Contracts[​](https://docs.celo.org/learn/celo-stack#celo-core-contracts) <a href="#celo-core-contracts" id="celo-core-contracts"></a>

A set of smart contracts running on the SwissDLT blockchain help users to adopt the most common tools. This set up Smart Contracts will be updated regularly. Currently wrapped native Tokens wBCTS and an uniswap fork are live.

### Applications[​](https://docs.celo.org/learn/celo-stack#applications) <a href="#applications" id="applications"></a>

Applications for end users built on the SwissDLT Ecosystem  The Metamask Wallet application is an example of an application. It allows end-users to manage accounts and make payments securely and simply by taking advantage of the innovations in the SwissDLT Protocol. Generally, applications take the form of external mobile or backend software: they interact with the SwissDLT blockchain to issue transactions and invoke code that forms the SwissDLT API or other smart contracts. Third parties can also deploy custom smart contracts that their own applications can invoke, which in turn can leverage SwissDLT Core Contracts. Applications may use centralized cloud services to provide some of their functionality.

### The SwissDLT Network Topology[​](https://docs.celo.org/learn/celo-stack#celo-network-topology) <a href="#celo-network-topology" id="celo-network-topology"></a>

The topology of a SwissDLT network consists of machines running the SwissDLT blockchain software in several distinct configurations.

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

### Signers[​](https://docs.celo.org/learn/celo-stack#validators) <a href="#validators" id="validators"></a>

Signers gather transactions received from other nodes and execute any associated smart contracts to form new blocks, then participate in a consensus protocol to advance the state of the network. Singers are rewarded for their work and are members of the DAO.

### Archive Nodes[​](https://docs.celo.org/learn/celo-stack#full-nodes) <a href="#full-nodes" id="full-nodes"></a>

Most machines running the  SwissDLT blockchain software are either not configured to be, or not elected as, signers. Their primary role of archive nodes is to serve requests and to ensure an archive of the blockchain.  Archive nodes maintain at least a partial history of the blockchain by transferring new blocks between themselves and can join or leave the network at any time

### &#x20; <a href="#light-clients" id="light-clients"></a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://bcts-1.gitbook.io/swissdlt/general/architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.