No. My Blockchain had nothing to do with payments. The Blockchain is for authentication (protection from fake accounts) and tokens represented credits and licensing rights within the platform. The token wasn't even listed on any marketplace.
The glass-half-full here is it’s an incredible signal that one of the largest financial gateways in the world is _able_ to do this with current capabilities.
They are enforcing rigor, on agents, the same way they would on humans. Do people think Stripe's engineering team would have been able to progress if each individual (human | machine) employee was not under harness and guardrail, and just wrote code willy nilly according to their whims? Vibe coding is whimsical, agentic engineering is re-applying what brought and brings rigor to software engineering in general, just to LLM outputs. Of course, it's not only that and there are novel problem spaces.
Isn't there a rule against this - i.e. accusing commenters for using LLMs (the offensive language aside)? Implicitly there is [0], because I can't see how it adds to the conversation. So what if it sounds like an LLM? Soon you won't be able to tell the difference anyway, and all that will be left is some chance that you are correct. Comments should be judged their content merits, not on whether the commenter is native English speaker or not.
[0] > Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes.
Comments should get more thoughtful and substantive, not less, as a topic gets more divisive.
When disagreeing, please reply to the argument instead of calling names. "That is idiotic; 1 + 1 is 2, not 3" can be shortened to "1 + 1 is 2, not 3."
Don't be curmudgeonly. Thoughtful criticism is fine, but please don't be rigidly or generically negative.
They still need someone to review and hopefully QA every PR. I doubt it’s saving much time except maybe the initial debug pass of building human context of the problem. The real benefit here is the ability for the human swe to quickly context switch between problems and domains.
But again: the agent can only move as fast as we can review code.
What I'd really like to see is some kind of iframe that pins JS/wasm code within it to a particular bundle hash and prevents modification at runtime (even from chrome extensions).
Something more like a TEE inside the browser of sorts.
Not sure if there is anything like this.
100%, we want to add that but the data is expensive. If this has legs we will probably spring for Zillow or Redfin API access.
We actually hit a rate limit with the image API tonight, but we're caching everything we pull into a DB, so the more people use it, the less we'll have to rely on API calls.
> Because it's not about age verification, it's about setting up infrastructure to enable incremental enchroachment on privacy.
Yes. You are emphasizing a reason it would be a good idea.
Sideline the ulterior/hidden motive. Or at a minimum, force it into the open, where it has less of a chance. (Ulterior motives are kept quiet for a reason.)
> Fun fact: many ZK identity solutions run centralized provers and can be subpoenaed. Need to use something that generates proofs client-side.
Subpoenas are one of the many privacy problems solved by this.
If there is no log of your real identity tied to visiting a site, there is nothing to hack or subpoena.
A verifier can report you got keys validated. But they don't know what sites they were for.
Sites can ensure users are vetted for age. Without knowing who they are.
This is such a classic cryptography scenario, I don't know how it isn't being pushed to the center of this debate. Anything that reduces the practical tension between divisive goal posts is going to have practical benefit, and make worst case legislation much less likely.
You're confusing concepts and blockchain fundamentals. "Uncloneability" is the double-spending problem solved by proof-of-work/hashcash scheme. The 51% attack is not the problem, it's just a requirement for a PoW based blockchain to work. Just like how you have 1/3 honest node requirements in traditional BFT distributed database designs.
So cloneable cryptocoins is a thing? Where do I sign up wink.
IMHO cloneablitiy IS the problem, PoW is just a (very, very unfortunate) solution to that.
PoS (stake as in possession, not pledging) is IMHO inherently impossible, so PoW is all we got, now and for ever...
Curious, what do you think of Sellfy? It gives you email lists, and analytics.
I'm currently building an e-commerce platform like Etsy, and tossing up some ideas of what kind of features to provide for sellers with respect to their brand, email list, and analytics, paywalled content etc.
