Possible conflict with onename Explorer and QT(my fault) about stacks

[shea256]

OK we'll look into this.

Have you tried waiting a bit for the changes to take effect? If you're updating using the profile explorer there might be slight delay, overriding your changes from the QT if it happens after the QT update.

[41GrapeApe]

I have the name back to the original address created by onename and have now issued an update with QT changing my location just as a test and will wait and see what happens. It has it's first confirmation and I don't see the change via the explorer but I'll wait.

[41GrapeApe]

It was a username created via the profile explorer that I then got the private key for and imported it into QT. Other than a small hiccup all went well. I could make changes happen via QT.

I then transferred ownership to a new address successfully and could make changes happen.

Then for some unknown reason I logged into onename using the original phrase when I created the username which should now not control the name.? I wasn't thinking about this at the time I was just wanting to change the background image and just complacently went to the profile explorer first forgetting I had transferred it. It let me change it several times...???

I then later wanted to add orgs to my profile so I went to QT to add that and realized what I had done. I still own the name (grapeape) under Manage names but I couldn't make any changes happen though.

I then transferred the name back to the original address crated by you guys and issued a new update but changes don't take effect either.

The profile explorer works I can login and change things. I show that I own the name in QT but can't make any changes with it.

I apologize for the novel here but I wanted make sure you know what i did.

[muneeb-ali]

In our system, I'm seeing that u/grapeape is owned by NCj1gq8uxTTtBgTGDcoviU1aRgD5bHQD4U and that address is not owned by any of our wallets.

I think there are two separate issues here. First, looks like a bug in our login system which was letting you login with your old passphrase. We'll fix that in the next version. The login system checks if you have the pvt-key to the NMC address which was the last known owner. We should fetch the latest owner NMC address from the blockchain instead of checking it against our DB/cache. Because you transferred the name manually, in our cache/DB the owner was the previous address and you had the right pvt-key for the address. We'll fix this bug. However, remember that this is just a login to web interface thing and there is no way for us to make any changes to your profile if you're logging in with a pvt-key / NMC address combination that is not actually the owner.

The second issue is that for some reason you're unable to make changes. Try to make sure that you didn't try to send an update that had more than 520 bytes. There is a known bug in Namecoin where if you put more than 520 bytes of data in the value field then you can no longer update that name anymore.

[41GrapeApe]

You are correct about the address that owns u/grapeape. That's mine. I thought it was the original address that came from you guys I guess not. Leave it to me to find a bug I'm notorious for this stuff.

I don't think I issued an update with more than 520 bytes, I had made that mistake before and got a warning but who knows really. Am I understanding you correctly if I did I may have lost the name permanently?

Are you able to tell me the original address that the name was created with?

Right now if I login to onename I can still make changes my concern now is once you fix the bug I will loose all control.

[muneeb-ali]

If you issued an update > 520 then yes the name is lost forever. Or well until it expires in ~8 months.

I think the original address was N2ER9ARUVdQLne5KPYFWjXhH4KUkz6ooEq

Well the changes you can make are local to our DB and they don't really matter because they will not be reflected on the blockchain.

[41GrapeApe]

Thanks for checking on this and explaining things to me. I don't think I issued an update >520 but it's possible. At this point I think I'll just let it expire and reclaim later.

I went ahead and reserved u/grape and I'll just use that. Lesson learned...

Thanks to both of you for your help. I'll wait to close this for a few hours just in case either of you had anything to add.

[shea256]

Perfect, thanks @41GrapeApe. Closing.