Hi! Do you have an example that includes a full agent workflow?
139 karma · joined April 25, 2014
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.
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.
> 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.
No affiliation with the creator, btw, just thought it was a cool demo to share.
Username: demo@demohackernews.com
Password: demodemo