Hacker Newsnew | past | comments | ask | show | jobs | submit | jungong's commentslogin

2023 was a pivotal year for consumer crypto.

Dive into our report, where we unwrap everything that went down in the consumer crypto landscape in 2023 — the major events, trends, and innovations that painted the picture.


looking forward to seeing people building money legos on top of the stacks


The genesis block is now set!


saw your post on indiehacker :)

looks like a very cool landing page / personal portfolio!


thank you,


very cool!


Many thanks. I'm glad you liked them


This thread is something that I really want to hear it right now. Thanks for the positivity!


Opera works with Unstoppable Domains for the .crypto domains. Maybe you can look it up at UD's website https://community.unstoppabledomains.com/t/unstoppable-x-ope... to see how to manage the .crypto?


Not OP, but nothing on there seems to explain whether UD is just running a database-backed DNS server which they could change at their whim / govt order, or whether ownership and DNS records are actually stored on-chain ala Ethereum's ENS, or NameCoin.


Reading the website/github, the domains are stored on-chain, but UD provides an HTTP API (essentially a DNS-over-HTTPS resolver), and that could obviously be censored. It's not clear to me if Opera is reading directly from the chain or using UD's API, but I suspect the latter.


If that's the case, then I think that qualifies as reasonably decentralized, at least for me.

Theoretically, anyone could make a work-alike resolver service that used their own Ethereum node to query for results; in which case any attempts to censor UD could be routed around by pointing opera to a different dns-over-http server (assuming that is configurable, which is really up to opera, not the protocol).

I do like that idea actually -- if I published a self-signed SSL cert for my domain on the Ethereum blockchain, that could be returned and used to validate my domain, without any sort of CA having to be involved. The only trust needed would be that the HTTP-DNS-Ethererum server itself wasn't lying about which public key owned the on-chain domain record.


Also, Gitlab's remote work emergency plan is a good read too > https://about.gitlab.com/company/culture/all-remote/remote-w...


Also, most of people just read the headlines.


Agreed - it does seem like a cynical move. Now waiting on Justin to share the story from his side.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: