# Decentralisation by Design
## Decentralization by Design: How Torram Aligns with Bitcoin’s Core Ethos
Written by Torram Labs CTO, [Lee Raj](https://www.linkedin.com/in/leeraj/?ref=hackernoon.com).
One of the most powerful features of the Bitcoin network is its decentralization. As we built the Torram network, we aimed to align ourselves with this core ethos of Bitcoin. Creating peer-to-peer decentralized networks with complex economic incentives is no easy feat, but we were committed to building Torram in the most authentic way—true to Bitcoin’s philosophy.
Torram is a Proof-of-Stake network, where validators must stake tokens to participate.
Each validator runs three core pieces of software: the Torram node, a trustless Torram relayer, and Bitcoin Core.
The Torram network currently generates blocks in under one minute and is capable of producing them every few seconds. Approximately every 10 minutes, when a Bitcoin block is mined, Torram validators submit Merkle proofs to the Bitcoin blockchain. In testnet, validators are using tBTC. On mainnet, they will use real Bitcoin to submit data finality to the Bitcoin network. This is a critical feature of Torram that ensures decentralization and makes the network inherently Bitcoin-native. Economic guarantees and network security are backed by real Bitcoin.
Torram has attracted significant interest from validators since its alpha launch.
You can read more here:
🔗 [Torram’s Node Operator Program Receives Over 5,000 Sign-Ups in Less Than 72 Hours](https://www.dcnewsnow.com/business/press-releases/ein-presswire/794062648/torrams-node-operator-program-receives-over-5000-sign-ups-in-less-than-72-hours/?ref=hackernoon.com)
To put things into perspective:
• Bitcoin has \~22,000 nodes
• Ethereum has \~10,000 nodes
• Solana has \~5,000 nodes
These networks are among the longest-standing in crypto history, so we’re incredibly humbled by the crypto community’s enthusiasm for Torram.
For our testnet, we are initially capping the validator set to 30, with an institutional focus.
These are the validators in our Genesis set.
| **Validator Name** | **Website** |
| --------------------- | --------------------------------------------------------------------------- |
| Rhino | [rhinostake.com](https://rhinostake.com/?ref=hackernoon.com) |
| Enigma | [enigma-validator.com](https://enigma-validator.com/?ref=hackernoon.com) |
| Block Farms | [block-farms.io](https://block-farms.io/?ref=hackernoon.com) |
| Certik | [certik.com](https://www.certik.com/?ref=hackernoon.com) |
| MH Ventures | [mhventures.io](https://www.mhventures.io/?ref=hackernoon.com) |
| Kingnodes | [kingnodes.com](https://www.kingnodes.com/?ref=hackernoon.com) |
| Stakely.io | [stakely.io](https://stakely.io/?ref=hackernoon.com) |
| Matrixed.Link | [matrixedlink.io](https://www.matrixedlink.io/?ref=hackernoon.com) |
| Polkachu | [polkachu.com](https://polkachu.com/?ref=hackernoon.com) |
| KukisGlobal | [kukis-global.com](https://www.kukis-global.com/?ref=hackernoon.com) |
| Cryptech-Hacken | [hacken.io](https://hacken.io/?ref=hackernoon.com) |
| Allnodes | [allnodes.com](https://www.allnodes.com/?ref=hackernoon.com) |
| Lavender | [lavenderfive.com](https://lavenderfive.com/?ref=hackernoon.com) |
| GlobalStake.io | [globalstake.io](https://globalstake.io/?ref=hackernoon.com) |
| Artifact | [artifact-staking.io](https://artifact-staking.io/?ref=hackernoon.com) |
| Nexum Labs | |
| Republic | [https://republic.com/](https://republic.com/?ref=hackernoon.com) |
| Chainup | [https://www.chainup.com/](https://www.chainup.com/?ref=hackernoon.com) |
| Nodedao | [https://www.node.monster/](https://www.node.monster/?ref=hackernoon.com) |
| Stakecraft | [https://stakecraft.com/](https://stakecraft.com/?ref=hackernoon.com) |
| Cosmostation | [cosmostation.io](https://www.cosmostation.io/?ref=hackernoon.com) |
| 01node | [01node.com](https://01node.com/?ref=hackernoon.com) |
| Extra Mile (TV Asahi) | [extramile.jp](https://extramile.jp/company/?ref=hackernoon.com) |
| Chandra Station | [chandrastation.com](http://chandrastation.com/?ref=hackernoon.com) |
| Four Moons | [https://x.com/fourmoonsllc](https://x.com/fourmoonsllc?ref=hackernoon.com) |
| Validation Cloud | [validationcloud.io](http://validationcloud.io/?ref=hackernoon.com) |
| Swyke | [swyke.ai](https://swyke.ai/?ref=hackernoon.com) |
| BitsLab (NodeKeeper) | [scalebit.xyz](https://scalebit.xyz/?ref=hackernoon.com) |
| BitGo | [bitgo.com](https://www.bitgo.com/?ref=hackernoon.com) |
For more information and to start building, visit the links below:
[Follow us on X](https://x.com/Torram_xyz?ref=hackernoon.com)
[Follow us on LinkedIn](https://www.linkedin.com/company/torramlabs?ref=hackernoon.com)
[Join our Builders Community](https://t.me/torrambuilders?ref=hackernoon.com)
---
# 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://torram.gitbook.io/torram-documentation/technical-articles/decentralisation-by-design.md?ask=
```
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.