@gakonst@dcbuilder@tiagosada Haven't seen anything for alloy / arkworks yet! We're only exposing some higher level APIs for e.g. proof generation or tx building (yet). Would be nice to have bindings that just re-export. UniFFI seems great for that. We're also publishing something on it soon.
Full Kotlin / Swift web3 libs are kind of a lost case, slim ffi wrappers (for ethers-rs / alloy / arkworks) are the play for wallets. The core is there, nice wrappers are still needed. Indexing is actually still a painpoint, everyone is / was building their own data pipeline. There is some good room for easy extendable indexers (for custom user tx).
The nullifier is derived from *SK*. Agree that everything would be solved if it was derived from PK with this scheme, however list of PKs is small and easily exhausted through brute-force, thus privacy defeated. Epoch validity of nullifiers seems so far the easiest way to still allow for rotation. Another option to "fix" the scheme by finding other entropy that can be added to the PK in the nullifier.
@backaes@dcbuilder@bajpaiharsh244 you could make it more efficient by skipping the empty leaf proof by sticking to append-only and "socially agreeing" on the initial root (that it indeed just consists of empty leaves)
@backaes@dcbuilder@bajpaiharsh244 the batch insertion is basically just 2*n merkle proof verifications (each insert into the tree requires proof of empty leaf before and filled leaf afterwards). This trades off gas-heavy on-chain merklization in the semaphore contract with requring an off-chain sequencer
@heyellieday@m1guelpf@worldnetwork@dcbuilder yes, no doubt SecOps are important and logging creds is bad! for critical services there should also be log sanitizers before ingestion (e.g. we do this for other services that touch auth).
I'm always here for civilized discussions :)
@heyellieday@m1guelpf@worldnetwork@dcbuilder Needless to say that my initial response got triggered by the way *how* you were reporting on those things, which seemed to be not motivated my seeking facts, but rather attention (e.g. jumping to the worst possible conclusions about the db).
@heyellieday@m1guelpf@worldnetwork@dcbuilder why I'm saying seq. db ~= chain: it's independent and also will be permissionless. That's why rn batches help for privacy, later only scalability (it's untrusted). Anything extra needs to happen before. That's how the seq. is treated and e.g. does not receive insertions instantly
@heyellieday@m1guelpf@kesava_kirupa 1) That's staging, matching ts are just coincidence, prod is here 0xA8710B3ba329fc7B80a49F7C82E889D1340C99fb
2) Yes! Already doing batches.
3) Higher min batch size will be enforced, rn batches are ~tens of idComms
4) To link *usage* of the id, you need to know the *private key*
@androolloyd@stonecoldpat0 acutally "weekly active safes" (*sending* 1 tx) doesn't look too bad either! (even though this metric is a bit unfair since it doesn't count any received txs e.g. airdrops to users)
hacked together a quick dashboard here: https://t.co/3poMb1rXFY
[New post] StealthDrop: Anonymous Airdrops Using ZK Proofs
@nibnalin, @yush_g, and Adhyyan S. present StealthDrop, an anonymous airdrop utility using circom-ecdsa, enabling anonymous governance. (1/n)
(post in README of github repo)
https://t.co/RtbrMAGMF8