just to be clear the Mdw team did not refused to document anything (the mentioned issue was addressed, the endpoint at the time was not available for mainnet and testent Mdw instances)
-
that endpoint was in the repository from 24 Jul
-
at 2 Aug Shubhendu suggested me use
middleware/namesfor autosuggestion, without mentioning of that it may return outdated names: Add endpoint returning names starting with or contains passed string · Issue #114 · aeternity/aeternal · GitHub -
I was not able to use that endpoint and asked to document it in #121
-
at 20 Aug that endpoint was working: `middleware/names` returns "Not found" for registered names on testnet · Issue #120 · aeternity/aeternal · GitHub
-
at 23 Aug #121 was closed with the explanation of not actual “Not found” behavior instead of updating middleware documentation with
middleware/namesbehavior
I have to mention in general, that from time to time issues in middleware repository get closed without clear explanation and I have to reopen them several times to get them solved. Or they stay open but with an unclear tag like this one: Inconsistent fields naming in `middleware/names/reverse` · Issue #122 · aeternity/aeternal · GitHub
Also please note that the Mdw is a tool to index and query the aeternity blockchain data
I know it, I’m was asking for documentation or at least to make interface more obvious.
Please note also that the owner is not the the address associated with a name, for that you should use the pointers, as described in the protocol documentation.
It was my proposal as a workaround for issues like this one: Send to name in Base Wallet - #2 by vlad.chain. Usage of this approach was agreed with Stoyan and Philipp.
Also, wallet applications are the ones responsible to manage funds for the users, please do not try to shift responsibilities for it.
The Base app depends on the middleware and the aeternity node if they return unexpected results or changes existing functionality (like deploying update swagger operation ids by shekhar-shubhendu · Pull Request #124 · aeternity/aeternal · GitHub without any coordination with Base app team) it may break the Base app.