🚨 tld price incoming

Early legends who grabbed TLDs at 2.5 ATOM — you absolute chads.

Thank you for believing early.

As adoption heats up and since v2 is now live, we’re bumping the price to 25 ATOM per TLD.

Permanent ownership.

You set the rules + pricing on every subdomain.

All revenue from every registration under your TLD is all yours, baby!

No renewals. Ever.

All on Cosmos Hub.

This is real digital real estate. Prime names (.yourbrand, .game, .dao, country codes, etc.) are flying.

The window for launch pricing is closing.

Final call at 2.5 ATOM— then it jumps 10X on May 1st!

Go secure yours before the rocket leaves:

What TLD are you claiming? Drop it below :backhand_index_pointing_down:

#AtomRegistry #Cosmos #Web3 #OwnYourNamespace

2 Likes

I tried to get to get a tld and this happened.

  1. I used keplr+ ledger and got this error:
    **
    Incompatible Signing Requested**

Error: SIGN_MODE_DIRECT can’t be signed on Ledger. Contact the web app provider to fix this issue.
2. Then I used ledger directly and got the following two errors:
Commit failed: Cannot read properties of null (reading ‘sign’)
Commit failed: r.split is not a function
not sure what the issue is.

1 Like

oh shoot! my bad. i had to fix ledger so i put it on /ledger.html @ Atom Registry | Multi-TLD Web3 DNS on Cosmos Hub and haven’t updated the main page yet. /ledger.html works.

I am getting this error instead when I tried using the link you sent here:

  1. keplr + ledger:
    Commit failed: Chain error (2): Mismatched “*tx.ModeInfo_Multi”: {TagNum: 1, GotWireType: “varint” != WantWireType: “bytes”}: tx parse

  2. Using ledger directly:
    Commit failed: Ledger signing failed: Unknown error

1 Like

@l.malkowsky was you getting this on /ledger.html ?

YO,

Would be great if TLD are shown into keplr wallet directly.
I imagine it depends on keplr team to add it ?

1 Like

For ledger users just use this page: https://atomregistry.com/ledger.html. You can easily connect Keplr + Ledger and everything works smoothly :+1:

1 Like

i’ve prepared working DID compatible layer and shared it with @atomregistry to make domains resolvable through standard DID flows. it’s up to him whether he decides to adopt or integrate it. This is still a very early stage, so it’s not enough for full wallet adoption yet, but it’s small step forward :crossed_fingers: :atom_symbol: :purple_heart:

3 Likes

its not for me i keep getting the error:
Commit failed: Chain error (2): Mismatched “*tx.ModeInfo_Multi”: {TagNum: 1, GotWireType: “varint” != WantWireType: “bytes”}: tx parse

Not to be needy or nitpicky or anything but is it possible to add trezor, cosmostation and maybe tangem support for your creations @atomregistry ?

1 Like

good morning! shoot, this ain’t needy or nitpicky! its how builds get better. i have cosmostation. i’ll look into getting the others integrated. i’m also building a wallet bridge that will let any ibc wallet connect. thanks!

2 Likes

Are you using multisig address or trying to sign as part of multisig? Your error ‘tx.ModeInfo_Multi’ it looks multisig related. if yes, atomregistry/keplr/ledger may not support this multisig signing flow correctly yet. Try signing with a normal non multisig ledger account to confirm whether the issue is specific to multisig

1 Like

I don’t believe so. I know I created the cosmos wallet using ledger live then imported it into keplr to use. Could that have created a multisig issue?

You imported your cold wallet into a hot wallet?

i connect to my ledger in exactly same way, through keplr

Please try:

  1. update ledger firmware and the cosmos app
  2. update keplr
  3. close ledger live completely
  4. use chrome or brave ( https://atomregistry.com/ledger.html ) <-important ledger.html
  5. remove and re add the chain / account in keplr
  6. if it still fails, try the same action without ledger if possible just to isolate whether this is ledger signing related

I used the option to connect the hardware wallet to keplr.

I had to create a new cosmos address connected to ledger for it to work. Thanks for the help.

1 Like

Oh ok sorry. Thought you meant you imported the private key of ledger to keplr.