
Ogga Balooga #EGLDsqueeze
HT. baloo1989
Joined February 2020
- Tweets81.6K
- Following1.1K
- Followers1.5K
- Likes317K
Baloo.egld✖️ retweeted
🍕 PizzaLab: Your pizza is ready! That will be 12 EUR.
⚡ @MultiversX: Sure! I'll send the payment right away.
🍕 Pizzaiolo: How long will it take?
⚡ @MultiversX: Less than 2 minutes, right?
🍕 Pizzaiolo: No, that's how long it takes to bake the pizza.
⚡
Baloo.egld✖️ retweeted
WASMageddon on MvX.
The attack would have been tricky to pull off, and its success was uncertain. It relied on guessing memory offsets that match most validators' machines. Of course, even unsuccessful attempts could have poisoned the blockchain history with effects well outside of the blockchain design, and caused damage difficult to undo. Although stating again with a pretty low probability.
like rerunning the same contracts over small internal networks did not succeed, but we couldn't risk a chance of the unknown.
stupidly: some of the AI models blatantly refused to even analyse the deployed contracts, they knew it was an exploit, so they did not want to give answers.
THIS IS SO STUPID. when as a developer you cannot use frontier models to actually fix issues / debug / find why there is an attack or what the attack tried to do.
Your AI agent can now trade on OneDex. By itself.
OneDex MCP is live on #multiversx mainnet.
One endpoint. No API key. No extra fee.
aggregator.onedex.app/ai/mcp
▸ Autonomous agents (video)
1. Create a dedicated wallet for your agent. Small budget, separate from your treasury.
2. Store its key in GitHub Secrets or your server env. Never in code, never in an AI chat.
3. Set your rules in code: max per trade, allowed tokens, max slippage, daily budget.
4. Give the order: "Buy ONE with 0.3 EGLD".
5. The agent does the rest: quote → build → check → simulate → sign locally → send → confirm.
OneDex finds the route and prepares the transaction. Your agent signs. We never see keys. minOut enforced on-chain.
▸ Use it in Claude (2 minutes)
1. Open claude.ai → Settings → Connectors
2. Tap "Add custom connector"
3. Name: OneDex
URL: aggregator.onedex.app/ai/mcp
Authentication: No sign-in
4. Tap Add → Connect. 6 tools appear.
5. Keep "Needs approval": you approve every step.
6. New chat, ask:
"Using OneDex: swap 0.3 EGLD to ONE for my address erd1…, simulate it and give me the signingLink."
7. Open the link, check receiver + amount in your wallet, sign.
Only give the AI your public address (erd1…). Never your 24 words, key or password.
▸ Cursor, Claude Code, ChatGPT or any MCP client
Add the same URL as a remote MCP server. Exact configs in the docs.
Docs, 6 tools, TypeScript example:
onedex.app/agents
Baloo.egld✖️ retweeted
agents can now trade on MultiversX without anyone writing a bot.
OneDex just shipped an MCP server on mainnet. one endpoint, no API key, no extra fee, 6 tools.
the design is the part I'd copy:
- OneDex finds the route and builds the transaction
- your agent or your wallet signs locally, they never see a key
- minOut is enforced on-chain, so a bad quote fails instead of filling
two ways to use it:
1. in Claude, ChatGPT, Cursor or Claude Code: add it as a remote MCP connector, no sign-in. ask for a swap with your erd1 address. it simulates and gives you a signing link. you check receiver and amount in your wallet and sign. keep "needs approval" on.
2. fully autonomous: a dedicated agent wallet with a small budget, the key in your server env, and rules in code: max per trade, allowed tokens, max slippage, daily budget. the agent runs quote → build → simulate → sign → send → confirm.
my takes:
- the rules in code matter more than the model. the model proposes, the limits decide.
- give the agent a wallet you can afford to lose. never your treasury, never your 24 words in a chat.
- simulate before every signature. it costs nothing.
- next step I'd want: those limits enforced on the account itself, not only in the agent's code. [ROBERT: confirm you want to point at Guardians / multisig here, or cut]
this is what "agents on MultiversX" looks like when it's real: a tool any agent can call, and a chain that checks the result.
what would you let an agent do first with it?
Your AI agent can now trade on OneDex. By itself.
OneDex MCP is live on #multiversx mainnet.
One endpoint. No API key. No extra fee.
aggregator.onedex.app/ai/mcp
▸ Autonomous agents (video)
1. Create a dedicated wallet for your agent. Small budget, separate from your treasury.
2. Store its key in GitHub Secrets or your server env. Never in code, never in an AI chat.
3. Set your rules in code: max per trade, allowed tokens, max slippage, daily budget.
4. Give the order: "Buy ONE with 0.3 EGLD".
5. The agent does the rest: quote → build → check → simulate → sign locally → send → confirm.
OneDex finds the route and prepares the transaction. Your agent signs. We never see keys. minOut enforced on-chain.
▸ Use it in Claude (2 minutes)
1. Open claude.ai → Settings → Connectors
2. Tap "Add custom connector"
3. Name: OneDex
URL: aggregator.onedex.app/ai/mcp
Authentication: No sign-in
4. Tap Add → Connect. 6 tools appear.
5. Keep "Needs approval": you approve every step.
6. New chat, ask:
"Using OneDex: swap 0.3 EGLD to ONE for my address erd1…, simulate it and give me the signingLink."
7. Open the link, check receiver + amount in your wallet, sign.
Only give the AI your public address (erd1…). Never your 24 words, key or password.
▸ Cursor, Claude Code, ChatGPT or any MCP client
Add the same URL as a remote MCP server. Exact configs in the docs.
Docs, 6 tools, TypeScript example:
onedex.app/agents
Baloo.egld✖️ retweeted
1/9 @MultiversX and @BlockRunAI have signed a letter of intent to connect AI agent payments with #MultiversX’s financial infrastructure.
The goal is to explore how agents could use services and take part in economic activity on the network. 🚀
Baloo.egld✖️ retweeted
🤑 Okay, @MultiversX: $1,055 in monthly revenue as of yesterday. Best month ever.
📊 chainspect.app/chain/multive…
Baloo.egld✖️ retweeted
JPMorgan and DBS just linked their tokenized deposit networks. approved clients can move dollars between Singapore and the US at any hour, weekends included. both run on permissioned chains.
so how would I build a tokenized deposit on MultiversX, a public chain, with the controls a bank needs?
most of it is already in the token standard. no ERC20-style contract for the token itself.
ESDT tokens are native. you issue one through the ESDT system contract on the metachain and set properties at issuance:
- canFreeze: freeze one account's balance, nothing in or out
- canWipe: wipe the balance of a frozen account
- canPause: stop all transfers of the token, mint and burn still work
- canAddSpecialRoles: hand out mint and burn roles
then the one that matters for a deposit: ESDTTransferRole.
once at least one address has it, free transfers between arbitrary addresses stop. addresses with the role can send anywhere, and anyone can send to them.
so the design:
1. the bank's contract holds mint, burn and the transfer role
2. a client payment goes client → bank contract → client
3. in between, the contract checks the whitelist, the limits and anything else the bank needs. the token can't route around it
what a public chain adds: settlement at any hour, and a ledger an auditor or a second bank can read without asking for an export.
what it doesn't give you today: privacy. every balance is visible, and for a corporate treasury that's a blocker.
and the money behind the token is still a deposit at the bank. the chain moves the record, it doesn't replace the balance sheet.
question for builders: would you keep the whitelist in token roles, or in the contract?
Baloo.egld✖️ retweeted
Solana dropped the "mainnet beta" label today, after more than six years, and adopted Solana 1.0 as a shared version number for its network rules.
the label is the headline. the version number is the useful part.
with Agave and Firedancer both running the network, each with its own release numbers, operators need one number that says which rules their software supports.
our mainnet went live on 30 July 2020.
today one client runs the network, so a node release and the protocol rules mostly move together. the day a second client exists, that stops being true, and the rules need a version of their own.
Baloo.egld✖️ retweeted
While most chains are busy farming hype, $EGLD is already preparing for quantum computers… post-quantum account migration research, reward simulation via interactors, paginated delegation data and sui bridge providers moved to gRPC. All in one week.
Honestly i respect it. Builders shipping in silence when nobody's watching is usually how the next cycle starts… but the market doesn't care about code until it suddenly does. Too early or just ignored for you?
Baloo.egld✖️ retweeted
why did Friday's xExchange fix have to load a whole list from storage in the first place?
because of how the list is stored:
SingleValueMapper<ManagedVec<UnstakePair>>
one storage key per user, holding the entire encoded list. every get() reads all of it. every set() writes all of it back.
the other shapes the Rust framework gives you:
- VecMapper: one key per item plus a length key. reading item i is one small read, walking the whole list is N reads
- QueueMapper: a linked list in storage, push and pop at either end without touching the rest
which one is right depends on how your endpoints touch the data:
- you always need the whole list and it stays small → one value, fewer storage calls, simpler code
- you touch one entry at a time, or the list can grow → per-item keys
this contract is the first case, and it is bounded on purpose: unbond processes at most 20 entries per call (MAX_CLAIM_UNLOCKED_TOKENS). a loop over user-controlled data with no cap is the first thing I look for in a review.
and if someone wants an easy first PR: depositUserTokens in the same contract still calls update() and then get() on the same mapper, only to emit the event. same fix as Friday.
Baloo.egld✖️ retweeted
Crowdfunding platforms can lose business when investors’ payments arrive too late:
- An investor chooses a project and sends a bank transfer.
- Before the money arrives, the campaign closes or reaches its funding target.
60% of European consumers surveyed by Signicat in 2026 reported abandoning an online financial application in the previous year. Lengthy processes and excessive information requests were among the reasons.
Stock.estate uses Finance Computer to accept cards, Apple Pay and Google Pay on its website and in its app. Investors can pay directly when they choose a campaign, helping them complete their investment before funding closes.
Embed finance computer services in your platform.
Baloo.egld✖️ retweeted
Weekly Development Report as of Nov 15, 2026
#multiversxtech 👇🛠️
Baloo.egld✖️ retweeted
two MultiversX wallet provider PRs merged this week, and almost nothing in them is a new feature.
WalletConnect provider v6.2.0:
- overlapping init() calls now wait for the same initialization
- the provider stays "initialized" while the QR is on screen
web wallet iframe provider:
- concurrent calls share one iframe
- the iframe is removed on logout, even when the logout request fails
each one is two things happening at once, or one failing halfway.
building a dApp login? test those first: double-click connect, refresh mid-QR, logout with the network off.
Baloo.egld✖️ retweeted
$EGLD MultiversX last 24h: volume a bit softer, some whale selling and large orders mostly on the sell side.
Price still holding around $2.62 (+3.5%).
Just a quiet day or something bigger brewing? 👀
MultiversX ( $EGLD ) Market Update
Same score as 3 days ago: 3.1/10. Still stuck.
Volume is up +16% to $3M, but activity drops -7.3% and price slips to $3.00 (-4.1%).
101.2K txs at 1.17 TPS in 24h, the network is quiet.
Money is coming back, but users aren't. Bounce or bull trap? 📉👇
🔥 Fire Pit Season 1 has erupted!
101,517 ONE bought on OneDex. 188 tickets across 14 wallets.
🏆 Winner: erd1pkdgxk8kmwu8qz6t06y2cy66v3nr5newe4p4emztjeyhn80elyhqa9a92t
5 tickets (#97–#101). Prize: 17.42 EGLD
🎲 How it was picked (verify it yourself):
1️⃣ At eruption we announced a future MultiversX block: shard 1, block #40,599,043
2️⃣ Its randSeed didn't exist yet. Nobody could know or pick it, us included.
3️⃣ randSeed = 2a20b4fe…13fcc00
4️⃣ sha256(randSeed) mod 188 = ticket #98
5️⃣ Ticket #98 belongs to wallet erd1pkdg…a92t (tickets #97–#101)
🔎 Block: explorer.multiversx.com/bloc…
🔎 Recompute it in your browser: swap.onedex.app/firepit/veri…
Congrats to the winner. Season 2 coming soon 🔥
We started with a dream.
Some called it crazy. Some walked away.
We stayed.
Today $ONE gets a new face.
New logo. New UI. New concept.
Built by the community. Owned by no one. Owned by everyone.
The best tools are coming next.
Believe. 🔥
swap.onedex.app
Baloo.egld✖️ retweeted
It’s great to see OneDex step into a new chapter. The new look is 🔥 and it’s good to see the team keep building through the tough times. We’ve been following the journey and are looking forward to what comes next. 💙
We started with a dream.
Some called it crazy. Some walked away.
We stayed.
Today $ONE gets a new face.
New logo. New UI. New concept.
Built by the community. Owned by no one. Owned by everyone.
The best tools are coming next.
Believe. 🔥
swap.onedex.app
Baloo.egld✖️ retweeted
It took me a while to find that fire again. But here we are. 🔥
The crypto market isn’t exactly on our side right now. But guess what? It wasn’t when I launched OneDex either.
I’ve always believed that hard work, persistence, energy, and passion eventually pay off.
We’re not here for the easy days. We’re here to build something that lasts.
The fire is back. And we’re just getting started.
Believe. 🚀
🔥 THE FIRE PIT IS LIT.
Season 1 is live on OneDex.
Every ONE you buy on OneDex feeds the fire. When it erupts, one holder takes the prize.
🏆 Prize: 17.42 EGLD ($50, fixed at season start)
🎟 How to get tickets
• Buy ONE on the OneDex Swap page: swap.onedex.app
• 1 ticket for every 1 EGLD worth of ONE you buy
• Small buys add up. Your buys are summed per wallet across the whole season: 10 buys of 0.1 EGLD = 1 ticket.
• Max 100 tickets per wallet
• Any token can be used to buy ONE. What counts is the EGLD value of the ONE you receive.
💎 Hold to keep your tickets
• Keep the ONE you bought in your wallet until the eruption.
• If ONE leaves your wallet (sold or sent), your tickets go down.
• Only ONE bought during the season counts. ONE you already held before doesn't add tickets.
🌋 The eruption
• The pit erupts when 100,000 ONE has been bought and held through OneDex.
• Track the progress live on the Fire Pit page (🔥 icon in the header).
🎲 How the winner is picked (provably fair)
• At the eruption we announce a future MultiversX block, about 10 minutes ahead. Nobody, us included, can know its random seed in advance.
• Winning ticket = sha256(that block's randSeed) mod total tickets. Tickets are numbered in buy order.
• Block, seed, ticket list and payout transaction are all public. Anyone can verify.
ℹ️ Good to know
• 1 winner per season. The prize is sent in EGLD to the winning wallet.
• OneDex team wallets are excluded.
• No sign-up needed. Just buy and hold.
Feed the fire. 🔥
swap.onedex.app























