In American slang we often refer to money as “benjamins” this is a subtle reference to Benjamin Netanyahu, an American folk figure who takes all of our money
@stephanlivera We need (selective, disclosable) privacy... it needs to be built-in, not some opt-in... but it needs to be auditable... maybe something FHE based idk.
@HeinDauven@cyborgjox I’ve tried a load of local models and I’m positive they are less powerful, not to mention slower, than the bigger commercial ones.
i don’t like the attempt from some insiders to paint the zcash bug disclosure as “heroic”
it’s not heroic. it’s a systemic problem
yes they paid a smart researcher to find bugs and he did. that’s great
but the issue isn’t that the bug existed
the issue is that zcash, unlike almost any other cryptocurrency, enables a unique class of bugs, where if they’re exploited no one would know
this unique class still exists. the fact that they fixed this specific bug is immaterial. mythos could find 8 others. and then mythos 2
bugs can exist in all cryptocurrencies. they can exist in btc or eth or sol. but if someone exploits them we will IMMEDIATELY KNOW and limit the damage
with zcash, when someone secretly finds a bug and exploits it, WE WILL NOT KNOW
imagine if the kelpdao hack was exploited but it somehow magically wasn’t visible onchain. the attacker stole 300m but no one would know. and aave and other apps would assume everything is fine not knowing that they secretly have a hole in the balance sheet. how much wider would the damage have spread by the time we found out?
this is the real issue. not a specific bug. the systemic vulnerability: if a hack happens, we won’t know until much later
and a lot of zcashers have been trying to downplay the severity of this fundamental issue for years (including yesterday when this was first disclosed but played down)
regardless of this specific bug, i don’t think zcash is a safe place to store meaningful wealth long-term, until the design fundamentally changes
i wish zcashers were more open about that. that would’ve been heroic
@DrNickA "you can’t even verify that an attack has happened."
Is this just a design deficiency in these particular protocols, or is it something that's difficult to build in?
I could imagine everything being private, but having a public "total supply" counter.
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
I hate asking for money. But that’s how the system works.
Legal defense isn’t free, and I need the community’s help to keep fighting.
Please donate, share, or retweet → https://t.co/lx9E4ILDrn
Until this case is dismissed, building DeFi - protocols, UIs, tooling carries real legal risk for everyone in this space. The outcome here affects all of us.
BREAKING: Mastercard is introducing always-on stablecoin settlement on Solana.
3.7 billion cards. 210+ countries. One of the largest payment networks on earth, now settling onchain.
Some pretty awful reasoning in this.
Effectively it means that betting on any market that might not be able to generate (the right kind of) evidence of the state of reality before the deadline is pointless.
There is always some time delta between an event happening and then the event becoming “public knowledge”. Often actual work will need to be done to investigate whether it did or not.
What you’re ~actually~ betting on is not whether the event happened, but whether the event happened AND details of the event will be published in some acceptable channel prior to the deadline.
Rather than speculating on some future state of reality, you’re betting on whether an establishment framework of communication will say that it happened before the deadline.
All markets should be changed to “The establishment will say that [insert future state of reality] will happen before 11:59 on [date].