agora to sem saber se a Mlabs atualizou e ta entregando tudo isso mesmo que estão falando ou se é só propaganda pra vender produtos

Levantamento da mLabs mostra disparidades entre engajamento, audiência e viralização entre seleções classificadas para o Mundial de 2026 #copadomundo #mundodomarketing #redessociais #seleçãobrasileira mundodomarketing.com.br/bras…

nossa mano, eu fico de cara com a equpe de social midia lá da empresa que ficam agendando alguns videos que eu edito pra serem publicados via mlabs, e essa merda de mçabs comprime a porra do vídeo a ponto dele ficar parecendo uma grande bosta

Why are no MLABS proposals getting funded?

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-foundatio… 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.or… 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 👇

what would make you positive towers sui/mlabs

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.or… 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 👇

Currently we are in contract negotiations (under Tooling) with Mlabs and Mesh. Other projects have not yet applied despite an open and public link.

e ainda só fica passando propaganda do mlabs*****

acho que eu vou assinar o youtube premium unicamente pq não é normal o jeito que essas propagandas me estressam tipo e ainda só é do mlabs puta merda eu só quero ouvir uma MÚSICA

💻 Hiring: Senior Data Engineer - MLabs 📍 Remote - Europe (Netherlands, Poland, Portugal, Romania) | 💼 Full-time | 🧑‍💻 Web3 | 💰 $110K—$125K | 🕐 12 hours ago - June 11, 2026 MLabs is a premier infrastructure provider in the decentralized web (Web3) ecosystem. The company is hiring a Senior Data Engineer to design and operate the data foundation for a global payments network, focusing on reliable systems for wallet connections, transaction health, and financial reconciliations. 📋 Responsibilities include: - Designing and operating the data foundation for a global payments network. - Building reliable systems focused on wallet connections, transaction health, and financial reconciliations. 🔑 Requirements: - 5 years of experience in data engineering or data infrastructure with a proven track record. - Expert-level SQL skills and strong programming experience in Python or similar languages. - Significant experience with tools like Airflow, dbt, ClickHouse, BigQuery, Snowflake, or Athena. - Deep understanding of event-driven architectures and real-time data processing. - Proficiency in using AI-assisted development tools and maintaining code quality. - Experience designing systems with a focus on data quality and observability. 💡 Perks: - Fully remote with home office budget. - Team offsites and conference travel. - Learning & Development budget. - Generous PTO and parental leave. - Competitive salary equity. - Healthcare for US team members. 📩 To apply: Apply here apply.workable.com/mlabs/j/B… 🔗 Original post: linkedin.com/posts/remote-se… ⚠️ DYOR! I don’t verify every job. If someone asks to run files (even from GitHub) or ask for payment 🚩 likely a scam. ❗️ I'm not hiring myself! I just sharing fresh web3/crypto/blockchain roles DAILY for all levels! 💡 For Interns & juniors → t.me/crypto_vazima_english 💼 Mid/senior jobs → t.me/web3_jobs_crypto_vazima #DataEngineer #Web3 #Blockchain #RemoteJobs #Hiring #SQL #Python #Rust #BigQuery #Snowflake #Clickhouse #Airflow #Crypto #Engineer #TechJobs #SeniorEngineer #EuropeJobs

