Introducing: B-Harvest

Introducing B-Harvest: Unleashing Cosmos with dYdX!

Greetings, dYdX community!

I am Tree from B-Harvest! Get ready to embark on an extraordinary journey with B-Harvest. Since 2018, we’re known as Validators, Market Makers, and Research Kings. With extensive experience in validating across 25+ mainnets, including Cosmos-Hub, Axelar, Osmosis, Sui, and Secret, we’re here to bring our expertise to the dYdX Chain.

Validation is just the beginning. We’re R&D enthusiasts, making technical contributions to the Cosmos ecosystem and beyond. Our focus on enhancing Tendermint Core, Cosmos-SDK, and exploring performance improvements for appchains sets the stage for collaboration to take dYdX v4 to new heights.

And let’s not overlook our extensive trading experience. Allow us to introduce B-Harvest TaaS (Trading As A Service), born out of the synergy deriving from five years of blockchain research experience, TaaS is a powerhouse comprising four TradFi trading experts with a staggering combined experience of over 50 years. We’ve meticulously handpicked the crème de la crème, driven by our commitment to delivering unparalleled trading as a service for our partner DeFi protocols.

But that’s not all. We’re excited to join forces with dYdX to incubate and energize the Korean trading and dev community. Expert trading, innovation, and more await as we collaborate for mutual growth.

We have experience incubating Crescent DEX and believe in the paradigm shift dYdX will bring to Cosmos, elevating the DeFi experience and attracting a flourishing ecosystem.Get ready to revolutionize the game with B-Harvest. Together, we’ll leave an indelible mark on Cosmos. Excited to be onboard, and let the adventure begin!




Hi @Tree , B-Harvest team,

Appreciate you posting your profile! It’d be helpful if you could fill in your details and answer the relevant questions listed in the Validator Introduction Framework.

Please note that using the above intro format is encouraged but optional. We view this as an effective way for community members to evaluate the potential validators of dYdX v4 using a consistent, standardized framework. Many thanks!

Hey @Cliff ! Thanks for the suggestion We have written out the information in accordance with the new template, but cannot edit our post. Do you know how this can be done?

Hey @Tree ! It’d be great if you could just provide the details based on the framework as a separate reply in this post. Thanks!


  1. Entity name and location
    B-Harvest, South Korea

  2. Infrastructure location

Our presence is distributed across various locations including South Korea, Singapore, the United States, Germany, and others.

  1. What kind of hardware do you run? Baremetal, cloud-based…? In what geographic regions?

We employ public cloud services such as AWS and GCP for virtual machine instances, as well as OVH and Vultr for baremetal, spanning regions across Asia, North America, and Europe.

  1. Technical make-up of team (elaborate on no. of dev ops engineers, experience, etc.)

Our team comprises five skilled DevOps engineers, each bringing a unique set of expertise in software development, cloud architecture, data engineering, and security. With our extensive knowledge in Cosmos module and backend development, we are adept at creating advanced tools that contribute to the enhancement of blockchain networks.

  1. Years of experience

Since 2018, more than five years of experience in the blockchain field.

  1. What other networks are you running validators for?

We have extensive experience in validating across 30+ mainnets, including Cosmos-Hub, Axelar, Osmosis, Sui, and Secret. Now, we’re bringing our expertise to the dYdX Chain.

  1. Based on your participation in any previous testnets, mainnets, are there any best practices to be aware of? What are some things that made previous testnets, mainnet launches successful and/or things to avoid that have gone poorly?

A testnet is a critical step in discovering and resolving issues by running various tests in the same environment as the mainnet. Therefore, it should be treated with the same amount of care and attention as the mainnet. Failure to run a testnet for a sufficient period of time can expose vulnerabilities in the mainnet and lead to a major security incident.

Testnets are divided into internal testnets and public testnets. After internal testing on the internal testnet, we proceed with the public testnet, which is similar to the mainnet.

  • The internal testnet performs random tests on core logic, detects edge cases, verifies that features work, and allows for a fresh start if code modifications are needed.
  • The public testnet is a stabilized version with most edge cases removed to stress test and gather end-user feedback.

It is recommended to run both mainnet and public testnet and build a monitoring and response system in parallel. It also should include 24-hour monitoring tools, situation-specific response guides, and emergency contact systems and rules (e.g. response in 2 hours). Troubleshooting guides for common error cases, periodic specification updates, and communication channels with validators are necessary to keep the network running reliably.

  1. Do you have a validator voting framework and process?

We monitor all proposals with internal dashboard, and when deciding to vote:

  1. One of us reviews the proposal and shares it with the team.
  2. The proposal is discussed by the research and DevOps team, sometimes involving the CEO and other members for diverse perspectives.
  3. External opinions from individuals outside our team, gathered through Twitter and forums, are taken into consideration.
  4. Separate Telegram and Messenger accounts are maintained for most Korean and international delegates to communicate with supporters and discuss governance matters.
  5. Final opinions, determined through the steps mentioned above, are publicly announced on Twitter, especially for significant issues.

Additionally, we actively propose necessary or beneficial measures directly to the on-chain governance system. Notably, we were the pioneers in advocating for governance on the Cosmos Hub and have continued to do so multiple times.

  1. Are you planning to play any additional roles in the dYdX ecosystem (e.g. market maker, trader, indexer, front-end, other)?

Apart from validation, we will be making technical contributions to the Cosmos ecosystem, enhancing Tendermint Core, Cosmos-SDK, and exploring performance improvements for appchains. We are also a powerhouse in Trading As A Service (TaaS) with a team of TradFi trading experts. We aim to deliver unparalleled trading as a service for our partner DeFi protocols.

  1. Are there other products or services you want to highlight that could be relevant for dYdX?

Yes, we’re proud to introduce B-Harvest TaaS (Trading As A Service), a synergy of five years of blockchain research experience leading to trading on partner exchanges. We are also excited about incubating and energizing the Korean trading and dev community in partnership with dYdX.

  1. Any notable contributions in other ecosystems that you would like to highlight for the community?

We have previously incubated Crescent DEX and have made significant technical contributions to the Cosmos ecosystem. Our focus on enhancing Tendermint Core, Cosmos-SDK, and exploring performance improvements for appchains underlines our commitment to collaboration and innovation

1 Like