Master the Mempool.
Master Value in Motion.

Easily Support Custom Derivation Paths for Ledger and Trezor Wallets

While you can hold every private key in the palm on your hand, there are a staggering number of possible wallet addresses that can be generated from a seed phrase. And  advanced users may take advantage of these possibilities by using custom derivation paths on their hardware wallets to select new addresses. 

The ability to choose a custom derivation path is popular among developers (who need to access test nets) and whales (who have many accounts that they use to secure funds). And support for hardware wallets and custom derivation paths is a commonly requested feature for leading applications.

Having a native hardware wallet integration was the most requested feature for the 
Gnosis Safe multisig. Thanks to Blocknative, we were able to deliver an easy and trusted way to use a Ledger or Trezor device with a multisig using Onboard.js.

— Lukas Schor, Product Manager For Gnosis Safe

The latest release of Onboard.js enhances our hardware support module, adding the ability to choose from common derivation paths or enter a custom derivation path. Read on to learn about what custom derivation paths are and why supporting them matters. 

8 Lessons to Help You Master the Mempool

We want to wish the entire community well during the COVID-19 pandemic. While things are turbulent right now, we wanted to share a new post that dives deep into the mempool so that you can dig into an important part of the Web3 ecosystem.

Blockchains are transaction machines. But on-chain data represents value-at-rest — confirmed transactions. While pre-chain, or mempool, data explores value-in motion — transactions in flight. 

To date, the industry has largely focused on value-at-rest. This is an important piece of the Web3 puzzle. But for any transaction to be included in a block, it must move through the mempool. And unlike the blockchain — which acts as a definitive record — the mempool is chaotic, fragmented, and often unpredictable. 

In the course of building infrastructure to monitor the mempool, we've learned a lot about how it works. And at ETHDenver 2020 Matt Cutler, Blocknative's CEO and co-founder, shared some important lessons in his talk Mastering the Mempool:

Does Your Web3 App Support Hardware Wallets?

Hardware wallets — such as Ledger and Trezor — are popular among crypto whales and traders. They provide an additional safeguard for digital assets. But that extra layer of protection presents a challenge for Web3 developers — as hardware wallets do not have any built-in user interface for selecting, viewing, and switching accounts or networks. 

Before now, if you wanted your product to support hardware wallets, you had to build a custom user interface from scratch. This takes serious time and effort.

Thankfully, those days are gone!

We are excited to introduce the latest update to Onboard.js — Blocknative’s open-source user onboarding framework. A new hardware wallet module makes it easy to add support for hardware wallets for users of your Web3 application.

When One Billion Ethereum Transactions?

Web3 is taking root — transitioning from proof-of-concepts to enterprise-grade solutions. As specialists in the global mempool and the associated value in motion, the team at Blocknative looked back at 2019 and wondered, "How many public blockchain transactions have ever happened?" This quickly lead to "How many new public blockchain transactions can we reasonably expect in the coming years?" 

We were surprised that, as far as we could tell, no one had previously published answers to either of these questions. So we set off to generate our own results. And today we're happy to share our findings.

The results were surprising, exciting, and encouraging.