Shawn

Results 46 issues of Shawn

How do we make sure there is no or minimal downtime whenever we do releases, be it a mev-commit node upgrade, contract upgrade or the chain upgrade?

Mev-commit chain (core) contract deployment is managed by our nomad infra. L1 contract deployments have been executed through a Makefile that runs scripts directly on my machine via keystore. Makefile...

We will need to setup up a multisig for our upcoming validator registry that is deployed on mainnet. Gnosis safe seems like an industry standard, relevant docs: * https://docs.safe.global/home/what-is-safe *...

Currently we do not backup data/events specific to bidder/provider registrations that reside from the core contracts, nor the staked ETH amounts residing in those contracts. For mainnet we should enable...

`17864` has been the only chain ID we've been using for instances of the mev-commit chain. Now that we're nearing mainnet, we should make all contracts, clients, etc. able to...

See validator opt-in roadmap notion doc. This PR implements the core logic for reputational validator staking, and stETH delegations. Future PRs will deal with remaining work, tracked in https://github.com/primev/mev-commit/issues/132

bridge e2e test has not been working since all contract bytecode (and therefore addresses) were changed in https://github.com/primevprotocol/contracts/pull/85

Currently mev-commit chain base fees accumulate directly to this [arbitrary placeholder address](https://github.com/primev/mev-commit-geth/blob/553c7c336fe185ce4c4169b6e9ad1e8e71943826/core/state_transition.go#L465). Contract fees can be withdrawn from the contracts with [this address](https://github.com/primev/mev-commit/blob/9529ee86ccd9917a19df15f0f7de8d14259edfee/contracts/scripts/DeployScripts.s.sol#L25). Neither of these accounts represent a treasury,...

Production L1 deployments could utilize ansible and a dedicated machine for building the contracts, and deploying to mainnet. For now I've been building and deploying to Holesky by running forge...