MLabs

Just pinging a few DReps here - appreciate your attention 🙏 @blockdaemonhq @everstake_pool @Cardano_CF @Hideki_Takeshi @JaromirTesar @BullishDumpling @bigpey @phil_uplc @ATADA_Stakepool @ItsDave_ADA @Wiiinnie @nagamaru_panda @hix_coffeepool @longminswap @tempo_vote @dori_coin @Pooltoolio @TheOCcryptobro @liqwidfinance @quantumplation @ArmyofSpies @hisa_iokinawa @cryptofly777 @kyosuketakatuki @sachs_johnny @ada_ocean @Padierfind

Post-quantum signatures are becoming part of the infrastructure conversation for every serious blockchain. The timeline is finite, and leading chains should be preparing before the migration becomes urgent. That is the point of MLabs’ post-quantum signatures proposal. Today, Cardano scripts and dApps rely on signature schemes like Ed25519, ECDSA, and Schnorr. These are not quantum-safe in the long run. For public blockchains, the core concern is not decrypting old ledger data. It is future-proofing the signature and authorization assumptions that protect accounts, scripts, and high-value assets. This proposal takes one concrete slice of post-quantum readiness. Can Cardano support post-quantum signature verification at the script layer? The work is scoped around CPS-0027, “Approaches to Post-Quantum Signatures,” authored by an MLabs Tech Lead. github.com/cardano-founda… The work starts with the practical question. Which post-quantum signature scheme actually makes sense for Cardano? That means comparing candidates against Cardano’s real constraints, including signature size, key size, verification performance, implementation quality, and likely fit inside Plutus. From there, the proposal follows the normal Cardano engineering path. A CIP, cardano-base, Plutus Core, wrappers for Plinth, Plutarch, and Aiken, and then a working smart contract wallet demo that shows the capability end to end. So the goal is not just to write a research report. It is to take one concrete post-quantum signature path from evaluation to something Cardano builders can actually review, test, and use. Proposal link: hydra-voting.intersectmbo.org/votes/cardano-… For MLabs, the value proposition is straightforward. Cardano does not need to panic about post-quantum migration. But it should not wait until migration is urgent to answer the practical engineering questions. This proposal gives Cardano a concrete, reviewable, open-source step toward post-quantum readiness at the script and dApp layer. Our CTO gives an approachable overview 👇

@astroboysoup Understood - thank you

@MLabs10 Please don't tag me in Governance-related matters. I'll auto-vote no, and I'm deregistering before the end of the month.

Plutarch and Ply have been doing serious work in the Cardano ecosystem for years. MLabs' treasury proposal focuses on keeping that smart contract tooling reliable, compatible, and useful throughout the next protocol cycle. For anyone unfamiliar, Plutarch is a Haskell eDSL for writing efficient Cardano smart contracts via controlled compilation into UPLC. Ply helps serialize Plutarch scripts to and from CIP-57 blueprint-style artifacts with inferred types, protecting the on-chain/off-chain boundary without forcing teams to manage low-level type details. These are not flashy end-user products. They are part of the tooling layer that production Cardano builders rely on when writing and maintaining smart contracts. These tools have seen real ecosystem use, including production or project use by teams and protocols such as Liqwid, adopters of Agora, Djed, Clarity, Optim, and others. Our proposal seeks 12 months of quarterly maintenance and enhancement work for Plutarch and Ply. hydra-voting.intersectmbo.org/votes/cardano-… To keep priorities clear and transparent, we follow a hierarchy each quarter: 1. Critical breakages and serious vulnerabilities 2. Protocol-era and hard-fork compatibility 3. Bug fixes, correctness improvements, and optimizations 4. Documentation, examples, technical writeups, and developer-experience improvements This also includes Dijkstra-era readiness where relevant, keeping Plutarch and Ply aligned with Cardano ledger, Plutus, UPLC, and tooling changes as Cardano moves forward. The scope is distinct from earlier funding. Prior Fund9, Fund13, and Intersect support covered previous development, enhancement, and Conway-era compatibility. Rather, this proposal covers the next annual maintenance cycle, including critical breakage response, protocol-era compatibility, bug fixes, Dijkstra-era readiness, documentation, and related maintenance. Each quarter will produce public evidence of work completed including issues, PRs, releases, tests, benchmarks, documentation, changelog updates, technical writeups, and a maintainer review explaining what was prioritized and why. If Cardano wants production smart contracts to keep moving safely through protocol evolution, the tools behind those contracts need funded maintenance. With community support, Plutarch and Ply will remain reliable, efficient, compatible, and well-supported for the builders who depend on them. Our CTO gives an approachable overview 👇

@ThomasNordicADA @YoroiWallet @yutazzz @emurgo_io @eternlwallet @everstake_pool @Cardano_CF @BullishDumpling @bigpey @phil_uplc @ATADA_Stakepool @astroboysoup @ItsDave_ADA @Satoshi15121937 @nagamaru_panda 😅

@MLabs10 @YoroiWallet @yutazzz @emurgo_io @eternlwallet @everstake_pool @Cardano_CF @BullishDumpling @bigpey @phil_uplc @ATADA_Stakepool @astroboysoup @ItsDave_ADA @Satoshi15121937 @nagamaru_panda Last I checked I am not a DRep ser 🫣

