chore: remove table calculator

Author: ypatil12

docs/multichain/README.md

@@ -91,14 +91,9 @@ See full documentation in [`/source/CrossChainRegistry.md`](./source/CrossChainR
 
 #### Operator Table Calculator
 
-| File | Type |
-| -------- | -------- |
-| [`BN254TableCalculatorBase.sol`](../../src/contracts/multichain/BN254TableCalculatorBase.sol) | Abstract Contract |
-| [`ECDSATableCalculatorBase.sol`](../../src/contracts/multichain/BN254TableCalculatorBase.sol) | Abstract Contract |
+These contracts are **deployed by an AVS** and define custom stake weights of operators in an operatorSet. They are segmented by key-type. 
 
-These contracts are **deployed by an AVS** and define custom stake weights of operators in an operatorSet. The contracts are segmented by supported key-type (ECDSA & BN254). 
-
-See full documentation in [`/source/OperatorTableCalculator.md`](./source/OperatorTableCalculator.md).
+See full documentation in the [middleware repository](https://github.com/Layr-Labs/eigenlayer-middleware/tree/dev/docs).
 
 ---
 

docs/multichain/destination/CertificateVerifier.md

@@ -263,7 +263,7 @@ struct BN254OperatorInfo {
  * @dev The operatorInfoTreeRoot is the root of a merkle tree that contains the operatorInfos for each operator in the operatorSet.
  * It is calculated in this function and used by the `IBN254CertificateVerifier` to verify stakes against the non-signing operators
  *
- * @dev Retrieval of the `aggregatePubKey` depends on maintaining a key registry contract, see `BN254TableCalculatorBase` for an example implementation.
+ * @dev Retrieval of the `aggregatePubKey` depends on maintaining a key registry contract, see `BN254TableCalculatorBase` in the middleware repo for an example implementation.
  *
  * @dev The `totalWeights` array should be the same length as each individual `weights` array in `operatorInfos`.
  */