Blockchain Warrior, Crypto Samurai, Illiquid token buyer, Musician | prev. @krakenfx @BRDHQ (acq. Coinbase)

Joined August 2014
401 Photos and videos
Contrarian view - idc the tokenomics, buying a DEX token like $HYPE doesn’t work out in the long run. 🤷‍♂️
45
Gm
4
5
315
Jun 15
I know $STRK is privacy focused, and follows ZEC/the general market…but is it attracting devs? Early on in 2020 it was obvious that Solana was attracting quality, product-focused devs. It’s less obvious to me for Starknet, am I missing this?
193
Jun 15
Wait you didn’t buy $ZEC on the dip because you think someone actually exploited the pool? lol
3
11
112
5,505
Mike retweeted
Quick update on the last ~48 hours of Zcash Ironwood! 1. Protocol devs from across all the orgs met twice to discuss specification and implementation progress. Agreement on a couple additional changes: disabling Orchard pool bundles in coinbases, anchors as auth data for migration UX with hardware wallets, and the order that ZIPs and specs will be handled. 2. Ironwood circuit and ZIP 2005 integration drafts are going through the review process. @ValarGroup has already spun up testnets and his team has done a wonderful job scoping out and implementing some of the wallet-facing changes. We are beginning an Ironwood upgrade book for eventual consumption by auditors, wallets, protocol developers, etc.. 3. Formal verification work on Ironwood continues. A collection of different individuals who either have or will continue to work on formalization efforts will be meeting tomorrow where we'll settle on the specific strategy for getting the Ironwood SNARK formally verified. I'm hosting this and will post minutes and details after. Efforts from teams will be ideally combined where useful, existing approaches and progress unified and we'll figure out the easiest path for the next couple weeks. I've paused my own work on this to do Ironwood circuit stuff, but I'll be resuming on that tomorrow. These are the big pieces, there are also some major security auditing tasks taking place in the background -- at least three major firms are auditing Orchard currently, and multiple new AI auditing suites are hammering the codebases to ensure nothing else critical is sitting around anywhere. So far so good! Really proud of how much progress is being made every hour on this by all five of our major teams/orgs and our supporters inside and outside the community. Also love the general wartime vibe shift. Let's go!
UPDATE: The various orgs and protocol developers mentioned have agreed on the specific consensus rule changes for Ironwood, after settling the finer details. Here's a summary: 1. Ironwood introduces a new pool using the Orchard protocol, just like the existing pool. 2. The circuit for the Orchard protocol—which applies to both the existing Orchard pool and the new Ironwood pool—will have a flag that consensus rules can toggle. This flag disables payments to *other* users within that pool, while maintaining the ability to create change notes. (This enables a privacy safeguard.) 3. The old Orchard pool will have this flag enabled after the network upgrade, and payments to the old pool will also be disabled by constraining valueBalance. 4. Because payments are disabled on the old pool, wallets must send new payments to Orchard receivers (inside existing unified addresses) via the new pool, and they should also migrate funds away from the old pool. This combination enforces a bound on the circulating supply of ZEC through the use of the existing turnstile mechanism; the amount of ZEC that anyone can transact with is no more than the amount that is supposed to exist. Meanwhile, users' wallets can migrate funds to protect them from risk, which also gradually provides evidence that counterfeiting never took place. Now that we have this decided, we'll collectively move on to the implementations, specifications, and ecosystem support/outreach. (We also have many different auditing and formal verification efforts taking place behind the scenes to provide assurance about the circuit correctness. More on that soon!)
21
72
401
122,664
Jun 10
Stop personifying AI. It’s not “thinking” - it’s processing It didn’t “say” anything - it outputted something This is actually important.
2
4
174
Jun 10
In many cases, tech is filled with folks who think they’re so smart they don’t need profits. They turn their brain off and drink the old school Silicon Valley “grow at all costs” kool-aid. Meanwhile the pizza place down the street is a much more sustainable business (and in most cases, provides more value). With that said, it’s possible to cut through the noise. I’ve seen more practical founders that care about running a sustainable business on a realistic timeline. Those are the folks I look for and deeply respect. I’ve loved tech since I was a kid and still find it fascinating to this day. I’d just like to see tech businesses generally be a bit more responsible and sustainable. It’s time more people say the quiet part out loud.
Also appreciated getting the chance to discuss how data centers fit into the larger collapse of value in private credit and private equity. I have so many concerns about data center debt!
2
368
Mike retweeted
Jun 7
4. People who already understood the (obvious & long-discussed) possibility for undetectable inflation bugs, & risk-assessed & sized appropriately, are now realizing that formal verification can drop the risk *dramatically* fairly soon, & thus are *more* bullish than previously.
3
4
34
1,391
If you own 1 single bitcoin, it’s worth $62k. If you own 21 million bitcoin, it’s worth zero.
1
237
Here’s my dumb take post about why $ZEC is up: 1. Smooth brains who didn’t really understand what they invested in or what happened panic sold 2. Doom posters never held $ZEC or are part of the panic sold group 3. People taking a deep breath and sizing up the situation are buying or staying sidelined Result = zillions
15
14
172
12,401
Mike retweeted
Added some $ZEC at $365 IMO the bug being found and patched is actually very bullish for ZEC, and bearish for most of the rest of crypto - the reason is Mythos and other advanced AI will be able to find potential exploits in all crypto. ZEC just happens to be the one that has found and patched said exploit early, while most other projects haven't dealt with the issue yet.
31
31
223
9,909
I can’t take you seriously if you: 1. Unironically say cabal 2. Compare $ZEC to LUNA Thank you and gm
2
115
Mike retweeted
Replying to @mert
(i’m just joking. it’s true that we won’t know with absolute confidence but that’s just a technicality. practically we’ll know. and tbh we already know: it’s very very very unlikely that this was exploited)
1
13
1,228
Mike retweeted
Jun 5
Replying to @QwQiao
people don't understand that all this has done is fired up the core team to prove everyone wrong
14
16
182
7,094
Mike retweeted
Replying to @therollupco
sooo whitehat did his job and we got a generational entry?
1
7
396
Mike retweeted
Replying to @CryptyMike
The future will belong to the convicted.
1
3
94
Replying to @santisiri
En mi opinión, “It was just found” es un poco mucho. Taylor Hornsby es uno de los mejores auditores del mundo que más conoce este tipo de pruebas Zk.
1
22
4,493
But how do you know an attacker didn’t sell billions of ZEC
1
1
4
277