🛡️ Hiring: Product Security Engineer - MLabs 📍 Remote (Global) | 💼 Full-time | 🧑‍💻 Blockchain/Web3 | 💰 $75K—$85K | 🕐 12 hours ago - June 11, 2026 The company is a fast-growing, enterprise-grade software organization building Web3 infrastructure. They are hiring a Product Security Engineer responsible for embedding security into the product development lifecycle, with a focus on vulnerability discovery, adversarial testing, and threat mitigation. 📋 Responsibilities include: - Embedding security directly into the product development lifecycle - Conducting vulnerability discovery and security testing across blockchain protocols, smart contracts, and APIs - Performing threat modeling and security architecture reviews in distributed cryptographic systems - Analyzing trust model tradeoffs in applied cryptography 🔑 Requirements: - Proven experience in vulnerability discovery and security testing across blockchain protocols, smart contracts, and APIs - Strong threat modeling and security architecture review experience in distributed cryptographic systems - Deep knowledge of applied cryptography and ability to analyze trust model tradeoffs - Mastery of blockchain security practices and proficiency with security testing tools - Strong coding skills in Rust and/or Java, with understanding of memory safety and security risks 💡 Perks: - Competitive salary $75K-$85K - Work at the forefront of Web3 infrastructure and cryptographic innovation - Collaborative environment solving complex distributed systems challenges - Flexible working arrangements and professional growth opportunities 📩 To apply: Apply via the apply.workable.com/mlabs/j/3… 🔗 Original post: linkedin.com/posts/remote-pr… ⚠️ DYOR! I don’t verify every job. If someone asks to run files (even from GitHub) or ask for payment 🚩 likely a scam. ❗️ I'm not hiring myself! I just sharing fresh web3/crypto/blockchain roles DAILY for all levels! 💡 For Interns & juniors → t.me/crypto_vazima_english 💼 Mid/senior jobs → t.me/web3_jobs_crypto_vazima #ProductSecurity #SecurityEngineer #Web3 #Blockchain #Rust #Crypto #RemoteJobs #Hiring #Cybersecurity #DeFi #SmartContracts #WebSecurity #BlockchainSecurity #RemoteWork #TechJobs

📣🗳️SIPO DRepのCardano Budget 2026 Hydra投票内容を更新しました。 追加返信と再確認を踏まえ、MLabs: Encrypted Programmable Tokens with TFHE を Abstain から Yes に変更しました。 更新後の投票内容: Yes 31 Abstain 31 No 7 TFHEは、暗号化残高・暗号化送金能力をprogrammable tokensへ接続し、regulated stablecoin、institutional settlement、RWA、enterprise financeなど、公開残高が採用障壁となる領域にCardanoを対応させ得る戦略的公共財として評価しました。 一方で、Plutus costing、CIP / PR acceptance、early adopter、audit scope、MLabs横断capacityは引き続き確認ポイントです。 公式締切 2026/06/12 21:00 JST までは、追加回答、証拠、NCL制約、ポートフォリオ判断により、必要に応じて更新します。 sipo.tokyo/drep/budget-2026/

3. comecei a cnh do brasil (preciso terminar) 4. comecei curso de socia media do mlabs (preciso terminar) 5. tô prosseguindo minha leitura atual 6. comecei a pesquisar sobre cyberdeck mas não tenho dinheiro pra comprar uma raspberry pi 5 (mais de 1000 reais) pq estou DESEMPREGADA

Mlabs me fazendo querer contratar o youtube premium parabens! pROPAGANDA MALDITA

Cardano Builder DAO,20600000,YES STAG (Strategic Growth & Adoption Group),13000000,YES Tachys,8000000,YES Wormhole Cross-Chain Infrastructure,8000000,YES MLabs – Post Quantum Signatures,4010000,YES Wirex Payments Infrastructure,3960000,YES Mithril Protocol,3740000,YES MLabs – TrueInventory,2850000,YES Eryx ZK Capabilities,2500000,YES Daedalus Wallet Maintenance,2000000,YES Marlowe V2,1800000,YES Evolution SDK,1440000,YES MLabs – Better Arrays,1380000,YES MLabs – Encrypted Programmable Tokens (TFHE),1340000,YES Hardware Wallet Maintenance,1300000,YES MLabs – Grumplestiltskin 2,1140000,YES Cardano.nix,1140000,YES MLabs – Plutarch & Ply,1140000,YES MLabs – Covenant 2,1100000,YES Formal Verification Training,1000000,YES Nula,1000000,YES Oura,1000000,YES Rust Ogmios Client,800000,YES BloxBean JVM Toolchain,430000,YES UTxO RPC,420000,YES Cardano MCP,340000,YES Tx3,1400000,YES

