Avalanche Warp Messaging

[aaronbuchwald]

Documentation

https://github.com/ava-labs/subnet-evm/blob/warp-e2e/precompile/contracts/warp/README.md

Tasks

• Create messages database/backend that the validator is willing to sign #444
• Add signature request handler to the VM #445
• Create a new API endpoint and client (see plugin/evm/service.go and plugin/evm/client.go) to request and gather signatures (this can be replaced by a relayer that plugs into VM level App messaging) #446
• Pre-post precompile interface changes including VerifyWithContext + BuildWithContext placement #442
• Warp Precompile Solidity interface + Example Solidity contract to send and receive a message from Subnet A to Subnet B #443
• Warp Precompile #447
• Warp backend database pruning #471
• E2E Warp Demo and Basic E2E Test #448
• Warp E2E Stress Testing #449
• Add Warp Signers Threshold to Warp Message Format #698

[michaelkaplan13]

Calling out a dev dependency: We'll need the precompile solidity interface in order to filter for messages to be inserted into the messages database.

May want to consider moving the precompile solidity interface up to the top.

[aaronbuchwald]

Calling out a dev dependency: We'll need the precompile solidity interface in order to filter for messages to be inserted into the messages database.

May want to consider moving the precompile solidity interface up to the top.

The messages database in the first ticket should be the database of messages the validator is willing to sign, so there won't be a need to filter that as any message emitted by the precompile should go in.

Any message emitted by the Warp precompile, should be added to the database when it gets accepted, so it should just need the following interface:

type WarpBackend interface {
	AddMessage(ctx context.Context, unsignedMessage *teleporter.UnsignedMessage) error
	GetSignature(ctx context.Context, messageHash ids.ID) ([]byte, error)
}

I was thinking that the WarpBackend can take care of signing the message, so that it only needs to keep track of a messageHash and the signature that corresponds to it if present.

[aaronbuchwald]

@minghinmatthewlam to add a separate ticket to clean up the warp messages database and add to this ticket.

[minghinmatthewlam]

Added #471 into list of issues