CTL has been doing serious work in the Cardano ecosystem for years. This proposal is about opening it up to more developers. CTL is Cardano’s open-source transaction-building library, an off-chain/browser-friendly layer that helps dApps construct, balance, work with wallets for signing, and submit Cardano transactions. It has been part of the Cardano developer stack since the Alonzo era. This proposal builds on infrastructure that is already in production use. CTL has helped real teams build through multiple protocol upgrades, including projects like Indigo, Clarity, Genius Yield, Cardano Racers, Noble Steed Games, SingularityNET, and others. The opportunity now is to make CTL easier to use for developers who are not already working in PureScript. PureScript made sense historically, given CTL’s roots in the Alonzo-era Plutus ecosystem. But today, most dApp teams work in JavaScript and TypeScript. Teams that want CTL’s reliability often need wrappers, middleware, a separate PureScript service, or custom transaction-building logic. This proposal opens a better path. hydra-voting.intersectmbo.org/votes/cardano-… WP1 opens CTL to JS/TS developers through a supported public interface, while keeping the mature CTL core underneath. The goal is simple: broader access without throwing away the reliability CTL has built over multiple protocol eras. WP2 adds Koios as a first-class backend, giving builders another open-source, community-operated query option alongside Blockfrost and Kupo/Ogmios. WP3 keeps CTL current through quarterly maintenance and Dijkstra readiness, so downstream dApps can prepare earlier and move through the next protocol cycle with more confidence. The value proposition is straightforward. This is existing production-used infrastructure becoming easier to adopt. The scope is separated from OSC work: OSC is expected to cover core maintainership and Van Rossem work, while this proposal covers JS/TS access, Koios integration, and forward-looking Dijkstra readiness. Demand is already visible. CTL has production use today, TypeScript-facing integration needs already exist, and recent repo traffic showed 2,057 clones and 424 unique cloners in 14 days before the JS/TS interface even exists. If Cardano wants more builders, one of its most mature transaction libraries should not remain locked behind a niche language surface. CTL should be easier to adopt, easier to maintain, and ready for the next protocol era. We appreciate everyone taking the time to review, question, and consider the proposal. Our CTO gives an approachable overview 👇

I would like to see the quantum resistance signature proposal from @MLabs10 pass. I know we @clarity_dao would incorporate this into our governance flows for our clients and it needs to be done.

Another quarter — another Cardano.nix update. Cardano.nix is our reproducible #Cardano infra project. This Intersect milestone we: 🔹 Updated cardano-node & cardano-db-sync 🔹 Bumped Blockfrost 🔹 Private testnet: added Dijkstra-era genesis 🔹 Bug fixes And more. Details 👇 github.com/mlabs-haskell/…

Cardano Builder DAO is one of the clearest paths for treasury funding to reach active ecosystem teams. Round 2 builds on that progress with stronger governance, public KPI tracking, and improved accountability. Cardano’s builders are still here. They should have the resources to keep building. medium.com/tap-in-with-ta…

Join us in 30 minutes as we debate and share what is happening at the CB DAO. x.com/i/spaces/1wxWj…

@astroboysoup @_KtorZ_ Seeing some confusion here. Covenant is already being used by Konma for HaskLedger. The Solana/sBPF work reflects a real feature from that work, not "Solana" sprinkled in for hype. It also maps to Pillar 2, multi-chain tooling. Our CTO explains the scope here:

1.461M ADA for Covenant 2 by @MLabs10. Covenant sits between smart contract languages and blockchain bytecode. This proposal improves dev experience, docs, error messages and examples, while extending Covenant toward cross-chain compilation with Solana sBPF support. The aim: make Cardano easier for non-Cardano devs to reach. Worth funding? *Not a paid promotion

@astroboysoup Different design, different tradeoffs, different integration story. Healthy ecosystems have more than one implementation of important primitives. Happy to discuss the technical differences with anyone interested. Here, our CTO gives an overview of the proposal scope:

@astroboysoup Does that make FeesaSwap superior? Thats not our claim. FeesaSwap and Aquarium serve different roles in improving Cardano UX & growing usage beyond ADA holders. This proposal prioritizes the ecosystem (not an individual solution) and is aligned with Pillar 2 of the 2030 vision.

686K ADA to open-source Cardano fee abstraction. @MLabs10 wants to open-source and harden FeesaSwap, a live mainnet system that lets users pay fees in supported non-ADA tokens while ADA and collateral are handled behind the scenes. The upside: this attacks real UX friction. The concern: FeesaSwap already received Catalyst funding, so this needs to clearly deliver public infrastructure, not just product maintenance. Worth funding, or should wallets solve this themselves? *Not a paid promotion

Hate to break it to you but we're bootstrapped, and we need to keep the lights on like any other business. We have won many grants it's true - because we have a reputation of delivering what we promise, and because we have ambitions for what this ecosystem is capable of. Delivering our work is costly, but we do feel it will have tremendous impact for years to come.

IMO, the fee violates or ignores TENETS 3, 8, and 9, if not a couple others. If the fee is UnConstitutional, then so are these 55 proposals and will have to be resubmitted minus the fee. If they want to donate to the treasury, then do so, but it doesn't reduce the number of proposals well funded groups will submit like @MLabs10 with 10.

The 1000 cardano:native Proposal Fee @IntersectMBO & @IntersectCBC implemented to submit a budget request to the treasury ✅IS✅ or ❌IS NOT❌ Constitutional? How many of the "TENETS" does this requirement not uphold, ignore, or disregard? Do these actions meet requirements in the By-Laws, Membership Agreement, and Code of Conduct? Repost and tag your DREP and the Cardano Blockchain Ecosystem Constitutional Committee(s) and its/their members if these items are of concern. Yes, the reduction of spam proposals is very important. There are other ways to achieve this without placing a financial burden any stakeholders. COC Page is broken BTW. docs.intersectmbo.org/legal/policies…

Repo & Docs: github.com/Plutonomicon/p… plutarch-plutus.org/haddock/

Keep in sync with our latest Plutarch updates, part of our Core Tool Maintenance & Enhancement project. This video covers new type instances, plutarch-ledger-api updates, performance improvements, API cleanups, and more 👇