Had a really interesting conversation with Kaspa core developer @michaelsuttonil about the Kaspa Privacy Initiative today. We discussed our candidate architecture for a scalable shielded native KAS protocol, using covenants, ZK proofs, permissionless relayers and batchers. One of the biggest takeaways was how much of the infrastructure we're looking for may already be available through Kaspa's Based Apps and KIP-21. In our original design, one of the challenges was ensuring that batchers couldn't selectively omit user operations while claiming to have processed a complete batch. With Based Apps, user operations can be ordered directly on Kaspa L1 in an application-specific lane. KIP-21 provides cryptographic sequencing commitments, allowing a properly designed settlement proof to demonstrate that the relevant operations were processed correctly. That could remove a substantial amount of custom infrastructure we'd otherwise have to build ourselves. We also discussed canonical bridges, recursive proving and why sharding may introduce unnecessary complexity at this stage. Our next step is a small Based App feasibility PoC on TN10. We'll test lane ordering, execution, proof-based settlement, deliberate transaction omission and independent reconstruction before adding the actual shielded privacy logic. No architecture has been finalized. The goal remains to find the safest, most scalable and most decentralized solution, not to defend an earlier design. Really appreciate Michael taking the time to share his insights. Conversations like these are incredibly valuable. Technical feedback, criticism and contributions are very welcome! github.com/olafweller/kaspa-…