You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
safe transaction service has recently added support for aggregating signatures for off-chain messages.
the flow for them is similar to transactions, except they never get executed and instead are passed to other contracts, that check isValidSignature. for example, this enables sending cowswap orders in a completely off-chain manner.
One thing to keep in mind is that the way they are treated in safe UI is as a blocking call. If you want your 1271 signature back, you will have to wait for all signers to sign. You can use it as a way to kick off signatures for what you have locally, but then receive None back, and then you should go and fetch the signatures from the API using the client (or another wrapper method)
Overview
safe transaction service has recently added support for aggregating signatures for off-chain messages.
the flow for them is similar to transactions, except they never get executed and instead are passed to other contracts, that check
isValidSignature
. for example, this enables sending cowswap orders in a completely off-chain manner.we could support them via
AccountAPI.sign_message
Specification
see here for an example/reference:
https://gist.github.com/banteg/68ad51b133d447aa4a165bea0c7b91a1
see here for the client api:
https://safe-transaction-mainnet.safe.global/
Dependencies
depends on ApeWorX/ape#1508
The text was updated successfully, but these errors were encountered: