I think one mistake people make when looking at a new protocol is trying to understand every moving part on day one.
After spending some time with @NewtonProtocol , I stopped caring about memorizing the architecture and started paying attention to the moments where I actually paused and thought, "Wait... what's happening here?"

That's usually where the real user experience lives.

A clean architecture diagram is nice, but if a developer has to second-guess what's happening between submitting a request and getting a response, that tiny moment sticks in their mind more than any technical design ever will.
I don't see this as a weakness. It's just the kind of thing every infrastructure project has to polish over time. The technology can be solid, but confidence comes from clarity. The less time developers spend guessing, the faster they trust what they're building on.
That's the part of Newton I'm more interested in watching than price charts right now.
$NEWT
#Newt