XLS-74d and XLS-75d: Account Permissions #257
Conversation
| ### 4.2. Failure Conditions | ||
|
|
||
| * The `Account` hasn't authorized the `Delegate` to send transactions on behalf of it. | ||
| * The `Account` hasn't authorized the `Delegate` to send this particular transaction type/granular permission on behalf of it. |
There was a problem hiding this comment.
might need to add another failure condition:
When the Account is the same as Delegate, will get temBAD_SIGNER.
| ### 3.2. Failure Conditions | ||
|
|
||
| * `Permissions` is too long (the limit is 10), or includes duplicates. | ||
| * Any of the specified permissions are invalid. |
There was a problem hiding this comment.
might need to add another failure condition:
When the Account is same as Delegate, will get temMALFORMED
|
|
||
| ### 4.3. State Changes | ||
|
|
||
| The transaction succeeds, and the fee is charged to the `Delegate` account. |
There was a problem hiding this comment.
Currently, when a transaction is sent by a delegated account without the necessary permissions, it results in a tecNO_PERMISSION error. tec error still charges the fee from the delegated account even the transaction does not succeed.
There was a problem hiding this comment.
Yes, this section only addresses possible state changes from successful transactions.
| Delegate: "rKYLIE......" | ||
| } | ||
| ``` | ||
|
|
There was a problem hiding this comment.
might need to add a situation for multi sign:
for example, alice gives bob TrustSet permission, bob sends TrustSet on behalf of alice but this delegation transaction is multisigned by bob's multi signers.
| Destination: "rCHARLIE......", | ||
| Delegate: "rALICE......" | ||
| } | ||
| ``` |
There was a problem hiding this comment.
although mentioned before, maybe add a short description saying that alice initiates the transaction and it will use alice's secret.
No description provided.