Gonza Montiel e9fc4f271f Fix: 🏗️ Message encoding / decoding (#113) ... ## Summary of changes - We decided to remove the topics and nonce from the massage encoding since we don't use them (original commit: ee2a3f2fd4). - Besides, we already have a nonce at the Snowbridge message level f4ab5c2b2e/operator/primitives/snowbridge/inbound-queue/src/v2/message.rs (L105) - I had to recreate the static test for _encoding_ (happens in [DataHavenSnowbridgeMessages.sol](d12d40634f/contracts/src/libraries/DataHavenSnowbridgeMessages.sol) ) / _decoding_ (happens in [operator/primitives/bridge/src/lib.rs)](f9f9cc65fe/operator/primitives/bridge/src/lib.rs). Now it matches the current structure. The idea is that now we can test that we don't break the decoding in followup refactoring. - Fixes a problem with EigenLayer validator addresses. In all our contracts we were using `bytes32` to refer to a Solochain validator address. But on our Substrate change we actually expect AccountId20, so only 20 bytes. This was causing the decoding to fail. - I opted for the minimal change that would be to take the right-most 20 bytes to send that to our chain. But we might want aswell to limit our EigenLayer contracts to be only 20 bytes long. @ahmadkaouk showcase this [here](92a34c273c) - Adds a bash script to run the static test. The test will compile the contracts, run the encoding test, compile the operator, and run the decoding test. This saves a huge amount of time since we don't need to run the full e2e setup. The way of running it is the following: ```bash cd operator/test/scripts ./test_message_encoding.sh ``` - As a consequence of this PR, the execution relayer now works properly. EDIT: > [!IMPORTANT] **We decided to use 20-byte addresses in our contracts**. So what is stated above is not valid anymore. The change implies that the mapping from Ethereum addresses to bytes32 addresses now it's a mapping as follows: dd3ba99ac0/contracts/src/DataHavenServiceManager.sol (L51-L52) I've updated helper functions, tests, etc to be compliant with this change. The execution relayer and beefy relayer look stable now. --------- Co-authored-by: Ahmad Kaouk <ahmadkaouk.93@gmail.com> Co-authored-by: Ahmad Kaouk <56095276+ahmadkaouk@users.noreply.github.com>		2025-07-16 07:38:58 +00:00
..
build-binary.sh	fix: 🩹 update to allow BEEFY relayer to run correctly (#67)	2025-05-16 01:56:19 +00:00
build-contracts.sh	build: 🏗️ DataHaven operator setup (#6)	2025-03-17 17:57:14 +01:00
build-ethereum.sh	build: 🏗️ DataHaven operator setup (#6)	2025-03-17 17:57:14 +01:00
deploy-contracts.sh	build: 🏗️ DataHaven operator setup (#6)	2025-03-17 17:57:14 +01:00
deploy-datahaven.sh	fix: 🩹 update to allow BEEFY relayer to run correctly (#67)	2025-05-16 01:56:19 +00:00
deploy-ethereum.sh	build: 🏗️ DataHaven operator setup (#6)	2025-03-17 17:57:14 +01:00
force-beacon-checkpoint.sh	build: 🏗️ DataHaven operator setup (#6)	2025-03-17 17:57:14 +01:00
generate-beefy-checkpoint.sh	build: 🏗️ DataHaven operator setup (#6)	2025-03-17 17:57:14 +01:00
set-env.sh	build: 🏗️ DataHaven operator setup (#6)	2025-03-17 17:57:14 +01:00
start-relayer.sh	build: 🏗️ DataHaven operator setup (#6)	2025-03-17 17:57:14 +01:00
start-testnet.sh	fix: 🩹 update to allow BEEFY relayer to run correctly (#67)	2025-05-16 01:56:19 +00:00
test_message_encoding.sh	Fix: 🏗️ Message encoding / decoding (#113)	2025-07-16 07:38:58 +00:00