Engineer | Builder | Privacy and Decentralization for all
Houston, TX
Joined August 2010
- Tweets5.5K
- Following4K
- Followers836
- Likes10.3K
Miguel retweeted
I now realize how lucky and fortunate I was to have a job that didn't feel like one for the last 9+ years in crypto.
Doing something I loved, a mission I respected, and having full autonomy to solve to problems I thought were important is a super rare trifecta.
It's hard to explain this on a job application/resume, and finding what's next has been brutal, but I hope I can one day feel the magic again!
Miguel retweeted
🥳 We just reached $50K+ in settled transactions!
• $50,874.18 in all-time volume
• 566 in settled orders
• 151 unique accounts
• $16.18K volume in zcash:native
• 126 orders used Zcash (buy, sell, pay)
Brazil still leading, but India, Peru, and Venezuela already crossed the $1,000 milestone and are growing in usage!
Que time massa! #ZamosJuntos
Nosso time na Zcon7! 💛
Voltamos com aprendizados para compartilhar e ideias para desenvolver com a comunidade brasileira.
Agradecemos à @ZcashFoundation por tornar nossa participação possível.
Seguimos juntos pela privacidade. ¡Vamos! ᙇ
Miguel retweeted
I’m seeing a lot of questions about how the debate over ZCG and the Dev Fund will move forward and what happens to the proposals that have been put forward.
I posted an overview of how Zcash governance currently works on the Forum:
forum.zcashcommunity.com/t/f…
Miguel retweeted
Worth some thought of what would happen to Zcash governance and coin holder voting if a large exchange hack happens.
No, it wouldn't be catastrophic. In particular, a single hack only gives a small amount of influence, but one might imagine a world of multiple hacks over a few years, at which point the vote looks way less credible. Even then, Zcash can adapt, add checks and balances, etc. So this is a serious thing to consider, but not necessarily a reason to just reject coin holder voting outright.
But running the thought experiment will be useful, since it will tell folks a lot of what they want from a resilient and decentralized governance mechanism.
For example, it looks very different if coinholder voting retroactively decides funding prioritization vs if it’s deciding core protocol decisions.
Miguel retweeted
I hope everyone endorses this. Both sides seem unhappy so that tells me it's a good compromise.
IMO there's a lot of money fighting right now. Let's just get it done with. Get everything out in the open and fight about it. Then move on.
Money stuff and debating the treasury is overall zero sum. Focusing on growing Zcash adoption is IMO way more important and positive sum.
I care a lot about shielded transaction count (usage), network security (safety), and speed/quality (not sure on the metrics here).
I'm not the only one who picks the metrics of course. I hope people give feedback.
But that's my piece on all this stuff. Focusing on key metrics is probably better and more win-win than fighting over a fixed pie.
Miguel retweeted
Tachyon Group (led by Sean Bowe) and Shielded Labs just posted a proposal to reduce the treasury, end the flow of funding, preserve operational capacity, donate $50M to Network Sustainability, and create a Future Dev and Legal Defense Fund: github.com/aquietinvestor/zi… ⤵️
Miguel retweeted
Over the last few days, I’ve had the privilege of spending some time w the Zcash community IRL. Some thoughts:
- extremely welcoming, kind, and thoughtful people. Felt very included as a community member and market participant. Was also great to meet a bunch of Twitter friends in the flesh
- the community still feels incredibly grassroots. Many developers and longtime contributors present, notably a lack of investors and services firms that you regularly see at other conferences
- the last time I felt this way about a crypto event was in SF in 2015-2016
- still feels very ideologically-driven, which has pros/cons. Very different from the command and control style of governance that is common for L1 smart contract platforms
- undercurrent of conflict between “factions” that seem to primarily have formed between new+old guard. Think this needs to be resolved before it comes to a head
- overall I think the project would benefit from a more focused GTM, clear alignment on narrative (my vote is to focus on private SOV with credible roadmap to quantum resistance), and clear+public technical priorities (quantum, crosslink, ZSA, etc). Not immediately clear to outsiders what the priorities are, and much of the discourse on twitter revolves around the future of grants, etc. which feels distracting relative to the larger vision
Overall I’m happy to see zcash:native finally get the attention it deserves, grateful to have spent time with the incredible community, and I believe the project is in a clear position to continue to gain mindshare vs BTC.
Feliz cumpleaños a Zcash!
Miguel retweeted
Zcash enables anyone, anywhere to store value and to transact privately and securely. Zcash is the most important project in the world, because self-sovereign money is a requirement for human rights and for a durable and thriving civilization. ⤵️
Miguel retweeted
A new @Anoma powered browser wallet for Zcash has arrived!
Try out @zillions_app, explore its features and share your feedback.
Miguel retweeted
Thanks to everyone who came! It was really fun, and cannot wait for season 2 in SF. Thanks @RIFTHQ and @profiit for co-hosting this.
ps: yes, we will do it again!
Glimpses from our Zcash meetup in SF.
We had @_TomHoward from @ZcashLabs talking about Zcash, where we are with the project, and where we are headed, some nice Mexican food + Zcash onboarding.
Thanks everyone for attending, and thanks to @RIFTHQ for co-hosting this.
We can't wait to do season 2 of this.
Miguel retweeted
Let’s go! More than 20+ people contributed to Zcash via this.
ths now has NU7 enabled, smoother rollback and reorg commands and more stable.
The brightest minds are all being attracted to Zcash via @zypherpunks :)
Thus Spoke Zakura v0.4.0 is here
What’s shipping in this release:
> Fresh Regtest environments now run with NU7 enabled
> Sends and faucets are saved before execution, with payment status restored after client interruptions
> New reorg and rollback commands support testing against chain changes
> ths run creates an isolated environment, runs your command, and cleans up afterward
> The dashboard now supports QR payment requests and payments to external Regtest addresses
> New wallet CLI commands and dashboard updates ship alongside docs for setup, payments, mining, and operations
Try it, share feedback, or pick up an issue. We’d love to have you contribute
