Botanix Federation
Last updated
Last updated
The next version is a Federated EVM Sidechain. In this version of the Botanix EVM, we adopt a dynamic federated model. A single multisig set is established with 15 known trusted federated members. New members can be added and removed. We will utilize a round-robin proof-of-authority (PoA) consensus model with N federation members. This design is comparable to Liquid (on Bitcoin) and Polygon (on Ethereum).
One of the main differences with the previous version is that the network will be run by the Botanix Federation, consisting of fifteen independently chosen functionairies. This puts the security level aligned with (or close to) any other Layer 2 side chains and rollups.
At first, this version will be launched as our next public testnet version after the previous one is taken down. This testnet will make it possible for us to battle test the network of Federation members, the consensus and the block production. At the same time, partners will be able to test their applications on our chain. At this point, we call it Botanix Testnet V1.
After this version is battle tested and audited, it will form the basis for the Botanix EVM Mainnet. At this point, the Botanix EVM will really come to live and users are able to peg in their Bitcoin and start exploring the world of decentralized applications on top of Bitcoin.
There are four main building blocks to the Botanix Federation:
Simply said, peg-in means the process of transferring Bitcoin from its parent chain to the Botanix EVM. Users require a mechanism to move their on-chain Bitcoin from Layer 1 to Layer 2 on the Botanix EVM.
The Botanix EVM utilizes the internal taproot key to encode the Layer 2 address where the funds should be directed. As a result, a taproot address is generated, allowing users to repeatedly send funds to it. Following confirmation(s), a pegin proof can be constructed to verify that the funds have been successfully sent.
Pegging in can be done on the official Botanix Bridge.
Peg-out means the transferring of Bitcoin from the Botanix EVM chain back to the Bitcoin parent chain.
For this case, users provide any bitcoin address and sats amount that would like to withdraw. The Botanix EVM nodes will collect a quorum of signatures and release the funds.
Pegging out can be done on the official Botanix Bridge.
The ultimate goal for the Botanix EVM is to become fully permissionless and decentralized. However, to begin, the Botanix EVM will start with a federation of maximum 15 members. At this point, the ecosystem includes Botanix Labs and partner nodes, adhering to the standards set by the Botanix EVM protocol, namely verifying pegins, verifying pegouts and following the CometBFT consensus for block production. The Botanix Federation is also responsible for securing the multisig wallet that contains the pegged in funds.
Block selection: The Botanix Federation employs a round-robin selection mechanism, akin to the one described in the clique spec (EIP255), for choosing block producers.
At this point, anyone will be able to join the network (run their own node) but will not be part of the Botanix Federation that produces the blocks. The Botanix Federation members are carefully selected based on characteristics as uptime, security standards, geographical location etc.
Botanix uses threshold cryptography to secure the multisig (FROST). FROST is a threshold signature scheme that splits a Schnorr signing key into n shares for a threshold t, enabling t or more participants to collectively generate a signature valid with the verifying key.
Federation of a block producing and validating nodes (15 members)
FROST-style multisig consisting of federation members
Possibility to run non-federation nodes
Staking
Slashing staking participants
Dynamic federation
Testnet V1 will be our second and last testnet before going to mainnet. The main purpose of this testnet is to battle-test our code and get feedback from partners and builders. The code will be audited before mainnet is launched officially.
