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.
Chorus One has launched our liquid staking pool on Stakewise v3, enabling individuals to stake any amount of ETH and benefit from Chorus One’s enterprise-grade staking infrastructure and highest MEV yields! This article provides a step-by-step guide on how you can stake any amount of ETH on Chorus One’s vault, known as MEV Max.
To start staking on MEV Max, visit here.
Stakewise v3, introduced by the Stakewise DAO in 2022, addresses the challenge of stake centralization on Ethereum. The traditional complexity of setting up validators, including a 32ETH minimum requirement, technical demands, and the risk of financial penalties, has led to a decline in individual ETH staking. Stakewise v3 combats this by enhancing its liquid staking solution with mini staking pools called "Vaults." These Vaults make it possible for anyone to set up and run ETH nodes, mint osETH, accept delegations, or delegate ETH across multiple nodes in ambition to promote decentralization and mitigate network concentration. Vaults are completely customized by their operators, according to the configurations of their choice, fostering a diverse marketplace of ETH staking solutions.
Chorus One is expanding the possibilities of V3’s Vaults by extending our MEV optimization strategies beyond a select group of customers to encompass ALL ETH stakers. We hold decentralization as a core value, and through our partnership with Stakewise, take immense pride in making our enterprise staking infrastructure to everyone - all without any minimum requirements to stake ETH.
Below, we provide a brief breakdown of the various methods available for staking ETH and minting osETH with Chorus One. For a comprehensive understanding of the benefits associated with staking your ETH on Chorus One's liquid staking pools, we've covered all the details here. Check it out!
Chorus One's public vault invites users to stake any amount of ETH and mint osETH, enjoying the benefits of our enterprise-grade staking infrastructure, proven MEV strategies, world-class security measures, and network expertise. Access Chorus One’s Public Vault here.
We will also have private, tailor-made vaults for clients seeking individual, personalized agreements for their staked capital. With these private pools, user assets stay separate and are not commingled with other Vaults, thus offering the perks of liquid staking with enhanced security and all the other benefits Chorus One has to offer—higher MEV yields, top-notch security, network expertise, and more. To launch Private Vault with Chorus One, please reach out to us at staking@chorus.one.
In addition, we're making liquid staking more accessible to both our existing and new OPUS customers. Soon, our public pool will be seamlessly integrated into our Staking Dashboard, allowing OPUS users to dive into liquid staking, mint osETH, and leverage it in DeFi or hold it—all with just a few clicks! Stay tuned for more updates coming your way soon!
Now, moving on the staking guide.
6. After a few minutes, your transaction will be completed.
To learn more about our partnership with Stakewise, set up a private vault with Chorus One, or for any other queries, please reach out to us at staking@chorus.one
About Chorus One
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 45+ 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 immensely proud to support staking for Celestia - the first modular blockchain network that is optimized for ordering transaction data and making it available- as a genesis validator!
Celestia is a modular network that makes it easy for builders to launch their own blockchain by focusing solely on data availability. It allows developers to easily deploy blockchains on top of Celestia, much like deploying smart contracts. This accessibility empowers individuals to create their own unique rollups and blockchains, serving a multitude of purposes and ensuring scalability for a broader audience.
Celestia's data availability layer introduces innovative features like data availability sampling (DAS) and Namespaced Merkle trees (NMTs). DAS allows light nodes to verify data without downloading entire blocks, reducing costs compared to monolithic chains, while NMTs enable execution and settlement layers on Celestia to download transactions that are only relevant to them. Celestia offers its data availability layer to other chains for publishing data by paying for blobspace.
We've covered everything you need to know about Celestia in 10 questions - find it here!
As a permissionless network, Celestia uses Proof-of-Stake to secure its own chain. Like any other Cosmos network, users can help secure the network and engage in governance by delegating their TIA to a validator like Chorus One.
The following guide explains how you can stake your TIA easily with Chorus One.
TL;DR
Step 1: Login to https://wallet.keplr.app/ and search for Celestia
Step 2: Select the Chorus One validator
Step 3: Enter the amount of TIA you want to stake
Step 4: Approve the transaction. You have successfully staked TIA with Chorus One!
*Note that this guide has been written using the Celestia Mocha Testnet as it was written prior to Mainnet, however the steps remain the same.
After a few seconds, the transaction will be completed. You have now successfully staked TIA with Chorus One using Keplr!
If you have any support queries, please send a request at https://support.chorus.one/hc/en-us. If you would like to learn more about Celestia or start staking TIA with Chorus One, please reach out to us at staking@chorus.one
About Chorus One
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 45+ 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've developed a unique bridging solution that makes it possible for users to move their dYdX tokens to Cosmos, AND stake the tokens - all in just one go! To bridge and stake your DYDX, visit our novel bridging page
Who is this guide for: Users who wish to move their DYDX tokens from Ethereum to Cosmos + stake their tokens with Chorus One.
If you already have your DYDX tokens in the Cosmos ecosystem, you can stake them directly using your Keplr wallet, as explained here.
Step 1: Connect your Ethereum and Cosmos Wallets on Chorus One’s bridging page
Step 2: Enter the amount you want to Bridge and Stake
Step 3: Approve the Chorus One Bridge to interact with your wallet in order to stake your DYDX tokens
Step 4: Pre-Sign the transaction on your Cosmos/Keplr Wallet
Step 5: After 48 hours, your staking transaction will be completed through Chorus One!
Introducing Chorus One's Bridge and Stake solution for DYDX
The DYDX token, part of dYdX v4, serves a multi-faceted role. It empowers users to actively engage in governance decisions while also playing a crucial role in maintaining the network's operations and enhancing its security by staking their tokens.
To use and stake dYdX v4 tokens, the dYdX Chain needs to onboard users from various platforms, including rollups, Ethereum L1, other app-chains, and centralized exchanges, to its Cosmos version. Traditionally, bridging tokens from Ethereum to the Cosmos ecosystem has been a cumbersome activity.
To simplify the process and make staking on Cosmos a breeze for our customers, we have developed a novel solution, using dYdX's original bridging smart contract, that enables you to move your DYDX tokens from Ethereum to Cosmos in a swift, seamless transaction. Not only that, our bridging solution also allows you to stake your DYDX in the same flow, providing added convenience and efficiency!
To recap, dYdX v4 is the latest iteration of dYdX, one of the most prominent decentralized exchanges and premier trading platform for cryptocurrency. The DEX initially launched as an Ethereum-based Layer 2 solution and has now made a significant move by transitioning to its dedicated blockchain, known as the dYdX Chain (or dYdX v4), built using the Cosmos SDK. We've compiled all the essential information about the chain, complete with an in-depth exploration of their move to Cosmos and Chorus One's ongoing involvement with dYdX since the very outset. Check it out here.
1- Bridge & Stake in just 1 transaction: Our bridge offers a remarkably streamlined process for transferring DYDX tokens from Ethereum to Cosmos, setting a new standard in the industry. But it doesn't end here. You can take it a step further by staking your DYDX within the same transaction, allowing you to bridge and stake your DYDX simultaneously in one smooth action.
2- Simplified Onboarding: Our solution enables users from diverse platforms, including rollups, Ethereum L1, other app-chains, and centralized exchanges, to seamlessly join the dYdX Chain on Cosmos.
3- Security Assurance: Our bridging solution is underpinned by a meticulously audited smart contract, ensuring a straightforward and secure staking experience for users. The bridge contract underwent a thorough audit during its development by dYdX. Additionally, when it comes to our frontend and backend, we've adhered to strict secure software development practices as outlined by ISO requirements.
With an understanding of why we developed this bridging solution and how it enhances your staking experience, let’s proceed to a step-by-step walkthrough of utilizing our bridge.
*Since DYDX inflation goes to traders, dYdX stakers, in contrast, will receive 100% of the trading fees that are paid out in USDC.
2. To begin staking DYDX tokens with Chorus One, visit Chorus One’s bridging page and connect a) the Ethereum wallet that has DYDX tokens and b) the target Cosmos wallet where you wish to transfer the tokens to.
.png)
The next step helps you to pre-sign the staking transaction so that the tokens will be staked as soon as they reach the dYdX Chain, and you will be notified by us when the process has been completed if you choose to submit your email address.
We’re happy to answer any questions you may have! For any support queries, please visit here. Alternatively, if you’d like to learn more about staking with Chorus One, get started with staking, or anything else, please reach out to us at staking@chorus.one
About Chorus One
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 45+ 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.
Who is this guide for: Users who already have DYDX tokens in the Cosmos ecosystem and now want to stake them with Chorus One
If you wish to bridge your DYDX from Ethereum to Cosmos, check out our detailed guide here.
Step 1: Log into Keplr and connect your account
Step 2: Search for the dYdX Chain and look for the Chorus One Validator
Step 3: Click on Chorus One validator and enter the amount you would like to Stake
Step 4: Click on ‘Stake’ and follow the staking flow
Step 5: Approve Transaction. You have now staked DYDX with Chorus One!
dYdX v4 is the latest iteration of dYdX, one of the most prominent decentralized exchanges and premier trading platform for cryptocurrency. The DEX initially launched as an Ethereum-based Layer 2 solution and has now made a significant move by transitioning to its dedicated blockchain, known as the dYdX Chain (or dYdX v4), built using the Cosmos SDK. We've compiled all the essential information about the chain, complete with an in-depth exploration of their move to Cosmos and Chorus One's ongoing involvement with dYdX since the very outset in a comprehensive guide. Check it out here.
There are various utilities of the dYdX v4 token, DYDX, and amongst the most popular use cases are to engage in governance proposals and participate in staking.
To use and stake DYDX, the dYdX Chain needs to onboard users from various platforms, including rollups, Ethereum L1, other app-chains, and centralized exchanges, to its Cosmos version. To simplify the process and make staking on Cosmos a breeze for our customers, we have developed a novel solution that enables you to move your DYDX tokens from Ethereum to Cosmos and stake them with Chorus One in a swift, seamless transaction. If you wish to bridge your DYDX from Ethereum to Cosmos, check out our detailed guide here.
However, if you already have DYDX in the Cosmos ecosystem, you can directly stake them with Chorus One using your Keplr wallet. Let’s proceed to how you can do this with a step-by-step walkthrough.
*Since DYDX inflation goes to traders, dYdX stakers, in contrast, will receive 100% of the trading fees that are paid out in USDC.
5. Then, click on ‘Approve transaction’.
6. You will be redirected to the staking UX, which will show that your stake transaction is processing.
7. After a few minutes, your stake transaction will be complete! You can confirm that your transaction has processes by checking the block explorer here, as shown below.
8. Once you have confirmed your transaction, you have successfully staked DYDX with Chorus One!
We’re happy to answer any questions you may have! For any support queries, please visit here. Alternatively, if you’d like to learn more about staking with Chorus One, get started with staking, or anything else, reach out to us at staking@chorus.one
About Chorus One
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 45+ 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 Graph (GRT) is a decentralized indexing protocol for querying networks like Ethereum and IPFS. The protocol lets anyone make blockchain data easily accessible by building and publishing public APIs called subgraphs.
The Graph has decided to move the protocol to Arbitrum since bringing the protocol smart contracts onto a Layer 2 network allows for gas savings (up to 26x), faster transactions and still being able to ultimately rely on the security inherited from Ethereum.
For example, Indexers could open and close allocations to index a greater number of subgraphs with higher frequency, developers could deploy and update subgraphs with greater ease, delegators could delegate $GRT with increased frequency, and curators could add or remove signal to a larger number of subgraphs - all actions previously considered too cost-prohibitive to perform frequently due to gas.
You can delegate anytime over the next few weeks.
Currently, the reward share is 50% on Ethereum and 50% on Arbitrum.
Rest assured that your funds will be completely safe after the migration, and any unclaimed rewards will also move to Arbitrum, once you have moved your delegation.
4. You will then be taken to the following page. Here, Click on ‘Transfer Delegation’.
5. The Receiving Arbitrum One Wallet Address will already contain the same address as your current Ethereum wallet.
6. For your convenience, consider sending a small amount of ETH to this wallet address through the official Arbitrum bridge at https://bridge.arbitrum.io if you lack ETH to cover gas expenses. As an optional precaution, you can perform any transaction with the wallet to verify your control over it.
7. Then, click on the ‘Transfer delegation’ button. Your transfer will be initiated.
8. You will then see a countdown appear. Once the countdown reaches Zero, the migration will be completed, and your delegations will have moved to Arbitrum!
Note - Going forward, you will still be able to manage your delegations from this portal. Just make sure you're on the correct network, "Arbitrum One".
Here’s a walkthrough guide by The Graph Foundation to help you with the migration.
Additionally, if you have any questions, we are happy to answer them on our telegram channel at https://t.me/chorusone
About Chorus One
Chorus One is one of the biggest institutional staking providers globally operating infrastructure for 45+ 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.
Step 1: Log into the Sei App and connect your wallet.
Step 2: Search for Chorus One validator.
Step 3: Click on ‘Stake’ and review transaction
Step 4: Approve transaction
Step 5: You have now successfully staked SEI with Chorus One
Sei is a Cosmos SDK based open-source Layer 1 blockchain that leverages a novel consensus mechanism to become one of fastest blockchain in existence. It is purpose-built to cater to the unique requirements of decentralized trading, DEXes, and DeFi applications. Unlike traditional exchanges, which rely on an automated market maker (AMM) system, Sei adopts an order book model exchange approach, providing enhanced security, privacy, and user control over funds. By optimizing every layer of its stack, Sei creates a trading-focused blockchain that facilitates efficient and reliable transactions.
The easiest way to stake $SEI is using the Sei app at https://app.sei.io/stake
Welcome to the Fireblocks Guide for OPUS Staking. This guide is designed to help you stake with OPUS from your Fireblocks custody. We’ll leverage Metamask Institutional(MMI) chrome extension to seamlessly stake with OPUS.
1. First, connect your Fireblocks account to Metamask Institutional(MMI) wallet extension. Please download and install the extension from here.
2. Then, connect the desired Fireblocks custody vault to MMI.
3. To do this, in the Fireblocks custody, you need to click on the “Web3 Access” menu on the left hand navigation.
a. You will find a “Metamask Institutional user?” popup at the bottom of the page. Please click on “Connect account” to proceed with MMI connection.
b. Next, please select the desired vault to connect to Fireblocks and click on "Connect".
c. Metamask Institutional Wallet will show the custodian account connection request. Your Fireblocks vault will be connected to MMI once confirmed.
d. You should see the vault balance in MMI wallet
Now, your Fireblocks custody is connected to Metamask Institutional wallet. We are one step away from staking. We need to whitelist the staking contract now.
4. Whitelist the Batch Contract address in Fireblocks. In the Fireblocks Left hand navigation, please click on Whitelisted addresses menu and select the contract address on the screen.
5. OPUS Staking contract address is: 0x9b8c989FF27e948F55B53Bb19B3cC1947852E394
a. Goerli Testnet contract address is: 0x5FaDfdb7eFffd3B4AA03f0F29d9200Cf5F191F31
6. Based on your organisation approval policy, you will need to approval from multiple signers.
Next step is to stake with OPUS through MMI & Fireblocks custody.
7. Click on Connect wallet button in OPUS UX. Please select Metamask wallet in the walletconnect window.
8. Select the amount of stake on the slider and click “Confirm & Stake”
9. Approve the transaction on MMI
10. Approve the transaction on Fireblocks
11. After the transaction is confirmed on Fireblocks, you will see the staking transaction confirmation screen on OPUS.
