Marius Grigoras (@mvgrigoras) header
Marius Grigoras (@mvgrigoras) profile picture

Founder @xAudits @MGStaking Ex-Lead @NXP

web3 & AI
Joined February 2010
This project started in March 2021, in the apartment of a close friend, driven by passion, curiosity and a genuine belief in the early MultiversX ecosystem. I will never forget that afternoon. Thank you @StefanProcopiu 🫡 Another person who trusted and supported us from the early days was @_DrDelphi_ . Respect and appreciation for that support throughout the years, hats off! A new chapter is closing for me, 5+ years of building in web3, many emotions and memories. Once again, thank you all for your support, friendship and trust, it's been a beautiful journey. You have my respect! P.S.: As is mentioned below, staking operations are working as expected, no users action needed, transition was smooth.
Today, after more than 5 years of continuous operation, MGStaking has officially been transferred to a new owner. I’m deeply grateful to everyone who delegated with MGStaking and supported the journey along the way. What started as a validator became a real community around it. The handover was done carefully, with continuity and security in mind, and I genuinely believe the staking operation is in good hands of MrEGLD - wishing him all the best! Thank you for all the great moment together 🫡
7
3
44
3,271
Last 7 days to claim your BH airdrop before the project’s official closure. The remaining funds will be distributed to the most active participants and to long-term investors / holders who maintained their positions through 2025. We will review the active wallets (the ones from BHero infra) as well as those that held between 2022 and 2025. For those who believe they held for a long period and only sold in 2025 (before the airdrop announcement), you can drop an e-mail to [email protected] and we will review your wallet. For those who sold after the closure airdrop announcement (September 15th 2025), you can buy back from the market (or add the tokens back in your wallet) and still claim the airdrop using airdrop.bh.network (there is no issue - the snapshot remains intact). For those who still have assets in Metastaking (in xExchange.com) or in the LP and are only now withdrawing, you can contact us to the same [email protected] and we'll update the snapshot. We have replied to all emails sent so far to [email protected] 🙏 Thank you for all the support and believing in us!
This Post is from an account that no longer exists. Learn more
2
2
33
967
A good read. Once again, it’s proven there’s no such thing as 100% decentralization, we’re always dependent on APIs (RPCs, Oracles, etc) which in 99% of cases rely on classic web2 infra. If you control the oracles, you control the prices and the market. If you control the RPCs, you control the infrastructure.
The Oct 11 Crypto Crash — What Really Happened TL;DR: Roughly $60–90M of $USDe was dumped on Binance, along with $wBETH and $BNSOL, exploiting a pricing flaw that valued collateral using Binance’s own order-book data instead of external oracles. That localized depeg triggered $500M–$1B in forced liquidations, cascaded into $19B+ globally, and earned the attackers about $192M via $1.1B in BTC/ETH shorts opened on Hyperliquid hours earlier, but minutes before Trump tariff announcement. It wasn’t a USDe failure!! It was Binance’s design flaw, timed with macro panic (Trump’s tariffs) for cover. What looked like chaos was actually a coordinated exploitation of Binance’s internal pricing system, amplified by a macro shock and systemic leverage. 1️⃣ The Setup Binance’s Unified Account let traders use assets like USDe, wBETH, and BNSOL as collateral. Instead of oracle or redemption prices, Binance valued these using its own spot market - a major vulnerability. On Oct 6, Binance announced a fix to move to oracle-based pricing, but rollout wasn’t until Oct 14, leaving an 8-day window. 2️⃣ The Exploit During that window, sophisticated actors manipulated Binance’s order books, dumping ~$60–90M of USDe, driving it to $0.65 on Binance only (still ~$1 elsewhere). Because the Unified Account marked collateral to internal prices, this instantly wiped margin value and triggered $500M–$1B in forced liquidations. Then, Trump’s 100% China tariff headline hit, magnifying panic and liquidity stress. 3️⃣ The Profit Engine The same day, fresh wallets on Hyperliquid opened $1.1B in BTC/ETH shorts, funded by $110M USDC from Arbitrum-linked sources. As the Binance cascade unfolded, BTC and ETH cratered, those shorts netted $192M in profit before closing out at the bottom. Timing, precision, and funding paths all suggest coordination. 4️⃣ The Contagion Binance liquidations dumped BTC/ETH/ALTs into thin books. Other exchanges mirrored the collapse through cross-market bots. Market makers hedged across venues were forced to unwind everywhere. Result: $19B+ global liquidations, with many alts down 50–70% intraday, all triggered by <$100M of manipulated collateral. 5️⃣ Who’s at fault? Binance: design flaw + delay in oracle rollout = root cause. Exploiters: executed and timed the manipulation, profited via external shorts. Ethena (USDe): not at fault - protocol stayed 1:1 collateralized, redemptions normal, peg held everywhere else. 6️⃣ Aftermath Binance admitted “platform-related issues,” promised compensation for affected margin/futures/loan users, and rolled out minimum price floors + oracle integration. USDe remained operational, and the incident is now a case study in how exchange-side pricing errors can trigger system-wide liquidations. Bottom line: A ~$90M dump on Binance and a $1.1B leveraged short elsewhere sparked a $19B bloodbath. Not a stablecoin failure, but a masterclass in exploiting flawed collateral valuation during peak macro stress.
5
2
21
2,912
I’ve put all my energy, skills, time, and resources into BH Network over the past 4+ years. Tons of sleepless nights, countless hours spent with the team and the community, from code reviews to design, legal, marketing, business, incubations, meetups with builders, lawyers, accountants… all of it while desperately trying to make things work. Personally, what I’ll miss the most are the BHero launches, full of adrenaline, when the servers were barely holding up against the number of connections. It’s hard to put into words how those launches felt in the office, when we were literally all shaking with excitement, waiting to see the first transactions and whether the infrastructure would hold strong. BHero made history as a product. My biggest regret regarding the BHero story (excepting closing it) is that we didn’t manage to have a security asset on-chain through the Build21 project. That would have been their second stage, if the utility token launch had ended successfully. Unfortunately, they didn’t have enough support - neither from the MultiversX Foundation, nor from the community. That achievement would have truly mattered if it had happened, at least for the Romanian web3 ecosystem ..a page of history. We’ll see if at some point it will materialize… regardless of which L1 chain is chosen. I’ve learned an incredible amount, often the hard way, but that’s startup life - especially in web3. Although the most work went into topIQs (especially from a legal and technical perspective), once again life showed us that things rarely go as planned. A product can be the best technically, but if it’s too early for the market it’s targeting, all your efforts to drive revenue and adoption amount to nothing. Adoption cannot be forced; people need to feel they need that product, designed in that exact form. Entrepreneurship often says people don’t know what they want when it comes to high-tech devices. That may be true, but there’s always a dose of luck involved. Electric cars, for example, were not a success on the first try - but now they’ve taken off thanks to a mix of factors, and that’s no simple “coincidence.” What bothered me the most during these 4 and a half years wasn’t the work, the sleepless nights, or the lack of time with my family - it was the FUD and the completely unfounded toxic words. Those things hurt, no matter what you do. If you are an investor in a project whose price is not performing as expected, and the team is still there, working hard and doing everything humanly possible to make things work… maybe it wouldn’t hurt to think twice about the words you use. Even critical feedback is good, but we shouldn’t cross certain lines. I know web2 and web3 project leaders who have taken their own lives - I even had a corporate colleague who did it. We could have people’s lives on our conscience when we express ourselves that way. A huge thank you to Eddy and Petrica for trusting me as CEO of the project. They are truly special people - without them, I’d probably have ended up either crazy or in deep depression after this whole adventure. Eddy, thank you for having the courage to found and fully take ownership of a web3 company and for bringing us along on this journey—without you, this story would never have existed. I’ve learned a lot from you in SEO, marketing, and above all, what it means to be human in a world full of jackals. Petrica, you’re a super teammate - always ready to help, execute, and innovate. What more can I say, other than that I feel blessed to have met you and had you by my side. Thanks also to Alessandro, a man of values and integrity. Beyond the technical contribution in the past year, he also brought a great vibe to the team. Hats off—engineers with this kind of quality and morality are rare in web3. Even though in the past two years I haven’t been very close to the MultiversX team, I want to thank them too. In my opinion, there were mistakes regarding Metabonding and the forced parity vs eGLD, but looking back with a cooler head and putting myself in their shoes, it’s always easy to talk after the fact. I’d probably have done many similar things if I were in their place, trying to push the ecosystem and provide utility through different means. As I wrote in the announcement, we will not touch the liquidity in the LP (DEX). It’s entirely up to you whether you want to keep some or all of your tokens. The value of the airdrop is higher than the market value (around 5x). Of course, there is not a financial advice, but tat this point there’s no point in selling on the DEX (as I see some already did), it’s better to just claim the airdrop using airdrop.bh.network. If you’ve already sold, no problem - a snapshot was taken before the announcement. You can buy again from the market with the same amount and still claim the airdrop (exactly as it was in the snapshot). The dApp correctly shows the minimum between the snapshot and the wallet balance. For BHAgents, no snapshot was made (since it’s a much smaller and illiquid market). It’s enough just to have the NFT in your wallet. The airdrop value for BHAgents is $5 per NFT, about 2x the market value at the time of the announcement. Sincere thanks from the bottom of our hearts to all our supporters, investors, community, and everyone who believed in us. I’m truly sorry we didn’t achieve better results and that we’re stopping here, but unfortunately this is all we could do. There’s a limit we personally reached some time ago, and it’s not about financial resources—it’s about mental health, and about feeling that what you do truly has a positive impact for investors.
This Post is from an account that no longer exists. Learn more
35
10
156
11,391
Big congrats @ostanescu_, truly deserved 🫡
Excited to announce @ostanescu_ as an ambassador for @0xbasedNL As a co-organiser of ETHBucharest and a dutch resident we are so excited to be working with him in bringing Europe onchain.
16
1,358
For a web3 token, liquidity and trading volumes are absolutely essential because without them the token is just "there", but not really part of a real economy. Think of it like BVB (Bucharest Stock Exchange) vs Nasdaq. Even if you list a very good company on BVB, it won’t get the same attention, trading activity or capital flows as it would on Nasdaq. Why? Because Nasdaq has high liquidity, lots of traders and constant market activity. Ofc, is a chicken-egg problem and is much more difficult to list on Nasdaq vs BVB. Good projects naturally aim for high-quality, liquid markets, not just technically correct but with real activity. When a Web3 project creates a token, it’s not just for fun, but they’re trying to build an on-chain economy. That means people need to trade it, use it, and interact with it. For this, you need: a) Liquidity (real & on-chain - traders can enter and exit easily) b) Volumes (trading activity that shows the market is alive) c) Traders and activity (so the price is not stuck or easily manipulated) d) Native stablecoins and pairs (so it can connect to the broader economy - not bridges or other risky systems) No matter how much adoption or utility a project claims to have, tokens (as any other assets) are pre-speculative assets. The market is constantly trying to predict what the future of the project will be worth. For that speculation to even happen, there must be liquidity and activity - otherwise, no one can buy in or sell out. Let's discuss about Nvidia for example. It's not "really worth" $4.43 trillion in assets, but rather that this is simply ONLY the market valuation. That number comes from market capitalization => the current stock price × the total number of shares. It doesn’t mean Nvidia actually holds that much in cash or tangible assets. If tomorrow Nvidia sold all its factories, buildings, equipment, and added the cash from its treasury, the book value would be much lower than $4.43 trillion. The difference comes from the fact that the market pays a price per share that reflects: 1) Future expectations (how much Nvidia will grow) 2) Speculation (investors betting it will keep dominating AI and semiconductors) 3) Brand strength and market position (near-monopoly in AI GPUs) 4) Long-term profit potential So, market capitalization is more of a forward-looking market expectation, not a pile of cash the company already has. Turning back to web3 on-chain economy, a big part of success is actually about absorbing liquidity from the market of the chain you’re building on. If your chain has low liquidity, your token will struggle or die. If it has a vibrant, liquid market, your project can grow alongside it. Ofc, this doesn’t guarantee success, but it certainly helps, and major projects are looking for such a growth-friendly environment. It's simple math. Imagine a project with 1M$ daily volume. Uniswap, Aerodrome (and most of the top DEXs) are giving those 0.3% trading fees back to the project, increasing the liquidity (if using V2) or just claimable (if using V3). In one year, this is ~1.1M$ only from the volumes. For the first years of a project, this can make the difference between death, survival or ..success. In any business is about economy, we like it or not. Even more so for publicly listed projects.
6
1
40
2,490
Hey @nodejs devs! Meet @ratio1ai's R1FS & CStore: a decentralized edge toolkit that shards your data assets across many nodes and syncs it in real time. No single point of failure, ultra-redundant, low-latency, fully encrypted. Imagine the next "Google Drive" app with these properties: sharded storage, instant state sync & rock-solid uptime. More cool stuff incoming in the next period.
Ratio1 just leveled up! We’ve expanded beyond Python - NodeJS devs can now build with R1FS + CStore for decentralized storage & state mgmt. 3 roadmap items ✅ 1) Release of R1FS v1 (distributed file storage) with migration from v0.8. R1FS provides encrypted, sharded, secure, decentralized data storage across the network, preventing any single point of failure. 2) Release of R1FS v1 Local Endpoint v1. R1FS Local Endpoint provides non-native containerized apps with access to the whole decentralized R1FS storage - legacy apps can now access any decentralized stored data with proper credentials. 3) Release of CSTORE Local Endpoint v1 and migration from v0.7. CSTORE Local Endpoint provides non-native containerized apps with access to the decentralized in-memory database - legacy apps can now cooperate across decentralized compute continuum. Read blog below 👇
2
19
1,134
Real decentralized oracles doing their job - PoA consensus & PoAI fully traceable on @base. #Ratio1 🫡
1. Proof-of-AI uses automatic on-chain consensus 2. Automatic consensus requires oracle nodes to execute "robotic" on-chain transactions 3. Thus oracles need the get some $ETH in their own "robotic" wallets to automate these steps... ... Seems oracles are beginning to prepare... 😎
1
1
15
786
Marius Grigoras retweeted
Demo Today 📢 Hey Ratio1 community! Just a quick reminder - our live demo is happening today on Discord at: 🕢 19:30 Romanian time 🕕 18:30 CEST 🇺🇸 12:30 PM EDT (U.S. Eastern Time) We’ll be showcasing ChainStore and R1FS in action through a real-world app - a decentralized, encrypted Dropbox-style platform built with Next.js. 👥 Everyone is welcome - whether you’re curious, building on Ratio1, or just exploring decentralized infrastructure. 💬 We’ll also have a Q&A session after the demo, so feel free to bring your questions! 📍Join us in our official Discord: discord.gg/ratio1ai Looking forward to seeing you there!
7
26
1,660
Replying to @CGTNOfficial
You’re absolutely right - open source, data ownership, and encrypted (especially homomorphic) AI processing are essential for empowering users and ensuring privacy. The Ratio1 Protocol stands as a strong implementation of these principles. What Ratio1 Brings to the Table: 1. Open‑Source, Transparent Stack 2. Data Ownership & Private Execution 3. Decentralized Meta‑OS with Edge Compute & Blockchain 4. Economics That Reward Openness & Contribution How it Supports Your Philosophy: a. Open source = open control: Everything from models to SDKs to node software is visible and free. b. Users own their data and outputs: Homomorphic processing + federated learning ensures raw data never leaves user control. c. AI as infrastructure, not as lock‑in: You don’t send your data to a centralized AI; you deploy AI tasks to your devices. d. Economic alignment: Contributors are rewarded fairly; you’re not paying opaque fees or locked in to proprietary platforms.
3
8
2
27
2,180
Blockchain programming is the new low level embedded programming? Today I was thinking that young engineers have a good chance via blockchain programming to "know" how embedded programming really feels. What it means to write reliable, secure, and ultra‑optimal code in both spatial/memory and temporal complexity, because blockchain programming forces you to write embedded‑style code, where every byte, cycle, and cryptographic call costs real value. So security, efficiency, and absolute determinism aren’t optional, they’re mandatory, and the same rules apply for writing smart contracts: no space for mistakes. So… you didn’t have the chance to write firmware for a SoC? Writing a smart contract is close enough 🫡
2
21
705
PoAI v1 & Deeploy app work in progress with the #Ratio1 engineering team. From open source protocol to product - performance, privacy & real-world compute.
2
4
4
61
5,123
This week we had a meeting with @RosuGrigore together with @ratio1ai engineering team. This guy is brilliant and for sure has all the skills needed to transform/optimize "web3" as we know it now. Follow @pisquared and their progress with FastSet Parallel Claim Settlement. They deserve it.
3
9
1
72
2,789
🟦
Ratio1 building on @base - a thread 🧵
2
3
24
1,059
Sometimes I feel the same. Again ..in business is not about the best engine, but a good enough car on the right highway. Most of the product don't need a L1 or not even a L2. Most alt-L1s will need become L2s if they want to survive in any way or just to remain alive and secured enough. Or they just will be irelevant (similar with closing the doors). Not only because they failed as adoption and business, but because they will never scale economically. PoS security = capital. Without token value, liquidity, or native stablecoins, your chain isn't secure, it's subsidized from inflation forming a death spiral. Why would serious capital build on insecure ground? Or just why reinventing the wheel? At @ratio1ai we have 2 protocols: a) web3 systems SCs for GND, MDN, ND, plus encoding licensing logic, payment locks, oracle‑verified node availability, and reward conditions b) Ratio1 Meta‑OS + Web2 Oracles with On‑Chain Traceability We could build our own L1 or L2, we’ll have enough demand & TX volumes (from IoT devices, oracles, servers, SDKs, CSPs). But why reinvent the wheel and de-focus from building our real product? Just to look clever and ride the “web3 ordinary” hype train? “Oh, we built a new L1/L2!” Who cares. There are enough decent chains out there. What matters is real business, real users, distribution. Not vanity infrastructure. We’d rather plug into resilient, battle-tested infra as @base than burn time and capital on vanity chains. Ratio1 meta-os oracles are at most an "L3" on top of @ethereum but running directly on @base.
Unironically, I think most alt-L1s will become L2s @Celo showed the playbook: – Halved inflation from 2% to 1% – Reduced block times from 5s to 1s – Eliminated 300k+ lines of legacy code – Fully integrated into Ethereum’s ecosystem, the largest dev community in crypto – Carbon emission's cut in half (if you're into that) It’s just a better model
6
5
1
48
4,491
100% agree. Is not about "let's build more" and "the best product in the world". Without distribution, you don't exist.
Your job as a startup founder is to learn sales, branding, marketing, and distribution because its not just about the product.
5
1
24
1,809
Marius Grigoras retweeted
A weekend blog & thread. 1/ Most startups fail not because they can’t build - but because they build the wrong thing. Inspired by @mjskok’s timeless lecture, here’s how we designed Ratio1, a decentralized AI meta-OS, to solve real developer problems. (🧵 A 6-point framework every builder should use)
2
9
3
32
2,566
[5/8] Developers don’t need to: a) write low-level Telegram polling logic b) set up external servers or cron jobs c) manage blockchain RPC calls manually All of these are handled by Ratio1’s SDK in a few lines of Python.
1
5
299
[7/8] In simple words: ➡️ Anyone can build a bot or app on Ratio1 without worrying about backend infrastructure ➡️ You focus on your logic. Ratio1 handles deployment, horizontal scaling, and connectivity on a trustless network
1
5
258
[8/8] Imagine building: a) Edge device health monitors b) Industrial sensor data collectors c) Automated alerts for smart homes d) Management trackers for IoT-connected vehicles All using the same simple built-in design. That’s the practical power of Ratio1 for developers.
6
247