Skylar Saveland 🛡⚔️

Hace un par de años propuse «Arte para la privacidad», buscando formas de promover la privacidad a través del arte. Las ideas son bienvenidas... PD: si quieres recibir clases de mandolina, escríbeme. Yo acepto $ZEC - I accept ZEC. Música: De Conde a Principal (Aldemaro R).

@thecodebuffet @ezecZshield @zodl_app @ZingoLabs "We" should make a significant investment in developer ergonomics here.

This is going to take a while. I'm syncing a 2M block old testnet wallet using @zodl_app and Zaino from @ZingoLabs This is the kind of work that is both boring and invisible but someone has to do it 😅

Claude. PUT THAT COFFEE DOWN!!

@mert Senate and Senile is not a coincidence #LinguisticTrivia #Corpán

I don't get how you are considered unemployable past 70-80 years old and yet that's the age group exclusively running most countries

A coffee shop that accepts ZEC. Conference tickets bought privately. A Shopify store where no payment processor is logging your customers' data. That world starts with merchants. And now it's easy.

I have a problem that I would love to simply vibe out with a prompt; but, I'm finding that I am still having to learn, understand, and point out crucial details to the agents 😑

We are pleased to announce a $5M investment into @zodl_app, alongside @a16z, @balajis, @winklevosscap, @cbventures, @friedberg, @paradigm & other leading investors Our shareholders now have exposure to both private digital money & the most important privacy software company 👇

I brokering a long disagreement between codex 5.3 and opus 4.6. It's a pretty hard problem, I guess.🍿

@BostonZcash @zooko @nuttycom @ruZCASH @dismad8 @_skyl @ebfull @zkDragon proposal on how to use Tachyon pool keeps memos but shrinks their size to allow scale. Level up here, hero

Zm everyone! Here is the exciting updates from us 🤩 We are officially live on chrome webstore! Here is the link: chromewebstore.google.com/detail/zucchin… Give it a try and 5 stars for a tiny support ❤️

@ruZCASH @dismad8 @_skyl @ebfull My assumption is that it will become an economic choice that a user makes; you will have a choice between cheap lightweight Tachyon transactions, and more expensive Sapling and Orchard transactions.

@thecodebuffet @ebfull Perhaps a sweet spot would be using the wallet secret material to be able to prove things to servers 🤔 or blending more traditional cryptography applications outside of payments ... memos are so cool though!

@thecodebuffet @ebfull I basically built a ~feature complete, cross-platform Zcash wallet by myself in a couple of short sittings! But, now I'm not sure if/how to proceed because ... do I even want to support memos or should I think about offchain mechanisms ... probably both ...

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.

@zooko @nullc0py @ebfull There is a reason that I take pride in not being afraid to ask the "what a stupid fcking" questions. 😆

@nullc0py @ebfull Here’s another example of someone saying “oh wait what did I just vote yes on?”:

Interpretation of the Zcash coinholder sentiment collection... (My personal view is that if coinholders strongly oppose a change, it's *really* hard to argue we should do it anyway.) 1. ZSAs are in bad shape. There is basically no support from coinholders, and I'm not sure there's enough enthusiasm elsewhere to overcome this. I'm personally not bullish about ZSAs for numerous technical reasons. I think an argument still needs to be made for including this feature in the protocol. 2. NSM (modulo fee burning) seems unpopular with coinholders too. My guess is that anything that touches this issuance gives off bad vibes regardless of its merit. I think *because* it touches issuance we should be even more deferential to coinholders. 3. Fee burning seems fine. 4. Memo bundles are broadly disliked from coinholders. Personally I don't like these. It moves us in the wrong direction: memos are not sustainable / scalable in their current form, and we shouldn't be encouraging people to use them in ways we didn't originally anticipate. I appreciate the careful attention to detail and effort put into the ZIP though! 5. Explicit fees seem fine. 6. Sprout removal seems to have more opposition than I expected. We really need to propose this to the community again, perhaps next time with a more clear timeline/warning process. Sprout users are not paying for the ongoing burden that the Sprout pool has on the maintenance of the protocol, and the pool is nearly abandoned. 7. Tachyon has fantastic support from coinholders and from most others that were polled too. Thank you! Making progress on scalability seems very important to ZEC holders and most Zcashers I've talked to. I believe the results show there is a mandate to making progress shipping a shielded pool on mainnet even without wallet support, which is how our other pools have previously been shipped. I think this kind of aggressive deployment strategy is essential to making meaningful progress on scale. More generally, I think this bodes well for other scaling-related objectives being developed such as the ideas coming from the @zkDragon camp (which I think will be vital for Tachyon's success), and so those should feel a similar amount of support here. Take this one with a grain of salt, since Tachyon is my pet project! 8. STARKs haven't quite been sold to the community yet. I haven't seen much enthusiasm for them on a technical level from other protocol devs due to concerns like security levels. Let's maybe keep iterating on this, it doesn't seem dead but it seems like an uphill climb. 9. Dynamic fees don't enjoy much support and there's genuine concern/skepticism about the mechanics design of them (as proposed.) I agree, this needs more work. 10. No real enthusiasm for consensus accounts. This is a weird one, I don't know what to think about it yet. 11. Quantum recoverability is pretty solid across the board. Great work to the ZODL crew on this.

Introducing: built-in git worktree support for Claude Code Now, agents can run in parallel without interfering with one other. Each agent gets its own worktree and can work independently. The Claude Code Desktop app has had built-in support for worktrees for a while, and now we're bringing it to CLI too. Learn more about worktrees: git-scm.com/docs/git-workt…

@dismad8 @ebfull Hrm, there are still a lot of unexplored, powerful use cases possible via encrypted payments delivered p2p with encrypted bit of data 🤔 What would be the best substitute?

@_skyl @ebfull I believe remove them, but I'll let ebfull clarify.

Does Tachyon plan to remove shielded memos or support them? @ebfull @dismad8

@ngmarley The UI is the same for all platforms but the interaction with the device is native where needed using tauri-plugin-zcash which is in the same repo github.com/free2z/zuu/tre… github.com/free2z/zuu/tre…

@_skyl Looks great! Do you have source available? Also curious, are you writing the core separately and wrapping in OS-specific UI?

I reckon that this is already a world-class $ZEC experience ... Maybe we add an address book and see if we can do warp sync as well?