reminder that the united states of america is trying to jail a guy that wrote non-custodial code to help people keep their onchain activity free from surveillance
he did not launder money, did not have central control, his code was immutable. he did not commit any known crime. in fact, he did everything that fincen says and hired lawyers ahead of time just to make sure. didn't matter
he wrote code that individuals can keep their privacy. and they are trying to put him behind bars for this
the dutch have already convicted his cofounder
you can rug an entire country by releasing countless shitcoins, bomb whoever you want, but god forbid you write immutable code that keeps your finances private
@mert Witness
Witness is infrastructure for proof without exposure. You hold the witness to your financial activity. We verify without seeing. Zero knowledge, by design.
.@jswihart on why most exchanges don't support shielded ZEC:
"It's not regulatory. Regulated exchanges already KYC you, they know who you are. Supporting shielded ZEC is engineering work that customers haven't demanded yet."
@Gemini did it. Others could too.
The downfall of polymarket.
The team resolved the “microstrategy sells any Bitcoin by May 31” market to No.
The problem is they literally sold Bitcoin in May.
It’s not even up for debate. The filing says they sold Bitcoin. That’s a fact.
If a tree fell in the forest on May 31st, but someone didn't discover it until June 1st, then Polymarket would resolve that the tree fell on June 1st
If users can’t trust markets to be resolved based on what actually happened, the whole product falls apart.
Pretty hard to justify using a prediction market when objective facts apparently don’t matter.
This is basically free advertising Hip4 hyperliquid
Hyperliquid is just superior
“It is also important to find testers who are motivated to test the product. The testers should match the product personas - be part of the target market user group and are often early adopters or some of the leading edge customers.”
- ProdBOK 12.3.1