zk privacy is powerful. but audit-ability for hard money is a much stronger product. I feel that many people shilling the 'private/encrypted btc' angle don't realize that zk privacy is still extremely risky.
the best idea is having a private zk bitcoin pool in the future that is a fraction of the size of 21m. a large enough privacy set but not large enough to have negative implications on the overall 21m supply.
imagine having a 2T+ asset that cannot be audited and potentially printed lol
@permacrypt@ThePumponomics@gainzy222 turnstiles job is to prevent the supply from being inflated, not minting fake coins. Fake coins can be minted, withdrawn, and 'real' user coins stuck inside pools because of turnstiles.
@eyezenhour@mert@Evan_ss6 turnstile works the same way as a defi pool that gets drained and authentic users can't withdraw. if shielded supply gets minted and unshielded, users in the pool get stuck.
zk privacy is powerful. but audit-ability for hard money is a much stronger product. I feel that many people shilling the 'private/encrypted btc' angle don't realize that zk privacy is still extremely risky.
the best idea is having a private zk bitcoin pool in the future that is a fraction of the size of 21m. a large enough privacy set but not large enough to have negative implications on the overall 21m supply.
imagine having a 2T+ asset that cannot be audited and potentially printed lol
@mert@Evan_ss6 turnstile is a helpful tracking metric to maintain supply integrity, but not helpful in protecting users inside the pool. hardmoney thesis gets invalidated
zk privacy is powerful. but audit-ability for hard money is a much stronger product. I feel that many people shilling the 'private/encrypted btc' angle don't realize that zk privacy is still extremely risky.
the best idea is having a private zk bitcoin pool in the future that is a fraction of the size of 21m. a large enough privacy set but not large enough to have negative implications on the overall 21m supply.
imagine having a 2T+ asset that cannot be audited and potentially printed lol
@MartinShkreli Itβs less so the fact of knowing he implied diluting the share base by 100%+. More so asking him to say that part out loud on television.
Your infrastructure was compromised, so own up to it.
"Yeah but we didn't think anyone would RELY on that infrastructure" isn't an excuse
Trust in LZ will tank, and it deserves to, after this.
@ryanberckmans This is an exploit to aave regardless of how they want to structure and deflect the blame. Users will flock elsewhere, simple DD was not done with kelp. At the very least, this should have been a small isolated market.
@robin_linus If the hack was known to be coming for years, then surely people would be putting resources towards mitigating the potential hack.
Poor strawman imo.
Developer APIs are coming.
Get an API key, add a few lines of code, and your app has private stablecoin transfers.
No ZK expertise needed. No blockchain infra to manage. Just REST calls.
Early access β https://t.co/vEUy1SGViU
This is a known operational risk with Groth16. We chose universal SNARKs (Noir/UltraHonk) specifically to eliminate this failure mode β no circuit-specific ceremony means this entire class of vulnerability doesn't exist.
Privacy infrastructure shouldn't require a pinky promise.
We built Senddy's consumer app to prove the tech works.
But the real product is the infrastructure underneath - private stablecoin payment rails any developer can plug into.
Sub-penny transactions. On/Off ramps. ZK privacy by default.
Docs π
https://t.co/5j40KROYhr