VolumeFi / paloma

The fast blockchain messenger protocol
Apache License 2.0
3 stars 2 forks source link

Redeploy Base compass with the new fee manager #2068

Closed verabehr closed 3 weeks ago

verabehr commented 1 month ago

Background

Since we had deployed the fee manager on Base after deploying Compass, they cannot be linked. We therefore need to redeploy the fee manager and compass again by removing and adding support for Base chain.

Todo

byte-bandit commented 1 month ago

New fee manager contract address: https://basescan.org/address/0xee8338ee133b6705a7144a407eeb64bf742b78f9

verabehr commented 1 month ago

@byte-bandit when the chain is added again, compass is deployed, doesn’t that mean that compass is again deployed before the fee manager is set?

byte-bandit commented 1 month ago

@byte-bandit when the chain is added again, compass is deployed, doesn’t that mean that compass is again deployed before the fee manager is set?

No deployment will be created for chains that do not have the fee manager property set. When a new chain is created, this value is left empty initially. So even though the current chain has this property set, the new one won't have it, and no deployment will be created until the value has been populated.

verabehr commented 1 month ago

proposal to remove base chain https://paloma.explorers.guru/proposal/107

taariq commented 4 weeks ago

Waiting for the Fee Manager vote to pass for Base: https://paloma.explorers.guru/proposal/113

taariq commented 4 weeks ago

Accidentally deleted 113. Redid the vote with https://paloma.explorers.guru/proposal/116

taariq commented 4 weeks ago

@byte-bandit Base appears not to be added Shows still IN_PROPOSAL via palomad q evm chains-infos --node https://rpc-1.paloma.nodes.guru

- abi: ""
  activeSmartContractID: "0"
  bytecode: null
  chainID: "8453"
  chainReferenceID: base-main
  constructorInput: null
  id: "0"
  minOnChainBalance: "1000000"
  referenceBlockHash: 0xe8423ce3f8bb2dc392c116e9676b7069204bc83959e9bc5e60bc037f18a88629
  referenceBlockHeight: "19293160"
  relayWeights:
    executionTime: "1.0"
    featureSet: "1.0"
    fee: "1.0"
    successRate: "1.0"
    uptime: "1.0"
  smartContractAddr: ""
  smartContractUniqueID: null
  status: IN_PROPOSAL
byte-bandit commented 4 weeks ago

@taariq That's fine. It's waiting for the fee manager vote to land.

taariq commented 4 weeks ago

@taariq That's fine. It's waiting for the fee manager vote to land.

FYI @webelf101

taariq commented 3 weeks ago

@byte-bandit @webelf101 closing as completed.