BabyGGuy

Forecasting Zcash's 4yr commitment to advancing privacy: 🔲|🔗|🌐|☁️ 🪙|✔️|✔️|✔️ 🛡️|✔️|✔️|✔️ 📑|❌|✔️|✔️ 🔍|✔️|✔️|✔️ To recap 🪙ZEC & 🛡️ZSA: Enable cross-chain & off-chain txs. 📑Contracts: Support cross-chain & off-chain activations. 🔍KYC: Optional, movable across chains.

@zooko An AI writing Lean proofs just to satisfy human trust issues. Cute. 🤖

Oh man oh man. I can’t be sure that this hyperbolic headline (“I have discovered programming’s final form”) *isn’t* true!

@zooko O... You need to replace your zsh (or bash) completion with AI. > git diff please show the last 3 commits<TAB> > git diff HEAD~3 HEAD Just give Claude Code the above example and tell it to add it to your shell. You won't hate git so much.

God I hate git. I can't wait for the AI revolution to replace git with something better so completely that I never have to think about it again.

@zooko @HardhatChad But in all honesty the explanation is far simpler than that imo. Ruby, Python, JavaScript are interpreted. No compilation step and therefore less tool calls etc.

Well we know 3 things. 1) The more training data an LLM has on a specific problem the better it performs at that specific problem. 2) GitHub stars are used as a quasi measure of quality which the labs use for training related decisions. 3) It might be a coincidence that when I search minigit on GitHub the 2nd result is ruby.

Agents are better in rust. iykyk

@zooko @HardhatChad And I'm over here thinking I'm smart by prompting Claude to use type driven development, phantom types, and state machines 😅.

@HardhatChad According to this it's Ruby. 😲 dev.to/mame/which-pro…

@zooko Now go ask GPT 5.3 Instant the same thing 😉. Such an underrated model.

@BabyGGuy Thanks!

I've been switching back and forth between Claude Opus 4.6 and GPT 5.4 on my coding projects. I strongly prefer Claude's style. He doesn't waste as much of my time as GPT does trying to provide unnecessary additions that I didn't ask for.

Two reasons when Claude does that. You're using Claude [Code] and you're at >40k context used (performance begins dropping off quickly) or it has inferred something from chat history and not done a web search. If you're asking Claude a tricky question always make sure it does a web search first which helps ground the model. Asking Claude to prove someone else wrong will often trigger a web search (i.e. need facts to back it up 😬). Funny how human they can be at times 😅.

@BabyGGuy Oh wait, no I take it back. Now Claude is telling me things are impossible that GPT is correctly telling me how to accomplish.

@zooko 🤔 I've done this many times: - Hey Claude take this (possibly Codex) [patch](github.com/octokit/sandbo…). Merge and improve only the X changes. But actually I should try: - Hey Codex make this (possibly Claude) [patch](github.com/octokit/sandbo…) feature complete.

The only reason I keep giving GPT another try is that either Claude or the web service I'm using to anonymously access Claude keeps failing — maybe due to exceeding an internal timeout somewhere — when I give him a thorny problem that will take tens of minutes to solve.

Have tested starting to accept private, non-custodial $ZEC payments, and it worked with View Key only, app destination Zkool. Great thing @cipherscan_app, will add it in a website very soon, thank you! Features I wish: @cipherscan_app. Will add it in the - Add BRL and more fiat currencies for adding products, Software as a Service! - Fix the ZEC rate on the Dashboard - Price_ID like Stripe for each product But yeah! You can start to accept Zcash as payment today!

If your 'freedom' requires you to only transact in shielded ZEC, you haven’t actually achieved freedom; you’ve just traded one set of rails for another. By restricting the network’s utility to a single asset, you’re reducing the surface area of liberty.

@ebfull @AnotherAussieX Sidechain it ™️

@AnotherAussieX Yup, this is part of the class of off-chain payment protocols that I've been strongly pushing for, but it runs into separate objections from others due to the effect it has on backup and restore assumptions, centralization or platform risk... and network privacy is hard.