MLabs, a long time Cardano development firm, has a number of proposals for the community to consider. hydra-voting.intersectmbo.or…

Anastasia Labs is one of the most established auditing firms in the Cardano ecosystem and has audited numerous successful protocols. That said, we don’t rely on a single audit. Prior to working with Anastasia Labs, we completed two independent audits with MLabs and VacuumLabs and addressed their findings. Multiple audits from separate firms provide a much stronger security assurance than any single audit alone.

MLabs: Open-Sourcing FeesaSwap as Live Fee Abstraction Infrastructure on Cardano No 🚫 Fee abstraction could be useful for Cardano, especially for users who arrive through stablecoins, bridged assets, game tokens, RWA tokens, or other native assets and do not already hold ADA. However, FeesaSwap already exists as a live product, and I am not convinced the treasury should pay to open-source and harden infrastructure that primarily benefits the proposer’s existing product. The proposal also has no treasury return clause, weak treasury favourability, and active ecosystem demand is not clearly proven. For that reason, I am voting no. cardano-drep-dashboard.learn…

Intersect Hydra Voting results below, which include rationales for each, if you find any of this to be in error please send me a dm referencing the proposal name and rationale provided along with your counterpoints as to why I should change my vote. YES: - Intersect: Governance Coordination and Technical Stewardship for the Cardano Ecosystem Rationale: Critical operational infrastructure. Supports technical stewardship, incident response, release coordination, repository management, and governance continuity. Reduces operational risk while improving ecosystem resilience. - The Marketing Powered Demand Engine for Cardano Rationale: Directly targets enterprise adoption and lead generation. Cardano's challenge is no longer technology but demand creation and commercial awareness. - Cardano Builder DAO Rationale: Proven funding framework with measurable KPIs tied to Vision 2030. Improves capital allocation while maintaining accountability. - Support Cardano 2030: A Techstars Strategy for Global Ecosystem Adoption & Utility Rationale: Strong enterprise and startup pipeline. Connects Cardano to institutional networks and global founders capable of creating sustainable economic activity. - Amplify Cardano: Ecosystem Accelerator Community Led Marketing & Events Fund Rationale: Addresses Cardano's historical weakness in ecosystem promotion and project visibility. Supports growth of homegrown success stories. - DeltaDeFi: Cardano Flagship Exchange Treasury Loan Rationale: Repayable treasury loan with perpetual revenue share. Strong alignment between treasury capital deployment and long-term ecosystem upside. - Cardano Enterprise Adoption: Production Ticketing Platform Rationale: Existing business, existing customers, existing revenue. Represents a real-world commercial deployment with treasury repayment provisions. - DeFi Ecosystem Connectivity via Ledger Wallet with Clear Signing Rationale: Improves security and usability for Ledger users while unlocking additional DeFi participation and liquidity. - Dano Finance: DeFi Kernel, American Options, and Orderbook SDK Rationale: Expands Cardano's DeFi primitives, liquidity coordination, composability, and financial infrastructure. - GOV.EXE by TxPipe & gf Consulting Group Rationale: Government execution transparency represents a meaningful enterprise and public-sector adoption opportunity. - Tx3 by TxPipe: Open API Layer for Cardano's dApp Protocols Rationale: Improves developer experience and lowers integration friction for Cardano applications. - Cardano Content Creator Consortium (C4) Rationale: Education and content remain critical weaknesses across the ecosystem. Supports awareness and onboarding. - Cardano Business Development Network Rationale: Enterprise adoption requires dedicated business development capacity. Directly aligned with commercial growth. - Hardware Wallet Maintenance 2026-2027 Rationale: Security infrastructure is foundational to ecosystem trust and user retention. - Research Validation & Market Pilots - Intersect CPC Rationale: Provides evidence-based validation before large-scale deployment and funding decisions. - Intersect Technical Steering Committee Support Rationale: Supports governance coordination and technical oversight during ecosystem growth. - MLabs Core Tool Maintenance & Enhancement: Plutarch and Ply Rationale: Maintains critical developer tooling used throughout the Cardano ecosystem. - Catalyze Africa: Building Scalable Projects from CATS 2026 Rationale: Expands Cardano adoption into emerging markets with long-term growth potential. - Nula: Cardano's Token Streaming Protocol Rationale: Improves payroll, vesting, recurring payments, and enterprise payment workflows. - Cardano Enterprise Activation Sandbox Rationale: Provides an environment for enterprise experimentation and onboarding. - Cardano Budget Committee: Budget Process Improvement and Treasury Transparency Rationale: Improves treasury oversight, reporting, and accountability. - Full Integration of CIP-113 with Clear Signing across Ledger Products Rationale: Strengthens security, usability, and tokenized asset adoption. - Oura by TxPipe: Maintaining Cardano's Event Pipeline Rationale: Critical infrastructure relied upon by developers and ecosystem tooling. - UTxO RPC by TxPipe: Maintaining Cardano's Integration Standard Rationale: Important middleware for application builders and enterprise integrations. - Dolos by TxPipe: Maintaining Cardano's Lightweight Data Node Rationale: Improves infrastructure accessibility and operational efficiency. - Pallas by TxPipe: Maintaining Cardano's Core Rust Libraries Rationale: Core development infrastructure with broad ecosystem impact. - Civics Committee Governance Expert Led Sustainable Education Program Rationale: Governance education remains necessary for long-term decentralization. - BloxBean Java/JVM Toolchain for Cardano Rationale: Expands developer access through enterprise-friendly tooling. - Cardano MCP by Lido Nation & 2 Lovelaces Rationale: Supports developer tooling and AI-enabled ecosystem growth. ABSTAIN: - Wormhole Cross Chain Infrastructure Rationale: Significant opportunity, but concerns remain around bridge architecture, security assumptions, and long-term dependency. Further evidence desired. - Innovation & Growth DAO Rationale: Concept has merit but requires stronger accountability and overlap controls before treasury commitment. - Mithril Protocol Rationale: Important infrastructure but additional clarity around execution, ownership, and funding scope was desired. - DeFi Rails & Deployment Pilot Program Rationale: Valuable objectives, but execution boundaries and overlap with other initiatives require further validation. NO: - Bridge Fund RWA Real Estate Fund Rationale: Treasury should not function as a real estate LP. Risk profile, capital lockup, and mandate concerns outweigh potential returns. - Project Janus Rationale: Large request with significant technical complexity. Concerns around scope, governance, and execution risk. - High Performance Partner Chain Factory using Ouroboros Tachys Rationale: Strong technology, but uncertain near-term economic impact relative to treasury cost. - STAG Security Threat Assessment Guard Rationale: Valuable work, but funding level and structure did not sufficiently justify the ask. - Cardano Startup Mainnet Runway Rationale: Enterprise onboarding is important, but concerns existed regarding cost efficiency and projected outcomes. - Cardano Tooling DAO Rationale: Potential overlap with other funding mechanisms and insufficient differentiation from existing structures. - Paid Open Source Model Continued Rationale: Open source support is important, but accountability and measurable outcomes remain concerns. - Indigo Innovation Proposal Rationale: Interesting direction, but scope expansion across RWA, BTCFi, privacy, and revenue sharing creates execution risk. - Wirex Payments Infrastructure Rationale: Commerce is important, but concerns around structure, ownership, and ecosystem alignment prevented support. - Eryx Zero Knowledge Capabilities Rationale: Strong technology, but near-term ecosystem demand and measurable adoption remain uncertain. - MLabs TrueInventory Rationale: Useful tooling, but lower priority compared to initiatives with clearer commercial and economic impact.