Currently, proposal "description" text is used to generate the L1 timelock salt-hash. This is inconvenient as leads to coordination messiness with proposal data generation and proposal submission; there is also no clear update (description text gets posted on chain regardless). There is no restriction or on-chain enforcement to how the l1timelock salt can get generated; this PR instead uses the action address and chain ids.
Note that the proposal monitor fetches the salt from chain data already, and thus does not need any modifications.
Currently, proposal "description" text is used to generate the L1 timelock salt-hash. This is inconvenient as leads to coordination messiness with proposal data generation and proposal submission; there is also no clear update (description text gets posted on chain regardless). There is no restriction or on-chain enforcement to how the l1timelock salt can get generated; this PR instead uses the action address and chain ids.
Note that the proposal monitor fetches the salt from chain data already, and thus does not need any modifications.