fix: Remove secondary en
This commit is contained in:
parent
bcafc89a50
commit
faecea7624
GPG Key ID:
203B000478AD0EF1
48
assets.md
48
assets.md
@ -1,48 +0,0 @@
|
||||
---
|
||||
title: Assets
|
||||
description: Handshake Assets
|
||||
published: 1
|
||||
date: 2024-02-18T08:37:19.458Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-18T08:19:53.616Z
|
||||
---
|
||||
|
||||
# Assets
|
||||
|
||||
Here are free to use Handshake assets.
|
||||
|
||||
|
||||
## Monograms
|
||||
 
|
||||
|
||||
|
||||
[Solid Zip](/files/handshake_monogram_solid.zip)
|
||||
|
||||
 
|
||||
|
||||
[Outlines Zip](/files/handshake_monogram_outlined.zip)
|
||||
|
||||
## Wordmarks
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
[Wordmarks Zip](/files/handshake_wordmark.zip)
|
||||
|
||||
|
||||
## Website Favicons
|
||||
Just the plain black or white on transparent background monogram
|
||||
 
|
||||
|
||||
These are zip folders of the monogram resized to standard sized.
|
||||
|
||||
[Black.zip](/files/hns_black.zip)
|
||||
[White.zip](/files/hns_white.zip)
|
||||
|
||||
Alternative download link:
|
||||
https://cloud.woodburn.au/s/hns_assets
|
||||
|
||||
## I WANT EVERYTHING
|
||||
Here's a download of all the Handshake assets: [assets.zip](/files/assets.zip)
|
||||
39
auction.md
39
auction.md
@ -1,39 +0,0 @@
|
||||
---
|
||||
title: Auction
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T04:13:43.915Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T04:13:43.915Z
|
||||
---
|
||||
|
||||
# Auction
|
||||
|
||||
To prevent price sniping, Handshake uses a blind second-price auction called a Vickrey Auction. Users can buy and register top-level domains (TLDs) with Handshake coins (HNS).
|
||||
|
||||
In a Vickrey Auction, a participant is only aware of their own bid. The bids are revealed at the end of the auction when a winner is chosen. The winner pays the second highest bid instead of his or her own.
|
||||
|
||||
- Names were released weekly during a pre-determined 52 week schedule (until Feb 2021)
|
||||
|
||||
- Blind bids can be placed any time after a name is released.
|
||||
|
||||
- Bidding is open to everyone for 5 days beforethe reveal period.
|
||||
|
||||
- Bidders have 10 days to reveal their bid price.
|
||||
|
||||
- A winner is assigned the name and pays the second highest bid at the end of the reveal period.
|
||||
|
||||
- The winning bid is burned and permanently removed from circulation.
|
||||
|
||||
- Losing bids are returned.
|
||||
|
||||
- Names are renewed every 2 years by paying standard network fee.
|
||||
|
||||
For more information, read the [Handshake paper](https://hsd-dev.org/files/handshake.txt).
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
Vickrey Auction's scheme and example
|
||||
33
bobwallet.md
33
bobwallet.md
@ -1,33 +0,0 @@
|
||||
---
|
||||
title: Bob Wallet
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T06:12:01.987Z
|
||||
tags: wallets
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T04:25:34.505Z
|
||||
---
|
||||
|
||||
# Bob Wallet
|
||||
|
||||
[Bob Wallet](https://bobwallet.io) is Handshake’s premiere non-custodial wallet option built by the [Kyokan team](https://www.kyokan.io/)
|
||||
|
||||
{.align-right}
|
||||
|
||||
## Features
|
||||
Search and bid on domain names
|
||||
Manage domains and DNS records
|
||||
Send, receive, and claim HNS
|
||||
Run a full Handshake node
|
||||
|
||||
## Chrome Extension
|
||||
Bob wallet has a chrome extension similar to MetaMask where you can interact with Happs (Handshake Apps) like Shakedex and Niami through your browser. The extension allows you to search and bid on names, send and receive HNS, and manage Handshake TLDs. It runs a light weight SPV node and also doubles as a Resolver for Handshake names though https://www.hdns.io/.
|
||||
|
||||
## Claiming HNS
|
||||
If you had a GitHub account with 15 or more followers in February of 2019, you were entitled to an airdrop of 4,662.598321 HNS. Bob wallet has a built in tool that makes it easy for FOSS developers to claim this HNS under the “Add Funds” tab
|
||||
|
||||
## Shakedex integration
|
||||
Bob wallet has a built in integration with shakedex where you can list and buy domains in a decentralized manner under the “Exchange” tab. Listed names start at their highest price and decline gradually to their reserve price over a specified time frame.
|
||||
|
||||
## Name Claim
|
||||
Soon™
|
||||
50
chatrooms.md
50
chatrooms.md
@ -1,50 +0,0 @@
|
||||
---
|
||||
title: Chatrooms
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-08-05T04:27:29.161Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T04:41:22.692Z
|
||||
---
|
||||
|
||||
# Chatrooms
|
||||
|
||||
## Discord Servers
|
||||
|
||||
| Server | Description |
|
||||
| --- | --- |
|
||||
|[Namer Community](https://discord.gg/tYgYT9QcGG) | General Handshake-related discussion and support. The [Namebase](https://www.namebase.io) team is active on this server. |
|
||||
|[HNSDNS](https://discord.gg/ZNDqqM5GgB) | General Handshake-related discussion and support.|
|
||||
|[Bob Wallet](https://discord.gg/EC6Ta75wkk)| [Bob Wallet](/en/bobwallet) discussion and support.|
|
||||
|[Shakedex](https://discord.gg/CeBKWGjGwk)|Shakedex discussion and support.|
|
||||
| [dWeb Foundation](https://discord.gg/NkTZPsqn6S)|dWeb Foundation's official server.|
|
||||
|
||||
## Telegram Groups
|
||||
|
||||
| Group | Description |
|
||||
| --- | --- |
|
||||
|[Handshake (HNS)](https://t.me/handshake_hns)|General Handshake-related discussion and support.|
|
||||
|[Handshake Dev Chat](https://t.me/hns_tech)|Public room for devs to talk about the Handshake protocol.|
|
||||
|[Bob Wallet](https://t.me/bobwallet)|Group for [Bob Wallet](/en/bobwallet)|
|
||||
|[HandshakeTalk](https://t.me/handshaketalk)|Public discussion for those using Handshake, mining with HandyMiner, or using HandyBrowser.|
|
||||
|[Handshake Traders](https://t.me/handshaketraders)|Handshake trading group.|
|
||||
|[Sinpapeles](https://t.me/sinpapeles_official)|Official group for [Sinpapeles](/en/sinpapeles).|
|
||||
|[HNS Network](https://t.me/hnsnetwork)|Group for block explorer https://hnsnetwork.com.|
|
||||
|[HNS Tools](https://t.me/hns_tools)|Discussion group for Poolwatch, Auction Opening & Finale Telegram bots.|
|
||||
|[Handshake Mercenary](https://t.me/handshakemercenary)|Discussion group for forum https://handshake.mercenary.
|
||||
|
||||
|
||||
## IRC Channels
|
||||
|
||||
| Network | Channel | Description
|
||||
| --- | --- | --- |
|
||||
| [LiberaChat](https://web.libera.chat/#handshake)|#handshake|General Handshake-related discussion and support.|
|
||||
|[Matrix↔IRC Bridge](https://matrix.to/#/#handshake:libera.chat)|#handshake:libera.chat|Matrix bridge to LiberChat #handshake channel|
|
||||
|
||||
|
||||
## See also
|
||||
[Forums](/en/forums)
|
||||
|
||||
|
||||
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
title: Communities
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-09-11T05:38:49.863Z
|
||||
tags: communities
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-10T01:46:22.670Z
|
||||
---
|
||||
|
||||
# Communities
|
||||
|
||||
There are Handshake communities around the world. Find one that is near you.
|
||||
|
||||
|
||||
## North America
|
||||
- [HNS Canada](https://hnscanada.ca/) Canadian community
|
||||
- [Texas community](https://chapters.handshakedirectory.com/usa/texas/) by [Nole.tx/](https://twitter.com/nole__tx)
|
||||
- [Los Angeles community](https://chapters.handshakedirectory.com/usa/la/) by [Paul Singh](
|
||||
https://twitter.com/singhdotin) and [MigsMachine](https://twitter.com/MigsMachine)
|
||||
- [San Francisco community](https://chapters.handshakedirectory.com/usa/sf/) by [Steven Mckie](https://twitter.com/Steven_McKie)
|
||||
|
||||
|
||||
## Asia
|
||||
- [Taiwan community](https://chapters.handshakedirectory.com/taiwan/) by [Pei Hsun Kao](https://twitter.com/PeiHsunKao)
|
||||
- [Thailand community](https://chapters.handshakedirectory.com/thailand/) by [Michael Michelini](https://twitter.com/michelini)
|
||||
- [Vietnam community](https://chapters.handshakedirectory.com/vietnam/) by [Arrene Ng](https://twitter.com/auguryventures)
|
||||
- [India community](https://chapters.handshakedirectory.com/india/) by [Sajan Nair](https://twitter.com/AgaaminT)
|
||||
|
||||
|
||||
## Oceania
|
||||
|
||||
- [HNS AU](/communities/hnsau) Australia community
|
||||
@ -1,22 +0,0 @@
|
||||
---
|
||||
title: Conferences
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T04:15:57.510Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T04:15:57.510Z
|
||||
---
|
||||
|
||||
# Conferences
|
||||
|
||||
## Handycon
|
||||
|
||||
Handycon #1 was a two day conference on March 10th and 11th of 2021. You can find the full recordings of the event [here](http://handycon.promote.hns.to/) or on this [YouTube playlist](https://www.youtube.com/watch?v=0-ax0cEcuZk&list=PLABGm4mKXzKWnfbN2fGjsV4DD_qhXGwGq).
|
||||
|
||||
## Namescon
|
||||
|
||||
Handshake was able to get it's own track at Namescon in September of 2021. Speakers and panelist presented on the 22nd and 23rd of September, but due to Namescon's rules only 3 presentations were allowed to be archived from the conference. These can be found on this [YouTube playlist](https://www.youtube.com/playlist?list=PLmM69V42f8c4nvb8DvoF9wBRboEeNc-Uj). During the conference Namecheap announced that they were offering Handshake SLDs on their platform.
|
||||
|
||||
|
||||
|
||||
@ -1,34 +0,0 @@
|
||||
---
|
||||
title: DNS Hosting
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-09-11T10:02:11.115Z
|
||||
tags: dns, hosting, tools
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T13:01:58.716Z
|
||||
---
|
||||
|
||||
# DNS Hosting
|
||||
|
||||
DNS can be hard to set up. Here is a list of tools that makes Handshake DNS easier.
|
||||
|
||||
|
||||
## Varo
|
||||
Varo is a free and super easy to use DNS hosting provider by [e.skimo/](https://e.skimo)
|
||||
|
||||
Find out more at https://varo.domains/
|
||||
|
||||
Varo is open source so there are clones of it from other community members
|
||||
- https://reg.woodburn.au (Hosted by [Nathan.Woodburn/](/directors/nathanwoodburn))
|
||||
- https://dwebmarketplace.co.uk/
|
||||
|
||||
|
||||
|
||||
## Other Providers
|
||||
|
||||
### [DNS Simple](https://dnsimple.com/)
|
||||
|
||||
### [Arweave Nameserver](https://nameserver.arweave.dev/)
|
||||
|
||||
### [Sinpapeles](/sinpapeles)
|
||||
|
||||
@ -1,46 +0,0 @@
|
||||
---
|
||||
title: Enable HTTPS on Handshake domains
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T03:56:21.216Z
|
||||
tags: technical
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T03:55:04.774Z
|
||||
---
|
||||
|
||||
# Enable HTTPS on Handshake domains
|
||||
|
||||
|
||||
**DNS-based Authentication of Named Entities (DANE)** is an [Internet Security](https://en.wikipedia.org/wiki/Internet_security) protocol to allow [X.509](https://en.wikipedia.org/wiki/X.509) [digital certificates](https://en.wikipedia.org/wiki/Digital_certificates), commonly used for [Transport Layer Security (TLS)](https://en.wikipedia.org/wiki/Transport_Layer_Security), to be bound to [domain names](https://en.wikipedia.org/wiki/Domain_name) using [Domain Name System Security Extensions (DNSSEC)](https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions). TLS/SSL encryption is currently based on certificates issued by [certificate authorities](https://en.wikipedia.org/wiki/Certificate_authority) (CAs). Within the last few years, a number of CA providers suffered serious [security breaches](https://en.wikipedia.org/wiki/Certificate_authority#CA_compromise), allowing the issuance of certificates for well-known domains to those who don't own those domains. Trusting a large number of CAs might be a problem because any breached CA could issue a certificate for any domain name. DANE enables the administrator of a domain name to certify the keys used in that domain's TLS clients or servers by storing them in the Domain Name System (DNS). DANE needs the DNS records to be signed with DNSSEC for its security model to work. Additionally, DANE allows a domain owner to specify which CA is allowed to issue certificates for a particular resource, which solves the problem of any CA being able to issue certificates for any domain. [(Source: Wikipedia)](https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities)
|
||||
|
||||
|
||||
## External Guides
|
||||
There are many ways of enabling HTTPS on your site with DANE depending on your technical aptitude.
|
||||
|
||||
Beginners can try Handout, a combination webserver and nameserver with a single-command configuration script:
|
||||
|
||||
- [Handout guide](https://matthewzipkin.medium.com/building-a-secure-website-on-your-handshake-tld-a8922a950a4f)
|
||||
- [Handout Github repo](https://github.com/pinheadmz/handout)
|
||||
|
||||
These are more technical and detailed methods for advanced developers:
|
||||
|
||||
- [Using Apache and NSD on OpenBSD](https://www.sebastianrasor.com/blog/hosting-a-secure-website-on-the-handshake-protocol-using-dane)
|
||||
- [Using nginx and PowerDNS](https://blog.htools.work/posts/hns-pdns-nginx/)
|
||||
|
||||
To create a self-signed SSL cert and compute its TLSA record (for developers already running a nameserver and webserver):
|
||||
|
||||
- [Gist by buffrr](https://gist.github.com/buffrr/609285c952e9cb28f76da168ef8c2ca6)
|
||||
|
||||
## Configuring a secure webserver for both ICANN and HNS simultaneously
|
||||
- [How To Configure Apache/NGINX for switching TLS certs by domain name for HNS + ICANN dual name support](https://sorablog.eu.org/apache-nginx-with-hns-icann-domain.html)
|
||||
|
||||
## Additional Guides on Creating Handshake Websites
|
||||
These methods may not enforce https/DANE, and may have other security or centralization issues.
|
||||
|
||||
- [Namebase Guide on Creating Handshake Websites](https://learn.namebase.io/starting-from-zero/how-to-create-a-handshake-website)
|
||||
|
||||
## Accessing Handshake Domains Securely
|
||||
See [Resolving Handshake Domains](/en/resolving)
|
||||
|
||||
## Testing Tools for Handshake SSL
|
||||
- [Htools Site Check](https://sitecheck.htools.work/)
|
||||
15
excerpt.md
15
excerpt.md
@ -1,15 +0,0 @@
|
||||
---
|
||||
title: Excerpt
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T12:51:42.182Z
|
||||
tags: hosting, tools, websites
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T12:51:42.182Z
|
||||
---
|
||||
|
||||
# Excerpt
|
||||
|
||||
Excerpt is a simple blog hosting platform that allows you to deploy a blog to your Handshake name in minutes. Find out more at [https://excerpt/].
|
||||
|
||||
Created by [e.skimo](https://e.skimo)
|
||||
20
explorers.md
20
explorers.md
@ -1,20 +0,0 @@
|
||||
---
|
||||
title: Explorers
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-09-11T05:22:21.423Z
|
||||
tags: explorers, tools
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T06:01:43.634Z
|
||||
---
|
||||
|
||||
# Explorers
|
||||
|
||||
- [Niami](/en/niami)
|
||||
- [Cymon](https://hns.cymon.de/)
|
||||
- [HNS Fans](https://e.hnsfans.com/)
|
||||
- [HNS Network](https://hnsnetwork.com/)
|
||||
- [3xpl](https://3xpl.com/handshake)
|
||||
- [Blockchair](https://blockchair.com/handshake)
|
||||
- [HNS Explorer + Name Auctions](https://github.com/kurumiimari/hsexplorer)
|
||||
- [OSS Handshake Explorer](https://github.com/handshake-labs/)
|
||||
81
faq.md
81
faq.md
@ -1,81 +0,0 @@
|
||||
---
|
||||
title: FAQ
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-09-11T05:14:02.724Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T03:37:36.957Z
|
||||
---
|
||||
|
||||
# FAQ
|
||||
|
||||
## How do I use Handshake domains?
|
||||
See the [Getting Started guide](/en/getting-started)
|
||||
|
||||
Where can I buy?
|
||||
You can buy Handshake coins on Namebase with Bitcoin, or USD if you verify your identity. Other exchanges can be found [here](https://www.coingecko.com/en/coins/handshake#markets). As of 12 Dec, 2021 that list includes:
|
||||
|
||||
[MXC (HNS/USDT)](https://www.mexc.com/exchange/HNS_USDT)
|
||||
|
||||
[Gate.io (HNS/BTC)](https://www.gate.io/trade/HNS_BTC) [(HNS/USDT)](https://www.gate.io/trade/hns_usdt)
|
||||
|
||||
[Bittrex (HNS/BTC)](https://bittrex.com/Market/Index?MarketName=BTC-HNS) [(HNS/USDT)](https://global.bittrex.com/Market/Index?MarketName=USDT-HNS) [(HNS/ETH)](https://global.bittrex.com/Market/Index?MarketName=ETH-HNS)
|
||||
|
||||
[Namebase (HNS/BTC)](https://www.namebase.io/pro)
|
||||
|
||||
[Coinex (HNS/USDT)](https://www.coinex.com/exchange?currency=usdt&dest=hns&tab=limit) [(HNS/BTC)](https://www.coinex.com/exchange?currency=btc&dest=hns&tab=limit)
|
||||
|
||||
[Hotbit.io (HNS/USDT)](https://www.hotbit.io/exchange?symbol=HNS_USDT) [(HNS/BTC)](https://www.hotbit.io/exchange?symbol=HNS_BTC)
|
||||
|
||||
[ZTB(HNS/USDT)](https://www.ztb.im/exchange?coin=HNS_USDT)
|
||||
|
||||
[BIT(HNS/USDT)](https://www.bitrue.com/trade/hns_usdt)
|
||||
|
||||
[🤝 (HNS/BTC) (HNS/ADA) (HNS/DOGE) (HNS/LTC)](/🤝)
|
||||
|
||||
|
||||
## How do I stake?
|
||||
Handshake is not an ERC20 token on Ethereum and is not generally considered a "DeFi" asset.
|
||||
|
||||
You can earn money by selling subdomains within your TLDs by visiting the [Namebase Registry](https://www.namebase.io/registry) and entering your name. There is a one-time $100 staking fee (paid in HNS), though, on top of the other per-sale fees. This is not a decentralized service, it is a custodial service provided by Namebase. Any second-level domains purchased from a staked TLD are not ERC20 or any other kind of token.
|
||||
|
||||
You also have the choice of staking your names in a decentralized manner, with the possibility of doing so in a completely trustless manner. Check out [Badass Domains](https://badass.domains/) for more info on that.
|
||||
|
||||
## What wallet is there?
|
||||
|
||||
Currently there are three fully featured wallets; [Bob Wallet](/bobwallet), [Namebase](/namebase) and [ShakeStation](/shakestation). Bob Wallet is non-custodial software which can be used trustlessly, whereas Namebase and ShakeStation are custodial online wallets. You can not buy HNS from Bob Wallet or ShakeStation.
|
||||
|
||||
## What's with the @hns twitter?
|
||||
|
||||
The @HNS Twitter handle is a community-run account and periodically tweets/RTs relevant news, resources, and mentions of Handshake. The account was originally acquired by the project founders and has had its ups and downs of activity. There was a [long community discussion](https://github.com/handshake-org/handshake-web/issues/14) about how to use it going forward and it was decided that the best action was to effectively terminate the account and let the community speak for itself on twitter. Follow #HNS or $HNS to track actual community activity. @HNS has recently been activate in
|
||||
|
||||
## Is there a roadmap?
|
||||
No. There is no central HNS foundation, no marketing budget and no central development effort. Handshake is being built by a diverse group of contributors with their own personal road maps and funding.
|
||||
|
||||
## When Coinbase/Binance/Any other major exchange?
|
||||
Since there's no central HNS foundation nor central development team, the communication with those exchanges lies on the individual members of the community. You, as a Handshake Director, can also help contacting those exchanges and promoting HNS. For technical questions on this topic, check the [Dev Chat on Telegram](https://t.me/hns_tech).
|
||||
|
||||
## Who should I talk to about listing fees or promotional services?
|
||||
See above, there is no central foundation or marketing budget. There are a few decentralized fundraising efforts but they are focused on development and community building:
|
||||
|
||||
- [HNS Fund](https://hnsfund.titansofdata.org/)
|
||||
- [Handshake Institute](https://handy.wiki/wiki/Handshake_Institute)
|
||||
- [dWeb Foundation](https://www.decentralizedinter.net/)
|
||||
|
||||
## Can I use my current browser to visit Handshake websites?
|
||||
Yes you can. See [Resolving Handshake Domains](/resolve)
|
||||
|
||||
You can run an hsd full node with recursive resolver on a Raspberry Pi on your local network by following [this guide](https://gist.github.com/pinheadmz/a3e5ded7a4f0413e948a6a257c375891).
|
||||
|
||||
Note that while a resolver is the only component needed to browse HNS domains, security is a separate issue. At this time since no major browsers support DANE verification, an additional tool is necessary like [letsdane](https://github.com/buffrr/letsdane).
|
||||
|
||||
[Fingertip](https://impervious.com/fingertip.html) is a system extension that runs the hnsd light client and letsdane combined to enable trustless, private HNS name resolution and DANE-verified https for compatible browsers. There are available guides for [connecting Fingertip to Firefox](https://gist.github.com/pinheadmz/264e360742e8b35798bf88005e77f2f8) and a [video demonstration for connecting Fingertip to Chrome or Safari](https://vimeo.com/584892397).
|
||||
|
||||
[Beacon Web Browser](https://impervious.com/beacon) is an iOS app (Android, Desktop coming soon) that verifies DANE and can browse to Handshake websites natively and securely.
|
||||
|
||||
## What's this about reserved names? Can I get one?
|
||||
A snapshot of Alexa's Top 100,000 sites from 2019 is included and these websites can claim their respective TLDs on Handshake (ex: namecheap.com can claim .namecheap). More information on proving ownership and claiming is available on [hsd-dev.org](https://hsd-dev.org/guides/claims.html).
|
||||
|
||||
ICANN TLDs (.com, .org, etc.) were also included in the snapshot and can be claimed by following the same process.
|
||||
|
||||
@ -1,43 +0,0 @@
|
||||
---
|
||||
title: FireWallet
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-13T04:42:53.044Z
|
||||
tags: tools, wallets
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-13T04:42:53.044Z
|
||||
---
|
||||
|
||||
# FireWallet
|
||||
{.align-right}
|
||||
A fully opensource Handshake wallet that is just Fire.
|
||||
|
||||
|
||||
## FireWallet Browser
|
||||
FireWallet Browser is a python application that connects to any HSD node and hosts a web based wallet.
|
||||
It allows for sharing the wallet over a VPN or local network to a mobile device without the connecting device needing a HSD node.
|
||||
FireWallet Browser allows for custom plugins to be added. They are easy to code in Python so anyone can create them.
|
||||
Plugins can get [Niami](/niami) ratings for your domain, automatically set the DNS to a varo clone or even automate a WordPress site setup.
|
||||
|
||||
|
||||
### Features
|
||||
- Basic wallet functionality such as creating/importing wallets and sending/recieving HNS and domains
|
||||
- Sending to HIP2 domain aliases (this allows you to send HNS and domains to domains like @nathan.woodburn)
|
||||
- Download a list of all domains in a customizable format
|
||||
- Resend all pending transactions
|
||||
- Easy theming
|
||||
- Custom plugins
|
||||
|
||||
|
||||
<br><br><br>
|
||||
|
||||
|
||||
## FireWallet Desktop (Not maintained)
|
||||
FireWallet Desktop is a C# based wallet. It is only able to run on Windows and is no longer maintained.
|
||||
It has many batching features to allow for bulk actions.
|
||||
|
||||
|
||||
|
||||
## Links
|
||||
- [Website](https://firewallet.au)
|
||||
- [Support Discord Server](https://l.woodburn.au/discord)
|
||||
24
forums.md
24
forums.md
@ -1,24 +0,0 @@
|
||||
---
|
||||
title: Forums
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-19T05:59:48.531Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T04:48:08.919Z
|
||||
---
|
||||
|
||||
# Forums
|
||||
|
||||
## General Discussion
|
||||
|
||||
- Reddit
|
||||
- [/r/handshake/](https://www.reddit.com/r/handshake/)
|
||||
- [Handshake Mercenary](https://handshake.mercenary/)
|
||||
|
||||
## Regular shows and podcasts
|
||||
- [Skyinclude/](https://skyinclude.com/blog/) - Michael Michelini's podcast and blog
|
||||
- [Namer Stories](https://www.listennotes.com/en/podcasts/namer-stories-graham-j-wallace-r-WUtpOa2QK/) - [graham/](http://graham)'s podcast
|
||||
|
||||
## See also
|
||||
[Chatrooms](/en/chatrooms)
|
||||
@ -1,55 +0,0 @@
|
||||
---
|
||||
title: Getting Started
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-09-11T10:10:36.959Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T03:20:39.508Z
|
||||
---
|
||||
|
||||
# Getting started
|
||||
|
||||
## Use a Handshake DNS Resolver
|
||||
[Resolving Handshake Domains](/resolve)
|
||||
|
||||
## Buy Handshake coins (HNS)
|
||||
In order to acquire Handshake names, you'll need to first purchase Handshake coins (HNS). You can find an updated list of exchanges that accepts Handshake on [CoinGecko](https://www.coingecko.com/en/coins/handshake#markets).
|
||||
|
||||
Check out [Buy Handshake coins (HNS) - A walkthrough for purchasing HNS](https://learn.namebase.io/starting-from-zero/buy-hns) to learn how to use Namebase to buy HNS/
|
||||
|
||||
|
||||
## Get a Handshake name
|
||||
|
||||
There are a few ways to get a name on Handshake:
|
||||
|
||||
- Buying directly from Handshake via [auction process](/auction)
|
||||
- Buying from a secondhand marked such as [Namebase](/namebase) or [ShakeStation](/shakestation)
|
||||
- Claim a [reserved name](/reserved_names).
|
||||
|
||||
**Namebase**
|
||||
Visit [Namebase](/namebase) or [ShakeStation](/shakestation) and use the search to find names you want to own. Alternatively use an [Explorer](/explorers) to search for a domain.
|
||||
|
||||
**Owned — listed for sale**
|
||||
This name's auction ended, the name is owned by someone else and it's up for sale — you can immediately purchase it. If the seller has enabled "Make an Offer", you'll also be able to make them an offer for their name.
|
||||
|
||||
**Owned — unlisted**
|
||||
This name's auction ended, the name is owned by someone else and it isn't up for sale. If the owner has enabled "Make an Offer", you'll be able to make them an offer on their name.
|
||||
|
||||
**Unopened auction**
|
||||
This Handshake name auction hasn't started and placing a bid on this — around 30 minutes to confirm — will begin the auction.
|
||||
|
||||
**Active auction**
|
||||
This Handshake name auction is underway.
|
||||
|
||||
**Revealing**
|
||||
This name's auction recently ended and the winner will receive their name once the reveal period ends.
|
||||
|
||||
**Reserved**
|
||||
This name is either one of the existing ~1,500 blacklisted traditional TLDs or is reserved for a top 100,000 Alexa website.
|
||||
|
||||
|
||||
## Use your Handshake name
|
||||
|
||||
Check out the [using_names](/using_names) page to see what you can use your Handshake domain for.
|
||||
|
||||
14
handshake.md
14
handshake.md
@ -1,14 +0,0 @@
|
||||
---
|
||||
title: Handshake
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T04:08:59.896Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T03:11:04.797Z
|
||||
---
|
||||
|
||||
# Handshake
|
||||
Handshake is a naming protocol that’s backwards compatible with the existing DNS system. It does not replace the DNS protocol, but instead expands the root zone file where TLD ownership information is stored and the root servers with a distributed and decentralized blockchain-based system, which nobody controls and anybody can use. This allows the root zone to be uncensorable, permissionless, and free of gatekeepers like ICANN.
|
||||
|
||||
Every peer in the Handshake network cryptographically validates and manages the root zone, which also removes the need for the Certificate Authority system (CAs) entirely. Names are logged on the Handshake blockchain, which is essentially one big distributed zone file that anyone has the right to add an entry in.
|
||||
@ -1,51 +0,0 @@
|
||||
---
|
||||
title: Handshake Improvement Proposals
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T04:02:44.100Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T04:02:44.100Z
|
||||
---
|
||||
|
||||
# Handshake Improvement Proposals
|
||||
|
||||
"A Handshake Improvement Proposal is a technical document that attempts to standardize a feature or protocol extension across the Handshake ecosystem. It should be implementation-agnostic. If you would like to propose a specific change to `hsd` or `hnsd`, open an issue or pull request in the appropriate repository. HIPs are not consensus, they are not law, they may never be actually implemented in production. HIPs are just solutions to common problems that the Handshake developer community can use as reference in their own projects. They may change over time, or be replaced with newer HIPs." - [HNS-Dev.org](https://hsd-dev.org/HIPs/)
|
||||
|
||||
|
||||
## HIP-0 HIP Template
|
||||
The meta on proposing HIPs
|
||||
|
||||
[https://hsd-dev.org/HIPs/proposals/0000/](https://hsd-dev.org/HIPs/proposals/0000/)
|
||||
Author: [falci/](http://falci)
|
||||
|
||||
## HIP-1 Non-Interactive Atomic Name Swaps
|
||||
Describing a way to sell TLDs onchain without knowing your counter party beforehand. HIP-1 is what Shakedex is based on.
|
||||
|
||||
|
||||
[https://hsd-dev.org/HIPs/proposals/0001/](https://hsd-dev.org/HIPs/proposals/0001/)
|
||||
Author: Mark Tyneway
|
||||
|
||||
## HIP-2 Well Known Wallets
|
||||
Allow domain owners to attach crypto-wallet addresses to their TLDs using e.g. [falci/.well-known/BTC](https://falci/.well-known/BTC) for you Bitcoin address.
|
||||
|
||||
|
||||
[https://hsd-dev.org/HIPs/proposals/0002/](https://hsd-dev.org/HIPs/proposals/0002/)
|
||||
Author: [falci/](http://falci)
|
||||
|
||||
## HIP-4 Interactive Atomic Name Swaps
|
||||
Allow predefined counterparties to trade a TLD onchain at a predfined price
|
||||
|
||||
|
||||
[https://hsd-dev.org/HIPs/proposals/0004/](https://hsd-dev.org/HIPs/proposals/0004/)
|
||||
Author: [pinheadmz/](http://pinheadmz)
|
||||
|
||||
## HIP-5 Alternative Namespace Resolution
|
||||
Create a standard for hosting zone data at other locations not on at an IP address. The first implementation is for `_eth` which allows ENS on Ethereum to manage DNS records for Handshake TLDs like [.badass/](https://medium.com/@ca98am79/introducing-badass-domains-4d90bd48108b)
|
||||
|
||||
|
||||
|
||||
|
||||
[https://hsd-dev.org/HIPs/proposals/0005/](https://hsd-dev.org/HIPs/proposals/0005/)
|
||||
Author: [carson/](http://carson), [pinheadmz/](http://pinheadmz)
|
||||
|
||||
@ -1,81 +0,0 @@
|
||||
---
|
||||
title: Handshake Institute
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T05:23:05.333Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T05:23:05.333Z
|
||||
---
|
||||
|
||||
# Handshake Institute
|
||||
|
||||
The Handshake Institute is an independent advocacy and educational non-profit organization. The Handshake Institute works to promote decentralization through Handshake, but does so independently and it has no control over the Handshake protocol.
|
||||
|
||||
## Recent Grants
|
||||
### HNSFund Grant
|
||||
**March 17, 2021**
|
||||
The Handshake Institute gave a grant to [HNSFund](https://hnsfund.titansofdata.org/) in order to catalyze developer participation in the Handshake open source community.
|
||||
|
||||
The grant funds were transferred on March 16, 2021 through [Gitcoin](https://gitcoin.co/grants/1428/handshake-development-fund):
|
||||
|
||||
- \+ [150,000 PAN (~$13698)](https://etherscan.io/tx/0x1fdcea6acea9060106efc1dec750468194aaa36cbc4cb47b7755fe02aac56123)
|
||||
- \+ [20.727 ETH (~$37045)](https://etherscan.io/tx/0xf42a9aabb87bc8bad184cf3983fd45b7ec2509f670d8535a92266b8528598e80)
|
||||
- **Total** ~$50.7k USD
|
||||
|
||||
HNSFund received additional donations from other sources:
|
||||
|
||||
- ~$5,200 from Gitcoin Grants Round 9 donation matching
|
||||
- ~75,000 PAN ($7,096.50) from [Panvala League](https://panvala.com/) donation matching all Gitcoin donations made in PAN
|
||||
- 36,272 HNS ($14,474) from HandyCon auction donations
|
||||
|
||||
HNSFund used the grant to fund projects, organizations, teams and individuals to get involved in Handshake development
|
||||
|
||||
**Recipients**
|
||||
- [Kyokan](https://kyokan.io/) - The builders of Bob Wallet and Footnote received 3 ETH to build out a domain claiming feature for reserved TLDs and top 100,000 Alexa domains. They received another 2 ETH for continuing their work for the Handshake community.
|
||||
- skydroid/ - 3 ETH to improve their DoH infrastructure, start targeting other OSes besides Android, and hire a designer before Handshake community does a marketing push for them
|
||||
- skyinclude/ - 3 ETH to create tutorials for Bob Wallet (claiming reserved TLDs) and Shakedex (starting auctions and fulfilling auctions)
|
||||
- sulu/ - 500 DAI to create memes and marketing materials
|
||||
- hmail/ - 3 ETH for open sourcing their email service, writing documentation to make it easier for others to install, researching connecting email clients to mail servers over DANE, and creating a video tutorial of setting up DANE on their OpenBSD system.
|
||||
- falci/ - 3 ETH for open source development in Handshake
|
||||
- dees/ - 3 ETH for open source development in Handshake
|
||||
|
||||
Learn more about this round at [HNSFund](https://hnsfund.titansofdata.org/grants-and-bounties/grant-rounds/proposed-round-1)
|
||||
|
||||
|
||||
### HandyCon Grant and HNSFund Auction
|
||||
**March 10-11, 2021**
|
||||
|
||||
**Event Sponsorship**
|
||||
The **Handshake Institute** sponsored the first ever Handshake Conference, [HandyCon](http://handycon.promote/) [(non-dweb)](https://2021.handycon.xyz/). The Institute made a $2500 USD contribution to help with the organizing of the event.
|
||||
|
||||
Handshake Institute Director [Handshake Jesus](https://twitter.com/handshakejesus), was invited to join a [panel discussion](https://www.youtube.com/watch?v=Lv_2wkKMPWg) around support for the Handshake ecosystem. He was joined on the panel by [Kiba Gateaux](https://twitter.com/kibagateaux) of the [HNSFund](https://hnsfund.titansofdata.org/), members of the [dWeb Foundation](https://decentralizedinter.net/) and [Matthew Zipkin](https://twitter.com/MatthewZipkin) from [impervious](https://impervious.com/).
|
||||
|
||||
|
||||
**HNSFund Auction**
|
||||
The Handshake Institute collaborated with HNSFund, [Mark Smith](https://twitter.com/namesakemark) of [Namesake Domains](https://namesake.domains/), and HandyCon organizer [Michael Michelini](https://twitter.com/michelini) to organize a fundraising auction for HNSFund.
|
||||
|
||||
The auction was conducted by [Mark Smith](https://twitter.com/namesakemark) in which 17 domains were successfully sold for 85677 HNS with 34094 HNS of the proceeds being donated to the HNSFund.
|
||||
|
||||
Organizing Participants:
|
||||
|
||||
- [Michael Michelini](https://twitter.com/michelini) of [skyinclude](https://www.youtube.com/channel/UCYmhmyF5TnsovrFSBD3t5-A) and [Handshake Mercenary](http://handshake.mercenary/) organized this event and made videos of HandyCon available on [YouTube](https://www.youtube.com/playlist?list=PLABGm4mKXzKWnfbN2fGjsV4DD_qhXGwGq)
|
||||
- Mark Smith of Namesake Domains conducting the auction
|
||||
- [Johnny Wu (johnnywu/)](http://johnnywu/) & [Namebase](https://www.namebase.io) handled the auction transfers, logistics and coordinating to donate the funds to HNSFund.
|
||||
- [Kiba Gateaux](https://twitter.com/kibagateaux) provided auction preparation to raise funds on behalf of the HNS open source community
|
||||
|
||||
**Handshake Institue gifts jj/**
|
||||
|
||||
During a Q&A event with Handshake Creators [JJ](https://twitter.com/_chjj) and [Andrew Lee](https://twitter.com/2drewlee), the Handshake Institute gifted the Handshake name `jj/` to JJ, who accepted the gift. The Handshake Institute [gifted the name](https://hnsnetwork.com/txs/271f8045676cb263e545f881260d45fa2fc01475bd2f249fb77b4e161a898b5c) as an expression of gratitude for his work on Handshake.
|
||||
|
||||
|
||||
### ShakeDex Grant
|
||||
**February 20, 2021**
|
||||
[ShakeDex](http://shakedex.com/) is a decentralized exchange for Handshake names, and its creation brings a fully decentralized reverse-Dutch auction system that allows names to be bought and sold without intermediaries.
|
||||
|
||||
The Institute gave a [grant of 10000HNS](https://e.hnsfans.com/tx/8f33129fb1a8e45602b0fd5b36f435bf48fa6586b8a6a719c179c035eb40ac97) to the pseudonymous creator of ShakeDex, kurumiimari.
|
||||
|
||||
|
||||
ShakeDex Resources
|
||||
- [ShakeDex Web](http://shakedex.com/)
|
||||
- [ShakeDex on GitHub](https://github.com/kurumiimari/shakedex)
|
||||
13
hmail.md
13
hmail.md
@ -1,13 +0,0 @@
|
||||
---
|
||||
title: Hmail
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T05:23:50.041Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T05:23:50.041Z
|
||||
---
|
||||
|
||||
# Hmail
|
||||
|
||||
Hmail is Handshake's first email service, and only email service to allow you to use your own Handshake name. It was created by [sebastian.rasor/](https://en.handypedia.org/wiki/User:Sebastian.rasor).
|
||||
@ -1,28 +0,0 @@
|
||||
---
|
||||
title: HNS Tokenomics
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T04:07:06.390Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T04:07:06.390Z
|
||||
---
|
||||
|
||||
# HNS Tokenomics
|
||||
|
||||
## Overview
|
||||
HNS has a hard-cap of 2,040,000,000 coins. 66% of this was pre-mined and 46.6% of all HNS was aidropped to free and open source developers.
|
||||
|
||||
|
||||
|
||||
|
||||
> {.align-center}
|
||||
[https://medium.com/blockchannel/handshake-distribution-quadrants-f6199ff3cdcd](https://medium.com/blockchannel/handshake-distribution-quadrants-f6199ff3cdcd)
|
||||
|
||||
## Burning
|
||||
At the end of a [TLD auction](/en/auction) all the money paid by the winner do not go to anyone, it is burned (locked away and never usable again).
|
||||
|
||||
According to [Shake Stats](https://shakestats.com/) the HNS analytics website, over 1% of the total HNS supply has already been burned in auctions.
|
||||
|
||||
Many Handshake community members have embraced the burn meme and incorporated burning HNS into their applications like [shakedex](https://shakedex.readthedocs.io/en/latest/community_burn.html)
|
||||
|
||||
85
hnsfund.md
85
hnsfund.md
@ -1,85 +0,0 @@
|
||||
---
|
||||
title: HNS Fund
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T05:05:16.714Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T05:04:27.648Z
|
||||
---
|
||||
|
||||
# HNS Fund
|
||||
|
||||
HNS Fund is a community run development fund. It is the only source of non-VC, non-dilutive grants funding in the HNS community. Our goal is to support and empower our fellow open source developers and creators in their mission to create a free and open internet on the dweb.
|
||||
|
||||
The HNS Fund was created out of the need to source funding and coordinate builders within the HNS community because there is no Handshake Foundation, founding team, etc.
|
||||
|
||||
They give grants to community members that are working to expand the ecosystem, build tooling, create new use cases for personal TLDs, and make onboarding and adoption easier for people new to HNS. All projects must be [free and open source software](https://www.freeopensourcesoftware.org/index.php/Main_Page) and must follow the Handshake Community Guidelines to receive HNS Fund grants. Anyone individual, company, or, DAO is eligible for funding if they are devoting funds to FOSS development for HNS. The HNS Fund primarily focuses on these areas:
|
||||
|
||||
- Core Handshake protocol development
|
||||
- Domain management tools (e.g. claiming, registries/registrars, DNS records)
|
||||
- Wallets
|
||||
- Browser integrations
|
||||
- Auction tools
|
||||
- Educational content
|
||||
- Identity solutions
|
||||
- Community growth
|
||||
|
||||
## Values
|
||||
- Values
|
||||
- Autonomy
|
||||
- Community
|
||||
- Gifting
|
||||
- Collaboration
|
||||
- Experimentation
|
||||
- Memes
|
||||
- Freedom of Expression
|
||||
- Decentralization
|
||||
- Resilience
|
||||
- Mutual Support
|
||||
|
||||
## DAO Structure
|
||||
The HNS Fund follows a [holocracy](https://en.wikipedia.org/wiki/Holacracy) model where each team is independent and autonomous with complete control of how they operate and spend the resources allocated to them. Teams in the HNS Fund DAO are organized groups of Handshake community members that would like to contribute to the HNS ecosystem. Each team controls their own multisig and can use their funds however they see fit without requiring approval from any other team or Master Multisig signer.
|
||||
|
||||
[HNS Fund Teams](/en/hnsfund_teams):
|
||||
|
||||
- Grants
|
||||
- Bounties
|
||||
- Endowment
|
||||
- Ambassadors
|
||||
- Fundraising
|
||||
|
||||
## Treasury Management
|
||||
All funds are donated to primary HNS Fund Master Multisigs. This is to prevent phishing attempts and make accounting .much easier. Distributions to each HNS Fund DAO team are calculated each month and sent to each team's multisig after income for the month has been accounted and each teams allocation calculated. Each team controls their own multisig and can use their funds however they see fit without requiring approval from any other group or Master Multisig signer.
|
||||
|
||||
{.align-center}
|
||||
|
||||
|
||||
## HNS Fund Income Distribution
|
||||
|
||||
| Team | Share of income |
|
||||
| --- | --- |
|
||||
| Core Protocol | 20% |
|
||||
| Grants | 20% |
|
||||
| Bounties | 20% |
|
||||
| Endowment | 20% |
|
||||
| Fundraising | 10% |
|
||||
| Ambassadors | 10% |
|
||||
|
||||
Changes to treasury management over time:
|
||||
|
||||
- 01/2021 - 03/2021 - The HNS Fund originally gave out 80% of all donations as grants and 20% for bounties. kiba_gateaux/ was the only signer on the multisig.
|
||||
- 04/2021 - present - Created sub-teams to lead specific initiatives. Multiple independent multisigs with multiple signers on each.
|
||||
|
||||
|
||||
## HNS Fund History
|
||||
The HNS Fund was started in October 2020 as a way to help some of the early devs in the HNS community be able to work more on their projects.
|
||||
October 12th 2020 - The [Gitcoin grants page](https://gitcoin.co/grants/1428/handshake-development-fund) where 50% of all HNS Fund donations originate was created.
|
||||
January 10th 2021 - The first HNS Fund grant went to falci/ (TK page) on for [0.29 ETH](https://etherscan.io/tx/0xad5600edef3a8ddca5e175f0e2dd3fb1b5e49a5a18aeaddb1082b4f4ba4c7679) (~$400 at the time).
|
||||
March 11th 2021 - The first TLD auction that donated a part of all sales to HNS Fund was at the first Handy Con(TK Handycon page) after the closing keynote.
|
||||
March 16th 2021 - The Handshake Institute(TK page) gave a ~$50,000 donation to the HNS Fund in [Panvala tokens(tk panvala page) and Ethereum](https://handshake.institute/#hnsfund-grant).
|
||||
|
||||
|
||||
## See also
|
||||
- [HNS Fund Teams](/en/hnsfund_teams)
|
||||
- [HNS Fund Grant Rounds](/en/hnsfund_rounds)
|
||||
@ -1,28 +0,0 @@
|
||||
---
|
||||
title: HNS Fund Grant Rounds
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T05:10:15.371Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T05:10:15.371Z
|
||||
---
|
||||
|
||||
# HNS Fund Grant Rounds
|
||||
|
||||
You can find all the information you need for all past grant round such as who received funding, for what, and the transaction hashes of each grant in the official database of HNS Fund Grants.
|
||||
|
||||
| Round | Recipient | Grant Amount |
|
||||
|-------|-------------|--------------|
|
||||
| **0** | | |
|
||||
| | falci/ | 0.29 ETH |
|
||||
| **1** | | |
|
||||
| | falci/ | 3 ETH |
|
||||
| | shakedex/ | 10,000 HNS |
|
||||
| | Bob Wallet | 5 ETH |
|
||||
| | dees/ | 3 ETH |
|
||||
| | rasor/ | 3 ETH |
|
||||
| | skydroid/ | 3 ETH |
|
||||
| | skyinclude/ | 3 ETH |
|
||||
| | sulu/ | 500 DAI |
|
||||
| **2** | | |
|
||||
@ -1,50 +0,0 @@
|
||||
---
|
||||
title: HNS Fund Team
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T05:08:40.312Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T05:07:31.914Z
|
||||
---
|
||||
|
||||
# HNS Fund Team
|
||||
|
||||
The HNS Fund follows a [holocracy](https://en.wikipedia.org/wiki/Holacracy) model where each team is independent and autonomous with complete control of how they operate and spend the resources allocated to them. Teams in the [HNS Fund DAO](https://en.handypedia.org/wiki/HNS_Fund) are organized groups of Handshake community members that would like to contribute to the HNS ecosystem. Teams are funded through the HNS Fund Master Multisig based on total donations for that month. Each team organizes internally in whatever way works for them and gets positive results. Each team controls their own multisig and can use their funds however without requiring approval from any other team or Master Multisig signers
|
||||
|
||||
## Grants Program
|
||||
Grants go out to dedicated HNS community members who are continuously providing valuable contributions to the ecosystem. Grants can be for completely discretionary use or may have targeted features/conditions tied to it which will be discussed with grant recipients before they accept and receive their funding. You can view grant recipients on our [Grant Rounds page](/en/hnsfund_rounds).
|
||||
|
||||
Grants Team Leaders: Kiba_Gateaux/,
|
||||
|
||||
|
||||
## Bounties Program
|
||||
The Bounties Team manages open bounties in the HNS ecosystem. These could be to upgrade the HNS protocol, add a feature to an open source product like Bob Wallet, translating handy.wiki content to other languages, or really anything the see fit to develop the HNS ecosystem. They are responsible for vetting bounty requests, properly speccing out completion criteria, ensuring bounties are easy to participate in e.g. by providing supporting docs for a job, verifying bounty has been adequately completed, and distributing payments to winner. We maintain a spreadsheet of open bounties and payment transactions.
|
||||
|
||||
Bounties Team Leaders: Kiba_Gateaux/
|
||||
|
||||
|
||||
## Core Protocol
|
||||
For research and development of the core Handshake protocol and tooling. Generally for mid to long term projects that require in-depth knowledge of the protocol and extensive testing before deployment.
|
||||
|
||||
Team Leaders: pinheadmz/
|
||||
|
||||
|
||||
## Community Ambassadors
|
||||
Engage and liaison with other communities on behalf of Handshake and HNS Fund. Could be creating a dweb industry alliance, running Clubhouse calls, geo-specific communities, schmoozing at ICANN events, or DAO to DAO collaborations.
|
||||
|
||||
Ambassador Team Leaders: Tracy Fong, Mark Smith, Michael Michelini
|
||||
|
||||
|
||||
## Fundraising Events
|
||||
Organize and host events that drive donations to HNS Fund. Could be fundraising auctions, paid workshops, meetups with paid sponsorship, etc. Can be done in collaboration with other entities as long as a significant portion of revenue from the event is going to the HNS Fund (> 2%)
|
||||
|
||||
Fundraising Team Leaders: Colin Burke, Michael Michelini
|
||||
|
||||
|
||||
## Endowment
|
||||
In charge of creating a sustainable treasury for HNS Fund. The Endowment receives a portion of all donations to invest in DeFi. Interest earned on this principal is used to support HNS Fund and HNS ecosystem in perpetuity.
|
||||
|
||||
Team Leaders: Kiba_Gateaux/
|
||||
|
||||
|
||||
@ -1,41 +0,0 @@
|
||||
---
|
||||
title: HNSHosting
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-15T01:53:25.961Z
|
||||
tags: hosting
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T12:45:11.196Z
|
||||
---
|
||||
|
||||
# HNSHosting
|
||||
|
||||
[HNSHosting](https://hnshosting.au) is a simple and easy way to use your domain for a wordpress site.
|
||||
Wordpress allows you to have an easily customizable website on your Handshake domain.
|
||||
Powered by [Nathan.Woodburn/](https://nathan.woodburn)
|
||||
|
||||
## Features
|
||||
- Secured over SSL with DANE
|
||||
Anyone with a resolver supporting DANE will be redirected to the HTTPS version on your site and will have an encrypted connection using DANE for verification
|
||||
|
||||
- Fully Managed
|
||||
Control over plugins, users, access and everything with your site.
|
||||
|
||||
- Hosted with security in mind
|
||||
The worker servers are fully secured so that the only access is HTTP for web traffic.
|
||||
Any terminal access for maintenance is over a VPN tunnel to stop any unauthorized access. All SSH connections send a push notification to the admin's phone to alert him to any access.
|
||||
|
||||
- Regular backups
|
||||
The worker servers has weekly encrypted backups to an offsite location to allow recovery of any data if the server goes down.
|
||||
|
||||
## Pricing
|
||||
|
||||
- Free Licences supported by OpenSystems
|
||||
Up to 1 GB storage capacity.
|
||||
Claim via [Nathan.Woodburn/ discord server](https://l.woodburn.au/discord)
|
||||
|
||||
- Increased limits on request
|
||||
|
||||
## Tutorials
|
||||
|
||||
- [Setup for domains hosted in Namebase](https://l.woodburn.au/hnshosting_nb)
|
||||
69
hnssearch.md
69
hnssearch.md
@ -1,69 +0,0 @@
|
||||
---
|
||||
title: HNSSearch
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T12:32:02.125Z
|
||||
tags: websites, tools
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T04:57:24.624Z
|
||||
---
|
||||
|
||||
# HNSSearch
|
||||
|
||||
{.align-right}
|
||||
**HNSSearch** (Slogan: Your window into the dweb) is a search engine that exclusively indexes Handshake websites and that does not track any user or traffic information. The first beta went live in February 2021 with the official launch of Version 1 on the 28th of February. The shield in the logo of HNSSearch is a representation of the commitment to protect the privacy of its users by not gathering any information. Results are based on search queries and not previous searches.
|
||||
|
||||
## History
|
||||
|
||||
{.align-right}
|
||||
Version 1 of HNSSearch was released on the 28th of February after a two-week-long public beta and was meant to be a proof of concept. The design was a clone of Google with the addition of dark mode and additional features such as shortcuts.
|
||||
|
||||
V1 was well received by the community and received a lot of feedback and suggestions for improvements. The decision was made to not continue the development of V1, but to immediately start working on Version 2 that would have a new codebase as well as a new design and new functionalities. V1 was written mainly in PHP, used a MySQL Database, and was hosted on a conventional cloud provider.
|
||||
|
||||
LINDA (Living Indexer Navigating Decentralized Assets) is the crawler of HNSSearch and written in Python, the search engine itself is made by [MeiliSearch](https://github.com/meilisearch/MeiliSearch) and was written in Rust and the frontend is made with React. This new tech stack allowed for V2 to be hosted on dweb services such as [Akash](https://akash.network/) for the backend and [Sia Skynet](https://siasky.net/) for the frontend.
|
||||
|
||||
|
||||
## Search results
|
||||
|
||||
With V2 HNSSearch introduced search as you type powered by [MeiliSearch](https://www.meilisearch.com/). This allows the search results to be displayed in real-time as the search term is entered and allows the user to narrow down their query and stop if they have found what they are looking for. MeiliSearch also brings typo tolerant search results and as such provides a natural query language experience. The search results are purely ranked by hits and accuracy and no other ranking takes place. Therefore, the results are independent of user preference and previous search queries.
|
||||
|
||||
## Shortcuts
|
||||
|
||||
Shortcuts were proposed by community members and are derived from the !Bang feature of [DuckDuckGo](https://duckduckgo.com/bang).
|
||||
|
||||
Shortcuts can be used by entering the shortcut followed by a space and the search query (for example !nb hnssearch). By then pressing enter, the search query will be sent to the desired website and a new tab opens.
|
||||
|
||||
Available shortcuts:
|
||||
|
||||
- !hn => hnsnetwork
|
||||
- !nb => namebase
|
||||
- !hm => handshake mercenary
|
||||
- !sp => parking.sinpapeles
|
||||
- !ni => niami
|
||||
- !hf => e.hnsfans
|
||||
- !sh => shakestats
|
||||
|
||||
|
||||
## Specialty logos
|
||||
For special occasions, the logo on the front page was changed to commemorate the special occasion and to show love to other dweb projects.
|
||||
|
||||
> 
|
||||
Handy Con 2021
|
||||
|
||||
|
||||
> 
|
||||
Launch of HandyHost
|
||||
|
||||
> 
|
||||
Saint Patrick's Day 2021
|
||||
|
||||
## Future development
|
||||
The beta of V2 ended on the 19th of December 2021 and the website was taken offline. Currently, the developers work on refining and finishing V2 to release it and to open-source the code.
|
||||
|
||||
## External links
|
||||
- [Official Website (Handshake native)](http://hnssearch/)
|
||||
- [Official Website (mirror)](https://hnssearch.io/)
|
||||
|
||||
|
||||
|
||||
|
||||
43
home.md
43
home.md
@ -1,43 +0,0 @@
|
||||
---
|
||||
title: Home
|
||||
description: Handypedia the wiki for everything Handshake related
|
||||
published: 1
|
||||
date: 2024-02-26T05:45:20.892Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T02:55:52.074Z
|
||||
---
|
||||
|
||||
# Handypedia
|
||||
|
||||
Welcome to the Handshake Wiki,
|
||||
for all your Handshake information needs.
|
||||
This wiki is maintained by the Handshake community.
|
||||
|
||||
## Handshake
|
||||
{: .align-left}
|
||||
|
||||
[Handshake](/en/handshake) is a decentralized DNS root zone that eliminates the need to trust potential bad actors like ICANN and certificate authorities. Handshake uses peer-to-peer technology to operate with no central authority: domain ownership and transfers are carried out collectively by the network.
|
||||
|
||||
Handshake is a completely decentralized project and there is no official singular Foundation, Committee, Corporation, or entities in permanent unitary control of the protocol.
|
||||
|
||||
Handshake is the first successful implementation of a *distributed alternative DNS root zone*. Building upon the notion that the internet should be decentralized, Handshake is designed around the idea of using cryptography to control the creation and transfer of top-level domains, rather than relying on central authorities.
|
||||
|
||||
Handshake names have all the desirable properties of a top-level domain. They are secure, private, durable, useful, and difficult to counterfeit.
|
||||
|
||||
## Why
|
||||
Names on Handshake are valuable over legacy systems because they are secured by a decentralized peer-to-peer network. Handshake seeks to address the root problem with legacy DNS: all the trust that's required to make it work -- Not that justified trust is a bad thing, but trust makes systems brittle, opaque, and costly to operate. Trust failures result in systemic collapses, trust curation creates inequality and monopoly lock-in, and naturally arising trust choke-points can be abused to deny access to due process. Through the use of cryptographic proof, decentralized networks, and open source software, Handshake minimizes and replaces these trust costs.
|
||||
|
||||
Handshake names are:
|
||||
- Permissionless and borderless. The software can be installed by anybody worldwide.
|
||||
- Anonymous. Handshake does not require any ID to use making it suitable for the the privacy-conscious.
|
||||
- Private. When used with care Handshake can support strong privacy.
|
||||
- Censorship-resistant. Nobody is able to block or seize a name on Handshake.
|
||||
- Online and available 24 hours a day, 365 days per year.
|
||||
|
||||
|
||||
## Handypedia
|
||||
Handypedia is a community ran wiki for Handshake. You can [login with your Handshake domain](/login) to update this wiki.
|
||||
Please report any issues with Handypedia to [Nathan.Woodburn/](/directors/nathanwoodburn)
|
||||
|
||||
Handypedia collects basic analytics which can be accessed by anyone [here](https://umami.woodburn.au/share/l3nMbcAlMWLIZ1cC/Handypedia)
|
||||
42
mining.md
42
mining.md
@ -1,42 +0,0 @@
|
||||
---
|
||||
title: Mining
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T03:44:45.659Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T03:44:45.659Z
|
||||
---
|
||||
|
||||
# Mining
|
||||
|
||||
Handshake (HNS) is mined using a combination of the BLAKE2b and SHA3 algorithms.
|
||||
|
||||
**Handshake blockchain details:**
|
||||
|
||||
- Proof of Work (PoW) with difficulty adjustment after each block\
|
||||
- BLAKE2b + SHA3 hash algorithm
|
||||
- Block target time of 10 minutes
|
||||
- [2,040,000,000 HNS maximum total supply](https://www.reddit.com/r/handshake/comments/j9g3y8/faq_what_is_the_coin_emission_schedule_for_hns/)
|
||||
|
||||
It is not efficient to try and mine with CPU/GPU. Instead, ASICs specifically built to mine with the above algorithm combination are the way to go.
|
||||
|
||||
**List of known Handshake ASIC miners:**
|
||||
|
||||
- [Goldshell](https://www.goldshell.com/products/#hns): HS5, HS3, HS3-SE, HS-BOX, HS1/1-Plus, etc.
|
||||
- Various FPGA miners like MultMiner M1, Monad Imperium F2, Hummer Miner H1, etc. may also be able to mine efficiently
|
||||
|
||||
Depending on your hash power, it may also be beneficial to mine with a mining pool vs. trying to mine solo.
|
||||
|
||||
**List of Handshake mining pools:**
|
||||
|
||||
- [Handshake pool mining stats](https://miningpoolstats.stream/handshake)
|
||||
- Urkel
|
||||
- [ViaBTC Mining tutorial](https://support.viabtc.com/hc/en-us/articles/900001994586-HNS-Mining-)
|
||||
- [Poolin Mining tutorial](https://help.poolin.com/hc/en-us/articles/360055366031-Poolin-Supports-Mining-HNS)
|
||||
- [DxPool Mining tutorial](https://www.dxpool.com/help/en/hns-mining-tutorial)
|
||||
- [F2Pool Mining tutorial](https://f2pool.io/mining/guides/how-to-mine-handshake/)
|
||||
|
||||
A wallet address will be needed to store mining rewards. This can be a deposit address generated from an entity such as Namebase, or it can be generated locally using Bob Wallet or various other wallets that support Handshake.
|
||||
|
||||
See [wallets](/en/wallets) to get a list of wallets to you can use/
|
||||
14
myths.md
14
myths.md
@ -1,14 +0,0 @@
|
||||
---
|
||||
title: Myths
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T03:26:35.639Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T03:26:35.639Z
|
||||
---
|
||||
|
||||
# Myths
|
||||
|
||||
- Namebase created/owns Handshake -> This is false! Namebase is just the easiest way to get started using Handshake
|
||||
- Namebase is the only way to bid/buy Handshake names -> You can also use Bob Wallet
|
||||
48
namebase.md
48
namebase.md
@ -1,48 +0,0 @@
|
||||
---
|
||||
title: Namebase
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T12:32:36.408Z
|
||||
tags: wallets, websites
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T05:32:22.384Z
|
||||
---
|
||||
|
||||
# Namebase
|
||||
|
||||
{.align-right}
|
||||
|
||||
[Namebase](https://www.namebase.io) is an onramp for Handshake. Namebase did not create Handshake but is a member of its community.
|
||||
"Our mission is to enable freedom and safety on the internet"
|
||||
Namebase's goal is to make Handshake easy-to-use to enable mass adoption, and you can use the platform to easily buy and sell HNS as well as bid on, purchase, sell, and use Handshake names.
|
||||
|
||||
## Revenue Streams
|
||||
While Handshake is a non-profit movement, Namebase is a for-profit company building on Handshake. Its [revenue streams](https://learn.namebase.io/about-namebase/revenue-streams) include:
|
||||
|
||||
### Exchange
|
||||
While you may see other exchanges list HNS, Namebase is the only one fully focused on unlocking Handshake's potential. [Namebase Consumer](https://www.namebase.io/buy) can be used to purchase HNS with BTC or USD. There are no trading fees and the exchange aims to price HNS with a spread of 1-3% depending on market conditions.
|
||||
|
||||
### Namebase Pro
|
||||
[Namebase Pro](https://www.namebase.io/pro) can be used trade HNS for BTC using a traditional order book exchange similar to Binance and Coinbase Pro. Namebase Pro has some of the lowest trading fees (0.1% maker fee and 0% taker fee). Due to cryptocurrency regulations, those within the USA are currently unable to access Namebase Pro.
|
||||
|
||||
### Bidding
|
||||
Namebase's [bidding service](https://namebase.io/domains) makes it possible for anyone to participate in Handshake name auctions without needing to be a developer. No fees are charged for the bidding services. The mining fees that are charged for bid placements are paid to the miners who add your transactions to the Handshake blockchain, and do not get paid to Namebase.
|
||||
|
||||
### Marketplace
|
||||
The [Namebase Marketplace](https://namebase.io/domains) makes it easy to sell or purchase owned Handshake names. A 3% commission fee to sellers is collected when your name successfully sells.
|
||||
|
||||
### Namebase Registry
|
||||
The [Namebase Registry](https://www.namebase.io/registry) is a service that enables you to sell 2nd-level domains on your Handshake TLD. Namebase partnered with the creator of the .io registry to create this service that is compatible with existing registrars, making it easy to plug directly into their existing distribution channels. The Namebase Registry operates on a revenue-sharing model — after a $1 processing fee, 70% of proceeds go to the TLD owner and 30% go to Namebase.
|
||||
|
||||
## Backers
|
||||
Namebase is a [VC-backed company](https://namebase.io/about). Some of its backers include Fred Ehrsam of Paradigm, Balaji Srinivasan of Earn.com, Anthony “Pomp” Pompliano of Morgan Creek Capital, Eric Meltzer of Primitive Ventures, Robert Leshner of Compound Labs, Steve Jang of Kindred Ventures, and Josh Elman of Greylock Partners.
|
||||
|
||||
## Verifying
|
||||
Namebase is an incorporated company that has to follow normal AML/KYC laws like other onramps such as Coinbase. Learn more about their verification requirements here.
|
||||
|
||||
It is still possible to use Namebase to acquire Handshake names [entirely privately](https://learn.namebase.io/about-namebase/private-naming) without revealing any personal information.
|
||||
|
||||
## Social
|
||||
- [Twitter](https://twitter.com/namebasehq)
|
||||
- [Discord](https://discord.com/invite/V3aTrkp)
|
||||
|
||||
35
niami.md
35
niami.md
@ -1,35 +0,0 @@
|
||||
---
|
||||
title: Niami
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T12:33:11.758Z
|
||||
tags: tools, websites, explorers
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T05:26:53.639Z
|
||||
---
|
||||
|
||||
# Niami
|
||||
|
||||
{.align-right}
|
||||
Niami allows users to discover Handshake domain names from secondary domain markets like Namebase or Shakedex. The site also provides a Handshake block explorer, a portfolio manager, name ratings and the ability to open, bid on, or reveal names via Bob Wallet's browser extension.
|
||||
|
||||
## History
|
||||
Niami was published on October, 27th 2020. The site was created by [0xstefan](https://twitter.com/0xStefan). The domain auction features and the Handshake explorer were added later on September 15, 2021.
|
||||
|
||||
## Features
|
||||
### Ratings
|
||||
Ratings are automatically created for domain names that have at least been in a "REVEAL" state. Domain names can get up to 10,000 points but can never fall below 0. Each domain name starts with a score of 500. The calculation system rewards but also punishes names. For example a name gets rewarded if it's short or if it had a high auction price. It gets punished if it contains a hyphen or underscore or if it's not a word in any of the [supported languages](https://www.niami.io/faq).
|
||||
|
||||
### Handshake Explorer
|
||||
The Handshake explorer allows its users to search and navigate the Handshake blockchain. It can be used (among other things) to check current and historical address balances, transfer histories or status of transaction confirmations.
|
||||
|
||||
### Domain Name Auctions
|
||||
The domain name auction feature in combination with [Bob Wallet](/en/bobwallet)'s browser extension allows users to search, open, bid on or reveal names.
|
||||
|
||||
### Handshake Portfolio
|
||||
In January 2022, Niami introduced "Handshake Portfolio" to help users share and discover valuable domain names.
|
||||
|
||||
## External links
|
||||
- [Official Website](https://niami.io)
|
||||
- [Official Website (Handshake native)](https://niami)
|
||||
- [Niami on Twitter](https://twitter.com/Niami_HNS)
|
||||
@ -1,96 +0,0 @@
|
||||
---
|
||||
title: Reserved names
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-09-11T10:15:26.234Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T05:42:01.227Z
|
||||
---
|
||||
|
||||
# Reserved name
|
||||
|
||||
Existing TLDs and over 100,000 Alexa websites are reserved on the Handshake blockchain. Upon removing collisions, generic, and exclusions (e.g. 1 or 2 character names), approximately 80,000 names remain. Using the root key and DNSSEC, domain owners can cryptographically prove ownership to the Handshake blockchain to claim names. 100,000 was chosen as a number which the ownership is clear and has already gone through policy and process.
|
||||
|
||||
## End of the claims
|
||||
|
||||
Reserved domains were able to be claimed for 4 years after the launch of Handshake. This deadline has passed. Rather than let all the domains be registered by anyone after this deadline passed (how the original code was written), Handshake did a soft fork to stop the top 10,000 domains from being registered. If any of these 10,000 domains want to be claimed, Handshake will need to do a hard fork to re-enable claims.
|
||||
|
||||
## Existing TLDs
|
||||
All existing [ICANN TLDs](https://github.com/handshake-org/hs-names/blob/master/names/tld.json) ([ccTLDs](https://github.com/handshake-org/hs-names/blob/master/names/cctld.json), [gTLDS](https://github.com/handshake-org/hs-names/blob/master/names/gtld.json), [rTLD](https://github.com/handshake-org/hs-names/blob/master/names/rtld.json)) are reserved and can't be opened at auction.
|
||||
|
||||
## Alexa
|
||||
The Handshake blockchain pre-reserves the [top ~100,000 domain names](https://github.com/handshake-org/hs-names/blob/master/names/alexa.json) from the Alexa top 1 million domain names. Since the Handshake blockchain only thinks in terms of top-level domains, existing domains on the Alexa top 1 million are "converted" to TLDs.
|
||||
|
||||
For example:
|
||||
|
||||
`google.com` -> `google`
|
||||
`bbc.co.uk` -> `bbc`
|
||||
|
||||
### Rules
|
||||
In order to have your domain pre-reserved, there are a few rules implemented in generate.js that it must conform to:
|
||||
|
||||
- The domain's deepest subdomain must not be in the blacklist.
|
||||
- The domain's deepest subdomain must not be a pseudo-TLD for an existing naming project.
|
||||
- The domain's deepest subdomain must not be a trademarked name.
|
||||
- The domain must not collide with an existing top-level domain in ICANN's root zone, as all existing TLDs are also pre-reserved. For example, `google.com` would lose to `google`.
|
||||
- The domain must not collide with a higher-ranked domain. For example, `google.co.uk` would lose to `google.com`. Only the owner of the higher-ranked domain is able to redeem it.
|
||||
- The domain must not be deeply nested. `bbc.co.uk` will work, but `jeffs-blog.wordpress.com` will not.
|
||||
- The domain must abide by Handshake policy standards (no leading or trailing hyphens or underscores).
|
||||
- The domain must not be a single letter.
|
||||
- If the domain is ranked lower than 50,000, the domain must not be two letters.
|
||||
- If the domain is ranked lower than 50,000, the domain must not be an [English word](https://raw.githubusercontent.com/handshake-org/hs-names/master/names/words.json).
|
||||
|
||||
## Blacklist
|
||||
The following list is permanently reserved:
|
||||
|
||||
- `example`
|
||||
- `invalid`
|
||||
- `local`
|
||||
- `localhost`
|
||||
- `test`
|
||||
|
||||
## Late Additions
|
||||
Names which were added *after* the final snapshot:
|
||||
|
||||
- `charity` - A new gTLD added on ICANN's system.
|
||||
- `inc` - A new gTLD added on ICANN's system.
|
||||
- `ss` - ccTLD for South Sudan.
|
||||
- `xn--mgbah1a3hjkrd` - iccTLD for Mauritania.
|
||||
- `cpa` - A new gTLD added on ICANN's system.
|
||||
- `gay` - A new gTLD added on ICANN's system.
|
||||
- `xn--qxa6a` - iccTLD for .eu in Greek.
|
||||
- `llp` - A new gTLD added on ICANN's system.
|
||||
|
||||
Names which were *removed* after the final snapshot:
|
||||
|
||||
- `goodhands` - A gTLD removed from ICANN's system.
|
||||
- `jlc` - A gTLD removed from ICANN's system.
|
||||
- `panerai` - A gTLD removed from ICANN's system.
|
||||
- `spiegel` - A gTLD removed from ICANN's system.
|
||||
- `statoil` - A gTLD removed from ICANN's system.
|
||||
- `telecity` - A gTLD removed from ICANN's system.
|
||||
- `vista` - A gTLD removed from ICANN's system.
|
||||
- `epost` - A gTLD removed from ICANN's system.
|
||||
- `zippo` - A gTLD removed from ICANN's system.
|
||||
- `blanco` - A gTLD removed from ICANN's system.
|
||||
- `active` - A gTLD removed from ICANN's system.
|
||||
- `bnl` - A gTLD removed from ICANN's system.
|
||||
- `cartier` - A gTLD removed from ICANN's system.
|
||||
- `chrysler` - A gTLD removed from ICANN's system.
|
||||
- `dodge` - A gTLD removed from ICANN's system.
|
||||
- `doha` - A gTLD removed from ICANN's system.
|
||||
- `duns` - A gTLD removed from ICANN's system.
|
||||
- `everbank` - A gTLD removed from ICANN's system.
|
||||
- `honeywell` - A gTLD removed from ICANN's system.
|
||||
- `iselect` - A gTLD removed from ICANN's system.
|
||||
- `ladbrokes` - A gTLD removed from ICANN's system.
|
||||
- `mobily` - A gTLD removed from ICANN's system.
|
||||
- `mopar` - A gTLD removed from ICANN's system.
|
||||
- `piaget` - A gTLD removed from ICANN's system.
|
||||
- `srt` - A gTLD removed from ICANN's system.
|
||||
- `starhub` - A gTLD removed from ICANN's system.
|
||||
- `uconnect` - A gTLD removed from ICANN's system.
|
||||
- `warman` - A gTLD removed from ICANN's system.
|
||||
- `xn--mgbb9fbpob` - An iccTLD removed from ICANN's system.
|
||||
- `lancome` - A gTLD removed from ICANN's system.
|
||||
152
resolve.md
152
resolve.md
@ -1,152 +0,0 @@
|
||||
---
|
||||
title: Resolving Handshake Domains
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-09-11T05:16:11.845Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T05:50:52.713Z
|
||||
---
|
||||
|
||||
# Resolving Handshake Domains
|
||||
|
||||
Visiting HNS websites in your browser securely requires two pieces of software:
|
||||
|
||||
1. HNS Resolver: Looks up domain names and gets IP addresses for web servers to fetch website data. Also fetches DNSSEC data which are DNS records with cryptographic keys and signatures to ensure authenticity.
|
||||
1. DANE Verifier: Relies on a secure HNS resolver to verify SSL certificates from web servers and establish secure HTTPS connections.
|
||||
|
||||
There are many methods to visit HNS websites on your computer and there are trade-offs for each method.
|
||||
|
||||
## Methods
|
||||
|
||||
### hsd full node + letsdane proxy
|
||||
|
||||
[HSD](https://github.com/handshake-org/hsd)
|
||||
[LetsDANE](https://github.com/buffrr/letsdane)
|
||||
|
||||
> Security: HIGH
|
||||
> Privacy: HIGH
|
||||
> Decentralization: HIGH
|
||||
> Convenience: MEDIUM
|
||||
> Complexity: HIGH
|
||||
{.is-info}
|
||||
|
||||
HSD is the most bullet-proof piece of Handshake software available. It verifies every single transaction and every single block against every single protocol rule we have. It has the best security practices and the best privacy. It does complete recursive domain name resolution from the HNS root zone all the way down. letsdane is the best tool available for verifying DANE and establishing HTTPS connections to websites hosted on Handshake domains. It checks all DNSSEC records served by hsd and checks the certificate offered by the web server. Every cryptographic signature is verified. If a user installs both of these on the computer they are browsing from, there is very little surface for attack: your browsing history remains private and all data transmitted and received is private and secure.
|
||||
|
||||
|
||||
### hsd SPV node / hnsd light client + letsdane proxy (Fingertip)
|
||||
[Fingertip](https://impervious.com/fingertip)
|
||||
[HSD](https://github.com/handshake-org/hsd)
|
||||
[HNSD](https://github.com/handshake-org/hnsd)
|
||||
[LetsDANE](https://github.com/buffrr/letsdane)
|
||||
|
||||
> Security: HIGH
|
||||
> Privacy: MEDIUM
|
||||
> Decentralization: MEDIUM
|
||||
> Convenience: MEDIUM
|
||||
> Complexity: HIGH
|
||||
{.is-info}
|
||||
|
||||
Users install and launch the software. The light client syncs the blockchain (may take one minute or more). User must add a locally-generated certificate to their browser's trusted certificate store. User then must configure their browser to proxy all HTTP requests through the proxy so that DANE can be verified. Can be configured for a single browser like Firefox or the entire operating system can be run through the software. Light clients rely on hsd full nodes on the Handshake p2p network for block headers. This means that only SOME of the HNS consensus protocol is verified, like proof-of-work. External full nodes are required to resolve top-level domains from the HNS root zone. All data is verified, but the hsd full nodes you connect to will learn the top-level domains you are looking up.
|
||||
|
||||
There are available guides for [connecting Fingertip to Firefox](https://gist.github.com/pinheadmz/264e360742e8b35798bf88005e77f2f8) and a video demonstration for [connecting Fingertip to Chrome or Safari using the operating-system level](https://vimeo.com/584892397).
|
||||
|
||||
### Beacon Web Browser
|
||||
[Beacon Web Browser (currently only released for iOS)](https://impervious.com/beacon)
|
||||
|
||||
> Security: HIGH
|
||||
> Privacy: LOW
|
||||
> Decentralization: MEDIUM
|
||||
> Convenience: LOW
|
||||
> Complexity: LOW
|
||||
{.is-info}
|
||||
|
||||
Beacon is a web browser that works a lot like Fingertip but is self-contained. It is convenient since it requires no setup, but inconvenient since it requires a user to abandon their current default browser. The technical mechanism is similar to Fingertip but Beacon does not do recursive name resolution, meaning it relies on external DNS-over-HTTPS servers. It leaks domain names to those servers, but still verifies all data using the blockchain data it keeps internally from hnsd. If Chrome / Safari / Brave / Opera ever adopt Handshake in a meaningful way, this method will probably be the best we can hope for.
|
||||
|
||||
### Internal HNS resolver: hsd or hnsd without letsdane proxy
|
||||
[HSD](https://github.com/handshake-org/hsd)
|
||||
[HNSD](https://github.com/handshake-org/hnsd)
|
||||
|
||||
> Security: LOW
|
||||
> Privacy: HIGH (hsd) / MEDIUM (hnsd)
|
||||
> Decentralization: HIGH (hsd) / MEDIUM (hnsd)
|
||||
> Convenience: MEDIUM
|
||||
> Complexity: HIGH
|
||||
{.is-info}
|
||||
|
||||
|
||||
A user can install their own HNS resolver but neglect to install the DANE verifying software. This user will be able to browse to websites hosted on HNS domain names BUT NEVER SECURELY. This user can not establish an HTTPS connection but can still "see" HNS websites, assuming the web server allows HTTP connections without requiring or enforcing security. A user can even run hsd on a server and connect to it remotely. This is technically an external resolver and will require additional security (SIG0) to ensure that the received data is authentic.
|
||||
|
||||
|
||||
### External HNS resolver
|
||||
[HNSDoH](https://welcome.hnsdoh.com) <!--
|
||||
[hdns.io](https://hdns.io)
|
||||
[NextDNS](https://nextdns.io/)-->
|
||||
[resolvr](https://resolvr.info/)
|
||||
[HandshakeNames](https://handshakenames.com/dns-resolver)
|
||||
[Bob Wallet Chrome Extension](https://bobwallet.io/)
|
||||
|
||||
> Security: LOW
|
||||
> Privacy: LOW
|
||||
> Decentralization: LOW
|
||||
> Convenience: HIGH
|
||||
> Complexity: LOW
|
||||
{.is-info}
|
||||
|
||||
Access Handshake domains by getting DNS records from a public resolver. The most important thing to know about this method is that SOMEONE ELSE IS VERIFYING THE BLOCKCHAIN, NOT YOU. Since the blockchain is the root of all "trust" in this system, you are outsourcing absolutely everything including security and privacy. It may be possible to run a letsdane proxy in addition to these resolvers and establish a secure HTTPS connection between your browser and the web server. However, since the blockchain data is being served to you from some untrusted source we can not classify this method as truly secure. This is currently how Brave actually resolves "decentralized domain names" such as Unstoppable Domains and Ethereum Name Service.
|
||||
|
||||
### External proxy like hns.to
|
||||
[hns.to](https://hns.to)
|
||||
|
||||
> Security: EXTREMELY LOW
|
||||
> Privacy: LOW
|
||||
> Decentralization: LOW
|
||||
> Convenience: EXTREMELY HIGH
|
||||
> Complexity: LOW
|
||||
{.is-info}
|
||||
|
||||
Users are presented with an illusion that they can "see" websites hosted on HNS domains but really they are looking at a website hosted on legacy ICANN domain name. If there is any HTTPS security offered at all it is anchored in legacy certificate authority. The server knows the entire URL you are looking up and knows all data you send and receive to the web server. The proxy CAN ALTER DATA you send or receive to the web server, including links. This is currently how Puma browser resolves Handshake domains. This is marked as extremely low security as the proxy can view and edit any traffic.
|
||||
|
||||
> NEVER USE A PROXY TO ENTER PASSWORDS OR SENSITIVE INFO.
|
||||
{ .is-warning }
|
||||
|
||||
|
||||
## Features and Rankings
|
||||
### Security
|
||||
Can you trust the authenticity of the content you see in the browser? Can you enter private, personal or sensitive data into a website? Most browsers offer a "lock" icon in the URL bar when an HTTPS connection is established, meaning the answer to both these questions is "yes". Eavesdropping on your connection is impossible and altering data to and from both you and the web server is impossible. It's important to remember that HTTPS requires proper configuration by the website and domain name owners as well. Just because you have set up the proper tools on your computer does not mean every website is secure.
|
||||
|
||||
- **HIGH**: Secure HTTPS is available. Domain name has been cryptographically verified and web server identity has been cryptographically identified.
|
||||
- **LOW**: Secure HTTPS is not available. The chain of cryptographic verification is broken. Do not trust this content. Do not enter personal data into this website.
|
||||
|
||||
### Privacy
|
||||
Do any other entities (besides your browser and the web server) know what websites you are visiting?
|
||||
|
||||
- **EXTREMELY HIGH**: Everything about your connection is completely encrypted and obfuscated. Only possible with networks like Tor and NOT Handshake. This level is listed only as a reference point.
|
||||
- **HIGH**: Domain name lookups are done entirely on your own computer, no one else knows what domain names you are looking up.
|
||||
- **MEDIUM**: Only the top-level domain is leaked to another entity. For example, some service may know the URL you are seeking ends in .com but they do not know you are looking up google.com.
|
||||
- **LOW**: The entire URL is leaked to another entity. Someone out there knows exactly which websites you visit.
|
||||
|
||||
### Decentralization
|
||||
How many other services do you rely on for this connection? How easy is it for your connection to get censored or terminated outside of your control?
|
||||
|
||||
- **EXTREMELY HIGH**: It is essentially impossible for any entity to prevent your browser from connecting to the web server. Only possible with networks like Tor and NOT Handshake. This level is listed only as a reference point.
|
||||
- **HIGH**: You do not rely on any service or third party to connect to the web server. Everything about the connection is handled by your computer and the web server without any help.
|
||||
- **MEDIUM**: Some outside service is required, but that service can be provided by anyone (even yourself if you run your own service). If one service provider fails, ANY other provider can be used.
|
||||
- **LOW**: Your connection depends entirely on one single service. If they go down, you can not connect. If they decide to block you or ban you from their service, you can not connect.
|
||||
|
||||
### Convenience
|
||||
How easy is it to configure your computer to use this method.
|
||||
|
||||
- **EXTREMELY HIGH**: User does nothing except buy a computer. This is how the legacy DNS and certificate authority systems work.
|
||||
- **HIGH**: User changes some kind of setting in their operating system or in their browser's preferences, but otherwise doesn't have to do anything unusual.
|
||||
- **MEDIUM**: User installs new software on their computer, but otherwise doesn't have to do anything unusual or anything outside their every-day internet usage behavior.
|
||||
- **LOW**: User installs new software on their computer and has to change their ordinary behavior (like switching to a new browser).
|
||||
|
||||
### Complexity
|
||||
Related to convenience. What percentage of the internet population is capable of executing all the necessary steps to correctly execute this method?
|
||||
|
||||
- **HIGH**: Requires command-line tools, installing dependencies, shared libraries or compilers.
|
||||
- **MEDIUM**: Requires installing new software directly from a website or GitHub (i.e. not your device's "App Store").
|
||||
- **LOW**: Nothing required, user does nothing they do not already do every day with their device. Includes changing settings in an application or operating system.
|
||||
|
||||
|
||||
@ -1,31 +0,0 @@
|
||||
---
|
||||
title: Securing your wallet
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T03:29:02.471Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T03:29:02.471Z
|
||||
---
|
||||
|
||||
# Securing your wallet
|
||||
|
||||
## Tips to secure your HNS
|
||||
|
||||
**Security should be a very important concern for any HNS user (and web 3 in general).**
|
||||
|
||||
Here's few very useful security tips for securing your HNS wallet and securing you while browsing HNS sites:
|
||||
|
||||
- Not your keys - not your money
|
||||
This very simple rule applies to all cryptocurrencies. Do not use exchanges / light wallets (with wallet management from the heavy version on the server) and so on. If you need to buy a domain, and you want to do it using [Namebase](https://www.namebase.io), transfer there exactly as many coins as you need to buy this domain. To store HNS, it is better to use wallets that do not send your private keys anywhere, and interact with the blockchain directly from your PC. One of the really safe wallets for HNS is the [bob wallet](https://bobwallet.io)
|
||||
|
||||
<br>
|
||||
|
||||
- Securely store your seed phrases and private keys
|
||||
Don't store it in .txt file on desktop! Better take a piece of paper, and write seed there. It's more safe.
|
||||
|
||||
<br>
|
||||
|
||||
- Don't use handshake bridges
|
||||
If you're an active user of HNS sites, the worst thing you can do is add hns.is at the end of domains handshake. HNS bridges proxy all traffic of sites that you visit with it through itself, so it can modify content of sites, insert ads or even steal your cookies/passwords If you want to use hns sites on a permanent basis, you should install the resolver software. One good resolver is [fingertip](https://impervious.com/fingertip.html)
|
||||
|
||||
@ -1,23 +0,0 @@
|
||||
---
|
||||
title: ShakeCities
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T12:48:32.018Z
|
||||
tags: tools, websites
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T12:48:32.018Z
|
||||
---
|
||||
|
||||
# ShakeCities
|
||||
|
||||
[ShakeCities](https://shakecities.com) is a site offering free personalizable websites.
|
||||
This is a perfect way to start your journey into Handshake domains!
|
||||
Step into a new experience where Handshake domains become instant sites, and where everyone can create their own unique decentralized page.
|
||||
|
||||
Secured with HTTPS powered by DANE (DNS-based Authentication of Named Entities).
|
||||
But that's not all – ShakeCities goes beyond, allowing you to seamlessly integrate crypto addresses into your site, providing an easy way to get paid. Simply send crypto to `@yourname.shakecities` (or on our shorter TLDs `@yourname.onsc`
|
||||
|
||||
Your ShakeCity domain can be used to chat on [HNSChat](https://hns.chat) or to authenticate on any site using Varo auth (such as this wiki)
|
||||
Join us in building a decentralized, secure, and innovative internet landscape. Embrace the future with ShakeCities – where Handshake domains meet simplicity.
|
||||
|
||||
An example site is https://nathan.shakecities/
|
||||
26
shaker.md
26
shaker.md
@ -1,26 +0,0 @@
|
||||
---
|
||||
title: Shaker
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-09-11T05:20:46.199Z
|
||||
tags: tools
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-10T01:30:07.120Z
|
||||
---
|
||||
|
||||
# Shaker
|
||||
|
||||
Shaker is a discord bot used to verify ownership of a Handshake domain.
|
||||
This bot is managed by [Nathan.Woodburn/](/directors/nathanwoodburn) so please contact him if the bot has any issues.
|
||||
|
||||
## How to use
|
||||
1. Run `/verify` and enter your domain
|
||||
2. Follow the instructions the bot gives by adding the TXT record provided
|
||||
3. Wait a few minutes and run `/verify` again with the same domain as before to get the bot to check you added the TXT record
|
||||
|
||||
|
||||
|
||||
## How to add to your own server
|
||||
1. Invite the bot using [this link](https://discord.com/api/oauth2/authorize?client_id=1073940877984153692&permissions=402653184&scope=bot)
|
||||
2. Create a Verified domain role (eg. the Namebase uses `Namer` and the HNSDNS server uses `Domainer`)
|
||||
3. Tell the bot to assign verified users that role by using the `/setverifiedrole` command
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
title: ShakeStation
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T12:33:44.995Z
|
||||
tags: wallets, websites
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T05:52:46.216Z
|
||||
---
|
||||
|
||||
# ShakeStation
|
||||
|
||||
[ShakeStation](https://shakestation.io) is a custodial platform for Handshake users. ShakeStation did not create Handshake, but has been built by members of its community.
|
||||
|
||||
## Platform Offerings:
|
||||
### Auctions: Bidding, Revealing, etc.
|
||||
https://shakestation.io/auctions
|
||||
|
||||
### Name Claims
|
||||
https://shakestation.io/claims
|
||||
|
||||
### Marketplace
|
||||
https://shakestation.io/marketplace
|
||||
|
||||
### Portfolio: Name/TLD management
|
||||
https://shakestation.io/portfolio
|
||||
|
||||
### Account management
|
||||
https://shakestation.io/account
|
||||
Includes the capability to configure a .shakestation alias for others to send HNS to you, use for login for Handshake utilities like HNS Chat, etc. Example: ng.shakestation
|
||||
|
||||
(More to come...)
|
||||
|
||||
@ -1,35 +0,0 @@
|
||||
---
|
||||
title: Sinpapeles
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T12:34:06.703Z
|
||||
tags: tools, websites
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T05:58:46.831Z
|
||||
---
|
||||
|
||||
# Sinpapeles
|
||||
|
||||
{.align-right}
|
||||
Sinpapeles \[sĩm pa.ˈpe.les] (Spanish for "no papers" or "no ID") is a non-custodial project for Handshake domains content management.
|
||||
|
||||
## App.Sinpapeles
|
||||
[App.Sinpapeles](https://sinpaples.xyz/) is the main Sinpapeles project. It was created to help domain owners to add content or redirect from their Handshake domain to a legacy domain.
|
||||
|
||||
Its features include:
|
||||
|
||||
- [DANE](/en/dane) support: https for Handshake domains.
|
||||
- [Sia's Skynet](https://siasky.net/) to host unlimited static content.
|
||||
- DNS management, including `MX` records.
|
||||
- Unlimited subdomains.
|
||||
|
||||
## Parking.Sinpapeles
|
||||
[Parking.Sinpapeles](http://parking.sinpaples/) is an [open source](https://github.com/Falci/parking.sinpapeles/), free, landing page and domain listing for secondhand selling. It believes that the best place to advertise a domain is the domain itself.
|
||||
|
||||
Domain owners can add DNS records direct to [Handshake blockchain](http://parking.sinpapeles/about), which is monitored by Sinpapeles and automatically updates the Parking website.
|
||||
|
||||
## Profile Builder
|
||||
{.align-right}
|
||||
[Sinpapeles Profile Builder](https://sinpapeles.hns.siasky.net/) is an [open source](https://github.com/falci/sinpapeles-profile-builder) web app to generate static profile page. The builder allows the users to add unlimited number of links, including mail and phone number. It's also possible to customise background and foreground colours and font family.
|
||||
|
||||
After creating the profile, it's possible to download the source in HTML or JSON format and/or upload to SIA, which gives the user a permanent Sia link, like `https://siasky.net/AABLf0SIW_1-zfXW3SGgy9KHKaB2RCSch7Yo90_JpgzFPQ`
|
||||
@ -1,26 +0,0 @@
|
||||
---
|
||||
title: Trading HNS
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-09T03:40:46.328Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T03:40:46.328Z
|
||||
---
|
||||
|
||||
# Trading handshake
|
||||
|
||||
Handshake (HNS) can be traded at various different exchanges.
|
||||
|
||||
**Current list of HNS exchanges:**
|
||||
|
||||
- [Namebase](https://www.namebase.io/pro)
|
||||
- [Bittrex](https://bittrex.com/Market/Index?MarketName=USDT-HNS)
|
||||
- [Hotbit](https://www.hotbit.io/exchange?symbol=HNS_USDT)
|
||||
- [Gate.io](https://www.gate.io/trade/HNS_USDT)
|
||||
|
||||
**Market data aggregators:**
|
||||
|
||||
- [CoinGecko](https://www.coingecko.com/en/coins/handshake)
|
||||
- [CoinMarketCap](https://www.coingecko.com/en/coins/handshake)
|
||||
- [Coinbase](https://www.coinbase.com/price/handshake)
|
||||
@ -1,45 +0,0 @@
|
||||
---
|
||||
title: Using your name
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-06-24T04:15:26.843Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-10T01:25:01.099Z
|
||||
---
|
||||
|
||||
# Using your name
|
||||
|
||||
Domains can have many uses such as guiding users to websites, using as your identity, and other online resources.
|
||||
|
||||
|
||||
|
||||
## Websites
|
||||
- [HNSHosting](/hnshosting) - Free wordpress hosting service for Handshake domains
|
||||
- [Excerpt](/excerpt) - Free blogging website hosting for Handshake domains
|
||||
- [HNS Links](https://links.hns.au) - A free links page hosting service powered by [HNSAU](/hnsau)
|
||||
- [Site Manager](https://l.woodburn.au/site-mgr) - A web app to allow easy management of your Handshake websites
|
||||
- [Self Hosted](https://l.woodburn.au/website) - A guide to self host your website on a Linode server
|
||||
|
||||
|
||||
## Chats/Forums
|
||||
- [HNS Mastodon](https://mastodon.hns.au) - A Mastodon instance that allows people to login using their HNS domain.
|
||||
|
||||
|
||||
|
||||
|
||||
## Identity
|
||||
- [Varo Auth](https://auth.varo.domains/implement) - A php authentication system using Handshake domains as yor identity
|
||||
- [HNS Login](https://login.hns.au) - A OAuth2/OpenID Handshake login system. (This is the authentication used for Handypedia)
|
||||
- [Shaker](/en/shaker) - A discord bot used to verify ownership of a Handshake domain.
|
||||
|
||||
## Earn
|
||||
- [Sell SLDs via Namebase](https://www.namebase.io/registry) - Offer SLDs via popular registrars using Namebase's Registry
|
||||
- [Sell SLDs via HNS.ID](https://hns.id/stake) - Offer SLDs minted on the Optimism L2 chain using HNS.ID
|
||||
- [Sell SLDs via a Varo instance](/dns_hosting#varo)
|
||||
|
||||
|
||||
|
||||
## Other uses
|
||||
- [Link shortener](https://linkr) - A self hosted link shortener (Tutorial coming soon from Nathan.Woodburn/)
|
||||
- [HNS Cloud](https://cloud.hns.au) - A cloud service that uses HNS Login for user authentication
|
||||
23
wallets.md
23
wallets.md
@ -1,23 +0,0 @@
|
||||
---
|
||||
title: Wallets
|
||||
description:
|
||||
published: 1
|
||||
date: 2024-02-13T04:43:33.232Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2024-02-09T04:45:27.058Z
|
||||
---
|
||||
|
||||
# Wallets
|
||||
|
||||
|
||||
## Custodial Wallets
|
||||
- [Namebase](/namebase)
|
||||
- [ShakeStation](/shakestation)
|
||||
|
||||
## Self Custodial Wallets
|
||||
- [Bob Wallet](/bobwallet)
|
||||
- [FireWallet](/firewallet)
|
||||
- [FX Wallet](https://www.fxwallet.com/) (Not open source)
|
||||
- [CoinEx Wallet](https://wallet.coinex.com/) (Not open source)
|
||||
- [Palm Reader](https://github.com/pinheadmz/palmreader)
|
||||
25
🤝.md
25
🤝.md
@ -1,25 +0,0 @@
|
||||
---
|
||||
title: 🤝
|
||||
description: 🤝 Escrow Service
|
||||
published: 1
|
||||
date: 2024-09-11T05:12:25.486Z
|
||||
tags: wallets, escrows, exchanges
|
||||
editor: markdown
|
||||
dateCreated: 2024-09-11T05:12:25.486Z
|
||||
---
|
||||
|
||||
# 🤝
|
||||
|
||||
Trade cryptocurrencies securely using this escrow service created by [Eskimo](https://eskimo.dev/).
|
||||
This escrow is only available on the Handshake domain [🤝/](https://🤝)
|
||||
|
||||
## Currently Supported Currencies
|
||||
|
||||
| Token | Symbol |
|
||||
| --- | --- |
|
||||
| Handshake | HNS |
|
||||
| Bitcoin | BTC |
|
||||
| Cardano | ADA |
|
||||
| Dogecoin | DOGE |
|
||||
| Litecoin | LTC |
|
||||
|
||||
Loading…
Reference in New Issue
Block a user