Introduce yourself here and get free karma ;)
- Pinned by admin
Hey Namers, with vaccines rolling out and things finally opening up, Skynet ( ), Upshot ( ) and Akash ( ) are getting together for an after party following the June 4th-5th Bitcoin 2021 conference ( ) and YOU'RE invited!
Plans are to rent a yacht and the cost per project is $6k. I can personally contribute $600 and will defer to the community to make up the remaining 90%. Is there any interest from our Namers and Directors to contribute and participate in the event?
Fyi if the yacht falls through, then this location will be the backup:
I'm very happy to announce thatTLD has been gifted to Dxpool Team.dxpool/
Since I started in HAndshake (May 2020), one of the important objectives was to have initiative to give TLDs to friends, companies, institutions, etc. The main objective: to spread the word and open the eyes to the world on the decentralized web. For this reason, I started bidding on all kinds of names, specifically on September 18, 2020 I won Dxpool / and now the opportunity finally presented itself to give it to the Dxpool team. The wait was worth it and will pay off in the future.
I want to give special thanks to Handshake Jesus for his intermediation (I don't have a twitter, hahaha) and the entire community in general for moving forward on this long but intense and interesting road.
In a few days I will make you another interesting announcement about spreading the word.
All the best
The Shaker Discord bot is a light-weight solution to identity validation in Discord servers. It uses modern technology to ensure that the members of your Discord server are who they say they are. Shaker utilizes the Namebase Record Assistant to make verification a breeze for those who's names are on Nambase. Shaker also makes use of some of the most recent techniques that Discord has made available to developers: ephemeral slash commands. You no longer need to keep a separate channel for verification or bot command spam, members can verify anywhere in a way that doesn't disturb others.
If you're at all interested, you can add Shaker to your Discord server with this link:
If you have any feedback, feel free to leave a comment here:
Hey Namers, with a lot of upgrades coming to Namebase on the horizon, I wanted to share a bit more info on Namebase's upcoming roadmap.
For context, we've spent the last half year working to improve tooling for developers who may want to build on Handshake. dLinks ( ) was created to showcase how you can use Handshake names to create decentralized websites, Namer News was created to showcase how anyone can use Handshake names to log in ( ), the Namebase Record Assistant ( ) makes it easy for users to set DNS records on their own names, and HDNS ( ) was released so developers can easily build Handshake services without running their own nodes. And all of this can be found via the new developer documents at We also went ahead and quickly released a lightweight version of the Namebase Registry ( ) so we could unblock those who have been eager to jump start their subdomain business.
It's been really rewarding to see how all this has played out too. dLinks was a helpful case study for accelerating Fleek's integration of Handshake ( ), Handshake logins is now used for logging into the Handshake Wiki ( ) which gives you editing access, hmail.app uses the Namebase Record Assistant to set its auth TXT records, and HNS.to is now running HDNS so it should be a lot more stable now. And in just the first month since the registry's launched, more than 500 TLDs have already been staked!
Now that the developer tooling is in a pretty good place, we're reinvesting back into improving the Namebase core product. This includes rehauling our egregious onboarding experience, helping newcomers better undestand what Handshake is and how the auctions work so they don't get their personal names sniped, revamping the dashboard ( ), squashing papercut bugs like the annoying one that shows won names as "lost" for 20 blocks, launching referral and affiliate programs, integrating wire transfers and additional payment methods, and of course improving marketplace and make an offer features such as marketplace auctions, paid default sorting, batching names together for portfolio sales, regex and fuzzy search filters, setting a minimum for offers, declining offers, and buyer/seller communication.
In the meanwhile, the Handshake community will also continue to grow in parallel. The dWeb Foundation ( ) is taking the lead on pushing for browser adoption and coin listing, Directorsandmarksmith/are soon launching a name gifting platform that we think will be crucial for community growth (name gifting is a keystone to Handshake's culture and we're going to kick the platform off with an event, stay tuned), we're developing a code conduct together to honor and reflect our shared values, and we'll develop a crowdnerfing blocklist (rough draft at ) to discourage name squatting while encouraging name gifting.graham/
If you'd like to get involved with helping grow Handshake, you can check out for a lengthy list of explicit ways you can immediately get started! Specifically, our team at Namebase thinks that right under browser adoption, the most important event for Handshake is integration with other dWeb projects like Filecoin, and all it takes is a little outreach — perhaps you'd like give it a try? I've personally found other projects' communities to be super welcoming, which makes sense since if any of them reached out to our community about integrating, we'd be very excited to help as well!
Handshake is the gateway to the dWeb and our community already has great relationships with fellow dWeb pioneers like Skynet and Akash team, so let's keep reaching out to other projects to work together until the entire Internet stack is fully decentralized!
Ping me aton Discord (discord.namebase/) if you want help with getting started 🤝johnnywu/
So I've encountered some weird behavior with the Namebase authoritative nameserver. I noticed that positive results, such as returning data from a TXT question, will be returned as expected and will *not* be cached. If I have a known record and alter it, the change is immediately visible. The issue is that for negative results a cache of about a minute is implemented. This is an issue for services that use DNS records to authenticate a user's identity. I was wondering if this cache could be removed, or *at the very least* usage of the Record Assistant could flush this cache automatically? Thanks!
Hey Namers, I just wanted to share thatis now with its true Owner.nytransitmuseum/
I also want to use this post to talk about how you could use your daily life to potentially help the adoption & implementation of Handshake.
First things first we're all Internet lover's we all have "online friends". A lot of these people that we come into contact with through out our days rather you be hanging out with that friend you played Call Of Duty with as a teenager or someone you found in a cool coding discord. Whatever the case may be a majority of these people work for a living & that place of work could have not claimed there name. I'm not saying go out & gift names to random places/people willy nilly but just asking the people you come into contact with what they do for a living and just general questions. You could potentially get a new adopter to join us for the future.
Thank you for reading <3
Getting a reply from Namebase support is like winning the lottery - it doesn't happen often enough.
I have TLDs that I staked a month ago that are still not showing up on Encirca due to them not getting the names on the weekly new TLD lists. Emails to email@example.com have gotten no replies. What's the next step?tieshun.namebase/johnny.namebase/