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
Issue: Lora incorrectly visualizes the senders of the transactions in case of multiple rekeyed accounts to the same address and multiple transactions within the same group transaction. An example from localnet is attached. In reality, there is one transactions per account but they are shown as if they all come from the same one.
The text was updated successfully, but these errors were encountered:
This was actually a conscious decision to group like that as it helps show that those transaction were initiated from the app and that the account being rekeyed to the app account is how that was possible. If we changed to use the sender lifeline, then it would almost appear as though the transaction came out of nowhere.
I do agree though that this scenario visually looks weird, so I'll discuss this further with the team. Maybe there is a better way to represent all these concepts.
Do those payment transactions have the same sender and receiver, or is the receiver the app account or one of the rekeyed accounts?
These transactions all have different senders (i.e. the addresses that were rekeyed) but the same receiver (i.e. the address to which they were rekeyed, which is an app).
For a better visualization, perhaps another type of horizontal line could be introduced to show which address approved which transaction (e.g. a dotted line with arrow) but the sender of the transaction would be the actual address.
Issue: Lora incorrectly visualizes the senders of the transactions in case of multiple rekeyed accounts to the same address and multiple transactions within the same group transaction. An example from localnet is attached. In reality, there is one transactions per account but they are shown as if they all come from the same one.
The text was updated successfully, but these errors were encountered: