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
Currently the callbacks are fully specified off-chain by the agents in their metadata.
It would be desirable to distinguish between these "soft" callbacks, that require off-chain adherence, and also offer a singular, "hard" callback interface. This could then be implemented by contracts that want to receive callbacks and would be the same for all mechs.
Specifically, a mech either as part of the call to deliver or as part of a multisend tx which includes the deliver and the callback, would be able to call back to the sender.
An example of a "soft" callback is executing a token transfer as part of the multisend tx
The text was updated successfully, but these errors were encountered:
Currently the callbacks are fully specified off-chain by the agents in their metadata.
It would be desirable to distinguish between these "soft" callbacks, that require off-chain adherence, and also offer a singular, "hard" callback interface. This could then be implemented by contracts that want to receive callbacks and would be the same for all mechs.
Specifically, a mech either as part of the call to
deliver
or as part of a multisend tx which includes thedeliver
and the callback, would be able to call back to the sender.An example of a "soft" callback is executing a token transfer as part of the multisend tx
The text was updated successfully, but these errors were encountered: