To add a new protocol, you will need to fork the intents_landscape repo and add two new files (protocol filter python file and a static data file) by following the steps in this section.

If updating you will also need to fork the repo, but will instead make changes to the relevant files for the protocol in question.

Using _example.py as a template, copy this file and name it after the protocol you wish to add. Once this is done, provide the following information in the python file: as a template, copy this file and name it after the protocol you wish to add. Once this is done, provide the following information in the python file:

• Contract addresses for the protocol
• ABI (and/or function identifiers if needed) for referenced contracts
• Supported chains for protocol
• Deposit and fill function and event names

When specifying deposit information, only a deposit event is needed (deposit transactions are optional), however when providing fill information it is important to add a fill function name. Since most protocols will reject multiple transactions attempting to fill an already filled order, to accurately record multiple attempted or otherwise) fills it is VERY IMPORTANT to add a fill function filter as reverted events will not be recorded on the blockchain. Only adding a fill event filter will not result in reverted txs being picked up and thus will not fully provide filler competitive dynamics data.

Once a new protocol has been added, make sure to add it to the ENABLE_PROTOCOLS key in enabled_protocols.py .

Using the relevant protocol entry in intents_landscape make the required changes.

Please be especially careful with the following fields as it's important to consider carefully how the design of the protocol results in possible scores in these categories and clearly explain the justification.

• auction_design / auction_design_ranking / auction_design_details
• auction_openness / auction_openness_details
• filler_diversity / filler_diversity_details
• censorship_resistance / censorship_resistance_details
• filler_failure_resistance / filler_failure_resistance_details

The only accepted values for auction_openness, filler_diversity, censorship_resistance and filler_failure_resistance are Excellent / Good / Average / Poor.

After double checking the steps above to ensure the submission is valid (also see Contributions Guidelines), please open a PR to merge your changes to the `main` branch. Please only make changes to ONE protocol per PR.

To update information about an existing protocol, you will need to you will need to fork the intents_landscape and make changes to the relevant files for the protocol in question.

Note : if the changes relate to a major new version of the protocol which has breaking changes either in contract address / function or event names, please consider instead adding the new version as a new protocol and not updating the existing protocol definition files.

For example, for Across protocol there are two distinct versions that are each treated independently as acrossv2 and acrossv3.

If the changes relate to metadata or general information about the protocol, skip to part 2.

Using the relevant protocol entry in protocol_data make the required changes to any of the following:

• Contract addresses for the protocol
• ABI (and/or function identifiers if needed) for referenced contracts
• Supported chains for protocol
• Deposit and fill function and event names

When specifying deposit information, only a deposit event is needed (deposit transactions are optional), however when providing fill information it is important to add a fill function name. Since most protocols will reject multiple transactions attempting to fill an already filled order, to accurately record multiple attempted or otherwise) fills it is VERY IMPORTANT to add a fill function filter as reverted events will not be recorded on the blockchain. Only adding a fill event filter will not result in reverted txs being picked up and thus will not fully provide filler competitive dynamics data.

Using the relevant protocol entry in intents_landscape make the required changes.

Please be especially careful with the following fields as it’s important to consider carefully how the design of the protocol results in possible scores in these categories and clearly explain the justification.

• auction_design / auction_design_ranking / auction_design_details
• auction_openness / auction_openness_details
• filler_diversity / filler_diversity_details
• censorship_resistance / censorship_resistance_details
• filler_failure_resistance / filler_failure_resistance_details

The only accepted values for auction_openness, filler_diversity, censorship_resistance and filler_failure_resistance are Excellent / Good / Average / Poor.

After double checking the steps above to ensure the submission is valid (also see Contributions Guidelines), please only make changes to ONE protocol per PR.