Bread is one of the clearest examples of what Miden is for: private accounts that people can actually use.

sending crypto without extra details >>>

→ Buying coffee shouldn’t reveal your savings. → Paying rent shouldn’t reveal your salary. → Splitting dinner shouldn’t reveal your investments. → Buying a ticket shouldn’t reveal how much you have left. → Buying a gift shouldn’t reveal where else you shop. → Making a donation shouldn’t reveal every cause you support. → Paying a subscription shouldn’t reveal everything else you subscribe to. → Paying a freelancer shouldn’t reveal your company’s runway. → Getting an invoice paid shouldn’t reveal your other clients. → Receiving a refund shouldn’t reveal where you spend it next. → Sending $10 shouldn’t reveal the other $10,000. → Getting paid shouldn’t notify everyone you’ve ever paid. → Paying someone once shouldn’t let them watch your money forever. Your financial life shouldn’t have spectator mode. For crypto to become everyday money, privacy has to be the default. That’s why we’re building Bread 🍞🥐🥖 Early access below.

When I first started working on @joinbread you could just do a simple private send and even for that the receiver would have to manually import private notes. Now <2s proving on an iphone, seamless private sends, cross chain bridging, swaps and much more to come. @0xMiden coded

I haven’t been as excited about a programming language since when I first started learning Rust. Lean4 is an extremely powerful language. However, one thing it’s missing is good tutorials and examples! So I built an online Lean4 learning tool! I predict Lean becoming one of the most popular languages in the coming years amongst AI labs, blockchain researchers, and agents. It’s what powers verifiable auto-research. Lean4 increases the velocity at which humanity can make mathematical discoveries. To be ahead of the curve, learn some lean today! Open to feedback and suggestions! 😅 leanlanguage.app

Today, we're introducing the PriFi Stack. A new financial stack built around private stablecoins and privacy-preserving infrastructure to shape the future of finance.

Today we're announcing that USDCx on Miden is coming soon: a native, @USDC-backed stablecoin, issued by Miden via @Circle xReserve. Stablecoins on Miden will be private by default. Hold and transact USDCx without publishing your balances, counterparties, or payment history to the world.

another championship. I believe I can help make the Philadelphia 76ers a championship team and I am so excited to energize a new fan base and start this incredible journey one last time.   Thank you LA. Miami I’ll forever love and Northeast Ohio will always home! 🙏🏾🫡👑

BREAKING: LeBron James is signing with the Philadelphia 76ers on a two-year, $8 million deal with a player option, Klutch Sports Group and Klutch CEO and Game Over show host Rich Paul tells ESPN.

hello there the jacobian conjecture is false thanx to my close friend akhil for asking about it and my other close friend fable for working during the world cup final ((1+xy)^3 z + y^2 (1+xy) (4+3xy), y + 3 x (1+xy)^2 z + 3 x y^2 (4+3xy), 2 x - 3 x^2 y - x^3 z): \C^3\to \C^3, has jacobian determinant -2, and sends (0, 0, -1/4), (1, -3/2, 13/2), and (-1, 3/2, 13/2) to (-1/4, 0, 0)

AI has made it easier to write optimized code on day 0, but it is creating a new problem... Ask an LLM to write some code, and it will often reach for the most "correct" version - caching, batching, async, configurable strategies. Code that looks staff-level from the first commit. If you keep probing it to optimize further, it will come up with such absurd optimizations that you may not have even heard of. Most of these optimizations solve a problem you do not have yet. A function handling 50 records a day does not need a connection pool, a retry queue, and a pluggable backend. It needs to work and be readable. To be honest, we engineers have always over-engineered, but AI has lowered the cost of writing the complex version to nearly zero, so the lazy default (write the simple thing first) no longer feels lazy. It feels like leaving performance on the table. The result is codebases full of abstractions nobody asked for. Interfaces with a single implementation. Generic configs for cases that will never change. Vector operations and macros no one asked for. The skill that matters now is not writing optimized code. It is knowing when to stop optimizing. Premature optimization used to be expensive enough that most people avoided it by default. Now it is one prompt away. Good engineering judgement is about knowing which optimizations the problem in front of you actually needs. Hope this helps.

this is like KD joining the 72-9 warriors

Miden is building practical privacy for the future of finance. Institutions don’t want to build global-scale financial applications on transparent, public networks. A key reason for this: privacy Watch our full story, and learn more 🧵

Bye Dubai ‘Twas fun