chore: add comments

Author: yjamin

rust/main/chains/hyperlane-aleo/src/config.rs

@@ -31,6 +31,8 @@ impl ConnectionConf {
     ) -> Self {
         if let Some(consensus_heights) = consensus_heights {
             // Set the consensus heights in the environment.
+            // ZK proof generation is done differently for different chains and relies on these heights. These are hardcoded in the Aleo VM for all known networks, like testnet and mainnet.
+            // However, when we want to run the relayer with a local chain, that network is unknown and we need to set the correct heights there as well; this is the only way to set the heights.
             #[allow(unsafe_code)]
             unsafe {
                 // SAFETY:

rust/main/chains/hyperlane-aleo/src/types.rs

@@ -8,7 +8,7 @@ use snarkvm_console_account::Field;
 // The Aleo VM types all inherit a generic Network type, but that Type is not relevant for many structs of Aleo and is supposed to be more of an additional information for the internal VM processing.
 // They need this, because they generate ZK Proofs differently for different networks but the actual data of these types are the same across all Networks.
 // We pass CurrentNetwork into a lot of types, because we don't have to generate ZK Proofs in almost every situation - except when submitting a TX. There is one exception to this and that is when parsing/handling with Blocks.
-// The Block type verifies its validity on creation and that changes based on the Network type, thats why we have to pass the correct Type when dealing with blocks.
+// The Block type verifies its validity on creation and that changes based on the Network type, that's why we have to pass the correct Type when dealing with blocks.
 pub(crate) type CurrentNetwork = MainnetV0;
 /// TxID Type
 pub(crate) type TxID = AleoID<Field<TestnetV0>, { hrp2!("at") }>;