tynes

8 ms·

1.
by tynes 7y ago
Solving #1 is interesting because it would also be useful if you didn't care to use a Handshake name and also didn't want to depend on the traditional CA system. It could save the need to for companies to ever install a certificat
2.
by tynes 7y ago
Handshake is very different than Namecoin. Its possible to come to this conclusion by doing any amount of research. Please consider thinking before speaking in tribalism. There is no good trustless sidechain technology. Sovereign names can
3.
by tynes 7y ago
In blockchains, there is a difference between consensus and policy. The way that the Handshake recursive resolver works is not based on consensus. This means that people can insert rules for delegating a particular request to ICANN or to th
4.
by tynes 7y ago
I think ENS is queried more often in a different context than DNS, since many people access it via JSON RPC over HTTP. The interface is an Ethereum contract, although records could be cached in a DNS server if the server can hit an Ethereum
5.
by tynes 7y ago
> If names have to be renewed on a year-by-year basis, is there any mechanism for archival? Won't this be strictly worse for link rot? Blockchains are good for timestamping. The records on chain can be tracked over time but this doe
6.
by tynes 7y ago
Proof of Work solves that by preventing Sybil attacks - it's costly to mine (which is equivalent to signing off on, because it wouldn't make sense to sign an invalid block, you would get rewarded). It's the only signature sch
7.
by tynes 7y ago
Just make a fun website that is only accessible through the system. Businesses can own a cryptographic asset (their domain name) that can accrue value based on services provided. Potentially people may try to use their domains as collateral
8.
by tynes 7y ago
The JS implemention is a fork of bcoin, the JS Bitcoin full node and production backend. It binds to libunbound but you are right that you would want a lower level language for it to be more scalable. There is a rust implemention work in pr
9.
by tynes 7y ago
Yes but you risk keeping keys online
10.
by tynes 7y ago
Handshake is for top level domains. You can do quick updates using traditional DNS infrastructure at a domain underneath a Handshake top level domain. The benefit is that you have a cryptographic asset representing the top level domain, the
11.
by tynes 7y ago
To update DNS records, you need to submit a valid transaction to the network. People generally do not keep their keys connected to the internet to prevent this type of problem. It is possible to use Bitcoin Script to describe policies regar
12.
by tynes 7y ago
Unfortunately the seeder peers aren't up right now, see here for a fresh peers list https://hnscan.com/peers
13.
by tynes 7y ago
The way the the ENS integration would work is the DNS request for vitalik.eth would end up at a Handshake Authoritative Name Server and then there are certain blacklisted top level domains (.onion, .tor, .i2p, .bit and a few others) where a
14.
by tynes 8y ago
Satoshi Labs should consider a donation :) Since Trezor devices now support many coins, I'm sure that there is a much higher demand for the devices. If you are a purist, please update trezor-connect so that it doesn't rely on a Bi
15.
by tynes 8y ago
If you have any interest in participating in the community, please visit https://handshake.community
16.
by tynes 8y ago
Human intervention is important to the proper functioning of blockchain protocols. It's a myth that blockchains can just operate in a completely objective way without people. The point is to minimize the amount that people need to inte
17.
by tynes 8y ago
User experience around key management is poor. I agree that it needs to be improved, Handshake supports the industry standard HD Key Derivation following bip44 and has Ledger Nano support. The keys can be derived deterministically from a mn
18.
by tynes 8y ago
The root of trust comes from the accumulated proof of work instead of an organization. This is interesting because self signed certificates can be trustworthy if they are signed with the private key of the Handshake top level domain holder.
19.
by tynes 8y ago
Handshake (handshake.org) provides an SPV Proof that the DNS records held in it's zone are authentic. This means if an attacker wanted to spoof records, they would have to: 1) Eclipse attack the client, meaning that the client is on a
20.
by tynes 8y ago
I wish IBM could turn itself around
21.
by tynes 10y ago
I know of multiple bootcamp grads that currently work at Google. It is a thing