We at red·dev are elated to announce the support for the red·bridge project by the Avalanche Foundation @AvalancheFDN through the InfraBUIDL() grants program.
infraBUIDL() Program 🤝 red·bridge
The Avalanche Foundation is delighted to support @reddevinc in bringing privacy and selective disclosure services to Avalanche L1s.
Read more in the thread 🧵⬇️
Another red·bridge event is in Prague tomorrow. #Zcash and #Avalanche enjoyers are welcome! Thursday happy hour drinks and conversation 5:30 to 8:00 PM. https://t.co/X96uDIShsc
Two red·bridge events in Prague today and tomorrow. #Zcash and #Avalanche enjoyers are welcome! Today (Wednesday) wine tasting 5:30 to 8:00 PM. https://t.co/DxCLz6hPem
The future is being built at the intersection of AI & Blockchain. Proud to have our CEO @mrkit2u at Cornell Tech's 'The Programmable Economy: AI & Blockchain Redefining Markets' in New York City. Exciting times ahead! 🚀 #Cornell#Innovation#Zcash#Avalanche
@will__mcevoy "Our primary focus towards this end is Zcash – investing in it, *accelerating its adoption*, and *strengthening the ecosystem*. "
👀sounds like we have a lot in common! 🛡️➡️🌛
In this interview, we spoke with Arya from the @ZcashFoundation about his role, the advantages of Zebra over zcashd, key takeaways from Z|ECC Summit 2025 and more.
Learn more about Zebra:
https://t.co/4zuytMh44r
Software horror: litellm PyPI supply chain attack.
Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords.
LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm.
Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks.
Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages.
Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.
#Zcash community sentiment does not appear to be strong enough to support ZSAs at this time. Our red·bridge roadmap contemplated them. If and when they do get implemented, red·bridge will support them.
Full Throttle ahead on red·bridge!
there needs to be something greater than EIPs or ACPs or whatever else
some improvement proposal that's immediately being applied to all EVMs
EVMIPs or something
i want to bring 5564 to avalanche when it comes, it would pair perfectly with eERC and the upcoming @reddevinc bridge
if you can, vote for @reddevinc red·bridge on Retro9000 in the next 24 hours
@mrkit2u is doing a tremendous job in developing new tech at the intersection of two very new protocols on both @avax and @Zcash
when it goes live, the bridge will likely be the key avenue for ZSAs when they go live, and they'll all pass through avalanche fully encrypted from end to end
link to vote below
As we build red·bridge, we have created example code for any #Avalanche builder who would like to include support for Inter-chain Messaging (ICM) and Teleporter in their custom VM. We explain it here in this brand new episode of Benny Learns Blockchain. https://t.co/wRo5L8OG4Z
This holiday season, we at red·dev want to thank you for being part of our year. Happy holidays and may 2026 bring great opportunities!
#MerryChristmas#HappyNewYear2026
Thank you @Ahnor_Block from red·bridge!
“@reddevinc who are building RedBridge, are bringing Zcash liquidity and assets to Avalanche for privacy-enabled DeFi.
Why it matters
•Unlocks shielded transactions
•Brings Zcash users and capital
•Positions Avalanche as a privacy-aware settlement layer
They’re building a full L1 that connects Zcash to multiple networks with native privacy guarantees.
@arq_marii from our team attended the PMI Barcelona event on “Management of Chaos” — engaging talks on leadership, AI, data & PM Guide v8.
Looking forward to next year!
#waytogo
When ZEC hits $500, all you can say is “privacy.”
But when $AVAX reaches $5000, you know there are major institutional L1s running on top of it and they spend $AVAX to operate.
FIFA needs $AVAX to play football!
My god, that’s insane :)
Here's a ten slide presentation I did this past Thursday on #Zcash and @reddevinc's red·bridge for #Avalanche builders, sponsored by @AvalancheFDN. Zcashers, you probably already know all this! The intended audience is for people joining and trying to understand the ZEC pump.