Replies: 18 comments 58 replies
-
Importantly, the one component of this proposal that requires a hard fork is making the ICANN TLDs and Alexa Top 1K claimable again. I view this as necessary to do at some point, which is why it’s included. The community can decide through discussion on whether to do a soft or hard fork though. Generating excitement through increased TLD utility, the Alexa 1-10K available for auction, and effectively reducing the total $HNS supply by 56% can result in growing our community and funding development. In addition to being prepared to cover some developer costs in the implementation of this proposal, there should also be a community fund to pay news publications to cover the protocol changes in order to attract new users and builders. There can be HS3 miner giveaways to developers and the overall community. |
Beta Was this translation helpful? Give feedback.
-
I am definitely against this proposal. burning is virtue signaling and a real waste of energy/time and only helps traders in the short term. HNS needs funding, not 1 day of PR for an article saying we burn X million coins, which won't help anything. |
Beta Was this translation helpful? Give feedback.
-
Burning is idiotic. It's a no from me. |
Beta Was this translation helpful? Give feedback.
-
There are a lot of community suggestions to allow for all records on-chain, including MX and ALIAS. As we need to increase users, this can make Handshake more user-friendly and desirable. For those against this, provide your counterpoints. Otherwise, the proposal will be treated as allowing for these other records. |
Beta Was this translation helpful? Give feedback.
-
I fully support this proposal! Handshake needs to burn tokens to restore community confidence! When I bought ETH in 2015, it was priced at $0.7. At that time, ETH didn't have many developers, and no development teams were interested in joining. But when ETH reached $1,000, it became the Layer 1 blockchain with the most developers in the industry! That's how this industry works: price increases attract a majority of speculators, but also attract some value investors who start researching where the project’s value lies. Some people will stay and develop… Handshake has been around for so many years without any influence in the industry; it's time to make a change! I fully support you. |
Beta Was this translation helpful? Give feedback.
-
I love handshake |
Beta Was this translation helpful? Give feedback.
-
Support burn. Been saying this for years. |
Beta Was this translation helpful? Give feedback.
-
Burn it, or the project won't get up. Let's build it together. |
Beta Was this translation helpful? Give feedback.
-
Burn Baby Burn 🪙🤝🔥 |
Beta Was this translation helpful? Give feedback.
-
Burn it, and let's move on! 🔥 |
Beta Was this translation helpful? Give feedback.
-
I am mostly in favour of this proposal. Two observations on some of the non-critical suggestions 1 - Not in favour of tampering with the renewal process. It's fine the way it is 2 - In favour of on chain records of any kind as long as it does not exceed the 512 bytes allocated to each TLD. 3 - We can make domain names (Top 1K) and TLDs claimable for a longer period like 10 years. |
Beta Was this translation helpful? Give feedback.
-
I am stating this here just so its recorded. My current opinions and counter ideas are the following:
That stated, I did some quick research via AI, and we can have a 300 HNS block reward sent to a multi-sig (100 mil lifetime, ~10%). This will be 1,296,000 HNS per month, over ~6.5 years. This is NOT an advocacy for just sending 100m coins on a ledger to be dumped, like a faction appears to fear. This could be increased or reduced based on how fast we want to go vs LP, and community input. We would also want some sort of means to swap out governance people. There are existing ideas that we can use for that, and I can gather some of that info to share, but it is best we be able to do so, as it would be irresponsible otherwise. Additionally some discussion should probably be made with a document, in a GitHub If anyone wants to give constructive feedback on this, feel free to comment. |
Beta Was this translation helpful? Give feedback.
-
I support this proposal. It’s really interesting. Slightly concerned about the top 10,000 being squatted on but apart from that everything seems really good. I definitely think burning the extra tokens is the way to go. Lots of utility for Handshake coming on Cardano soon thanks to Digitalis and Blink Labs 🧪 |
Beta Was this translation helpful? Give feedback.
-
I'm happy to help fund core developers. Thank you for your contributions to the protocol 🤝 |
Beta Was this translation helpful? Give feedback.
-
Our stance On this proposal. For burn - there is too much pushback on a reallocation. Core devs such as Nodar and Zipkin are opposed to any reallocation and imagine miners would be too. The tech and the infrastructure are built first for the developers and maintained by the miners - we are the users and need to respect the foundation of tech and upkeep we are built on. For Alexa 1k + ICANN TLD for claim again, releasing Alexa 1001-10k for auction. But against too much HNS coin allocated to that Alexa 1k + ICANN TLD, they had 4+years to claim that coin, give them enough now to renew for 100+ years. For “ReRecord” and having DNS records on the TLD root / on-chain. This will add a lot of direct utility for names and give more transactions. Those who want to still point to name servers and do off-chain or elsewhere can still do so. Happy our https://rerecord.skyinclude.com was included here. For fee renewal and reducing block size from 600 to 200 - have we done math on this? I’d just want to be careful that WHEN (not IF) we get mass adoption, we become another “expensive Ethereum L1” and people are complaining about high fees. Or is this “relatively easy to adjust” later? For now it is acceptable, but if we are a global root zone this may become costly for those in international markets. |
Beta Was this translation helpful? Give feedback.
-
Burning the airdrop, making ICANN TLDs claimable, and adding records on-chain is the way forward. Is there an effective way to burn the coins, perhaps through an auction-style burn? This would prevent us from facing the same situation again. Fee and renewal limit adjustments should be reconsidered; miners will still earn enough. Transactions will peak with on-chain records. Jesse's idea for a dynamic fee makes sense as long as it doesn't negatively impact users with 3-5 records. I also support Sajan's suggestion of opening the Alexa 1000-10000 names. Thanks, Nole, for making this proposal—it's clearly the direction the community wants to go. Let's set the plan in motion as soon as possible. |
Beta Was this translation helpful? Give feedback.
-
Burning is idiotic. It's a no from me. |
Beta Was this translation helpful? Give feedback.
-
What is the definition of community consensus? If there’s no consensus about what to do with the coins, maybe we should just focus on adding records and unblocking domains? |
Beta Was this translation helpful? Give feedback.
-
Based on community feedback, an alternative proposal is to be presented: Burn Baby Burn. There are currently 628M HNS in circulation, and 890M HNS left unclaimed for open source developers. The primary component is officially ending the open source developer airdrop. The secondary component is making ICANN TLDs and Alexa Top 1K claimable, which requires a hardfork. Overall, this proposal is aligned with the Handshake ethos due to the absence of a centralized foundation or group receiving an airdrop reallocation.
Burning Open Source Developer Airdrop
Rather than reallocating the remaining 890M HNS airdrop, this will be officially removed from the total supply. The arguments for ending the open source developer airdrop include:
Having coin issuance solely derived from POW miners can strengthen $HNS price stability. Removing the possibility of $HNS being created at a zero-cost basis, whether from the open source developer airdrop or name claims, will effectively establish Handshake as an authentic POW chain once-and-for-all. $HNS trending to zero over the past few years is arguably based on the murmurings of this free coin issuance and shroud of the actual coin supply. Rather than allowing these original traits determine the collective price of circulating $HNS, burning will free $HNS from the shackles. The value of $HNS will more accurately be based on the utility of the coin (eg. bidding, renewals, updating records), TLDs in existence, and overall adoption of the protocol. By $HNS increasing in price, this should result in more developers and users overall.
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 1K and ICANN TLDs for claiming. ICANN TLDs will be permanently reserved for the ICANN TLD owners, and the Alexa Top 1K will be reserved for the ICANN domain counterpart (eg. openai.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 for these remaining names. In order to update records, transfers, or renewals, $HNS will need to be acquired on exchanges at market prices. The previously allocated 188.3M $HNS, while technically never in existence, will effectively be deducted from the total supply. The Alexa 1,001-10,000 will become available for auction at the commencement of the hard fork.
Adjusted HNS Coin Total Supply
Based on August 25, 2024 (blockheight 239,664) [1]:
Fee and Renewal Limit Adjustments
This proposal also includes lowering the renewal limit from 600 to 200 per block. Instead of renewals being .1 $HNS every two years, this will effectively create a competitive fee market for miners and TLD owners. This renewal limit adjustment will have a two-fold effect by increasing demand for $HNS and hashrate to secure the network.
ReRecord On-chain (HIP-018)
A and AAAA records can be added to the TLD on-chain. This “allows users to point to an IP address (host), on the HNS blockchain, without needing to also setup or use a name server service, at the bare TLD level” [2] [3]. Here are the benefits for allowing A AAAA records on-chain:
Implementation
If there is community consensus, including support from Namebase, @nodech has agreed to write the code and be the lead developer. There should also be additional developers to review and assist where needed. This support may come from existing members or outside the community. Hey TX is willing to contribute towards implementation efforts. The community can raise the remaining funds necessary to cover costs as needed. Per @pinheadmz, funding for core developers should derive from outside the chain.
As a reference, below is a job description for a core developer:
Cryptocurrency Protocol Engineer: Add features, test, and maintain a layer-1 blockchain daemon based on Bitcoin (UTXO/PoW) written in NodeJS.
[1] https://hns.cymon.de/stats
[2] https://rerecord.skyinclude.com
[3] https://github.com/skyinclude/HIPs/blob/HIP018-Adding-A-AAAA-Records/HIP-XXXX-adding-A-AAAA-records.md
50 votes ·
Beta Was this translation helpful? Give feedback.
All reactions