Mismatch in u/ ownership about stacks HOT 21 CLOSED

We're working on a profile updating tool for the typical user and should have it out in the next couple of days.
In the meantime, if you're somewhat tech savvy, you can update your profile as follows:

1. download/install Namecoin-Qt or Namecoind
2. use the OneName profile builder and grab the JSON
3. calculate your WIF formatted private key from the passphrase (just a sha256 then a conversion to base58check - you can use https://github.com/halfmoonlabs/coinkit for that)
4. import your WIF into your namecoin client (you should now see the username in your possession)
5. perform a "name update" operation with the new JSON profile data

from stacks.

Hi rxl,

Thanks for the tip. I'm savvy enough to have installed coinkit, however my python is rusty. What command do I run on the sha256([12 words given to me])?

Thanks again

edit: Figured it out, thank you so much!!!

from stacks.

check out the section "Custom brain wallet keypairs" - it handles the sha256 for you

from stacks.

Hi again rxl,

I've familiarized myself with coinkit's functions however now I am left with another problem:

The mnemonic I was given, when run through coinkit, outputs a different NMC address than what the blockchain has.

The blockchain says that NBmcAHJqvaBuHNagYXSdPyXo4AP7gVgKdb owns my u/
The mnemonic given to me outputs to N5jVY6wY8kZ3DKHvBRwgYbiXUN7Fk4VFVc.

What information can I provide you to help find out the root cause of this? I have the NMC available to donate to this project - I know you guys are burning a ton :).

I have my secret key that was emailed to me.

from stacks.

Saw you were having the same issue as me and thought it would be good to pipe up.

I've got to grips with coinkit and can import the passphrase into a NamecoinKeypair. If I dump the private key in 'wif' format, I can import it into Namecoin-QT fine. However the u/name I registered through the onename site doesn't show up in my client.

I then checked the address listed when I name_show for my registered u/name, this address listed in the result differs from my coinkit NamecoinKeypair.address like you've reported.

I checked the passphrase/private key was correct by importing it into my bitcoin client, which provides the same public address as that which was generated and is visible on my onename.io profile page. This makes me think that the passphrase I put into coinkit is correct and the error isn't there.

I'm more than likely the one doing something wrong, but it sounds to me like we're in similar situations

from stacks.

Ok, I'll look into this for you. Sometimes the name transfer hangs and doesn't get dispatched.

from stacks.

Hi @bobberb and @ChrisPapaioannou, can you please tell me your OneName usernames so we can look into this issue? This is most probably a case of name_update() not processing at our end and we can re-send it. Our servers got overloaded on launch day and since then we've added more backend infrastructure and are in the process of verifying that all user registrations got activated on the blockchain.

from stacks.

Hey, my username is u/chrisp. Thanks for looking into it

from stacks.

It was a failed name_update() at our end. Just resent it. Here is the transaction:

http://bitinfocharts.com/namecoin/tx/11a45dcea948ea50ab824fcd4cb1b6eda958e36c92a375cd6ccafdeef000ecc7

Try checking now if the ownership is correct. For everyone else who is experiencing the same issue, we're re-confirming all name_updates and will re-send them if we find any inconsistencies. Thanks for your patience!

from stacks.

u/jbrikman for me, thanks for the update.
On Mar 13, 2014 10:59 AM, "Muneeb Ali" [email protected] wrote:

It was a failed name_update() at our end. Just resent it. Here is the
transaction:

http://bitinfocharts.com/namecoin/tx/11a45dcea948ea50ab824fcd4cb1b6eda958e36c92a375cd6ccafdeef000ecc7

Try checking now if the ownership is correct. For everyone else who is
experiencing the same issue, we're re-confirming all name_updates and will
re-send them if we find any inconsistencies. Thanks for your patience!

Reply to this email directly or view it on GitHubhttps://github.com/onenameio/onename/issues/1#issuecomment-37542756
.

from stacks.

@muneeb-ali Brilliant, the name has now shown up in my client, thanks

from stacks.

@bobberb looks like you had the same problem and we resent a (successful) name_update. Do let me know if the issue has been resolved for you.

from stacks.

@bobberb I noticed your PGP public key isn't displaying right. If you're using pastebin to host your PGP key, make sure you click the RAW button and use that url.

For you, it's http://pastebin.com/raw.php?i=8kN7yfvS instead of http://pastebin.com/8kN7yfvS.

from stacks.

Also @bobberb, I would take down that screenshot. Even though you blocked out the passphrase, it wouldn't be that hard to hone in on a few of the words and brute force the rest.

(example: looks like the first letter in your first word is a lowercase "L" and the last word ends with "ion")

from stacks.

@rxl yes, the reason I was so prompted to edit so quickly after signing up was my mistake in not choosing the pastebin raw version. Good call.

from stacks.

@muneeb-ali

All resolved -- you guys rock!

from stacks.

Please check again, name_update's are not being sent for registrations through your site.
This is not an isolated case, it's systematic. I've checked with several names.
You are not releasing the names that are registered on your site!

from stacks.

Thanks for reporting this. We're under a spam attack as we speak and are holding the profiles in our "hot wallet" for longer than usual. We've confirmed that the profiles for earlier registrations were sent out correctly and for the recent/current registration there is a lag as we fight out the spam attack. We'll send out recent/current profiles in a bigger batch soon (right after we're done with handling the attack!) Thanks for being an early user and any pointers/help for mitigating the attack can help as well.

from stacks.

Can we email support to ask for the release of a given username? What is the current time one should wait for the usernames to be released?

from stacks.

@ianthius Here is the transaction that confirms your name transfer:

http://bitinfocharts.com/namecoin/tx/d90627b069a597accd1680d63080f89fc8fe767c30241b9b897ca32a0a290999

Please, confirm that your NMC address matches now. And yes, you can email [email protected] for support regarding this issue. We're also rolling out an update that should stop the issue from happening in the first place.

from stacks.

@syntx we were able to mitigate the attack on our servers and have re-enabled live name transfers, please check again and let us know if new name registrations are getting transferred out properly. Thanks!

from stacks.