Hi! Do you have an example that includes a full agent workflow?
HN user
raykyri
about me: https://raymond.xyz
For those looking for applications outside crypto, this might also be interesting: https://docs.ezkl.xyz/
It's similar to Succinct but for proofs of ML models instead of RISCV. So you could generate a proof on some private data, on your computer or in a trusted environment, and submit the proof to show that you pass a fraud check without revealing any of your data.
I've been on Brave with vertical tabs since the beginning of the year now. It doesn't seems like most people know about it, but it's more compact and faster than Arc and I couldn't imagine going back to Chrome now.
Other criticisms aside, fees are <10 cents for many transactions on Eth rollups right now, and will drop another 10x in the next six months if not more. (Only true since around the last month.) USDC is nice for international money transfers, though still niche. I don’t think anyone cares if you trade crypto on the streets, just don’t get rubber hosed.
The space has suffered a lot from adverse selection towards grifters. UST alone captured many of the earnest attempts towards payments and took them down with it.
Here's the archived page if anyone else is getting a 503 error. https://web.archive.org/web/20210122161324/https://bloodknif...
This paragraph from the blog post doesn't completely address your comment (or even most of it), but it seems useful to have as a reference as I've almost always missed it:
How Handshake conflicts with ICANN All 1500 of the existing ICANN TLDs are blacklisted on Handshake for backwards-compatibility. This means that end-users resolving their DNS through Handshake can still access .com domains as normal. New ICANN TLDs can theoretically conflict with Handshake TLDs, but ICANN isn't issuing new TLDs for another few years. When ICANN does issue new TLDs, they’ll only allow at most 500 new TLDs per year. The likelihood of conflict is low even though conflicts can technically happen. In the future, it's up to the community to decide which names take precedence. We believe Handshake names will take precedence because people will find them more useful, and I’ll cover why I think Handshake can gain adoption even in the face of ICANN’s network effects in another blog post.
Google Cache, if anyone else is having trouble accessing Medium right now: https://webcache.googleusercontent.com/search?q=cache:rU5Ohf...
Here's a login. You can also make one up (no email verification required).
No affiliation with the creator, btw, just thought it was a cool demo to share.
Username: demo@demohackernews.com
Password: demodemo