Gravity Support

[MechanicalTyler]

Related Github tickets

• Pigeon Gravity - Register Orchestrator Keys With the Gravity Module VolumeFi/paloma#503
• Pigeon Gravity - Act as an oracle to observe ethereum events VolumeFi/paloma#515
• Pigeon Gravity - Send observed events to Paloma Gravity Bridge VolumeFi/paloma#516
• Pigeon Gravity - Relay transactions from the Paloma Gravity Bridge VolumeFi/paloma#518

Background

This PR contains the necessary Pigeon-side functionality to for the Gravity Bridge.

• Pigeon monitors Paloma for send-to-eth requests to an evm chain
• Pigeon monitors the evm chains for events of send-to-paloma and attests those to paloma
• The need to register orchestrator keys with paloma was removed because Pigeon already sends the necessary information to paloma

This is broken at the moment because upstream paloma changes to keep-alive seem to have left an out-of-sync proto lookup. Merging #256 should fix this.

I've also skimped on the testing here because I've been pushing hard to get a working bridge. I suggest we go to testnet and circle back to complete testing before mainnet.

Testing completed

• test coverage exists or has been added/updated
• tested in a private testnet

Breaking changes

• I have checked my code for breaking changes

[byte-bandit]

Looks pretty straight forward. I have left some comments, but mostly nitpicking.

There's also some TODOs left that we should address. Will there be a follow up ticket?

That being said, I suggest we wait before we drafted a new Pigeon release later today before bringing this back into master.

[MechanicalTyler]

I think I've addressed all of your comments @byte-bandit. This PR will remain in draft until both it and the Paloma PR are ready to be merged.

[MechanicalTyler]

This should now be ready for merge. Paloma has been fully merged.

[taariq]

LFG!