Chorus One is proud to be a validator on Berachain, a high-performance modular EVM compatible blockchain powered by Proof-of-Liquidity. In this article, we provide an overview of everything you need to know about Berachain, how it works and use cases.
Berachain, currently in Testnet phase, is changing how DeFi users access liquidity, supercharging applications, and providing flexibility and adaptability to the thriving digital economy. It combines the capabilities of the Cosmos SDK and introduces its novel 'Proof of Liquidity' as well as their new modular implementation of the EVM called Polaris. This not only tackles current obstacles but also paves the way for fresh avenues of creativity and advancement within the DeFi industry.
Berachain is a DeFi-focused Layer 1 blockchain running on Proof of Liquidity consensus built on the Cosmos SDK. Berachain emphasizes modularity in its design approach. By incorporating Polaris, Berachain not only ensures EVM compatibility but also supports a modular framework that allows for easy separation of the EVM runtime layer and crafting stateful precompiles and unique modules enabling the creation of smarter and more effective contracts.
Berachain operates a tri-token system: BERA (native token of Berachain i.e gas), HONEY (stablecoin) and BGT (governance token). Berachain Blockchain also provides a user-friendly interface and a comprehensive array of tools for developers and builders to create and deploy their applications.
Proof of Liquidity is a concept introduced by the Berachain team that enables users to stake various tokens and delegate this stake to validators. Users can stake assets like BTC, ETH, L1 tokens wBTC, wAVAX, wETH, wADA, and stablecoins.
Proof of liquidity models seeks to address challenges in common decentralized systems like liquidity fragmentation and stake centralization. Though Proof of Liquidity builds on the concept of proof of stake, the token used for staking is no longer the same token used for many on-chain actions. Moreover, the sole way to acquire new governance tokens (BGT) is through providing liquidity into DeFi applications.
Image source: Berachain Documentation
The concept behind PoL implies that users stake different tokens to enhance the chain's liquidity and bolster the Layer 1 security at the same time. This setup enables users to earn fees by contributing liquidity through staking while also receiving block rewards. Moreover, users have the option to mint HONEY by providing assets as collateral and utilize them within the Berachain ecosystem without constraints.
Berachain's EVM compatibility is derived from the Berachain Polaris EVM library, which enhances the EVM experience compared to the traditional Ethereum setup. Polaris Ethereum not only provides the standard Ethereum features but also empowers developers with the ability to design stateful precompiles and custom modules for crafting smarter and more robust contracts.
Polaris can be easily integrated into any consensus engine or application, including Cosmos-SDK. This modular approach streamlines the EVM integration process and reduces the time and overhead cost for developers to implement their own EVM features.
For DeFi Users - Berachain BEX
BEX is Berachain’s decentralized exchange that allows users to add liquidity to an asset pool and receive trading fees and incentives.
BEX introduces the concept of House pools, which serve as the backbone of the exchange. These default pools hold significant importance as they generate BGT rewards, which could be staked later with validators to participate in governance.
BEX also introduces Metapools, a liquidity pool where LP tokens can then be used as part of an asset pair in another pool, helping to increase capital efficiency across the chain.
Berachain Bends allow users earn interest and rewards by supplying assets like (ETH, BTC, and USDC) and borrowing HONEY. On Bend users can deposit collaterals to contribute to the platform liquidity, earn BGT rewards by utilising and borrowing HONEY within the ecosystem.
Berps
Berps by Berachain (Perpetual Futures Contract Trading) provides users with endless trading opportunities with a wide array of asset access EVM and Cosmos. It is liquidity efficient, robust and easy to use.
Chorus One will be providing staking services and contributing extensive knowledge in infrastructure development to the network. Our role as validators in the Berachain community symbolizes a collaborative effort aimed at delving into new horizons and enhancing the potential within this ecosystem.
Users providing liquidity in the BEX liquidity pools will gradually accumulate BGT, and can be used to create and vote on governance proposals such as proposals that decide on which LP pools receive BGT emissions. BGT can also be burned 1:1 for BERA. This is a one-way function, BERA cannot be converted into BGT.
Reach out to staking@chorus.one to get started or to learn more.
To read more about Berachain, we recommend the official documentation available in docs.berachain.com.
Chorus One is one of the biggest institutional staking providers globally, operating infrastructure for 50+ Proof-of-Stake networks, including Ethereum, Cosmos, Solana, Avalanche, and Near, amongst others. Since 2018, we have been at the forefront of the PoS industry and now offer easy enterprise-grade staking solutions, industry-leading research, and also invest in some of the most cutting-edge protocols through Chorus Ventures. We are a team of over 50 passionate individuals spread throughout the globe who believe in the transformative power of blockchain technology.
Imagine a world where online interactions don't come at the cost of your privacy. Where you can participate, transact, and share data on your own terms, shrouded in a cloak of cryptography. This is the future envisioned by Aleo, a revolutionary blockchain project that throws open the doors to a privacy-centric internet. Let's delve into Aleo, exploring its technology, participants, and the diverse ecosystem it cultivates.
At its core, Aleo is a layer-1 blockchain that leverages zero-knowledge proofs (ZKPs) to unlock unprecedented possibilities for private applications. ZKPs allow users to prove the legitimacy of information without revealing the underlying data itself. This translates to applications where users can participate, interact, and share data confidently, with their privacy remaining more sacred.
Credit: A credit is the native asset of the network. It is used to pay for deployment and execution fees of zero-knowledge programs. Credits can also be staked on the network as a form of governance to protect the integrity and security of the protocol.
Microcredit: A microcredit is a subdivision of the native asset (credit). One credit can be further divided into smaller units, and a microcredit is one millionth of a credit.
Prover: A prover is a node on the network that computes zero-knowledge proofs. These proofs, which can be of two types (solutions and transactions), are crucial for validating and securing transactions and activities on the network.
Solutions: In the context of zero-knowledge proofs, a solution attests to the execution of a randomly-sampled Aleo program. When a prover successfully proves the execution, a reward is distributed to both the prover and the stakers on the network.
Transactions: Transactions attest to the execution of user-deployed Aleo programs. When a prover provides a valid transaction proof, a transaction fee is rewarded and distributed to the network.
Stakers: These individuals contribute to the network's security by locking up their Aleo credits (ALEO), earning rewards in return.
Validators: Similar to traditional blockchains, validators verify transactions and secure the network, ensuring its integrity and preventing fraud.
The robust architecture of Aleo rests on three key pillars:
AleoBFT is a DAG-based BFT protocol inspired by Narwhal and Bullshark. Validators propose batches of transmissions, await 2ƒ + 1 signatures, certify the batch, and advance rounds synchronously for an honest majority. In odd rounds, validators elect a leader for the previous even round, ensuring availability thresholds are met. This process ensures all validators advance together, assuming honesty.
Here’s how the Quorum for Block Production in Even Rounds is achieved:
The native token of the Aleo ecosystem, Aleo credits (ALEO), serve multiple purposes:
How Aleo Credits are distributed:
AleoBFT operates over a simple set of data structures - a committee, batch proposal, and block. Let’s understand these one-by-one:
Committee:
Batch Proposal: In each round, every committee member suggests a batch to certify, using batch proposals to communicate and maintain agreement on the DAG's status. Each batch proposal contains a Batch ID, Batch Header and a Batch Certificate.
Block: A block is created when the commit rule is activated in AleoBFT. It includes a block header, a sequence of batch certificates, ratifications, solutions, transactions, and a list of aborted transmission IDs.
The true mark of a successful blockchain lies in its ability to foster a vibrant community and diverse applications. Aleo boasts a rapidly growing ecosystem with projects already exploring its potential across various domains:
Talking about recent updates - Aleo is now considered as one of the top 5 fastest-growing ecosystems for overall developers. Also, Aleo has completed the security audits of snarkOS & snarkVM, which was performed by Trail of Bits.
Aleo worked hard to make the technical details of the project easier to understand. They've simplified and explained the main basics in a straightforward way. For example:
As a validator and staking infrastructure provider, Chorus One is deeply impressed by Aleo's groundbreaking approach to privacy in the blockchain space. The potential to unlock entirely new use cases and empower individuals with greater control over their data resonates deeply with our mission to build a more inclusive and accessible crypto ecosystem.
We're particularly excited about the unique technology stack, including snarkOS and snarkVM, which pave the way for scalable and efficient privacy-preserving applications. We believe Aleo has the potential to significantly impact various industries, from DeFi and healthcare to supply chain management, and Chorus One is proud to be a part of this journey. We are looking forward to actively contributing to the network's security and growth through staking infrastructure and look forward to witnessing Aleo's continued development and the exciting applications it enables.
Website: https://aleo.org/
Twitter: https://twitter.com/AleoHQ
Youtube: https://www.youtube.com/@AleoLabs/featured
Github: https://github.com/AleoHQ
Discord: https://discord.gg/aleo
About Chorus One
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 50+ Proof-of-Stake networks, including Ethereum, Cosmos, Solana, Avalanche, and Near, amongst others. Since 2018, we have been at the forefront of the PoS industry and now offer easy enterprise-grade staking solutions, industry-leading research, and also invest in some of the most cutting-edge protocols through Chorus Ventures.
Since its introduction in 2008, the Bitcoin whitepaper has marked the beginning of a transformative journey. Nations have embraced it as official currency, companies have added Bitcoin to their assets, and in 2024, Bitcoin ETFs are actively being traded. Despite these advancements, Bitcoin has struggled to shed the perception of being merely a store of value, akin to digital gold. While it's true that facilitating smart contracts was not Bitcoin's initial aim, the explosive growth of decentralized finance (DeFi) prompts a thought-provoking question: could the functionalities of DeFi be integrated into Bitcoin?
This is where Bitcoin Layer 2 solutions, or L2s, come into play. Below, we'll delve into one of the most thrilling projects in this realm - Stacks.
⚡️Chorus One is proud to join the latest team of signers on Stacks and further enhance the network’s security and decentralization. Learn more here.
It's widely acknowledged that Bitcoin stands as the most decentralized and secure blockchain. However, the high cost of its block space, low TPS, along with the need for additional computing resources among other factors, have made the development of smart contracts on its platform particularly challenging. This situation paved the way for the emergence of networks dedicated to smart contracting, such as Ethereum. Stacks, however, offers a solution to this issue.
Stacks is a novel layer built atop Bitcoin and it extends the utility of the most secure and decentralized blockchain by introducing smart contracts and dApps functionalities without altering Bitcoin's core protocol. This integration is facilitated through the Proof of Transfer (PoX) consensus mechanism, a pioneering approach that reuses Bitcoin’s Proof of Work (PoW) to secure the Stacks network, enabling smart contracts that directly interact with Bitcoin state and transactions. The goal of the Stacks layer is to grow the Bitcoin economy, by turning BTC into a productive rather than passive asset, and by enabling various decentralized applications. The Stacks layer has its own global ledger and execution environment, to support smart contracts and to not overwhelm the Bitcoin blockchain with additional transactions. It also provides mechanisms for higher performance, such as fast blocks, decentralized peg, and subnets.
The question of the necessity for a Bitcoin Layer 2 revolves around the potential of integrating fully-expressive smart contracts into Bitcoin. Successfully embedding such functionality could revolutionize Bitcoin's application, ushering in new use cases worth hundreds of billions, including stablecoins, NFTs, and Automated Market Makers (AMMs). This evolution would transform Bitcoin from a passive asset into a cornerstone of digital finance, significantly boosting its demand, value, and utility by enabling a wide array of yet-to-be-explored applications.
For blockchains with native smart contract capabilities, essential features include the ability for smart contracts to be fully secured by the network's security mechanisms, such as hash power in Proof of Work (PoW) systems or staked assets in Proof of Stake (PoS) systems. This ensures that smart contracts benefit from the same level of security as the underlying blockchain. The smart contracts not only need to have ‘read’ but also ‘write’ capabilities. As a layer on top of Bitcoin, Stacks plans to bring these features to Bitcoin through the following elements:
STX: STX, the native token of Stacks, plays a pivotal role in the PoX (Proof-of-Transfer) consensus mechanism, serving two main functions: (a) incentivizing miners to secure the Stacks global ledger, which operates independently of Bitcoin's Layer 1, and (b) ensuring the operational continuity of the sBTC peg by providing rewards to threshold signers involved in the peg mechanism. STX was distributed to the public through the first-ever SEC-qualified token offering in US history and currently enjoys a market capitalization of over $4B.
PoX: Proof of Transfer (PoX) is a unique consensus mechanism to the Stacks blockchain that is designed to leverage the security and robustness of Bitcoin, while allowing Stacks to introduce smart contracts and decentralized applications (dApps) on top of Bitcoin. In typical Proof-of-work (PoW) systems, miners must solve complex mathematical problems. In PoX, miners must transfer a base cryptocurrency (in this case Bitcoin) to join the mining process. This Bitcoin is transferred to STX holders that participate in the network by sta(c)king their STX STX tokens, thus securing the network. So in PoX, you’re bidding Bitcoin in the hopes of being selected to add the next block to the chain versus committing computation power in the case of PoW. Like other networks, the miners on Stacks get block rewards but in STX and not BTC. This dual mechanism integrates the economic incentives of both Bitcoin and Stacks.
Stacking: Stacking is not staking, but the fundamental concept is very similar. Staking involves locking up token X and getting rewards with staking yields in the same token X. Eg - Stake SOL and get rewarded in SOL. Stacking mandates depositing STX tokens to get rewarded in a different token (BTC). This synergy between BTC and STX is interesting and actually incentivizes BTC holders to participate in the STX ecosystem. STX holders on the other side are incentivized to stack their tokens to be rewarded in arguably the most decentralized and secure cryptocurrency token BTC.
Signing: Post the Nakamoto release, the role between Miners and Stackers has been segregated. Where previously, miners decided the contents of the block and also decided whether or not to include them in the Stacks chain, now they would only be deciding the contents of the block and the stackers would be taking on the role of deciding whether to include them in the block or not. Stackers validate and sign blocks through a distributed signing protocol, requiring a significant fraction of locked STX to agree on block inclusion, thus preventing forks and enhancing the chain's integrity. Chorus One is proud to join the team of signers on Stacks along with other industry leaders likeBlockdaemon, NEAR Foundation, DeSpread, Alum Labs, Kiln, Luganodes, Copper, and Figment.
sBTC: sBTC is a fungible token that is pegged 1:1 with Bitcoin to enable Bitcoin holders to participate in the Stacks ecosystem. Users who want to interact with BTC and developers who want to create apps with BTC programmability can both use sBTC, thereby extending BTC’s utility beyond Bitcoin. To deposit BTC into sBTC, a Bitcoin holder would create a deposit transaction on the Bitcoin chain. This deposit transaction informs the protocol of how much BTC the holder has deposited, and to which Stacks address the holder wishes to receive the sBTC. The sBTC system responds to the deposit transaction by minting sBTC to the given Stacks address. To withdraw BTC, a Bitcoin holder creates a withdrawal transaction on the Bitcoin chain. This withdrawal transaction informs the protocol of how much sBTC the holder wishes to withdraw, from which Stacks address the sBTC should be withdrawn, and which Bitcoin address should receive the withdrawn BTC. In response to this transaction, the sBTC system burns the requested amount of sBTC from the given Stacks address and fulfills the withdrawal by issuing a BTC payment to the given BTC address with the same amount.
Clarity: Stacks also has its native programming language called Clarity, crafted with a focus on safety and security. The inspiration for Clarity's development was drawn from analyzing and addressing vulnerabilities commonly found in Solidity. By integrating these lessons, Clarity was meticulously designed to offer a secure coding environment, prioritizing the prevention of exploits right from its core. You can read more about Clarity in the online book - Clarity of Mind.
Total supply: ~1.82B
APY: 6% (BTC)
We currently support infrastructure for over 50 networks, and we're thrilled to announce that Stacks will mark our inaugural support for a Bitcoin Layer 2 solution. This is a significant milestone for Chorus One, largely due to the exceptional team behind Stacks, whose expertise and dedication have been evident over many years of development.
If you have STX tokens and would like to stack them, feel free to reach out to one of our experts at staking@chorus.one.
To read more about Stacks, we recommend the official documentation available in docs.stacks.co.
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 50+ Proof-of-Stake networks, including Ethereum, Cosmos, Solana, Avalanche, and Near, amongst others. Since 2018, we have been at the forefront of the PoS industry and now offer easy enterprise-grade staking solutions, industry-leading research, and also invest in some of the most cutting-edge protocols through Chorus Ventures.
Summary
A technical in-depth guide of our OPUS Pool to demystify pooled staking with Stakewise and restaking osETH on Eigenlayer with Chorus One.In a nutshell, the steps are as follows:
These simple steps will get you ready to participate in the restaking ecosystem. If you’re interested in reading more about what happens in each step, below we will unravel what happens under the hood.
Go to Opus Pool, connect your wallet and deposit some ETH into our Stakewise vault. Traditional staking usually requires a staker to deposit 32ETH to spin up a validator on Ethereum in order to start earning rewards. Our 1-click staking experience enables users to stake any amount, powered by Stakewise. Stakewise v3 offers a permissionless, non-custodial pooled staking solution enabling any node operator to create a “vault”. A vault is essentially an isolated staking pool managed by the node operator and providing an automated process for ETH deposits, reward distribution, and withdrawals. You can learn more about Stakewise in our extensive guide here.
Under the hood: On a more technical level, when you stake into our Stakewise Pool, the flow works as follows:
A user deposits ETH into our MAX-MeV Stakewise vault. Once enough ETH has accrued (32 ETH), we can deposit a new validator in our vault. This is done by running an additional piece of software, stakewise v3-operator, alongside our usual Ethereum validator infrastructure, which listens to Deposit events and initiates the validator registration process. This architecture offers some very unique features. For one, the permissionless onboarding. Stakewise makes it possible to create your own vault with customized experiences, such as a private vault- only allowing stake from whitelisted addresses, a public vault- allowing stake from everyone, MEV smoothing and many more. Secondly, the ability to initiate a forced-exit by the Stakewise DAO. The Ethereum protocol requires validator exit messages to be signed with the validator signing key (the key held by the node operator required to operate the validator for signing blocks and attestations).
This means that, until EIP-7002 is implemented to support signing exit messages with withdrawal credentials (the key the staker holds to withdraw their funds), users depend on the node operators to exit validators on their behalf. To remediate this potential attack vector in a fully permissionless environment, there are certain steps a node operator must go through when registering a new validator. They submit shards of their signing keys to all Oracles through a process known as Shamir-secret sharing, a secret sharing algorithm which enables trustless and secure sharing of distributed, private information. Moreover, the pre-signed exit transaction messages are sent to the oracles in an encrypted manner. This allows the DAO to exit a validator on their behalf, should a node operator go rogue. Once oracles have approved registration, the operator sends the validator registration transaction to the so-called Keeper contract- essentially the brain in the architecture- which executes the deposit on-chain. EIP-7002 is still in its design phase, but it will open up new solutions to remove the need for Oracles by enabling the execution layer to trigger validator exits under certain conditions.
After a successful validator registration process, we’re ready to run a validator and collect rewards in our vault. Similarly to other liquid staking protocols, Stakewise relies on several oracles to fetch rewards from the Beacon Chain. Since The Merge, Ethereum’s architecture consists of the Consensus Layer (“Beacon Chain” which contains the consensus state and validator management) and the Execution Layer (“the EVM” which handles execution payloads, maintains a mempool of transactions). While combining both layers facilitated an easy transition to a Proof-of-Stake chain, it left the communication between both layers via Engine API somewhat limited- the Consensus Layer can query the Execution layer, but not the other way round. Essentially this means there’s no trustless way for the EVM to connect to the Beacon Chain to e.g. fetch validator rewards data. As a workaround, Stakewise employs trusted Oracles which regularly fetch rewards data from the Beacon Chain and vote for the rewards/penalties from all vaults. The vault rewards are saved as a Merkle tree and uploaded to IPFS, e.g see this example. The Merkle root is saved in the Keepers contract, again, the brain of our architecture. If you’re not familiar with Merkle trees, proofs and roots, they are one of the founding blocks of how Ethereum works, here’s a recommended read.
Essentially, it’s a data structure that helps us verify data consistency and make efficient proofs of inclusion (Merkle-proofs) to verify a piece of data is in the tree. More concretely, since the Merkle root is stored in the Keepers contract, it’s easy to verify that the stored Merkle tree hasn’t been tampered with.
To keep a vault’s state up to date, the Keeper contract needs to be “harvested”, meaning that the vault can fetch the Merkle root from the Keeper and derive validators rewards/penalties to update its state. If the state isn’t updated in a specified timeframe, any user interaction will be blocked.
With EIP-4788, which is implemented in the upcoming Dencun Upgrade (currently being rolled out to all testnets), the parent (previous) beacon block root will be included directly into the execution block enabling the EVM to access the block root from a trusted source, and thus removing the need for an Oracle and instead, enshrining it in the protocol. The way it will work is similar to the implemented workaround- the parent beacon block root represents the hash of the entire header of the previous block. A smart contract deployed on Ethereum will hold a limited number of parent beacon block roots, such that the execution layer can derive the consensus state in a trustless manner.
With this foundational knowledge in mind, let’s look at a specific example transaction of someone depositing 0.01 ETH into our Stakewise vault:
You can see the address which deposited 0xe46825... calls the deposit function on the Chorus One vault address 0xe6d8d8… . As we mentioned in the previous section, the v3-operator listens to DepositEvents emitted. Looking at the event logs, we get a good glimpse into what happens when you deposit into a vault:
The address is recorded along with the amount of your stake (assets), resulting in a number of “shares”which are calculated as follows: assets * total shares in vault / total assets in vault, see contract code for reference. The calculated shares will be the indicator how much of the rewards accrued by the Ethereum validator will be paid out to the staking address.
Once you’ve deposited successfully in our Stakewise vault, you can go ahead and mint your osETH in 1-click. The minted osETH should be visible in your wallet after the transaction was successful. If it’s not visible, you may need to add the token manually, e.g. for MetaMask see this resource.
Under the hood: As mentioned above, Stakewise offers a liquid staking token called osETH to provide liquidity to its stakers. This is a fantastic improvement on the staking experience, because you get a representation of your staked ETH which you can use to earn additional yield in the DeFi world. During vault setup, a node operator may choose to configure a vault that allows to mint an ERC20 token or whether the vault is tokenless. The issued liquid staking token- osETH- is overcollateralized, meaning the underlying assets in the vault are worth more than the osETH issued in order to cover potential losses from slashing. The biggest risk for staking is the risk of getting slashed, e.g due to double signing, which could result in losing part of the stake. Slashing is usually the consequence of bad key management practices that optimise for speed rather than consistency. It’s therefore important for node operators to apply sound security and key management practices, in order to minimize the risk.
One interesting feature of osETH is that it has a built-in slashing protection mechanism for its stakers. During the minting process you might have noticed that you can only mint up to 90% of the staked ETH. The excess backing insures stakers against poor staking performance or slashing events. Such penalties are absorbed by the excess backing.
To keep track of this, Stakewise defines a certain parameter known as “position health” which monitors the value of osETH minted relative to the value of their ETH currently staked in the Vault (see in screenshot above). The value can be Healthy/Moderate/Risky/Unhealthy. A “Healthy” position means that minted osETH doesn’t exceed 90% of the staked ETH. If the value of minted osETH grows faster and suddenly exceeds 92% of the staked ETH in the vault, the position status will move to “Unhealthy”. Let’s look at a concrete example: Imagine a user minted osETH against a staked position worth 100 ETH in Vault X. Suddenly, Vault X decided to increase its fees much higher than other vaults. During an incident, the node operator was forced to migrate their keys and started producing inconsistent attestations and downtime causing inactivity leaks all resulting in penalties and lower profit accrued in the vault. On top of that the bull market hits and demand for Ethereum validator exceeds current supply making the validator activation queue extremely long, but still growing overall TVL. A month later the minted osETH is now worth 92.01 ETH, making the user's position status "Unhealthy" and opening up for liquidation because the value of minted osETH relative to their ETH stake exceeds the liquidation threshold, i.e. is >92% enabling the DAO to liquidate a vault (if you remember, they have the ability to exit validators on a node operator's behalf), in order to ensure the excess backing of osETH.
The final step in our OPUS Pool journey let’s you restake your freshly minted osETH and other liquid staking tokens with EigenLayer.
Now what’s Eigenlayer and why will it bring more yield? To sum it up: “Restaking offers stakers the flexibility to contribute to the security of multiple networks, potentially earning rewards, verifying trust, or engaging in blockchain events. Users that stake $ETH can opt-in to EigenLayer smart contracts to restake their $ETH and extend cryptoeconomic security to additional applications on the network”. To read more about how it works, head to our blog article on Eigenlayer.
Under the hood: As of the time of writing, no AVS are live on mainnet yet. Until the EigenLayer protocol goes live with EigenDA (AVS developed by the EigenLayer team), restakers will receive restaked points as a measure of the user’s contribution to the pooled security, while securing the opportunity to be rewarded as an early restaker. Once AVSs go live, you will be able to delegate to Chorus One and receive rewards from your restaked ETH or Liquid Staking Tokens. This graph below shows what will happen once we enter this Stage:
The (re-)staker deposits their osETH (or other Liquid Staking Tokens) into the EigenLayer StrategyManager contract, which is responsible for accounting and allowing restakers to deposit LSTs into the given strategy contract. When users deposit into the StrategyManager, the funds are transferred to the respective LST’s StrategyBaseTVLLimits contract e.g. osETH or stETH, which returns shares proportionally to the users stake. The number of shares is calculated using an internal exchange rate which depends on the total number of deposits.
Here’s an example transaction of a user depositing osETH into the StrategyManager via our OPUS Pool. The event logs show the address where the funds were deposited from (depositor), the address of the token contract (in this case osETH token contract), and the address of the strategy contract (the address of the osETH strategyBaseTvlLimits contract).
Once the AVSs go live on mainnet, restakers will be able to delegate their LSTs to Chorus One. This is done by calling a function on the DelegationManager which manages delegation and undelegation of the stakers to operators. As of now, this functionality is paused, so stay tuned for the next EigenLayer mainnet upgrade and don’t miss your chance to delegate your restaked tokens to your favourite node operator.
A step-by-step guide to staking ETH on OPUS Pool
Restake with EigenLayer Seamlessly via Chorus One's OPUS Pool: A Detailed Guide
Learn more about Adagio, Chorus One’s pioneering Ethereum MEV-Boost client
MEV Max - Introducing Chorus One’s Liquid Staking Pool on Stakewise V3
Considerations on the Future of Ethereum Staking
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 50+ Proof-of-Stake networks, including Ethereum, Cosmos, Solana, Avalanche, and Near, amongst others. Since 2018, we have been at the forefront of the PoS industry and now offer easy enterprise-grade staking solutions, industry-leading research, and also invest in some of the most cutting-edge protocols through Chorus Ventures.
After what might have been the most anticipated launch so far, we're thrilled to be part of the continued innovation of blockchain technology by championing Dymension, as they work to pioneer the 'Internet of RollApps' with their unique modular features. Chorus One runs a public validator node and has also invested in Dymension through Chorus Ventures.
Dymension makes it easy for anyone to create and deploy their own blockchain, while providing its users the infrastructure and flexibility to scale and compete with other modern-day blockchain implementations.
In this guide, we'll cover what Dymension is and how it's pushing the boundaries of blockchain capabilities.
Unlike traditional blockchains that integrate data availability, consensus, settlement, and execution into a single layer, Dymension adopts a modular approach. This innovative method allows delegating one or more of these components to external chains, significantly enhancing performance, scalability, and efficiency.
Dymension aims to improve upon the current reliance on shared bandwidth systems used by many popular blockchains by using a multi-layer blockchain protocol. Consisting of a network of modular blockchains, known as "RollApps", these blockchains are powered by the Dymension Hub which is responsible for both consensus and settlement.
While initially the Dymension team will oversee RollApp approvals, the network aims to evolve into a permissionless ecosystem with the ultimate goal of serving as a decentralization router that connects RollApps to the crypto economy. In the long run, this will allow Dymension to be a "Internet Service Provider" for crypto and blockchain technologies.
To further detail its architecture, Dymension utilizes the Cosmos SDK for interoperability across blockchains, enabling RollApps to efficiently communicate and transact. The use of Tendermint Core for consensus ensures high security and fast transactions across the network. This technical foundation allows Dymension to support a wide range of applications, from finance to gaming, by providing developers with the tools to create highly scalable and customizable solutions.
As Dymension evolves, its architecture is designed to support a growing ecosystem of decentralized applications, ultimately facilitating a seamless connection between users and blockchain services on a global scale.
Dymension's unique proposition lies in its sophisticated modular architecture, designed to decentralize and optimize the components of blockchain functionality. By enabling external chains to handle aspects like data availability, consensus, and execution separately, it aims to not only significantly boost performance but also provide improved scalability and efficiency for all.
Here's how the Dymension team explains the ecosystem:
Dymension is similar to a full-stack web application where users interact with RollApps (front-end), Dymension (back-end) acts as the coordinator for the ecosystem, and the data availability networks (database) provide a place to publicize data.
Using the Cosmos SDK, Dymension incorporates a staking mechanism that enables participants to stake or unstake tokens with validators. This feature is central to maintaining the security and integrity of the network, allowing stakeholders to contribute to the ecosystem actively.
To kick off Genesis Rolldrop Season 1, Dymension is working to incentivize its users and builders by providing a significant allocation of tokens to pay tribute to three verticals within crypto, culture, money, and tech.
The tokenomics ($DYM) as of Feb 6th is as follows:
Total Supply: 1,000,000,000
Chorus One Valoper address: dymvaloper1ema6flggqeakw3795cawttxfjspa48l4x0e2mh
The Inter-Blockchain Communication Protocol is an important aspect of Dymension. IBC is a battle-tested bridging protocol that allows secure communication between different chains. RollApps connect to the IBC economy via Dymension Hub, similar to how a server connects to the internet via an internet service provider.
Dymension is working to reduce the reliance on centralized and commonly used multi-sig bridges prevalent in Ethereum and L2 ecosystems with IBC-connected rollups. By utilizing IBC for rollups, Dymension validates that all funds deposited into a RollApp are as secure as the Dymension Hub itself.
We firmly believe Dymension stands at the forefront of the next generation of blockchain technology, with its modular architecture promising to improve upon scalability and efficiency challenges faced by traditional blockchains. As supporters and collaborators, we continue to advise the team to best position themselves for a successful mainnet launch and beyond.
We are excited about the potential of Dymension to revolutionize the blockchain ecosystem, reinforcing our commitment to innovation and the growth of blockchain technology.
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 50+ Proof-of-Stake networks, including Ethereum, Cosmos, Solana, Avalanche, and Near, amongst others. Since 2018, we have been at the forefront of the PoS industry and now offer easy enterprise-grade staking solutions, industry-leading research, and also invest in some of the most cutting-edge protocols through Chorus Ventures.
We're proud to announce our latest partnership with BitGo, an industry-leading digital asset custodian, to provide institutional-grade staking for ZetaChain. In this article, we provide an overview of everything you need to know about ZetaChain and how it works. To start staking ZETA seamlessly with Chorus One, simply reach out to us at staking@chorus.one!
Facing the decision of which blockchain to build on is among the most challenging dilemmas for developers. Various factors, including the security of the underlying chain, cost, and its throughput, play a crucial role in influencing this decision. With the proliferation of blockchains, it has become evident that no single chain can dominate them all. Thus, the notion of interoperability has gained significance. Interoperability entails the capacity for users to engage in transactions across multiple chains, resulting in increased liquidity, enhanced capitalization, a larger user base, and greater innovation in use cases overall. Numerous mechanisms have endeavored to address this challenge through means such as bridges (e.g., Wormhole, Allbridge), and interoperability standards (IBC). However, these initiatives still grapple with problems like centralization, diminished user experience, the necessity for protocols to conform to specific standards, and vulnerability to exploits. Achieving genuine interoperability remains elusive at present. This is precisely where ZetaChain steps in.
ZetaChain is a Proof-of-Stake blockchain built on Cosmos SDK and Tendermint PBFT (Practical Byzantine Fault Tolerance) consensus engine. As a result, ZetaChain enjoys fast block time and instant finality. Smart contracts on ZetaChain support arbitrary logic that executes conditionally on external chain events, and can directly update external chain states via its TSS (Threshold Signature Scheme) signed transactions. ZetaChain thereby enables omnichain dApps that interact with different blockchains natively and directly without wrapping or bridging any assets. Unlike Ethereum where a smart contract can be trusted to manage assets according to predetermined rules, except on ZetaChain, a smart contract can leverage and manage assets on any connected blockchain.
If you've ever explored bridging or engaging in cross-chain transactions, you've probably encountered the challenge of true interoperability. Blockchains usually operate as closed systems, limiting transactions to the state of their respective blockchain. External information integration into the blockchain without a trusted third party, like an oracle, is not reliably achievable. For transactions that span multiple blockchains, reliance on a trusted intermediary, often a CEX (centralized exchange), is currently necessary. Consequently, there's a lack of a decentralized, permissionless, and public service enabling generic atomic transactions involving multiple blockchains. Even platforms like Cosmos, while enabling the creation of interoperable blockchains, require additional bridging mechanisms to connect with chains beyond the IBC ecosystem.
ZetaChain aims to solves this problem of partial interoperability.
In this section, we break down the different architectural elements of ZetaChain and its roles.
Validators : ZetaChain uses the Tendermint consensus engine, each validator node can vote on block proposals with voting power proportional to the staking coins (ZETA) bonded. We cover more about the ZETA coin below. Just like other chains, validators need to be online all the time, ready to participate in the constantly growing block production. In exchange for their service, validators will receive block rewards, and potentially other rewards such as gas fees or processing fees, proportional to their bonded staking coins. Contained within each validator is the ZetaCore and ZetaClient. ZetaCore is responsible for producing the blockchain and maintaining the replicated state machine. ZetaClient is responsible for observing events on external chains and signing outbound transactions. ZetaCore and ZetaClient are bundled together and run by node operators. Anyone can become a node operator to participate in validation provided that enough ZETA are staked. Chorus One is one of the node operators and you can stake your ZETA with us to ensure high rewards backed by robust security.
Observers: Observers are tasked with monitoring external chains for relevant transactions. This observer system is segmented into two key roles: sequencers and verifiers. The sequencer's responsibility is to identify relevant external transactions, events, and states, reporting them to the verifiers. The verifiers verify and vote on ZetaChain to reach consensus. The sequencer does not need to be trusted, but at least one honest sequencer is needed for liveness.
Signers: ZetaChain possesses a set of standard ECDSA/EdDSA keys that facilitate authenticated interactions with external chains. To prevent any single entity or a small fraction of nodes from having the ability to sign messages on behalf of ZetaChain on external chains, these keys are distributed across various signers to ensure that only a supermajority of them can sign on behalf of ZetaChain and it employs bonded stakes and a system of positive and negative incentives to ensure economic safety.
In practice, all above roles (except sequencer) are collocated in the same computer node, sharing software and credentials such as validator keys and bonded stakes and the associated rewards/slashing.
ZETA token is a multi-chain utility token that play various roles like:
Total initial supply: 2,100,000,000 (two billion, one hundred million)
Inflation: 10% of the total supply (210m ZETA) is allocated to the initial emissions pool on ZetaChain. This pool allows for block rewards targeted to sustain and secure the network over the first 4 years of network growth. After this pool is depleted, the protocol will introduce a planned 2.5% inflation through validator rewards, separate from the emission curve. More information here.
As we’ve seen above, ZetaChain promotes true interoperability between different blockchains and has a unique mechanism to facilitate that. There’s no disagreement over the fact that we’ll have dozens of chains with their own use-cases and the current interoperability solutions do not provide a great user experience or efficient capital flow. We’re proud to be steadfast supporters of ZetaChain and the Cosmos ecosystem in general and look forward to the variety of applications that ZetaChain can enable. From multi-chain NFTs to omnichain DeFi, the possibilities are endless.
Ready to stake $ZETA? Simply reach out to us at staking@chorus.one, and we'll get you set up in no time!
About Chorus One
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 50+ Proof-of-Stake networks including Ethereum, Cosmos, Solana, Avalanche, and Near amongst others. Since 2018, we have been at the forefront of the PoS industry and now offer easy enterprise-grade staking solutions, industry-leading research, and also invest in some of the most cutting-edge protocols through Chorus Ventures.
In an era of rapid technological evolution, Soarchain emerges as a vanguard in the automotive industry, redefining the landscape of vehicle-based applications and services. By harnessing the power of blockchain and hardware, Soarchain simplifies the complexities of vehicular connectivity, offering a platform for applications ranging from real-time insurance adjustments to AI-driven diagnostics and safety enhancements. With its Layer-1 Decentralized Physical Infrastructure Network (DePIN) built on the Cosmos SDK, Soarchain is set to transform the mobility sector, offering a more inclusive, transparent, and scalable alternative to the proprietary networks dominating today's market.
In this article, we explore how Soarchain unlocks dePIN’s full potential.
Quick pit stop to share that we at Chorus One are on the journey with Soarchain as proud investors.
However, please note that our support and enthusiasm for this venture should not be interpreted as financial advice. While we're keen to explore the blockchain landscape with Soarchain, we advise you to make investment decisions based on your own research and judgment. Consider us as companions sharing insights, not as guides for your financial journey.
In a gist, DePIN refers to decentralized networks that employ the use of hardware to enhance data collection for specific use cases. For a wider view of the entire ecosystem, please refer to Mesari’s 2023 report.
Traditional Verification Methods and Conflicts of Interest:
Unwanted Permission Layers and Security Vulnerabilities:
Scalability Constraints and Oracle Problem:
Specific Network Challenges:
Verification in DePIN Projects:
Incentive Challenges:
Soarchain tackles these through decentralized sequencers, governance frameworks, and a layered approach to network architecture, enhancing scalability and privacy.
Soarchain introduces a robust architecture for onboarding new factory manufacturers and hardware providers in a secure and scalable manner.
Manufacturers can generate a Certificate Signing Request (CSR) using the on-chain Root Certificate through governance proposals. Soarchain aims to incorporate tier-1 manufacturers. This specifically targets those incorporating secure elements in their Electronic Control Units (ECUs) or modules, a growing trend for enhanced security in automotive electronics. This integration will unlock new possibilities on Soarchain, like supply chain management, manufacturing process optimization, and trustless Over-the-Air updates for ECU firmware/software, a long standing costly challenge.
The system allows factories to submit governance proposals for inclusion, followed by proposals to issue a certain number of certificates. A key concern is that issuing non-time-bound or non-quantity-bound certificates grants manufacturers indefinite production rights. This could lead to a lack of accountability for their manufacturing processes and the products they produce. This innovative approach leverages Cosmos SDK and democratizes the onboarding of new manufacturers. It ensures that every level of the manufacturing and device integration process is secure, flexible, transparent and scalable.
Scaling with the Runner Network - The Celestia of DePIN
To address scalability, Soarchain implements a layer-2 solution with runner nodes that handle the bulk of data processing. This significantly reduces the load on the main blockchain and enhances the network's capacity to handle large data transactions. Runner nodes in Soarchain parallel the function of sequencers in the Celestia network. They manage data flow, gather public keys, create Merkle trees, and submit these summaries to the blockchain. From the Layer 1 perspective, the addition of thousands of vehicles and hundreds of thousands of new messages translates to only a moderate increase in network transactions.
Soarchain employs a Verifiable Random Function (VRF) within its core layer-1 virtual machine to dynamically select a consensus group from the pool of runners, preventing data validation centralization and potential collusion, operating like a decentralized sequencer. Runners in the consensus group are tasked with receiving, ordering, and verifying messages from vehicles, using these to create Merkle trees. They then generate and submit claims about these trees to validate their honesty and correctness. The system involves a distributed key generation process (Shamir Secret sharing algorithm) and threshold public key encryption to ensure that the content each runner submits is identical, maintaining the integrity of the verification process.
Users can operate a 'runner' via the Motus Connect and Drive mobile app. This setup allows users to earn extra network rewards. Runners are akin to Celestia's light clients but with an added responsibility: they sequence messages and verify their authenticity, ensuring the content is original, unaltered, and plausible. Similarly, more runners in Soarchain increase the number of supported vehicles, thereby expanding the network's message broadcasting capacity (as long as a certain percentage of full / validator nodes operate as runners).
Runners are also required to delegate a minimum amount of tokens to a validator. This serves two purposes:
Just like that, Soarchain presents the first ever mobile / app based shared sequencer to operate light clients.
Soarchain has integrated zk-SNARKs, particularly through the Groth16 scheme, to ensure robust data verification while maintaining confidentiality. This technology allows vehicles to generate cryptographic proofs of data authenticity and integrity without revealing the underlying data, thereby preserving privacy.
The use of zk-SNARKs, particularly through the Groth16 scheme, allows for efficient management of multiple proofs for similar types of PID data, crucial in Soarchain's network. Soarchain employs a unique method to verify the plausibility of PIDs (Parameter IDs) through two approaches: individual analysis of each PID and joint analysis of PIDs with known high correlations. Each Performance Indicator Data (PID), like fuel pressure or engine temperature, is validated meticulously, ensuring the accuracy and reliability of data transmitted via distributed MQTT brokers. This process ensures user privacy, as it doesn't require decrypting plaintext data on the public blockchain. Instead, plausibility checks are conducted while preserving privacy. This is made possible through specially designed arithmetic circuits, verified using zero-knowledge methods, ensuring that no sensitive data is exposed during the verification process.
The oracle problem, particularly in the context of Soarchain, refers to the challenge blockchains face in accurately interacting with external, real-world data. For Soarchain, this data is physical, real-time mobility information generated by sensors, cameras, and actuators on vehicles and road users. The key issue is ensuring the data's authenticity and that the data sources are honest. To address this, Soarchain uses hardware equipped with a secure element, ensuring that a) the hardware runs the intended firmware, preserving the operational integrity, and b) private keys corresponding to public keys and certificates are securely stored, safeguarding the security, integrity, and authenticity of the data.
Once these pre-verification checks are completed, the data is transformed into "messages" akin to transactions and sent to Soarchain's verification layer. This layer constructs Merkle trees using these messages and generates a proof once a certain number of messages are aggregated. The proof is then submitted to the chain, and the metadata of the data is immutably recorded on the blockchain. This process enables any entity on the chain to interact with a reference to the proven and verified data originating from real-life sources.
To overcome the oracle problem's scalability constraints and complexities, Soarchain combines decentralized oracle systems with hardware-accelerated and proof-based mechanisms. While centralized oracle solutions pose a risk of single-point failure and require significant trust, decentralized oracles, though more secure, often lack a hardware-accelerated, proof-based system. Soarchain's runner architecture not only serves as an incentivized, trust-minimized oracle network, but it also acts as a scaling layer. This allows for the aggregation and proof of pre-verified data messages without needing to submit each message in full to the blockchain. This method significantly reduces the burden on the blockchain while maintaining the integrity and trustworthiness of the data being processed.
In conclusion, Soarchain stands at the forefront of revolutionizing decentralized mobility and related applications. Its robust Layer 1 blockchain technology enables a myriad of real-world applications, from decentralized ride-sharing platforms, offering a more equitable and transparent system, to smart parking solutions that ensure secure, fraud-resistant transactions. Additionally, Soarchain plays a pivotal role in the coordination of autonomous vehicles, promoting safety and efficiency through real-time communication and decentralized consensus.
Soarchain represents a significant leap forward in the world of decentralized networks. Its innovative governance framework, the integration of zk-SNARKs for data verification, and the unique approach of using runner nodes and a decentralized sequencer collectively forge a path towards a more secure, scalable, and trustable digital future. With these technologies, Soarchain is not just solving the present challenges of dePINs but also paving the way for the untapped potential of hardware based decentralized networks.
About Chorus One
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 50+ Proof-of-Stake networks including Ethereum, Cosmos, Solana, Avalanche, and Near amongst others. Since 2018, we have been at the forefront of the PoS industry and now offer easy enterprise-grade staking solutions, industry-leading research, and also invest in some of the most cutting-edge protocols through Chorus Ventures.
The Cosmos ecosystem is one of the most diverse in crypto as it allows for experimentation and simple bootstrapping of new ideas, due to the accessibility of the Cosmos SDK stack. The result is the launch of multiple chains on a monthly basis, each one targeting specific issues or innovative solutions. As a recent highlight, the Cosmos Hub is on the forefront, with the implementation of ICS v1 (“replicated security”), becoming the first shared security solution in production.
The previous edition of our Quarterly Insights report covered the basic concepts and related projects pushing the boundaries for innovative solutions in staking. You can download it here.
This article starts a series of reviews of well known projects, aiming to uncover the present state of these “long lived” protocols. This edition focuses on Injective, a fast and cheap blockchain built for finance, featuring 0.9s block times and less than $0.01 fee per transaction. Injective provides infrastructure that is optimized for enterprises to build a diverse array of institutional grade financialapplications. An example of a high level contribution is the module that allows the implementation of an on-chain order book. The OpenDeFi Foundation is the non-profit organization behind the Injective protocol. Backers include high profile names, such as Binance, Jump, Pantera and Mark Cuban.
Injective is a Layer 1 (L1) blockchain built on top of the Cosmos SDKand the CometBFT Consensus protocol. The network is operated by60 validators at the time of writing. The number of validators may seem low when compared to other delegated PoS blockchains (e.g.Solana: 1900 validators), but it can still be considered similar to otherCometBFT based chains. The protocol is proof-of-stake based and has a limited validator set to optimize for throughput. The expected tendency is for the network to be secured also by social consensus,with delegators working on identifying more reliable and trustedvalidators to delegate to.
In the Injective case, the super-majority is formed by 4 validators that hold more than 33% of voting power at the time of writing.Aware of the risks imposed by centralization, and to incentivize contributions from other node operators to the development of the ecosystem, the Open DeFi Foundation recently announced theFoundation Delegation Program to increase the voting power controlled by relatively smaller validators.
From a validator's perspective, Injective can be a demanding network to run due to its short block times and, consequently, higher chance of failing to sign blocks. This characteristic is reflected in the validator “uptime”, which varies from 80% to 99% on Injective amongst all validators, while for other networks the uptime is on average closer to 100%. The update process has consistently been well-managed and smooth. Overall, we have a positive impression of the network's technical architecture.
The most popular dApp on Injective is Helix, a decentralized exchange that allows for spot and derivatives trading of cross chain assets. More than $10B have been traded since the launch in November 2021, with derivatives being responsible for $9.3B. The total value locked in pools (TVL) is $11.5M and the most active perpetual markets are BTC/USDT and ETH/USDT. INJ/USDT is the most liquid spot market.
Helix creates a seamless trading experience, with a user interface comparable to a centralized exchange, low costs and advanced features, such as order types, graphical indicators and liquidity analysis. To start using Helix, users can connect from a Metamask, Keplr, Ledger, Cosmostation, Leap, or Trezor wallet.
The Open Liquidity Program (“OLP”) is an initiative recently announced to foment on-chain liquidity: beginning June 13, 2023,60,000 INJ can be earned during each epoch by those executing trades through the API or on decentralized exchanges built onInjective. The program prioritizes deep, long lasting liquidity, by using the following metrics to measure the quality of the activity: dual sidemarket making, uptime, volume and spread. All information on the reward calculations and API can be found in the OLP docs here.
Additionally, the first Injective Hackathon recently concluded, with the submission of 300 projects, and 357 builders, attracting developers, entrepreneurs, and blockchain enthusiasts, the four week online event fostered new innovations across Web3. Highlights from submissions involve options trading, asset management tools, money marketing platforms and NFT marketplaces. Additionally, the Injective Ecosystem Venture Group is a group of prominent institutions and venture funds that have come together to back the future of the protocol with a $150 million initiative. The focus is to support promising projects building within a diverse array of sectors including interoperability, DeFi, trading, PoS infrastructure, rollups and scalability solutions. Visit the official page to be informed on criteria and the process to apply.
Given Wormhole integration and IBC compatibility, from the userperspective, it is fairly easy and cheap to interact with multiple blockchains from- and to- Injective. According to the Map of Zones, Injective communicates with 19 different Cosmos chains. The biggest flow of assets happens between Injective and the CosmosHub.
In May 2022, the protocol started working with the Wormhole bridge, making it easier for users and developers to interact with other blockchains. The most common asset bridged to Injective isUSDT, with more than 11 million of USDT at the time of writing. Other bridged assets include wETH, USDC, SOL, wMATIC and LINK.
Also, in March 2023, Cascade was launched - a layer-2 testnet that utilizes the Solana’s Sea Level Virtual Machine (SVM) provided byEclipse. This means that Solana developers can test their apps for use in the Cosmos without needing to change the programming language or tooling used. More information can be found here. April 2023 was the time for Injective to start communicating with Polkadot. The integration happens through the Celer Bridge, and allows users to transfer INJ, ATOM, ASTR and DOT between the Injective blockchain and the Astar parachain. More information can be found here.
Injective mainnet is live since November 2021. INJ, its native token,has multiple purposes in the ecosystem, as it is used:
I. to secure the PoS chain;
II. to participate in the on-chain governance;
III. to pay for exchange fees, and in the buy back and burn model;
IV. as margin and collateral backing derivatives positions. The current supply of INJ is 600m tokens and it increases over time through block rewards - incentives to token holders when locking INJ to help secure the Proof of Stake (“PoS”) network (“staking rewards”).
The emission rate (“inflation”) at the time of writing is 10% per year, and 62.5% of INJ total supply is currently locked in staking, resulting in 15% yearly yield. INJ is being traded at $7.94 and the fully diluted market cap is $794million. INJ price has been showing resilience throughout this bearmarket, as it was able to recover a good part of its value, despitemost of the market still struggling with low prices in the same period.
According to IntoTheBlock, Injective has a 94% concentration bylarge holders, i.e. whales - addresses with more than 1%; and investors - addresses with more than 0.1% of circulating supply.
The protocol suggests a global minimum fee structure, meant tofavor those adding liquidity to markets, also known as “marketmakers''. Maker fee is 0.01% of the total amount of the order, whilemarket taker orders - those trading against the orderbook, pay0.02% of the trading amount. Although the maker/taker model iscommon on centralized exchanges, Injective fees are half of what auser would pay when trading on Binance, for example. For a more indepth analysis of fee models in different exchanges, we recommend this article by Deribit.
Additionally, as a way to support the applications, the protocol transfers 40% of trading fees back to the dApp. This value can be used to source the trading activity on the exchange, offering fee rebates and other incentives to increase financial yield to users. The other 60% are kept by the protocol and periodically auctioned in exchange for INJ. The INJ proceeds of this auction are then burned, thus creating a potential deflating mechanism in the total INJ supply. Each application built on top of Injective may implement fees and incentives in a slightly different way. For example, Helix adds discounts to the taker fees, depending on the amount of INJ staked by the user and the amount traded in the last 28 days. Discounts start at 7.5%, when staking 25 INJ and trading volume $100,000. It can get to 80% for users staking at least 75,000 INJ and $100m trading volume.
Injective has been actively working on growing its ecosystem, tackling the different aspects to promote the activity and adoption of the network. On the TVL level, Injective is the 52nd chain on the DeFiLlama ranking. There are relatively few spot and derivative markets with significant liquidity levels - greater than $10,000 on the top of the book, and trading volumes are still low compared to otherdecentralized exchanges. On the other hand, Injective provides a fully on-chain experience, in contrast with most decentralized exchanges, through its order book and seamless trading experience, including advanced order types and technical analysis tools, that are partially unique in the crypto space, and we consider to be good differentials for the protocol.
Centralization of stake in a small number of validators is another concern for this network. Both points are subjects of the initiatives created by the Foundation and presented in detail in the previous sections.
When looking at tokenomics, the INJ token is one of the most valuable assets in the Cosmos, second only to the $ATOM token according to Mintscan. It also has multiple use cases, from staking to buy back and burn auction, which tend to power the demand and keep its value in the future. In terms of price, it has shown resilience compared to most assets in the Cosmos ecosystem during the recent tumultuous times crypto and global markets went through. The staking yield of around 15% annually is also aligned with other high value Cosmos chains.
As our final impressions, Injective seems to be taking the right steps to address its short comings while pushing ahead with its coremission. Chorus One is an Injective validator. You can find more information on how to stake INJ tokens on https://chorus.one/crypto-stakingnetworks/injective or reach out to us: staking@chorus.one.
To stay up to date with Injective
Blog: https://blog.injective.com/
About Chorus One
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 50+ Proof-of-Stake networks including Ethereum, Cosmos, Solana, Avalanche, and Near amongst others. Since 2018, we have been at the forefront of the PoS industry and now offer easy enterprise-grade staking solutions, industry-leading research, and also invest in some of the most cutting-edge protocols through Chorus Ventures.
