Baloo.egld✖️ (@necessities1989) header
Baloo.egld✖️ (@necessities1989) profile picture

Ogga Balooga #EGLDsqueeze

HT. baloo1989
Joined February 2020
Photo by Baloo.egld✖️ (@necessities1989)Photo by Baloo.egld✖️ (@necessities1989)Photo by Baloo.egld✖️ (@necessities1989)Photo by Baloo.egld✖️ (@necessities1989)Photo by Baloo.egld✖️ (@necessities1989)Photo by Baloo.egld✖️ (@necessities1989)Photo by Baloo.egld✖️ (@necessities1989)Photo by Baloo.egld✖️ (@necessities1989)Photo by Baloo.egld✖️ (@necessities1989)Photo by Baloo.egld✖️ (@necessities1989)
Baloo.egld✖️ retweeted
🛡️ @MultiversX: 1,000+ validators every day for 346 days. Over 11 months without dipping below four digits. 📊 chainspect.app/chain/multive…
2
12
1
60
1,361
Baloo.egld✖️ retweeted
Hashi mainnet is live🔥 Very proud of this one. A big, big day for #Sui
Hashi mainnet is live. Bitcoin holders can now use their $BTC as collateral to borrow stablecoins and access managed vaults on Sui. 20+ partners are expanding access across custody, trading, and DeFi. Here’s what’s live and what’s next: 🧵
64
102
6
690
25,247
Baloo.egld✖️ retweeted
Great seeing @EAPESCLUB expand right inside xPortal's Discover. Dive in! 🦍
YOOOO TRIBE!!! EAPES pulled up in @xPortalApp! Our #Solana dApp is NOW LIVE in xPortal's Explorer! Born on #MultiversX. Expanding on Solana. GTS Season 1, My Collections, Launchpad, Marketplace & Draven. ONE TRIBE. BIGGER JUNGLE. #EAPES AMAZING FRIDAY and a KICKASS WEEKEND!!
7
18
1
81
9,051
Baloo.egld✖️ retweeted
Manual processes are the biggest obstacle to operational efficiency for 4 out of 5 of asset-servicing firms surveyed by @Fenergo. For investment platform teams, that raises a practical question: how much manual work does each card deposit create? 🧵👇 (1/4)
1
23
73
1,293
Interesting timing 🤔 @FinanceCompute is expanding its one-integration financial infrastructure across all 30 EEA countries, while @XMoney has just launched international bank transfers to 27 countries. ⬇️
You can now send money internationally with X Money, directly from 𝕏 X Money now supports international bank transfers to 27 countries, with recipients receiving funds in their local currency Supported countries: 🇦🇺 Australia 🇦🇹 Austria 🇧🇪 Belgium 🇨🇦 Canada 🇨🇾 Cyprus 🇪🇪 Estonia 🇫🇮 Finland 🇫🇷 France 🇩🇪 Germany 🇬🇷 Greece 🇭🇰 Hong Kong 🇮🇳 India 🇮🇪 Ireland 🇮🇹 Italy 🇱🇹 Lithuania 🇱🇺 Luxembourg 🇲🇾 Malaysia 🇲🇽 Mexico 🇳🇱 Netherlands 🇳🇴 Norway 🇵🇭 Philippines 🇵🇹 Portugal 🇸🇬 Singapore 🇸🇮 Slovenia 🇪🇸 Spain 🇸🇪 Sweden 🇬🇧 United Kingdom And everything happens directly inside 𝕏 Here's how it works: 1. Open the Money tab and select Send Money 2. Tap Send a wire and choose the destination country 3. Enter the recipient's name, address and bank details 4. Enter the amount, review the exchange rate and confirm Depending on the destination, you'll need an IBAN, SWIFT/BIC, account number or local banking code And the fees are surprisingly straightforward: • $1.65 + 0.65% per international transfer • Same fee across all subscription plans • No separate currency conversion fee from X Money • Most transfers arrive within 1–2 business days • Up to $15,000 per transaction • Up to $15,000 sent per day • 30-minute cancellation window You'll see the converted recipient amount before confirming, although intermediary or receiving banks may charge additional fees And here's another useful protection If a transfer is returned because of incorrect bank details, X Money refunds the amount sent, even if exchange rates have changed. The original transfer fee is not refunded International wires currently support personal bank accounts in these 27 countries, with the feature still in beta for eligible U.S. X Money users No separate money-transfer app required Just open 𝕏, choose the recipient, and send money directly to their bank account Another major step toward making 𝕏 the everything app
4
7
52
1,589
Baloo.egld✖️ retweeted
the xExchange API merged a cleanup PR this morning. 95 files, no new feature. the kind of work every dApp backend needs and nobody tweets about. the reasoning is 4 lines: - internal errors reached clients verbatim - Prometheus labels and the guest cache kept growing - logs couldn't be parsed - no tests at the edge what changed: 1. every request gets an id. a valid incoming x-request-id is echoed back, otherwise one is generated. it goes on the response and on every log line. a user sends you a failed call, you search one string. 2. clients get "Internal server error". the real error goes to the log. a stack trace in a response is a free map of your backend. 3. request id, helmet and CORS now run before body parsing, so even a 413 or a 400 carries those headers. 4. the guest cache only takes bodies of 16 KB or less that have a query, keyed by SHA-256. a cache with no cap is a slow memory leak. 5. metric labels are bounded. query = the sorted root field names, origin = "none" or "other" when missing or invalid. raw user input as a label means a new time series per request. 6. a small edge test harness that needs only Redis and runs in CI. 31 edge tests, 659 overall. none of this touches the contracts. but when something breaks at 3 AM, this decides if you find it in 5 minutes or 5 hours. if you run an API in front of your contracts: which of these 6 do you have today?
5
8
63
2,076
Baloo.egld✖️ retweeted
xExchange merged a small PR today that every contract team should copy: reproducible release builds. the problem: you read the source on GitHub, but what runs on chain is a .wasm file. how do you know one came from the other? what mx-exchange-sc #1081 does: - release builds run inside a pinned Docker image, sdk-rust-contract-builder v12.0.0 - the reproducible-build workflow from mx-sc-actions is pinned to one commit - it runs by hand from the release tag, for one contract or all of them - the release notes get the image and the codehash of each .wasm appended their test release for token-unstake: the wasm built in CI was identical to a local build. same codehash. that line is the point. same source + same pinned toolchain = same bytes. anyone can rebuild it, hash it, and compare with the code hash of the deployed contract. two details I like: - the CI action is pinned to a commit, not a branch. a moving CI dependency is a supply-chain hole - the build starts from the tag, by hand. a release is a decision, not a side effect of clicking publish if you ship contracts on MultiversX: could you rebuild your deployed wasm byte for byte today?
3
8
49
1,555
Baloo.egld✖️ retweeted
Embedded finance solves different problems across industries. - B2B software & SaaS: put business accounts, cards and payment workflows inside the tools companies already use. - Retail & ecommerce: let customers pay within the shopping journey. - Transport & logistics: connect driver payouts and fuel cards to fleet operations. - Healthcare: bring payments into patient booking and billing. - Telecoms: integrate wallets into mobile services. - Education: connect tuition payments to student portals. For B2B software platforms, this can mean helping customers collect payments, manage expenses or pay suppliers without switching tools. Embedding financial services can give users more reasons to stay, open new revenue streams and make everyday tasks easier to complete within your platform. When did you start considering embedded financial services for your platform?
2
35
1
108
1,317
Baloo.egld✖️ retweeted
Bear markets don't build projects,people do. To everyone still here, providing liquidity, reporting bugs, believing: you are OneDex. We keep building. Together. ❤️
Your LP can work harder. Add liquidity on OneDex, stake the LP in a farm, earn ONE. 🔥 ONE/WEGLD: 15.1% APR
 💧 USDC/WEGLD: 6.6% APR swap.onedex.app/farms APR is variable and changes with volume and TVL.
