Skip to content

Releases: primev/mev-commit

v1.3.0-rc1

15 Dec 12:47
c95c50b

Choose a tag to compare

v1.3.0-rc1 Pre-release
Pre-release

Changelog

v1.2.4

31 Oct 18:10
ca8ad5c

Choose a tag to compare

Changelog

v1.2.3

21 Oct 03:52
eea5ad5

Choose a tag to compare

Changelog

  • eea5ad5 feat: release for validatoroptinhub, rewardsdistributor, blockrewardsmanager contracts, vanillaregistry changes (#838)

Added 3 new contracts + improvements to VanillaRegistry contract for more use cases. Also updated deployment script due to etherscan v1 api deprecation.

RewardsDistributor - For future token or ETH distributions to operators/validator owners/platforms.
Design: https://www.notion.so/primev/RewardDistributor-Design-2696865efd6f80b2a4f0e6b8fc3ab0c4

BlockRewardsManager: To be used by builders to pay proposers via the payProposer(address feeRecipient) function (includes optional protocol fee)

ValidatorOptInHub: Replacement for ValidatorOptInRouter contract, allows more registries to be added + design improvements:
https://www.notion.so/primev/Validator-Opt-In-Hub-vs-Opt-In-Router-2806865efd6f80ce9529e392ae3190c7

VanillaRegistry: MinStake/slash can now be 0, operator now must be whitelisted for a validator to be considered opted in.

v1.2.2

10 Oct 18:16

Choose a tag to compare

Patch release updating the provider node, exposing the bidder address for bids received by the provider api.

Changelog

  • 6d5eabb feat: expose bidder address to provider

v1.2.1

06 Oct 22:08
28a54c0

Choose a tag to compare

A non-breaking patch release updating the provider registry. This release does not affect bidder or provider nodes.

Changelog

v1.2.0

30 Sep 14:30
e01198b

Choose a tag to compare

This release is a major breaking release for the mev-commit network. We are launching a new settlement chain. The new chain will have a different chain ID and hence no state from the previous chain will be transferred. Users will have to withdraw their deposits/stakes/rewards and bridge them back to Ethereum L1. The old chain will still be available under a different URL for users to access and withdraw their funds. You will need to configure this URL manually to connect using the mev-commit node and issue transactions or directly access the contracts using JSON-RPC.

This marks a significant development for the team as we are using our own consensus client implementation. This calls for a fresh slate. Also upgrading the software should be straightforward as most of the contract interfaces and APIs will remain the same. There are a few new features:

Features

  • Bidders can now pass positional constraints for the transactions in the bid. Providers will have to accomodate this in the decision logic to prevent getting slashed. Check the docs for details on usage.
  • Bidder deposit UX is revamped. Previously bidders had to deposit funds into windows during which they would send bids. With the new UX, bidders can deposit funds per provider for sending bids. Also they can enable EIP-7702 authorization to automatically topup their deposits with providers. These deposits are not time-based as a result bidders dont need to keep depositing if they are not sending bids. They only need to deposit once their previous deposit is used up.
  • The slash amount in the bid is now set to the bid amount by default if not provided.

Breaking changes

  • For bidder nodes, the autodeposit mechanism is no longer available. Instead bidders should use the new deposit functionality. The APIs and CLI options for autodeposit are deprecated. Please check the docs for details.

NOTE: After Ethereum L1 block number 23476932 the mev-commit DNS addresses will point to the new protocol versions. The mev-commit nodes running the older version after this will see the node hitting errors related to contract calls. Separate DNS addresses will be provided for users to run the old version in order to withdraw all funds from the chain.

Full Changelog: v1.1.6...v1.2.0

v1.1.6

05 Aug 18:33
9a69838

Choose a tag to compare

This patch release adds a few new APIs for both Bidder and provider nodes.

Bidder API

  • GET /get_bid_info
    Provides detailed information about bids sent from the bidder node. It only saves history of the last 1000 blocks.
  • POST /claim_slashed_funds
    Used to claim any funds accumulated for the bidder in the provider registry as a result of slashing.

Provider API

  • GET /get_commitment_info
    Provides detailed information about commitments made by the provider node. It only saves history of the last 1000 blocks.
  • POST /withdraw_provider_reward
    Used to withdraw the accumulated provider rewards.

Notifications API

  • New notifications added related to failed transactions on mev-commit chain.

Changelog

v1.1.3

15 May 22:01

Choose a tag to compare

Changelog

v1.1.2

11 May 18:40
a9c75f0

Choose a tag to compare

Changelog

v1.1.1

15 Apr 23:01

Choose a tag to compare

This patch release brings some fixes to the mev-commit v.1.1.0 version.

  • Fixes issue preventing graceful shutdown of the nodes.
  • Fixes an issue in the oracle service to correctly mark commitments as settled.
  • There was also an issue with the new notifications added related to the validator opted-in status. An issue causing duplicate notifications was fixed.
  • Updates documentation and some network defaults for better checking incompatible software.

Users are requested to download the new release and update the nodes.

Full Changelog: v1.1.0...v1.1.1