Transfer bug about Names

Hello, admin, I have a searious trouble, an important bug.
My aename is ‘dead.test’ for adress’ak_JFkVmYeY9iP4gmKexBHx7t1aAj1R6FGvBdWaZRBVLuuzWv83j’
I had sent 50 AE to ‘dead.test’ on ‘https://base.aepps.com/send’, the hash is ‘https://explorer.aepps.com/#/tx/th_g6oeTsyqeFKka7bX6Lcf7qBMxKrXfwEGcJDFnqyGBTnAaqNr7’,
but the recevied adress is ‘ak_2WZoa13VKHCamt2zL9Wid8ovmyvTEUzqBjDNGDNwuqwUQJZG4t’, its not mine, I lost 50 AE, I don’t know what reason and how it works.
According to aeknow.org the dead.test aens is registered to address:
https://www.aeknow.org/aens/query/Dead.test
Name hash: nm_k9C26LsmrrB8s6URnDAFmKbQfkQzA4A5aEFif2cFoDYYeXaJp

In the Base [email protected], we decided to use the owner field instead of pointers to make the interface more user-friendly. To get owner address for a specific name, the Base app requests middleware. Currently, https://mdw.aepps.com/middleware/names/dead.test returns two records for dead.test name that have different owners values:

  • ak_2WZoa13VKHCamt2zL9Wid8ovmyvTEUzqBjDNGDNwuqwUQJZG4t
  • ak_JFkVmYeY9iP4gmKexBHx7t1aAj1R6FGvBdWaZRBVLuuzWv83j

This wasn’t expected behavior, the Base app uses the first record.

The middleware team refused to document middleware/names endpoint properly: https://github.com/aeternity/aepp-middleware/issues/121

I have created an issue in Middleware to address this: https://github.com/aeternity/aepp-middleware/issues/150

hello @davidyuk,
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).

Also please note that the Mdw is a tool to index and query the aeternity blockchain data (not to be the base-app backend):
for the particular name the Mdw returns two records because the name have been registered two times:
by ak_2WZoa13VKHCamt2zL9Wid8ovmyvTEUzqBjDNGDNwuqwUQJZG4t
from height 16754 to height 92723 and afterwards by ak_JFkVmYeY9iP4gmKexBHx7t1aAj1R6FGvBdWaZRBVLuuzWv83j from 117285 to 167285, the latter being the current owner.

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.

Currently (height 133804) there are no pointers defined for the name dead.test as reported by both the nodes (ex sdk-mainnet, mdw node ):

{
  "id": "nm_k9C26LsmrrB8s6URnDAFmKbQfkQzA4A5aEFif2cFoDYYeXaJp",
  "pointers": [],
  "ttl": 167285
}

and the Mdw name search:

{
  "id": 1672468,
  "name": "dead.test",
  "name_hash": "nm_k9C26LsmrrB8s6URnDAFmKbQfkQzA4A5aEFif2cFoDYYeXaJp",
  "tx_hash": "th_6Q4sRA73iTjeTy6HAapEUsScTrohDr9y63gh3XswHnPWifdGV",
  "created_at_height": 117285,
  "owner": "ak_JFkVmYeY9iP4gmKexBHx7t1aAj1R6FGvBdWaZRBVLuuzWv83j",
  "expires_at": 167285,
  "pointers": null,
  "transaction_id": 7079696
}

Also, wallet applications are the ones responsible to manage funds for the users, please do not try to shift responsibilities for it.

1 Like

hi @Aeternity0, thanks for reporting the issue on the base-app, we will fix it asap.
We will refund your AE as soon as possible, which is most likely tomorrow. Thanks again for reporting!

1 Like

I hope this error can be fixed soon!
I think this is a serious bug, I hope that .aet will not be in the same situation.
I registered two more names, unfortunately, the same error occurred, which is very unsafe.
tmall.test yuan.test
One name corresponds to multiple addresses.
I feel that my feedback is valuable and worthy of reward, not just refund.
Also, I think that all you are developing too slowly. My son is almost three years old. Should he wait for his son to grow up?

@Aeternity0 your feedback is valuable indeed. and we appreciate it.

re: rewards: @ae-vlad is in charge of tipping. :slight_smile:

what are your expectations around speed of development? can you elaborate on this?

the base aepp makes between 2 and 4 releases per month and we address user input all the time.

thanks!

2 Likes

@noandrea

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)

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: https://github.com/aeternity/aepp-middleware/issues/122

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. 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 https://github.com/aeternity/aepp-middleware/pull/124 without any coordination with Base app team) it may break the Base app.

And then? NO follow up.
Who can help me?
Haven’t returned my lost tokens yet?
@Jantine @stoyan_ae @ae-vlad

I am happy to send you 50 ae. Just lmk know which address.

Thanks and apologies for the delay.

ak_2sv2qcpsW7TxZPbZmvJ1ycNR6a3UkMBvhC8PPmnaG18wkLzzNr
Thanks!

Here you go:
th_22rLX4PqhL2SfSoFJj1J7w1JMwDLrWgGbr3LXkPGqhthwyDFaM

Apologies for the delay.