Viewing profile — tynes
tynes
HN member- Joined
- Fri, Mar 18, 2016, 4:08 PM UTC
- HN karma
- 18
- Public activity
- 21 items
- HN profile
- View on Hacker News ↗
About tynes
Recent public activity
-
comment
Comment #22724899
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 …
-
comment
Comment #22312072
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 …
-
comment
Comment #22312016
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…
-
comment
Comment #22311511
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…
-
comment
Comment #22311293
> 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 re…
-
comment
Comment #21002651
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 wou…
-
comment
Comment #21002624
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. P…
-
comment
Comment #21001783
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 …
-
comment
Comment #20627509
Yes but you risk keeping keys online
-
comment
Comment #20627484
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 …
-
comment
Comment #20627451
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 …
-
comment
Comment #20627439
Unfortunately the seeder peers aren't up right now, see here for a fresh peers list https://hnscan.com/peers
-
comment
Comment #20627385
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…
-
comment
Comment #19530262
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 upd…
-
comment
Comment #19241732
If you have any interest in participating in the community, please visit https://handshake.community
-
comment
Comment #19241063
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 p…
-
comment
Comment #19241036
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 …
-
comment
Comment #19240982
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 wi…
-
comment
Comment #19240451
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) Ecli…
-
comment
Comment #18760785
I wish IBM could turn itself around
-
comment
Comment #12940828
I know of multiple bootcamp grads that currently work at Google. It is a thing