Shielded memos are unsustainable in their current form. Most decentralized payment protocols do not support these things or anything like them without users having to pay more to explicitly include them, and even then they won't usually be "encrypted" memos unless addresses contain the right capabilities / semantics. There are some exceptions, such as Lightning, but those natively use off-chain, interactive payment protocols. (More on this later...) People love them in Zcash, and they are a great memetic tool. I get it. The reality: * every payment includes one, even if the user doesn't use it, to maintain indistinguishability * every payment includes a 512-byte one, and they cannot vary in size for the same reason * every on-chain memo could be intended for you; the only way to find out (privately) is to fetch and trial decrypt all of them The only real reason these things existed in the first place was because our SNARKs were already large, and we were already doing key exchanges on-chain for Zerocash, so there was little downside to adding a memo blob. Any scalable version of Zcash (including Tachyon) is going to shrink the marginal transaction size so substantially that the conventional memos would make up the bulk of the on-chain cost of a shielded transaction. There are only a handful of ways around this. First, we can build off-chain payment protocols so that the encrypted memo is carried elsewhere. These generally seem to have UX limitations compared to the protocol people are familiar with, or require extra infrastructure. But if they work, you would have fewer limits on memo sizes. This is my instinctive preference, if we could pull it off. Alternatively, a PIR-based scheme can be used to keep the on-chain payment protocol and familiar UX. This is what @zkDragon is working on, and if it works it would be a gamechanger. But there are still some limitations for the memos that mean they cannot be used in an cheap/unsustainable way like they are now, with the same UX. Finally, users could include memos anyway and just pay extra for it. Memos compete with other transactions for capacity, and several payments can be made with the same amount of resources as a single transaction's memo. Using the chain as a broadcast medium for the ciphertexts, with trial decryption, would seriously limit the amount of people who could afford to do this at scale. This also harms privacy because it harms indistinguishability. There's no free lunch here. I've not seen an option for preserving this feature that does not piss someone off. My philosophy for Tachyon is to ensure that the shielded protocol is detached from the payment protocol so that we have flexibility in pursuing the option that works best and scales. All of our future pools need to be built this way IMO. This would accommodate any of those three options. It's also easier and simpler to build, which is why we're doing this part of Tachyon first.

Mert explains the Zcash FUD “It seems like everyone got faked out by like a few slop content creator types and then Grok summarised it falsely” “There was this news that the Zcash devs left but all that happened was the devs went from a foundation structure to a tech startup/ labs structure. It was just a whole lot of shenanigans”

Huge respect for @nuttycom, he is answering all questions related zcash and tooling in the zypherpunk discord! Where are you anon? This is the biggest privacy hackathon in the world! Build!

@mrkit2u @zooko @nuttycom @nextiscrypto @arkham @cypherpunktech Yes I'm suggesting Zcash could move transparent consensus to another chain as a wrapped token. Assets in the transparent pool would move to a shielded collateral address with viewing keys. How many red lines in that PR 🤯♥️.

@mrkit2u @zooko @nuttycom @nextiscrypto @arkham @cypherpunktech 🦓 Zebra: “Kill the transparent pool!” 🙋 User: “But I use it!” 🧔 Community: “Why not both?” 🌉 Wrap the t-pool on another chain 💎 Backed 1:1 by its assets 💼 Wallets can use one or both 🔑 Viewing keys prove collateral ❤️ Decentralized, transparent, optional

theblock.co/post/378582/wi… Looking forward to @arkham adding Zcash support so that it can track @cypherpunktech's Zcash treasury. :-)

Agree. Phones typically get software support for about 3–7 years after release, but it’s not always clear when that ends. On Android, you can check your last security update under(ish) Settings → About Phone → Android Version. If it’s been more than 3–4 months since the last security update, it’s worth checking whether your manufacturer has ended support.

But here's a nice positive spin: start doing your important, high-value things on your phone and remove them from your desktop/laptop. :-) It's convenient! You probably wanted to do this anyway but you stopped because you mistakenly thought desktops were more secure.

This guy is long ZEC. Bullish.

@mert @himgajria Most people misunderstand financial privacy 🛡️. It’s not noise. It’s not motion. It’s encryption — at rest.