---
# System prepended metadata

title: Handshake Developer Call 5/14/2020

---

# Handshake Developer Call 5/14/2020

## News

### ENS Registered `.ens`

This means that they were able to claim 136,503.364187 HNS along with the Handshake name `.eth`. They registered the name but did not include any DNS data.

[JSON Parsed from Chain](https://gist.github.com/tynes/70db1b9f078d554d35f415f9f5784979)
[HNScan Link](https://hnscan.com/tx/a162aab7dcfa338cb5238e63bc1c99347db5e2f92fa614765433ce9157cb3889)

### Airdrop Deduplication

If you signed up for the airdrop on the website (before it became automated) then you were deduplicated from the automated portion of the airdrop.

https://twitter.com/hudsonjameson/status/1258785341894471688?s=20

### IRC #handshake Community

Come chat with on on IRC, `irc.freenode.net/#handshake`

### Upcoming Hackathon

There are talks of doing an online hackathon soon, all based on IRC. Please reach out if you want to learn more or help out with producing it. There will be a more formal announement in the future.

## Issues/PRs

### Conflict issue with pending ICANN TLDs

The `.music` Top Level Domain is months away from launching in the ICANN system and the auction on Handshake is ending soon.

https://www.namebase.io/domains/music
https://github.com/handshake-org/hs-names/issues/6

### Fix SYNTH Record Resolution

`SYNTH` records are a way for a Handshake name to save some space on chain by encoding the IP address as a base32 string as the name in the NS record. There are not any tests around this resource record and this PR fixes some bugs along with adding some tests.

https://github.com/handshake-org/hsd/pull/444

### Name Claim `REGISTER` Bugfix

A bug in the wallet prevented anybody that claimed a name to be able to `REGISTER` the name, or update its DNS records and claim the HNS associated with the name. A patch was merged, but it requires the user who claimed a name to recreate the wallet. It is easiest to do this by exporting the mnemonic and then creating a new wallet with a mnemonic. See the [API docs](https://hsd-dev.org/api-docs).

https://github.com/handshake-org/hsd/pull/438

### RPC getnames Response Too Large

The `getnames` RPC method no longer works without a hack to `hs-client`. It was known that this would eventually become a problem. If any applications depend on this functionality, please comment on this GitHub issue.

https://github.com/handshake-org/hsd/issues/447

### Node.js v14 Issues

There is an issue with the latest version of Node.js that is causing `hsd` to crash. Please do not use Node.js v14.

https://github.com/handshake-org/hsd/issues/445

### hnsd Progress

pinheadmz has been making more progress on
a mainnet ready `hnsd`.

https://github.com/pinheadmz/hnsd/tree/mainnet1

### Handshake Resource Record Guide

There is an [open PR](https://github.com/handshake-org/handshake-org.github.io/pull/69) on the docs to add a new guide to hsd-dev.org to explain the Handshake Resource Record types. This includes information regarding the type of resource you need to correctly delegate authority to a nameserver running elsewhere.

https://github.com/handshake-org/handshake-org.github.io/blob/436e67b479c1df2ce7d79e083eda6a66f51291d1/src/guides/resource-records.md

## Extra

What does the community want to talk about?