@fuel-bridge/message-predicates
Advanced tools
Most messages sent from the base chain to Fuel will use a predicate as the message recipient. These predicates allow anyone to spend the `InputMessage` but verifies that a specific script is used in the transaction to ensure security and reliability that
Most messages sent from the base chain to Fuel will use a predicate as the message recipient. These predicates allow anyone to spend the InputMessage but verifies that a specific script is used in the transaction to ensure security and reliability that the message is handled appropriately.
The Message to Contract Predicate is for messages that are trying to send a data payload to a designated Fuel contract. This predicate verifies that the script bytecode hash for the transaction matches for the designated Message to Contract Script and that there are no other InputMessages with data in the transaction other than the first input. If these conditions are met, then the predicate evaluates as true.
The message to contract predicate relies on a script that performs only the following operation:
process_message on the contract with ID that matches the first 32 bytes in the message data field, while forwarding the exact amount of base asset specified in the InputMessage amount fieldBuild:
pnpm forc build --release
cargo run --bin fuel-contract-message-predicate
Run tests:
cargo test
Code must be formatted.
pnpm forc fmt
cargo fmt
The primary license for this repo is Apache 2.0, see LICENSE.
FAQs
Most messages sent from the base chain to Fuel will use a predicate as the message recipient. These predicates allow anyone to spend the `InputMessage` but verifies that a specific script is used in the transaction to ensure security and reliability that
We found that @fuel-bridge/message-predicates demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.