Denis Davidyuk

SW can pretend that "transaction remove" exist on the protocol level by adding a button that would send 0 ae from the account to itself with the correct nonce and...

> Nonce is higher than needed it should be within current nonce + 1 and current nonce + 5 because otherwise, the node won't accept such tx. > This type...

https://aeternity-workspace.slack.com/archives/C01SL6FKMEZ/p1742900614348859

Alternatively, you can remember exposed addresses per domain to don't ask confirmation if it was exposed before. Because anyway aepp can remember the address in cookies, but it needs to...

The current approach to get [all registered names](https://github.com/aeternity/superhero-ui/blob/8a48d4cc817685e77462382e8be9893d58a6a60a/src/App.vue#L81) on the initial load seems inefficient. I'm proposing to resolve names using middleware exclusively and on-demand.

> The reason is that chainNames are from the backend and they are cached, so the new changes could be delayed. So, now it shows the correct name? What is...

I see the same issue:  https://superhero.com/users/ak_gvxNbZf5CuxYVfcUFoKAP4geZatWaC2Yy4jpx5vZoCKank4Gc the problem is that `linkPreview` is not present in response of [`/pin/`](https://raendom-backend.z52da5wt.xyz/pin/ak_gvxNbZf5CuxYVfcUFoKAP4geZatWaC2Yy4jpx5vZoCKank4Gc) endpoint

Currently, it works fine, but I propose adding metadata allowing tools (autorest) to understand that these integers are actually dates. The problem is that the metadata is not enough because...

I mean OpenApi, yep. > Human readabilty is a UI feature, not a protocol feature. Still, the node raw response may be seen by a human 🤷‍♀️ > One reason...

It is implemented in https://github.com/aeternity/aepp-calldata-js/pull/279 , it needs to be merged by @dincho and released after that.