What problem does your feature solve?
Today all API signing flows assume that the user is signing a payload where the active wallet account is the source account of the transaction. This ignores scenarios where the account is an active signer on a shared account, or any other multi sign scenario on the classic side.
Also, with the addition on CAP-71, soroban auth entries can be delegated to other addresses(including contracts). Today, we only support the ability to sign an auth entry where your account is the address bound to the SOROBAN_CREDENTIALS_ADDRESS_V2.
What would you like to see?
- More flexible transaction signing constraints + changes to the sign tx modal to allow for mutli-sig patterns and to provide the UX for users to understand the weights involved and the delegation pattern.
ADDRESS_WITH_DELEGATES field should be explorable in the sign transaction modal. This is a tree of SorobanDelegateSignature that represents that delegation chain on the transaction. This would be mostly informational at transaction sign time but could inform the user on the signature state of the auth entries.- Support for signing auth entries where the bound address in
SOROBAN_CREDENTIALS_ADDRESS_V2 != the wallet account in order to provide support for signing as a delegate on behalf of another account.
What alternatives are there?
N/A
What problem does your feature solve?
Today all API signing flows assume that the user is signing a payload where the active wallet account is the source account of the transaction. This ignores scenarios where the account is an active signer on a shared account, or any other multi sign scenario on the classic side.
Also, with the addition on CAP-71, soroban auth entries can be delegated to other addresses(including contracts). Today, we only support the ability to sign an auth entry where your account is the address bound to the
SOROBAN_CREDENTIALS_ADDRESS_V2.What would you like to see?
ADDRESS_WITH_DELEGATESfield should be explorable in the sign transaction modal. This is a tree ofSorobanDelegateSignaturethat represents that delegation chain on the transaction. This would be mostly informational at transaction sign time but could inform the user on the signature state of the auth entries.SOROBAN_CREDENTIALS_ADDRESS_V2!= the wallet account in order to provide support for signing as a delegate on behalf of another account.What alternatives are there?
N/A