feat: Add Move Authenticator support #442
Conversation
| /// and optionally wait for finalization. | ||
| pub async fn execute_with_move_authenticator<I: PTBArgumentList>( | ||
| mut self, | ||
| fn_call: MoveAuthenticatorFnCall<I>, |
There was a problem hiding this comment.
I did think about that. The problem is that the inputs need to be resolved from the transaction but we can only do that before the transaction is finished since we need information from the builder.
There was a problem hiding this comment.
the inputs need to be resolved from the transaction
Can you elaborate on that? What data is only available from the builder but not from the built tx?
There was a problem hiding this comment.
Basically the inputs to the auth fn must end up being inputs in the transaction, and we can't do that if we build the transaction first. Or at least it would not be as simple. We would have to have a whole separate process to amend the transaction with these inputs and again ensure that everythin is valid. So, probably possible but also probably quite complex. Still, I can give it a try later if you want.
There was a problem hiding this comment.
inputs to the auth fn must end up being inputs in the transaction
This is not the case, so we can simplify
DaughterOfMars
force-pushed
the
feat/move-auth
branch
from
b9e9baa to
48cab0d
Compare
thibault-martinez
force-pushed
the
feat/move-auth
branch
from
7d758a3 to
e9b223d
Compare
| } | ||
| } | ||
|
|
||
| impl PartialEq<&IdentifierRef> for Identifier { |
There was a problem hiding this comment.
I'm actually not sure why this is needed, to investigate
Description
Adds support for authenticating using an Abstract Account via a move authorization function. This PR adds basic support for constructing a Move Authenticator variant of the
UserSignatureand also convenience function to execute a transaction builder with the appropriate data.Closes iotaledger/iota#9407