From: Tyler H <tyzbit@gmail•com>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Numerifides - Proposal for Decentralized trust/authority on Bitcoin blockchain
Date: Sat, 21 Apr 2018 12:35:28 +0000 [thread overview]
Message-ID: <CAEegQfVLWSySWfCbSmGG4V0i6GMpgyUr=86Qzb4YE9s+M5K1gg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
Greetings,
I have been working on a proposal called Numerifides which would provide a
general method to register human-readable names and arbitrary data (such as
username->GPG key, domain->IP address, Lightning node Alias-> URI, etc).
Here are the key highlights:
--New transaction type called "numerifides" transactions
--Lock up Bitcoin for a certain amount of time to make the mappings valid,
discourage "namesquatting"
--Transaction puzzle attached to transactions to allow community consensus
revocation of highly contested names or "squatted" name mappings.
--Transactions are RBF so if name is contentious or miners wish to censor,
one honest greedy miner can include the censored user's high-fee
transaction)
--Solves Zooko's triangle of Secure, Decentralized and Human Meaningful
Full working spec is here: https://github.com/tyzbit/numerifides
I'd love feedback and possible enhancements, as I know this early rough
draft does have a lot of room for improvement (I also think it would be
remiss to incentivize filling blocks with data like this, and a possible
change proposed on the lightning-dev list by ZmnSCPxj is a P2WSH defining
the mapping that is gossiped about outside of the Bitcoin network, but I'd
like to hear all comments).
Thank you for your time.
Tyler Hawkins
[-- Attachment #2: Type: text/html, Size: 2312 bytes --]
next reply other threads:[~2018-04-21 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 12:35 Tyler H [this message]
2018-04-25 6:58 ` Tyler H
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEegQfVLWSySWfCbSmGG4V0i6GMpgyUr=86Qzb4YE9s+M5K1gg@mail.gmail.com' \
--to=tyzbit@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox