Is there a way to undo naming a account?
I have assigned a name to my account but would like to undo it.
Thanks
There is a new release of Waellet rolled out today v0.3.4 which allows extending names. It is already listed in firefox, the chrome web store is currently pending review. Release v0.5.8 · waellet/waellet · GitHub
Regarding base aepp:
The feature is being implemented here and will be released asap: NameDetails: Add ability to extend names by CedrikNikita · Pull Request #1368 · aeternity/aepp-base · GitHub
3 Likes
Correct - Utilities > Naming System > Your Names and there you can see the Extend button.
The Extend button is extending it to the maximum possible period, by default for now. - which as @marco.chain mentioned above, currently is 50000 blocks (specified in the protocol).
2 Likes
Can I also see somewhere when I have to update? Is it possible that this information also gets added 
thank you by the way! Great that you’ve integrated it.
1 Like
Nice! Thanks for sharing this. Also thanks for the info. So whenever I extend a name it automatically extends for 50000 blocks (but I can do it at any time, today for example). So I’ve got a time window of 50k blocks to do that from time to time 
an any way it answers my first question so thanks a lot!
If you have the extension installed in your browser it is automatically updated when the browser extension store approves the new version.
i talked to @hanssv.chain the last days because I have an idea where extending the TTL could be solved with a smart contract based solution which incentivizes users to extend names of others by getting a small reward.
I already started programming it and unfortunately some helpful and necessary AENS built-in methods for Sophia are missing and require another hardfork.
AENS.update is absolutely mandatory for the solution I want to provide
AENS.owner and AENS.expires_at would also be good and are - in my opinion - absolutely inevitable to build a secure and useful AENS marketplace (which is also something I respectively kryptokrauts are planning to work on)
I would definitely like to see these built-in methods being available with the next hardfork.
6 Likes
Thank you. Very valuable feedback. I’m not sure where we should collect this, I’m a bit worried that it gets buried here in the forum. You should maybe open an issue on GitHub for each of the functionality you suggest / need.
Any better suggestion?
actually there already exist issues that cover the required functionalities:
- New VM-function to lookup the TTL of a name - AENS.expire_by(name : string) : option(int) · Issue #179 · aeternity/aesophia · GitHub (AENS.expire_by)
- New VM-function to lookup the owner of a name - AENS.get_owner(name : string) : option(address) · Issue #188 · aeternity/aesophia · GitHub (AENS.get_owner)
AENS.update is - as far is I know - already implemented but not being published as it is consensus breaking.
there was also some kind of uncertainty I had regarding pointers. I think currently it is required to put in all existing pointers to the update. so there must be a way to return the map of all current pointers.
3 Likes
The pointer situation has to be clarified - probably the best would be to slightly change the protocol from the next hard fork and only allow pointers to be a “proper” map (i.e. unique keys) I think that would work best in the long run.
aesophia/GH-179/188 are already merged
Finally, given how AENS.update is implemented, it is trivial to extend a name:
// AENS.update available from IRIS hard-fork
AENS.update(owner, name, Some(RelativeTTL(extend_by)), None, None)
I.e. you don’t need to fill the pointers (== None) if you don’t intend to change them!
1 Like
that is nice!
so is it now already possible to perform AENS.update? because last information I got is that a hardfork is required to support this.
I also think that a map with unique keys should be the way to go. I got really confused these days discussing this here 
No, the linked documentation is for iris - the next hard-fork.
Unfortunately we can’t change the VM on the fly 
2 Likes
Are we going to be able to extend the names in the base aepp before they start expiring or will we have to use waellet? It would be ironic since waellet cannot even send to .chain names yet.
Edit: I see it is possible to extend on the base app now, good job team
3 Likes
Waellet can send to .chain names, make sure you have the latest version- 0.4.2
2 Likes
I don’'t see the option to Extend Name? I downloaded from playstore today
Hey,
This screen is on the web version of base aepps, and should be the same for android and ios as well (for base aepp version 0.22).
Can you try using it instead or manually downloading the apk from Release v1.0.3 · aeternity/aepp-base · GitHub ?
I’ll investigate what the issue is with the android playstore.
1 Like
@bruteforce.chain - curious if the above problem (set as default/extend name grayed out) had gotten any resolution? I’ve the same situation on just one of my .chain names.
On my cellphone the picture as is above, and I can’t ‘set as default’ that name (I want to) to the address. On PC, however, that name IS set as the default name and no problems.
Thanks!