Replies: 17 comments 42 replies
-
Easier way is to ask if it's King Lee or not.
Why is the Ethereum model sought after? As we've seen with Impervious, it's good for initial sales but then what? Where's the incentive to use these domains?
What value has Superlink added to Handshake? They've acquired a bunch of surnames, made a site, and then nothing. Their Discord is full of people asking for refunds. What if someone on this airdrop list doesn't want it? Who decides where their allocation goes?
At least 20 SLDs on a TLD to quailfy? This is easily gameable.
Handshake Stimulus Check...that rewards quantity over quality. Plently of people with objectively garbage TLDs are regularly hawking them to other folks with similar portfolios in the Namebase Discord (this is also gameable, and will add more nonsense to the chain). Later in the document you claim there will be "enforcement" and such activity is not tolerated. How will this enforcement happen?
I hope y'all have a plan to stretch this money and aren't just looking to become millionaires overnight. The community is rather skittish about a small group of people controlling a bunch of money...although, giving them a stimulus check may quiet the grumbles (until they do the math and see how much they'll actually get).
Seems like this should be reworked to allow people to claim.
Who is this investor group?
Ruggable
What is this "new standard"?
"Can" should be "will," unless y'all have other ways to make money and stay solvent.
Gameable. The enforcement mentioned previously in this document doesn't extend here.
There are other systems out there. Digitalis seems like it will be a better alternative. This deference to Ethereum doesn't sit well with me for reasons I'm unable to find the words for right now.
This has dragged on long enough, and Alexa ranking doesn't even exist anymore. Just be done with that but reserve ICANN names forever.
"Will all this HNS be dumped onto the open market? What about my token price? Y'all are gonna destroy HNS!" <- things people will say (not me) At a high-level, this proposal sounds like:
This sounds like a squatter's dream. I don't see how any of these changes will encourage (serious) builders to come to the blockchain. I see finance bros finding this a good opportunity to grift with a hint of legitimacy. Money is hella attractive so at first glance this proposal is exciting...it's just that I see more downsides than upsides. |
Beta Was this translation helpful? Give feedback.
-
|
First off, thanks for taking the time to provide a thorough response. I desire a thriving ecosystem of builders and users for Handshake, and believe this proposal offers that. This is a starting point; adjustments can be made based on community feedback. To address some of your points directly: Superlink is a tremendous asset to the HNS ecosystem. While Superlink’s situation with gaining adoption for their platform (eg. several wallet integrations) and HNS (eg. Carbon Browser) has had successes and failures, they have great potential and talent. Suggestions are welcome for the inaugural community members. As mentioned in the proposal, those suggested members must opt-in in order to be one of the first members of the Republic of TLDs. The first cutoff date already passed, which includes off-chain registries. There’s no gaming that; I already have rough data from several registries. As far as the 2nd cutoff for TLD Communities, feel free to share suggestions on how to prevent fraudulent activity. This is primarily why only on-chain registries are being considered due to their transparency. This part of the airdrop can also be removed if the community believes that to be the best solution. The TLD owner airdrop rewards quality over quantity. Please read this again: “The airdrop amount will be proportional to the amount burned at the last on-chain auction for the HNS name. This will encourage quality domain registrations and overall chain activity, while dissuading spam.” I agree that the community should be skeptical over any forms of centralization. As I’ve devoted 4+ years to HNS, my passion derives from the prospect of ensuring freedom online for existing Internet users, and more importantly, future posterity. If any of this was solely about money, I wouldn’t have ever been involved with HNS. For owners claiming their TLD airdrop, I agree that it would be best for the custodian to allow claiming. If we were to move forward with the next stage of this proposal, the hope is that ShakeStation and Namebase would announce that claiming capability. This would establish trust with whoever does that, and could also result in TLD owners transferring their TLDs over to that custodian if their existing one hasn’t obliged. Andrew can be the one to provide specifics as to the investor group. It’s important for the dSLD application to be programmable that can fit the particular needs of online influencers. The technical team (Kyokan) will research and innovate in these different areas (L2, payment address, etc.). As to the reserved names, the community decided during last year’s soft fork discussion to include the Alexa Top 10K. If the community consensus has changed on this, that should be discussed. As of now, this proposal dictates that the Alexa Top 10K be claimable for four more years, and then released for claiming. With the efforts from Handshake V2, there are many huge companies and websites that may discover HNS and claim their HNS TLD. While your conclusion is foreign to me, I respect your freedom to speak. Overall, I firmly believe that a reinvigorated focus, combined with better coordination and resources, provides Handshake the best opportunity to reach its fullest potential. |
Beta Was this translation helpful? Give feedback.
-
|
Out of everything, giving money to businesses/tlds is a hard no for me. That whole idea in the proposal needs to just be If anything, most to all funding should go to a non-profit entity, and im generally not ok with any money going to build a VC entity. That was not really clarified, but we don't need backroom deals on any money from the chain. If you think differently, justify why ecosystem funds should serve to reward/re-reimburse any business in the ecosystem and not be just for public goods (commons) in the eco. Kudos. |
Beta Was this translation helpful? Give feedback.
-
I'm unfamiliar with Stacks on Bitcoin but a hard fork proposal is unnecessary for an L2, you can just get a team and build it.
I read this the first time and what came to mind immediately was someone using several wallets to create auction drama. Nothing's stopping someone from dropping 100k HNS across several auctions to gain something greater in the future. Web2 domain speculators buy domains for thousands of dollars to flip for millions. This behavior is commonplace.
I believe you. I don't believe Andrew.
Eskimo doesn't like this proposal so idk about that. Is Namebase interested in this proposal?
Is anyone involved with this a marketer? Influencers are constantly moving to the next hot thing. I'm skeptical that crypto developers understand how to build what today's influencers "need."
I can break it down further:
Thanks for addressing some of my concerns but my last paragraph still stands:
We don't need to follow the UD model of chasing after integrations and neglecting working on building new experiences for the Web. I promise you there will be 2 Chainz should this fork happen as proposed. |
Beta Was this translation helpful? Give feedback.
-
|
ditto. im definitely not supporting a new giveaway of funds for no apparent reason. |
Beta Was this translation helpful? Give feedback.
-
|
Based on community feedback, an alternative proposal is to be presented: Burn Baby Burn. Learn more and share feedback here: #69 While the former proposal is a pro-active approach, the latter is a pure approach. |
Beta Was this translation helpful? Give feedback.
-
|
I like a lot of this in spirit, but:
Overall this proposal is basically the It would honestly be simpler to just vote on creating a multisig + foundation and give it a block reward, then after vote on creating an L2. The L2 is honestly a nice-to-have, but we need a lot of core foundational stuff figured out 1st, and if there is a multisig with millions usd, that is not gonna be very hard to get builders to hire. If taking this as-is, I would say a hard no. |
Beta Was this translation helpful? Give feedback.
-
|
Yes. I am funded by Sia via grant, but even then im funded as a community project and as a public good. my entire code base is MIT. My funding is for me to build, not for supporting a business. So I have a hard no against any funding to a project that's not under a grant structure or clear terms of what it is for. I will be launching a business, but no one is going out and supporting the business, they are supporting the R&D that is public goods code and its all on GitHub. So for a minimum if you wanted to justify giving money to any ecosystem project, they would need to FOSS everything to fall under that, and I don't think namebase is ever going to do that and I don't see others either, and multiple I know have investor funding, which means their goals are a business, not to build tech, and FOSS'ing is likely going to be Now, to be clear: Lume as a project won't deny any donations, but those donations are always intended for public goods R&D and project objectives that help communities Lume is in. I never ask anyone to give me capital to run a business and say its a |
Beta Was this translation helpful? Give feedback.
-
|
As for funding marketing or anything else that's not code, that should be a community decision with a non-profit entity or other means to be accountable. That would not and should not be part of a chain giveaway of funds direct anyone's wallet with a |
Beta Was this translation helpful? Give feedback.
-
|
Oh and that I would take a BTC maxi stance on that, that a group with property ownership in HNS is a |
Beta Was this translation helpful? Give feedback.
-
|
@pcfreak30 There's an edit button, every reply is a new email lol |
Beta Was this translation helpful? Give feedback.
-
sorry 🙃 . |
Beta Was this translation helpful? Give feedback.
-
|
Completely agree with what @NetOpWibby said. The plan looks extremely difficult to execute without any clear explanation of how this whole proposal will add actual value to the chain.
|
Beta Was this translation helpful? Give feedback.
-
|
Hey Andrei, thanks for your comments. In short: this proposal will increase the overall chain activity from users to TLDs to coin demand.
|
Beta Was this translation helpful? Give feedback.
-
|
A hard fork proposal isn't necessary for an L2...you can just build it. Same as all the L2s on Ethereum. |
Beta Was this translation helpful? Give feedback.
-
|
I support token reallocation towards single organization that would push the ecosystem. Could be the DAO, but doesn’t matter much if founders will be solid. Handshake is dying because there is no organization with enough skin in the game and incentives to push it forward. Other ecosystem companies actually don’t need token grants because they already hold presumably most of the circulating supply, and they will benefit from just token appreciation. To raise cash, the organization may sell reserved TLDs for stablecoins or raise funding from Namecheap etc who generates revenue now out of handshake TLDs. Selling for tokens wouldn’t be as efficient because it would not create a lot of cash inflows to the ecosystem. Cash from sales can be spent on operations, development and bizdev. But what matters more is the strategy for adoption. One strategy that may work is to focus on blockchain wallet and web3 browsers ecosystem, pushing handshake as universal naming system. Adopting handshake to legacy DNS has failed so far and I doubt it will ever be supported by major browsers. And for names to be wanted, they need to dominate certain platform (like TON names in Telegram, ENS names on Ethereum, etc). The role of organization will be to partner with L1/2/3 chains, wallets, exchanges, dapps to dominate their community. And spread from chain to chain, from dapp to dapp. Run giveaways, drops, exclusive features for TLD owners, and all this crazy crypto activities which actually work. |
Beta Was this translation helpful? Give feedback.
-
|
I think both BIND DNS and RPC DNS will have a place in HNS. So I do agree with you to an extent. Though
Overall the browsers problem is something I plan on solving myself in the long term as part of Lume, but there are a lot of common things that HNS could fund, if it had the money. Kudos. |
Beta Was this translation helpful? Give feedback.
-
I don’t believe raising from VCs today is possible for handshake without very compelling story and the team. Easier to invest in any other naming project that does proper bizdev and adoption. Again, someone needs to step in with serious intentions and capabilities to run the organization and get adoption to convince the market. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing your ideas. I agree that the HNS community could benefit from better coordination and leadership. For adoption, we’re focused on onboarding huge communities (crypto, censored, etc.) to the L2’s first application, which will increase overall awareness for Handshake. The layered airdrop is akin to crypto activities that can help incentivize the use of HNS and create buzz in the near-term. |
Beta Was this translation helpful? Give feedback.
-
|
Proposal 68 really makes sense, thanks heytx. HNS is facing an important threshold, so let us have a high consensus. |
Beta Was this translation helpful? Give feedback.
-
|
What makes sense about this? This proposal has less consensus than the re-allocation proposal. |
Beta Was this translation helpful? Give feedback.
-
|
Disclaimer: With nothing but respect for the author(s) of this proposal, the following assessment is intended to pinpoint deficiencies in the strategic viability of the proposal’s elements. Views may read as critical; but are constructive in nature. They are as follows: There’s more contradiction than cohesion in this proposal. This isn’t to imply this was the author’s intent; but sadly it READS as if THE PEOPLE aren’t a priority focus of the strategies outlined. (Note: NamerTips believes @heytx has an authentic commitment to ensuring HNS serves THE PEOPLE. We support, respect and appreciate his efforts and those of the HeyTx team.) **The HNS protocol and token NEEDS the people. This embedded notion that every effort to move HNS forward MUST cater directly to devs, VCs and TLD holders manufacturing their registration numbers is the Achilles heel of HNS’ potential. HNS’ challenges won’t be solved with 'soft forks and good job token reallocations'. Let the record reflect how they’re merely band-aids that benefit a select few. Why continue perpetuating this cycle?** This proposal uses words including “enforcement” which is a major red flag. “Decentralization” and “ownership” are the core appeal of HNS. The sheer idea of enforcement for any reason could imply the protocol isn’t as liberating as once touted. Anyone familiar with ownership at its core will know that regulations can disrupt confidence in people, places and things. HNS literally can't afford anymore lost confidence. All decision-making on behalf of the protocol and token should be carried out by the TLD OWNER and TOKEN HOLDER communities. (Obviously through votes.) This doesn’t apply if the foundation of what HNS represents has been changed though. If this has occurred behind the scenes, make it clear. THE PEOPLE shouldn't be mislead into believing HNS is “FOR ALL” when it’s really just “FOR US”. In addition, the cuddling up with Ethereum idea is NOT the way to go. Not because there’s anything wrong with Ethereum itself. If a TLD owner makes the choice to factor the Ethereum chain into how they manage THEIR TLD, that’s fine. But let’s not make Ethereum a front-facing variable for a protocol that was just being promoted as superior because it’s Bitcoin-native. Also, don’t outcast TLD owners who CHOOSE to integrate with some other chain. There has been enough separation among the community for a few cycles now. At this point, HNS has an identity-crisis fueled by many of its most vocal stewards. There’s an aroma of special interests that adds to the stigma around what being a Handshake supporter and name holder means. Let’s be honest, 11+ million names registered doesn’t carry as much weight as it once did. It’s a heyday stat. We get it. Names are cheap to register and there’s nothing else to do with the token but sell it off (when you can) and register names. Nobody cares besides folks in the HNS community and THAT'S the problem. This proposal should be revisited. Not because it’s bad. It simply doesn’t align with the promoted ethos of HNS. Now, if a more centralized narrative is what a certain portion of the community wants, and they VOTE for it, then OK. Just understand the risk of turning off some of this protocol's most innovative minds and contributors would be a consequence. Like it or not, there are other TLD naming options cropping up; and they’re aiming to be more palatable for the public than HNS has been since its inception. HNS being touted as an asset to the DNS system isn’t hearty enough to feed the education, entertainment and empowerment needs of THE PEOPLE. With EVERYTHING stated, NamerTips will be submitting an advisory proposal here soon. After all, the community could use advisory boards at this stage. The proposal will omit the heavy technicals for the sake of focusing on bringing in the people. It’ll be a final attempt to constructively cite what NamerTips is confident will help get the HNS protocol/brand in sync with THE PEOPLE. (SPOILER ALERT: It has nothing to do with promoting a handful of front-facing efforts as the best the HNS protocol has to offer.) Till then….. |
Beta Was this translation helpful? Give feedback.
-
|
Hi NamerTips, I always appreciate your thoughtful views. Thank you for sharing this constructive feedback, and I look forward to reviewing your advisory proposal. |
Beta Was this translation helpful? Give feedback.
-
|
What do you guys think about combining both proposals (reallocation/multisig and HNS v2) and just raising funds from the same investor group but for L2 only? We can leave L1 as it is because it’s doing an amazing job of keeping alternative internet root zone secure and decentralized and we move all creative ideas to L2? If the plan was to raise money for L2 one way or another and we have an investor group who’s willing to provide funds in exchange for coins, why not just raise for L2 only? This L2 can have a dedicated governance token, utility token or any other form of a token. We can also create a treasury, DAO, foundation, multisig or a company on this EVM compatible L2 + original chain can remain as it is right now. We can even burn airdrops on L1 and create new airdrops on L2 to combine all the interests of all community members. Miners are happy, token holders are happy, businesses are happy, we gain funding and an L2. Sounds like a win win for everyone. |
Beta Was this translation helpful? Give feedback.
-
|
No one should be using the locked funds to fund their personal business(es). It should be used to fund developers working to provide value to Handshake. That's not a popular idea either but it's better than this V2 proposal. I'm now of the opinion that Handshake should be left alone and whatever ideas I have for it should be its own chain. |
Beta Was this translation helpful? Give feedback.
-
|
L1 remains as it is now. We can even burn all the coins which are not claimed. We move everything to L2 (DAO, multisig, federation of TLDs, airdrops, raising funds for coins). What’s the contradiction? |
Beta Was this translation helpful? Give feedback.
-
|
If you "rethink L1," aren't you proposing to change it? Changing it doesn't adhere to "core values." Unless I'm missing something. |
Beta Was this translation helpful? Give feedback.
-
|
My point is that we don’t have to rethink L1 because like you mentioned before HNS is doing a great job of being decentralized internet root zone. Everyone in our community agrees with this I think. Hence why I think it’s better to approach new investors with this pitch: “L1 achieved its goal of being decentralized internet root zone now we need to bootstrap business models and use cases, that’s why L2 exists.” |
Beta Was this translation helpful? Give feedback.
-
|
if an L2 can get funding for VC's to shill registries and the investment goes towards an ecosystem wallet/entity (501c3 and/or multisig, NOT a vc entity), then I can get behind that if anyone actually finds a group. Else we need to hard fork L1. |
Beta Was this translation helpful? Give feedback.
-
|
What NetOpWibby said |
Beta Was this translation helpful? Give feedback.
-
|
We’ve always said Handshake is an experiment, and the purpose of an experiment is to learn from them and iterate. While the developer community doesn’t like to talk about price, the reality is the difference between a FOSS project and a cryptocurrency is that there’s a price. Handshake’s price is down 90% 5 years since it launched at a market cap of $7M and trading at about a penny. As Thomas Sowell once said, “Prices are signals that convey underlying realities.” If you compare Handshake to bitcoin that didn’t even have a price for the first few years, bitcoin was trading at $800 by year 5 at a market cap of $10B. Bitcoin was over 1000x more valuable in the same timespan even though Handshake had a head start by coming out the gate with a much higher valuation. So what are the underlying realities for Handshake?
Before we get into talking about the various proposals, I think it’s important acknowledge Handshake has an adoption problem that’s reflected in its price. Is this something we can agree on? |
Beta Was this translation helpful? Give feedback.
-
|
The large airdrop really should have been split and used half way to fund the ecosystem. |
Beta Was this translation helpful? Give feedback.
-
|
@pcfreak30 agreed. All these proposals address reallocating the unclaimed airdrop to use to fund the ecosystem. @eskimo why do you think there's no development? You've developed interesting projects like hnschat. Why don't you think there were more users? |
Beta Was this translation helpful? Give feedback.
-
I also killed hnschat because a lack of usage. A chat using handshake names was cool, but people preferred to use 1 of the other 10,000 chat apps. If the community actually cared they would've used it and tried to get others to use it. It was a bad look to newcomers/outsiders if everyone in the community uses discord/telegram while at the same time they linked everyone to hnschat as a use case. The problem in handshake is the community, which is also the same problem as every other crypto project. People are involved because they think they are going to profit somehow, and then businesses try to profit off of everyone. Point is, you can't name 1 thing people can do in handshake that doesn't cost money; that's the problem, and giving away more money to people that have essentially created the problem won't solve the problem, it'll make it even worse. The only thing I agree with in the entire proposal is having hsd core devs receiving HNS. Zipkin having to go get another job when he was one of the most knowledgeable and helpful core devs here is crazy. I also definitely agree with Rithvik receiving something as well. Without him, Shakestation wouldn't exist, he helped me so much. As for nodech, he's getting paid for his work on hsd by namecheap, I would say he shouldn't receive anything. Subsidizing his salary so he can do work he's already doing which benefit namebase makes no sense. Either way, at this point I have no faith in the community, or anyone else to properly manage the funds besides a few people that aren't even part of this proposal, so I'm against it, and at this point, also against any proposals at all. |
Beta Was this translation helpful? Give feedback.
-
Why. Why do people keep doing this?
So...why compare it?
Phrased another way, the "if we build it, they (developers) will come" strategy was going to fail. It's basic business 101. The meta for ANYTHING you want to galvanize people around is community. The biggest and most successful crypto projects have cultivated community. Our community is so toxic, we drive people away. I unblocked a community member today after maybe 8 months of having them blocked?
IIRC, you and the other co-founders of Handshake prided yourselves on the "hands-off" approach to stewardship...this also applies to marketing. The airdrop wasn't advertised at all (Twitter is not an effective marketing strategy). A few developers can only do so much...y'all had the resources to be the marketing arm and chose not to. It's weird to now be like, "can we agree there's a problem?" You've mentioned "price" 6 times...HNS isn't a currency, it's a utility token. I think this is where our core values diverge. At a high level, we all want adoption. You want your (potential) bags to be worth millions, I want millions of Handshake-based domains and websites on the internet. A handful of developers have carried the protocol on their backs for nearly half a decade. That's nuts. Patting yourself on the back with millions of HNS/USD for a "job well done" is insane. |
Beta Was this translation helpful? Give feedback.
-
|
I did outreach and tried gifting names, getting people and devs to use HNS for about 2 years now. Here’s the summary:
My understanding of current situation is that we lack killer use case (BTC had Silk Road and Wikileaks since 2011) and no one actually knows what type of use case it might be. One thing is clear, decentralized internet root zone exists and works as intended. I don’t see any reason why we should change anything on the protocol level. When it comes to further development and adoption of Handshake I think it make sense to move all the creativity to L2 so that we don’t risk losing what’s working extremely well already now. Boosting adoption/recognition of HNS is a pure business move which has nothing to do with how technology works on L1 level. |
Beta Was this translation helpful? Give feedback.
-
|
I believe this to be an attempt by Andrew Lee to misappropriate even more Handshake. Nothing was done with the original HNS they were allotted and the Founders aside from JJ have been mostly ineffective since launch. Would be good to know where their initial 100mill HNS they were assigned at launch went to. Anything that doesn’t include an explicit statement from JJ should be seen as a hostile takeover of the chain. I’ll say nothing further. |
Beta Was this translation helpful? Give feedback.
-
|
Dapps are all that is needed. If you haven't built a dapp or shared valuable info to people in a region that is censored, you won't understand. Those who do don't have the time to explain. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry but that doesn't make sense. Yes we need people to build things, but fundamental lego's are either immature or just don't exist. They are needed before more webapps. |
Beta Was this translation helpful? Give feedback.
-
|
We have to agree that the majority of people who really love HNS are losing money, especially miners, and if the fork has a positive effect on the price of HNS, it is good for the ecosystem as a whole. But the allocation of 2:
|
Beta Was this translation helpful? Give feedback.
-
|
Everyone, but somehow, i agree with Andrew G that HNS needs the market, the market needs HNS's change. |
Beta Was this translation helpful? Give feedback.
-
|
so a more suitable amount of unlocks, @heytx. Hopefully, I believe Nole will lead us... |
Beta Was this translation helpful? Give feedback.
-
|
BURN THE COINS AND GET TO WORK So many people are complaining about price and that there aren’t enough people building in the space. The demand of decentralized blockchain that enable privacy is only on the incline. Many people are trying their way at manipulating the protocol through these complaints on adoption in the space, while the entire industry is this way. Do you not have any awareness of the current economic conditions? There needs to be a greater focus on getting people from point A to point B. Pointing directly to decentralized hosting solutions, that allow people to get involved with building. There are many intelligent people in the space, but there is now too much emphasis on individuation. It’s great that you have your companies, but those companies are not a focus within Handshake. Decentralization is selfish. It only cares about focusing on the best utilities in the ecosystem. hns.cymon.de - Great Job. Bob Wallet & Atomic Swaps - Great Job. There are plenty of 3 & 4 letter tlds. Plenty of 3-letter tlds for under 100$ USD. Guess where many of them are? (gasp) Namebase. Many, many, many 4 letter tlds that still are not minted! Handshake is one of the most important projects for the shift that’s occurring. Keep it simple. This project is increasing in demand because it offers what no other project does, AND it has a comfortable position in the corporate environment. As much as we love them, Monero can't say the same. Monero represents the IDEA of what Bitcoin was supposed to be. It's too much of a threat to be commercially viable at the moment. With projects like MASQ, you may have people migrating their marketplace and not relying on Tor. BURN THE COINS AND EXPOSE THE PARASITES. We will continue to build and thrive. BOOHOO , nobody’s building anything. GET A JOB & GET TO WORK. We do not need to turn a unclaimed coin allocation into a fundraising initiative. The v2 proposal by nole.tx is a shameful "money grab" and attempt at gatekeeping style governence. 35% of coins to 6 "communities". "Many diverse contributions of the Skyinclude Team, including marketing initiatives, Asian community,". He really said Asian community as a diverse contribution. Wow. 26 million HNS each, so you can support your gatekeeping initiatives. BURN THE COINS. |
Beta Was this translation helpful? Give feedback.
-
|
Im not for this proposal as-is, but the crux of it is at a minimum we need protocol funding. If you ignore everything else, ask how do we get the core dev's hired full time so they don't need to work at a bitcoin think tank or anywhere else. IMO, if you cannot give solutions other than flailing your arms and screaming |
Beta Was this translation helpful? Give feedback.
-
|
Please stop this claiming-airdrop / re-distributing the coins thing. Giving out free money design did not work. It was well thought and planned before execution but it did not work. dSLDs are not what HNS is for. It's a fork in the vision of HNS in which we believed in first place. All we need is an easy way to use the TLDs or say build the pipelines for the data to flow. The very first and major mistake made was giving out millions of HNS to people when the chain started and auctioning out all the names in first year. I know people have claimed boat loads of TLDs and they are doing nothing for HNS and in-fact they are bad mouthing HNS and these are the people who got involved from beginning. All this was planned. Did it work out ? So please don't mess it again as people who will join in future will see this as another money grab. Mass/retail doesn't care about what few people think. They see the monetary policies and activities and given the current scenario, re-allocating funds will make it difficult for further integrations. This is not a 6 people's/TLD's chain. So yes BURN THE COINS and form a for-profit organization and get VC funding to do your thing. . |
Beta Was this translation helpful? Give feedback.
-
|
Im not for this proposal as is, but the crux of it is at a minimum we need protocol funding, and that cannot be ignored, and everyone who wants a burn or no action gives no actual solutions other than an effective |
Beta Was this translation helpful? Give feedback.
-
|
When this project started it did not promise any funding to any one. If it dies this way then let it be, forking and allocating coins will create a mess and that will surely kill this project. So I don't want HNS to be killed with this proposal. |
Beta Was this translation helpful? Give feedback.
-
|
And 20/20 I would consider that a mistake. Funding should have been created from the start, and not all of it given in an airdrop. So steel-manning: it dies because we Bitcoin as a whole was unique and Satoshi has the time and resources to not really ask for money. We obviously don't know how he had that, but the fact is, HNS does not have the same benefit. Trying to treat them in the same spirit is a fallacy overall for funding. |
Beta Was this translation helpful? Give feedback.
-
|
The only thing I can think about is - Write a roadmap to build a product where any TLD can be plugged in and a website can be hosted with minimal effort, might be using Akash Network, so that even a normie can host a website within few clicks & Who will be working on it & then release the funds in batches after successful completion only. dSLDs is the wrong direction IMO. |
Beta Was this translation helpful? Give feedback.
-
|
FYI, I am building IPFS hosting, part of the Sia tribe that will launch EOY, and im looking at Akash getting involved for infra. HNS just has no part in this yet, unless you consider supporting domains via DNSLink, which I want to do. So as it stands, any dev time HNS gets will be a side effect of any other chain its friends with. Nothing is really being 100% on HNS itself.
|
Beta Was this translation helpful? Give feedback.
-
|
Based on community feedback, an alternative proposal is to be presented: Burn Baby Burn. Learn more and share feedback here: #69 While the former proposal is a pro-active approach, the latter is a pure approach. |
Beta Was this translation helpful? Give feedback.
-
Handshake V2
Genesis Ideas of Handshake
The initial phase of Handshake was centered on three fundamental ideas that were focused on fostering a community and providing a decentralized alternative to ICANN:
Checkpoint
The idea of establishing a decentralized alternative to ICANN has been embraced by the domain and blockchain communities. Despite the absence of centralized leadership, progress has been made within the community, particularly in the areas of marketing, development, and network establishment. Notable events since Handshake launched in 2020:
Lessons Learned
The two key components in the Handshake launch plan, the airdrop giveaway of HNS to open-source developers and the donation giveaway of invested VC funds, did not yield the intended results.
A significant part of Handshake's ecosystem launch strategy was an airdrop intended to increase developer awareness and support. However, the airdrop that targeted open-source developers had limited success, with only approximately 2.9% of the allocated 900 million HNS claimed.
This outcome highlighted an important learning opportunity: simply giving away coins does not necessarily align incentives. This is similar to the challenges associated with unconditional basic income models, where reciprocal behavior is not mandated.
Also, the entire $10.2M raised from reputable funds, including Founders Fund, a16z, and Sequoia Capital, was immediately donated to support open-source non-profit organizations, such as Apache, Arch Linux, Debian, Gnome, OpenSSL, TOR [3]. Consequently, this allocation led to the unavailability of funds for critical areas such as exchange listings, partner integrations, and further developmental initiatives.
Identities & Communities
Identity is not limited to a mere name or number. It is a reflection of oneself in social, formal, and institutional contexts, and it shapes one's connections with societal institutions.
In essence, a name linked to community membership represents an identity more accurately than a standalone name. For instance, AliceBob.ReligiousBelief, AliceBob.Country, or AliceBob.bitcoin better describes the person, than the name, Alice Bob, alone.
For instance, the two individuals known as Andrew Lee within the Handshake community are frequently mistaken for each other, yet they are seldomly confused with any other individuals bearing the same name. The primary source of confusion lies in their concurrent involvement in the communities associated with Bitcoin, Handshake, and Joseon. To distinguish between the two, individuals often make reference to their non-overlapping affiliations, identifying them as "PIA Andrew" or "Purse Andrew."
Digital Communities
Humans, being social creatures, have an innate desire to belong to groups. The evolving digital landscape has enabled us to engage in a wide array of digital communities, from crypto alpha groups and educational forums to influencer networks and crypto/NFT communities. Ideally, we would like to have the same digital identity across all these communities, although there can be exceptions. Having control over our digital identity is a key benefit.
Market for Communities
Communities connect individuals who share common values. The strength of a community is fueled by the size of its membership, the depth of connections among its members, and the unwavering belief in its values.
For example, the Bitcoin community has grown significantly through bringing together individuals who appreciate decentralized currency and open source technology. It's difficult to quantify the total number of Bitcoin community members and the strength of their connections, but it's clear that these numbers are increasing in proportion with the price of Bitcoin. Ultimately, Biitcoin’s market cap reflects the value of its community.
The majority of communities lack a ticker or market price, yet it is worth considering whether more should. As confidence wanes in institutions and mainstream media, individuals are increasingly turning to communities as a reliable source of truth. Nevertheless, it is important to recognize that communities are fallible, and tribal instincts can override judgment and reason for far longer than necessary.
In general, free markets excel at disseminating information that can highlight truths and discredit misinformation. Communities are able to swiftly distinguish between truths and falsehoods related to their specific areas of focus and expertise. There are abundant opportunities to capitalize on communities, ideas, or movements. This can result in rewards for those communities that grow and are trustworthy.
Communities on Handshake
SLD mints is an exciting emerging use case for Handshake. TLD owners can mint SLDs off-chain via Namecheap and Varo, or on-chain via HNS.ID and Forever.domains. The monetization of TLDs through SLD mints increases the value of TLDs, thereby generating value for the network, as HNS tokens are burned to acquire TLDs.
Through SLD mints, TLDs are essentially minting community membership cards for new members that buy SLDs because they align with the values projected by a particular TLD. Handshake is an ideal system for communities where members can have IDs (SLDs) for the communities they join (TLDs). In the future, communities might want to issue tokens in addition to IDs. Handshake is the only open source technology that allows any online community to have access to all of these monetization options.
Handshake V2: Launchpad for Communities
Summary
The purpose of the Handshake V2 proposal is to apply lessons learned since Handshake launched. This includes fixing the airdrop model and further incentivizing activity by those that have been adding value to the network. Overall, the aim is to have better organization and resources within the Handshake community. The proposal consists of four main components: reallocating the unclaimed airdrop, forming a company to kickstart Handshake V2, developing an EVM-based L2, and making the remaining reserved names claimable.
Reallocation
There are currently 622M HNS in circulation, and 890M HNS left unclaimed for open source developers. This sizable airdrop was expected to have been claimed shortly after launch and in circulation.
Current HNS Supply
As of July 31, 2024 (blockheight 236,087) [4]:
Airdrop to Inaugural Communities
This airdrop is open for community discussion and must be approved by the initial advisory board. These inaugural recipients are being offered this airdrop due to their historical and prospective contributions to the HNS ecosystem.
The inaugural communities will consist of the first members for the Republic of TLDs, the future governance for funding the Handshake ecosystem. Potential inaugural recipients must submit the following details in order to be considered:
Airdrop to TLD communities
This 45M HNS airdrop is intended for TLD owners and the communities established therein. There will be two cutoff dates, which will reward early TLD communities, and also future communities that are incentivized by this airdrop. The desired result of this two-pronged airdrop is for the TLD owners to reinvest the funds in their existing community, in addition to marketing and outreach initiatives.
The first cutoff consists of 31.5M HNS, or 7% of the overall airdrop allocation. This first cutoff concluded on July 31st 2024, and is dedicated for on-chain and off-chain SLD registries, such as Namebase Registry. These registries will be worked with directly to deliver accuracy, trust, and transparency. The airdrop amount will be based on the USD amount earned at the time of registration for the respective TLD, which may involve converting HNS or ETH earnings. This measurement is based on the market and ensures the TLD communities that are the most valued will be rewarded accordingly. There must be a minimum of 20 SLD registrations in order to be considered for this airdrop. As of July 31st, there are 212 HNS TLDs staked with the NB Registry that qualify for the airdrop. The TLD and the airdrop amount earned will be tallied at a later date and shared publicly.
Registries Included:
Open for Discussion:
The second cutoff consists of 13.5M HNS. The cutoff date is February 3rd, 2025, which coincides with Handshake’s fifth birthday. This later cutoff will encourage newcomers as well as other community participants to register, stake, and build communities around their TLDs. Only TLDs staked on dSLD registries, such as HNS.ID or digitalis, will be considered for this airdrop. The reasoning is that dSLD registries are more transparent by nature and should be promoted. In order for existing web3 namespaces (.eth, .btc, .sol, etc.) to qualify for this airdrop, their respective TLD(s) must be bridged over to the HNS TLD counterpart. This will mean that HNS is the active root zone in addition to providing DNS record functionality for their respective namespace.
As this airdrop is intended to encourage positive-sum behavior and community growth, TLD owners that promote cashback programs or self-registering SLDs will not be tolerated. A cashback program is defined as refunding SLD registrants, but may be distinguished from marketing activities such as occasional giveaways. TLD owners that are registering SLDs for the sole purpose of this airdrop will be excluded. Accordingly, there will be extra scrutiny on the larger TLD communities. It is therefore expected that fast growing TLD communities need to publicize their activities and prove their contribution to the network.
All TLD Owners
A total of 45M HNS will be airdropped to all HNS TLD owners. The domain must have been minted by February 3rd 2025, and has to be active by the hard fork date in order to receive the airdrop. The airdrop amount will be proportional to the amount burned at the last on-chain auction for the HNS name. This will encourage quality domain registrations and overall chain activity, while dissuading spam.
Domains may be held on Namebase, ShakeStation, Bob Wallet, or another HNS wallet provider. For domains held with custodians (eg. Namebase), it is at their discretion to allocate the airdrop to individual accounts. For HNS names bought on the secondary market, the airdrop amount will be based on the amount burned for the name’s last on-chain auction. As of July 31st 2024, there were 11.3M domain registrations and 62.5 million HNS burned during auctions. As of now, this roughly equates to a full refund, although that’s subject to change with increased market activity.
HNS V2 Company
Outline
Founding Members & Board
The HNS V2 Company will be governed by a part-time volunteer board consisting of key stakeholders. Board members will not be paid salary or commission. The acting managers for the HNS V2 Company will be long-time community members, including Nole Oppermann, Founder of Hey TX, and Andrew Lee, Handshake co-creator. Other founding members include Namebase, Kyokan, and Superlink. They will collectively be responsible for assisting with the hard fork, HNS L2 development, and dSLD application. Delegation of responsibilities include Namebase helping with the protocol, Kyokan with the technical coding for the L2 and application, and Superlink with the design. The board will include these founding members, in addition to others as determined by the HNS community. New participants may be added to these efforts to contribute according to their own ability.
HNS L2 (revolution)
To improve and extend Handshake as a platform for communities, we propose developing the ability to mint SLDs and issue TLD tokens via introduction of an L2 chain. Combined, this will enable TLD owners to mint SLDs on-chain without leaving the Handshake ecosystem, while providing an option for TLD owners to further launch tokens.
An EVM-based L2 would also enable bridged HNS to trade on decentralized exchanges and integrate with EVM based infrastructure including wallets and block explorers.
A Handshake L2 with EVM will improve user-friendliness for the following use cases:
Since Handshake is a fork of Bitcoin, the L2 explorations are based on how L2 systems are currently designed on Bitcoin.
Rollups
Rollups bundle transactions off-chain and then aggregating it back to the L1 via some form of compact proof. There are two popular types of rollups in the Ethereum world: Optimistic roll-up vs ZK roll-up.
Optimistic Roll-up
Optimistic roll-up operates under the assumption that all transactions are valid unless proven otherwise. This setup requires a multisig controlled by a validator network to inscribe new rollup blocks to L1. In the case of a false transaction, a time-delay challenge-response system is used to halt withdrawals from the main chain.
ZK Roll-up
Zk roll-up utilizes Zero Knowledge proofs to condense validity of all transactions within the proof itself, allowing it to operate under a more trustless environment. The validity proof can be verified directly on L1 before being inscribed on main chain. Whole the validity proof is computational intensive, it does not require a multisig to inscribe new proof onto main chain
Alternative L2
Spiderchain to be researched. However, trust minimization and scalability are preliminary concerns.
Validators (assuming zk roll-up)
L2 Behaviors
SLD Registry Behaviors
Pre-HF requirement
We will need some place for TLD to create a digital community. It does not need to be on footnote, and it should be okay to temporarily use a centralized system for digital communities until the L2 launch.
HF requirement
We will need a way to verify validity proof on HNS L1, and make a coin spendable only if the validity proof checks out. This is done via 'op_cat' and taproot script on Bitcoin L1. We might be able to do something simpler on Handshake depending on how much we can customize consensus rule. Unlike BTC, there is no need to make our solution overly generalizable.
rev id application
The first application built on top of the HNS L2 will be rev id, a decentralized platform for social media creators. The team will closely collaborate with creators to incorporate desirable features. Communities will have the ability to mint dSLD’s, and have their own community token. The HNS V2 Company can receive a portion of the dSLD registrations as revenue. At launch, there will be several social media creators with community sizes larger than one hundred thousand members. This has the potential to be Handshake’s killer app through millions utilizing HNS names.
Future Governance
Republic of TLDs
445M HNS will remain to expand the Handshake ecosystem via a Republic of TLDs.
A network of digital communities coordinates together and practically functions as decision-making mechanism for Handshake, similar to a republic of communities. Contrary to a republic of communities where individuals’ voting power is weighted based on the amount of tokens they own, handshake digital communities vote based on the number of SLD users they have onboarded.
A handshake digital community is an association of people who work together for the betterment of the protocol. For example, the hsd core developers can form a digital community with a mission to maintain the protocol, whereas an influencer can form one with a mission to bring new users to the ecosystems.
A digital community can gain voting power via one of two ways:
A digital community can delegate all or part of their votes to other digital communities. For example, if digital community A has onboarded 10 SLDs and delegated 5 to digital community B, both digital communities will have a voting power of 5.
A SLD user may also re-delegate their vote to another TLD, or to burn their vote entirely by delegating to no one, if they do not agree with the voting direction of their respective TLD. It is recommended a TXT record should be updated to reflect delegation choice of an SLD.
Application Process
There will be an application process where proposals are submitted before the Republic of TLDs. Proposals may be submitted for development, marketing and business initiatives, and other potential benefits to the HNS ecosystem. This future governance model will empower the HNS community to continue advancing the protocol and ecosystem.
A proposed member and/or recipient must state the following:
Technical Considerations
SLDs
As SLDs are a central piece to this system, we need a sybil resistance way of onboarding SLDs. We require all eligible SLDs to be onboarded to an ENS-like system, as described in HIP-005, in order for the TLDs to receive voting power. A burn amount may be added to SLD registration in future proposals if the community deem it necessary to increase the level of sybil resistance. Voting power is based on the number of SLD owners, rather than the number of registered SLDs. Individual owners are determined by public addresses.
Footnote
We propose the footnote protocol as a decentralized method for digital communities and users to coordinate. Footnote is a decentralized protocol designed to work with handshake to store and share a small amount of data.
All digital communities are required to register their TLD on footnote and publish the following information:
All proposals and discussion around the proposals should also be published on footnote.
New L2
HIP-005 supported decentralized SLD registry using an ENS-like system on any EVM-compatible chain. In order to better support future iteration of the digital community systems, we propose a new EVM-compatible, proof-of-stake L2 to be launched with its stakes pegged to handshake. Such a system will be able to provide a more permanent data storage for footnote, a better burning mechanism for SLD registration, as well as any other future improvements to the system.
SLD sovereignty
While TLDs are sovereign, the SLDs can be censured or revoked for violating the communities’ rules and values. This is a necessary condition for the TLD owner, such as a community leader, to enforce the rules and values of the community. As the TLD represents the community, the SLD owner should abide by, and not contradict, the community. Obviously, some communities’ governance will be less restrictive than others.
Remaining Name Claims
With the soft fork of February 2024, the unclaimed Alexa Top 10K and ICANN TLDs were locked. This hard fork proposal includes unlocking the Alexa Top 10k and ICANN for claiming. ICANN TLDs will be permanently reserved for the ICANN TLD owners, and the Alexa Top 10K will be reserved for the ICANN domain counterpart (eg. discord.com) for an additional four years from the hard fork date. While initial $HNS allocations were included for claiming reserved names, this early adoption mechanism will be removed. 10 $HNS will be attached for each of the remaining 11,509 name claims in order to be utilized for updating DNS records, transfers, and renewals. The previously allocated 188.2M HNS, while technically never in existence, will effectively be deducted from the total supply.
Adjusted HNS Coin Supply
Based on July 31, 2024 (blockheight 236,087) [4]:
Other Considerations
The Vision
The vision is to cultivate humans' potential through ensuring freedom of speech, communication, and assembly online with HNS-based technology. From the perspective of many, freedom of speech online has been the focus, but this proposal expands beyond that. There will be an emphasis on building and emboldening diverse communities through Handshake’s deliverance of freely communicating and assembling online. Current events, online and the physical world, highlight the importance of this.
Crypto represents the tokenization of human energy. Massive human energy equates to a valuable community like Bitcoin. HNS can currently be considered a small, passionate community with periodic flickers of energy. While the individuality warrior streak of HNS will remain, this new iteration will bring the coordination and impact of an army.
HNS is a secret hidden in plain sight. From a technical standpoint, HNS is DNS on blockchain. Coupling that with a few enhancements, there are opportunities for limitless communities to coalesce around HNS TLDs. This has never been possible before and has the potential to be a significant improvement on the online community experience.
There is admittedly a pivot from the “build it and they will come” camp. This has been attempted repeatedly over the years without garnering acclaimed success. The HNS L2 (revolution) and first application (rev id) will be built based on direct input from some of the largest content creators and influencers online. This ensures massive distribution on Day 1 of the application’s release. Increasing publicity and usage will have a positive impact on the overall HNS ecosystem.
On the topic of centralization, this proposal will be decided on and implemented by the community. We fully expect (and hope) that the Handshake V2 proposal has amendments based on thoughtful feedback from the community. A primary goal is to have better coordination in the short-term. POW will remain; none of this proposal can be implemented unilaterally. No one, individually or collectively, will be controlling the protocol itself. At the beginning, the implementation of HNS was complex and multi-faceted [1]. Making improvements and iterations demonstrate that there is life within the community and ecosystem. The February 2024 soft fork was a demonstration of this. The potential passage of this proposal does not dictate that there be a singular voice, but rather, all voices of the community will be amplified.
Providing grants through this multi-layered airdrop reallocation to diverse individuals, groups, and businesses will accelerate building and growth. This reboot effort is necessary in establishing a healthy, thriving ecosystem. Half of the overall airdrop reallocation (445M $HNS) will be dedicated to a self-governing funding mechanism to continue progress for the HNS community. This will ensure that current (and future) community projects or initiatives receive adequate funding and attention.
The contents herein are not one-dimensional; the perspectives of community members (builders, miners, entrepreneurs, TLD and coin owners, etc.) have been taken into consideration. The outlined focuses in this proposal will ensure that we as a community accomplish what's necessary to ensure massive adoption for HNS.
HNS is a revolution. We all know that it is a solution to real world problems. HNS represents and embodies rugged freedom; online and the physical world. This proposal is an evolution of Handshake in order to spread this freedom-enhancing technology across the world. We all want to change the web. Let’s make it happen.
[1] Handshake Original Whitepaper https://hsd-dev.org/files/handshake.txt
[2] Web3 Naming Registrations from Encirca https://altroots.com/stats
[3] Grants & Sponsors https://handshake.org/grant-sponsors/
[4] https://hns.cymon.de/stats
[5] https://rerecord.skyinclude.com/
[6] https://github.com/skyinclude/HIPs/blob/HIP018-Adding-A-AAAA-Records/HIP-XXXX-adding-A-AAAA-records.md
Beta Was this translation helpful? Give feedback.
All reactions