Dax

2.1K posts

Dax banner
Dax

Dax

@dev_skill_issue

There is no cloud just other ppl's computers. I write apps for them. Prev USAA, MetaMask, advertising, back in crypto doing zero knowledge @ZeraLabs

React Docs Katılım Mayıs 2024
453 Takip Edilen4K Takipçiler
Dax
Dax@dev_skill_issue·
@toly I do love what I have been hearing about the stablecoins and privacy on solana.
English
0
5
25
222
toly 🇺🇸
toly 🇺🇸@toly·
Privacy is coming, it’s just not going to get users to switch. But an established protocol will add privacy to keep users.
Solana@solana

.@Toly on why privacy becomes a moat after PMF

English
6
24
227
30.7K
Dax
Dax@dev_skill_issue·
Privacy patch on all 3 ZERA pools today. Removed an on-chain (spendPub, viewPub) registry PDA from deposit_v3. Pat noticed it created a permanent retroactive de-anon index if viewSk ever leaked pivot from wallet → viewPub → scan every note ever addressed to that wallet. This is why we test and take feedback thanks everyone.
English
9
31
137
2.6K
Dax
Dax@dev_skill_issue·
@SocioEconoQuant @ZeraLabs it currently works as a PWA so it will run in any mobile wallet like solflare and backpack... but yes a self contained wallet would be killer
English
1
0
17
408
Dax
Dax@dev_skill_issue·
Love pushing a whole new version stay tuned for some interesting blog posts about our v3 circuits at zeralabs.org/news @ZeraLabs
English
16
33
115
3.7K
Random Guy (CSWAP MODE)
Random Guy (CSWAP MODE)@RandomGuyCSWAP·
@dev_skill_issue all $ZERA all chads can’t thank you enough for all the effort that you have put into developing the best privacy tech, but we would all love to have you live once again to hear from you and do some Q&A
English
5
2
38
695
Dax
Dax@dev_skill_issue·
On the backend we are already approaching v3 of the contracts w security upgrades and better support. @ZeraLabs
English
26
36
135
2.9K
Dax
Dax@dev_skill_issue·
btw the SOL pool deposits and withdraws feel native now. You send SOL, you get SOL. No manual wSOL wrapping, no leftover wSOL ATAs to clean up, no mental overhead. Under the hood the contract handles the wrap on deposit and the unwrap on withdraw.
English
10
36
122
4.1K
Dax
Dax@dev_skill_issue·
why three separate programs? 1/ Upgrade blast radius. If we ship a subtle circuit bug that only shows up at scale, the damage is contained to one pool. Other pools keep running. You can pause/upgrade/migrate independently. 2/ Proof-system binding. Each pool has an asset_hash that's part of the Groth16 public inputs. Separate program IDs → separate PDAs → separate merkle trees. A USDC proof literally cannot verify against the SOL pool's tree. Compromise isolation by design. 3/ Governance. Different assets may want different fee structures, burn rates, pause authorities. A monolith forces convergence. Separate programs let ZERA's policy diverge from USDC's over time.
English
8
25
101
8.2K
Dax
Dax@dev_skill_issue·
Multi-asset burn math is the tricky part. Each token has a different USD price and different decimals. We read Pyth feeds on-chain per deposit, compute the burn in USD, route that value through Meteora → ZERA → burn. While Stablecoins skip the oracle being 1:1.
English
14
18
95
4.4K
Dax
Dax@dev_skill_issue·
as part of the sdk we built out commands to bring up a new asset: • Mints the pool program • Initializes merkle tree + vault + fee vault • Wires the Pyth price feed for burn math • Signs the admin config tx Adding the next asset is now an easier process for everyone. Which one should we light up next?
English
9
7
52
724
Dax
Dax@dev_skill_issue·
Long weekend burning the midnight oil
English
11
11
71
1.4K
Dax
Dax@dev_skill_issue·
Building out an SDK for everyone to use esp AI agents isn't too hard we have all the base code already @ZeraLabs
Dax tweet media
English
10
34
120
10.2K
Dax
Dax@dev_skill_issue·
So if your argument here is "verify our claims yourself," well guess what? The community has done exactly that and found affiliate injections, DNS leaks, unconsented creator fundraising, and a KYC-gated reward system built on a fully traceable ERC-20 token. The code being open is what enabled people to catch these issues, not what excuses them.
English
0
0
3
151
Dax
Dax@dev_skill_issue·
Open Source ≠ Trustworthy by Default And tbh open source can be a great pre requisite for trust, but its not the whole story. For example the affiliate link injection in 2020; where Bravrewrote URLs to Binance, Coinbase, and Ledger with referral codes, was in the open-source code and still shipped to users. And nobody caught it until users noticed. Or how about the VPN silently installed on users' machines in 2023? This too shipped through the open-source repo. So open source only works as a trust mechanism if there's enough independent auditing happening, and y'all have repeatedly demonstrated that controversial changes slip through without community review.
English
2
0
11
456
Dax
Dax@dev_skill_issue·
@brave is a masterclass in marketing over substance... a bloated Chromium fork that cosplays as a privacy tool while running a crypto ad network that requires KYC to cash out.
English
9
7
42
2.7K
Dax
Dax@dev_skill_issue·
@brave Plus one study measuring phone-home telemetry doesn't validate an entire privacy brand. Privacy is a system-level property, not a single metric.
English
1
0
3
330
Dax
Dax@dev_skill_issue·
@brave The crypto features aren't about empowering users... they're a monetization engine for Brave Software. Every controversial "mistake" they've made (referral links, ad replacement, BAT without consent) just happened to make them money.
English
0
0
13
651
Dax
Dax@dev_skill_issue·
@brave Brave's business model is advertising. They just replaced Google's ad network with their own and slapped a "privacy" label on it.
English
1
1
15
647