[NameSys] New Records, HTTP Support and Stealth Payments


NameSys is back with major feature upgrades !

:exclamation:In our introductory post, we had announced the release of v1.0 with basic ENS records and IPNS support. We are now glad to announce the release of v1.1 with major feature upgrades !

:point_right: MORE RECORDS

We have added several more records to NameSys and the full list now features:

  • Address (ETH) :white_check_mark:
  • Address (BTC) :white_check_mark:
  • Avatar :white_check_mark:
  • Contenthash :white_check_mark:
  • Email :white_check_mark:
  • URL :white_check_mark:
  • Github :white_check_mark:
  • Discord :white_check_mark:
  • Farcaster :white_check_mark:
  • Nostr :white_check_mark:
  • Twitter :white_check_mark:
  • PubKey :x:
  • Address (LTC) :x:
  • Address (DOGE) :x:
  • Address (SOL) :x:
  • Address (ATOM) :x:
  • Zonehash :x:

:x: Remaining Records will be added in the next version v1.2

:point_right: HTTP GATEWAY

:exclamation: Users can now specify custom HTTP Gateway as records storage or router and benefit from fast resolution !

:exclamation: We have also enabled our own default HTTP Gateway (ccip.namesys.xyz) which will work by default if the user doesn’t have any storage specified. In other words, users may now save more gas and start using NameSys with only 1 transaction of migrating the Resolver !



:point_right: STEALTH PAYMENTS

:exclamation: The biggest upgrade to NameSys is the Stealth Payments feature ! With the ability to update ENS records infinitely with NameSys, two parties can interact in an encrypted manner using their respective RSA (2048 BITS) public key records. For example, if Bob wants Alice to pay an invoice (to one of Bob’s private addresses), he can encrypt the invoice with Alice’s RSA public key and post the resulting cipher as a record. Alice can then read this encrypted record, decrypt its contents with her private RSA key and pay the resulting invoice !

:exclamation: In comparison to UmbraCash, NameSys is 99% cheaper since it incurs 0 additional cost for the stealth feature. Moreover, the invoice routing is significantly more private since there are no on-chain logs !



Read more about the stealth payments specs

:exclamation: We’d also like to thank the ENS DAO for their support through Ecosystem Grant. If you have questions or comments, please fire away !

[CC: @bendi]