fuellabs / bridge-message-predicates Goto Github PK

Migrate the predicate code from the bridge repo.

The current hashing routine to verify script bytecode is overly complex. Simplify by implementing in assembly instead

The latest fuel spec now allows for messages to be natively retryable from the protocol level. This means the predicate no longer needs to check for the correct inputs/outputs or a gas minimum. It only needs to check the inclusion of a specific transaction script (one that calls "process_message" on the target contract)

The MessageReceiver should have a function (maybe called fn requested_outputs() -> str[512]) that allows a contract to state what optional outputs they want to fully process a message. This would be used by an automated relayer service to better construct relaying transactions.

Refer to the original bridge repo to build a more generic message to contract predicate

There are a few breaking changes in the latest fuel core release that require a recompile of all code using the latest forc.

Tests are currently broken which I think has to do with the latest fuel-core release. Get the tests working and added back to the CI

We need to add tests for the negative cases as well as the positive cases.

There is currently no way to get the asset ID of a change output through the GTF opcode. Although the security of the predicate is still guaranteed due to only input coins of the base asset being allowed and other change or coin outputs are not allowed, it would still be a good idea to add an explicit check.

Investigate adding this check as soon as work begins on adding to the GTF opcode: FuelLabs/fuel-specs#402

CI is currently failing due to formatting checks, we need to update this predicate to use the latest version of sway that's compatible with beta4

blocked by: FuelLabs/sway#4601

InputCoins are currently being used in place of actual InputMessages until they are implemented in the rust SDK