Bitwise is acquiring @AttestantIO, a non-custodial institutional Ethereum staking provider with $4B in staked ether.
Why? We fell in love with the Attestant team and their work.
They are:
- Ethereum staking experts. Staked since Beacon chain genesis. CTO Jim McDonald @jgm has contributed to the consensus protocol, from design through specs to code.
- Open source contributors. Maintains Vouch (multi-node validator client) and Dirk (distributed remote keymanager), which is used by 23% of Lido's node operators.
- Engaged community members. Publishes research on client diversity, consensus node performance, mev, restaking, and more.
None of this will change post-acquisition. We'll aim to protect and amplify the protocol focus, open source contributions, and community engagement.
Over the coming months we'll rebrand Attestant to Bitwise "Onchain Solutions". At Bitwise, our goal remains to be a great partner to clients and good stewards of this ecosystem. Now expanding into non-custodial onchain investments solutions is a step we're thrilled to be taking.
Grateful and excited for the journey ahead together with the Attestant team —
@pintail_xyz It's definitely the case that not all builders provide payloads to all relays, because we commonly see a mix of payloads when querying multiple relays. I don't know the extent to which that this is the case, however.
@pintail_xyz Vouch will use the largest bid from all queried relays that isn't in the excluded list, so as long as at least one relay returns a payload from a non-excluded builder you won't have to use a local payload.
@mevproposerbot@ultrasoundmoney Bad bot. It was virtually all withdrawals, and the proposer lost out on better payloads due to the relays accepting them in the bid value.
@stevifi@superphiz@AttestantIO Vouch is a validator client, Dirk is our signer. The biggest difference between Dirk and web3signer is that Dirk uses threshold signing, which means that you don't need to have multiple copies of the same key on different computers for resilience, or rely on a central database.
@JayBuidl@superphiz@AttestantIO Vouch provides the same level of protection for execution clients as consensus clients, as for the consensus client to accept a block as valid its paired execution client must validate the payload as well.
@zkcat_eth@AttestantIO@superphiz Consensus and execution clients are paired; if the execution client paired with consensus client A accepts a block and the execution client paired with consensus client B does not accept the block the consensus clients will have different heads.
@sir_yves@AttestantIO@brian_armstrong@dcinvestor@coinbase It's very similar to the consensus layer as per https://t.co/0Jlb1k7sDk because consensus and execution nodes are paired, with the execution node being driven by the consensus node for deciding on the chain head.
Perhaps worth a new article...
New article looking at validator returns post-merge, comparing with my previous modelling, and considering the growing role of third-party block builders. https://t.co/X5CmrTuCgP
@TimBeiko Deprecate goerli. Point smart contract devs to sepolia. Start a new testnet with an initial 1MM validators and large total supply to allow validator testing. Bonus points for reducing ejection balance to 30 Ether.
With the #Ethereum Merge expected next week, we're delighted to share our latest article:
"Exploring Execution Block Rewards: September 2022"
https://t.co/Dxtz0s0STE