3
20
2
73
994
Baloo.egld✖️ retweeted
Platforms don’t need “a card”. They need the right card for the job: 💼 Control team spend 🎁 Turn rewards into branded cards 📱 Issue virtual cards in-app and add them to Apple Pay or Google Pay One API. Physical or virtual. Built for Europe. xmoney.com/products/issuing
6
20
1
89
4,388
Baloo.egld✖️ retweeted
open-weight models closed the quality gap. the new bottleneck is serving: cost per token, latency under load, and where your data is processed. Alpha has joined NVIDIA Inception to scale that layer. alpha.sh/blog/alpha-joins-nv…
9
33
2
115
6,862
Baloo.egld✖️ retweeted
🪙 @FinanceCompute integrates @MultiversX (~600 ms settlement), @xMoney_com (payments and licensing), and @xPortalApp (wallet, balances, and rewards) into a unified financial infrastructure, accessible via a single API. financecomputer.com/
1
6
1
39
1,647
Baloo.egld✖️ retweeted
XMN, (xMoney) on Xportal shot up 35% this morning, now I Know why. 🤔🙃😎🌄
🪙 @FinanceCompute integrates @MultiversX (~600 ms settlement), @xMoney_com (payments and licensing), and @xPortalApp (wallet, balances, and rewards) into a unified financial infrastructure, accessible via a single API. financecomputer.com/
3
23
1,100
Baloo.egld✖️ retweeted
New on OneDex: Claim all -Dashbord ✨ Farms, Staking, Boost, X Stake, NFT staking. All your rewards in one place, claimed with one tap. Big thanks to our community member who suggested it. You asked, we built it the same day. Keep the ideas coming 🙏 👉 swap.onedex.app/dashboard
2
35
1
111
1,422
Baloo.egld✖️ retweeted
🤑 Monthly revenue on @MultiversX reached $1,142 on Tuesday, more than in any month before. 📊 chainspect.app/chain/multive…
1
14
71
1,399
Baloo.egld✖️ retweeted
the models are open. the hard part is serving them fast, cheap, and where you choose. @alpha_dot_sh × @nvidia inception. 👊
open-weight models closed the quality gap. the new bottleneck is serving: cost per token, latency under load, and where your data is processed. Alpha has joined NVIDIA Inception to scale that layer. alpha.sh/blog/alpha-joins-nv…
12
37
1
187
5,143
🍕 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. ⚡
4
6
33
2,061
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.
8
13
2
121
5,109