8000 Well Known directory for wallets address by Falci · Pull Request #5 · handshake-org/HIPs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Well Known directory for wallets address #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Feb 19, 2021
Merged

Well Known directory for wallets address #5

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8f07632
first iteration
Falci Oct 7, 2020
f27488f
Removes HIP number
Falci Oct 13, 2020
68042d9
Update HIP-xxxx.md
Falci Oct 13, 2020
af87bf8
Assign HIP number
Falci Feb 19, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
49 changes: 49 additions & 0 deletions HIP-0002.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
# HIP-0002 : Well Known directory for wallets address

```
Number: HIP-0002
Title: Well Known directory for wallets address
Type: Informational
Status: Draft
Authors: Fernando Falci <http://iamfernando/>; Mark Tyneway <@tynes>
Created: 2020-10-07
```

## Abstract

This HIP describe how to publish a wallet address in a domain.

## Motivation

Wallet address are not human friendly. Sending an address normally involves "copy & paste" and is near to impossible to do via voice channels.

Since Handshare is all about owning domains, we could use them as alias to our wallet address.

### Protocol

The basics of this protocol consists in serving the address in an HTTPS request to the [.well-known diretory](https://tools.ietf.org/html/rfc8615). For security reasons, we should only HTTPS.
The address should be located at `https://<domain>/.well-known/wallets/SYMBOL`.

For instance `https://example/.well-known/wallets/HNS`.

### Dynamic or Static

This proposal doesn't define if the content served should be static (file in the disk) or dynamic (unique address per request).

### Security Concerns

Requests should be made using only HTTPS. Handshake's HTTPS requests are secured by DANE & PoW.

### Non HNS domain

This protocol can also be used with non-HNS domains (aka ICANN).

In this case, the security would rely on CA. It should be a consumer choise to accept it or not.

### Non crypto-currencies address

It's also possible to define a non-crypto symbol, such as `/.well-known/wallets/USD`, which should return an [IBAN](https://www.iso.org/standard/41031.html).

## References

[SLIP-0044](https://github.com/satoshilabs/slips/blob/master/slip-0044.md) can be used as a symbol reference.
0