Professional Validator and Staking Service Provider. Stake with us in: #CELESTIA, #CCD, #DYMENSION, #FUEL, #SEDA , #QUICKSILVER, #AVAIL, #STARKNET #ESP #ATOM

Joined January 2022
1,084 Photos and videos
Cosmos Hackathon Kick Off Deets on the upcoming MAD easy hackathon with 2000$ in prizes ๐ŸŽค @RoboMcGobo @Rekt_Zerker โฐ Mon Jun 15th, 16:00 UTC ๐Ÿ‘‡ Set your reminders x.com/i/spaces/1NxarrAoRQgKj
31
35
57
4,261
Live peers for XRPL EVM: keeping node connectivity practical ๐ŸŒ Running an XRPL EVM node means dealing with one of the most common infrastructure problems: peer connectivity. Static peer lists can be useful as a starting point, but they become outdated very quickly. A peer that was visible from one node yesterday may not be reachable from the outside today, and when a node starts struggling to connect, that difference matters. That is the reason behind Cumulo Live Peers โšก We built it as a live peer checker for XRPL EVM mainnet and testnet, updated every 30 minutes and available through both a public dashboard and API. The goal is simple: continuously detect which peers are actually reachable, remove unstable entries, and provide node operators with a peer list that is useful in real operational situations. How Cumulo Live Peers works ๐Ÿ› ๏ธ Every 30 minutes, the system creates a new candidate pool using several sources: ๐Ÿงฉ Our own XRPL EVM nodes ๐ŸŒ RPC endpoints from validators in the ecosystem ๐Ÿ“š Addrbooks and peer lists collected from validator resources ๐Ÿค Peers contributed directly by operators Each candidate is then tested through a direct TCP check against its P2P port. If a peer cannot be reached from the outside, it is not included in the published list. We also avoid adding peers just because they appeared once. To be included, a peer needs to show consistent stability across roughly the last 5 hours of observations. If it disappears, becomes unreachable or stops behaving reliably, it is automatically removed after a few cycles. A useful list, not just a longer one ๐Ÿ”Ž It is designed to publish a peer list that operators can actually trust when they need to recover or improve connectivity. Peers are scored based on: ๐Ÿ“ˆ Recent stability ๐Ÿ” Outbound activity โœ… How many independent sources confirmed the same peer ๐ŸŒ Geographic diversity This helps reduce noise and avoid peer lists filled with random entries that may not be helpful in practice. For operators, especially during a connectivity issue, quality matters more than quantity. Ready to use ๐Ÿš€ The live peer lists are already available here: ๐Ÿ”— Mainnet: cumulo.pro/services/xrplevm_โ€ฆ ๐Ÿ”— Testnet: cumulo.pro/services/xrplevm/โ€ฆ ๐Ÿ“– Full technical documentation: github.com/Cumulo-pro/Cumuloโ€ฆ Why this matters ๐Ÿง  At Cumulo, we operate validator infrastructure across XRPL EVM, Cosmos and modular networks, and peer connectivity is one of those topics that looks simple until something breaks. Cumulo Live Peers is our way to make this part of node operations more practical for the XRPL EVM ecosystem: live checks, public data, reproducible logic and continuously updated peer lists without manual maintenance. We hope this becomes useful for XRPL EVM validators, node operators and infrastructure teams. Feedback, suggestions and validator contributions are very welcome ๐Ÿค
2
3
82
๐Ÿ—ณ๏ธ We voted YES to Starknet v0.14.3 Voting is now active to approve @Starknet v0.14.3 as a minor upgrade, and Cumulo has already cast its vote in favor. This upgrade brings key improvements to the network: โšก๏ธ More frequent blocks and lower latency with SNIP-40 ๐Ÿ’ธ Dynamic L2 gas base fee tied to the STRK price through SNIP-35, improving fee predictability โš ๏ธ RPC 0.8 deprecation: teams should migrate to RPC 0.9 or 0.10.1 / 0.10.2 ๐Ÿ“… Sepolia testnet: June 9 ๐Ÿ“… Mainnet target: June 22, 2026 As validators on Starknet, we continue supporting upgrades that make the network more efficient, predictable, and ready for its next stage of decentralization. Review the full notes and participate in the vote ๐Ÿ‘‡ community.starknet.io/t/starโ€ฆ
2
3
103
โš›๏ธ What really happens with gas when you pay many recipients at once on @cosmos ? We published a new article exploring multi-send on @cosmoshub through a real testnet case study, using actual transactions to measure how gas behaves as the number of recipients increases ๐Ÿ“Š With Gaia v27.0.0, multi-send gas is no longer purely linear. It now includes a quadratic surcharge designed to make large-scale spam increasingly expensive, while keeping legitimate use cases accessible ๐Ÿ›ก๏ธ In the article, we cover: ๐Ÿ”น What multi-send is and why it matters ๐Ÿ”น How gas works in Cosmos Hub ๐Ÿ”น The quadratic surcharge introduced in Gaia v27.0.0 ๐Ÿ”น Real gas data from testnet transactions ๐Ÿ”น The empirical formula behind the total gas cost ๐Ÿ”น Why this matters for validators, developers, protocols and users At Cumulo, we are validators on @cosmoshub โš›๏ธ and for us, running infrastructure also means testing, measuring and explaining how the network behaves in practice. Read the full article here ๐Ÿ‘‡ ๐Ÿ‡ฌ๐Ÿ‡ง EN: medium.com/cumulo-pro/multi-โ€ฆ ๐Ÿ‡ช๐Ÿ‡ธ ES: medium.com/cumulo-pro/multi-โ€ฆ Real data. Real transactions. Real infrastructure ๐Ÿ› ๏ธ
2
5
96
๐ŸŽ‰ Congratulations to @Concordium on 5 years of mainnet! Cumulo has been validating Concordium since the very beginning, and weโ€™re proud to have supported the network throughout this journey. Privacy, identity and trust at the protocol level have always been key pillars of Concordium, and they are becoming even more relevant as blockchain infrastructure evolves toward verified humans and verified agents. Excited to keep building and validating alongside the Concordium ecosystem for the next chapter ๐Ÿš€
๐ŸŽ‰ 5 years ago, Concordium mainnet went live. We started with a simple belief: Trust should be built into the protocol. Five years later, that foundation powers verified identity, privacy-preserving accountability, settlement infrastructure, and now the trust layer for AI agents. Verified Humans. Verified Agents. One Protocol. Hereโ€™s to the next 5 years. ๐Ÿš€
1
5
95
๐Ÿš€ Cumulo validator & infrastructure report: last 2 weeks Although it does not always show on the surface, these past weeks have been packed with lot of technical work, and projects like @cosmos and @celestia continue to stay very active across upgrades, coordination, and infrastructure operations. Check our internal infraestructure activity over the last two weeks: ๐ŸŸ  @cosmoshub / testnet: voted YES on Prop #301 for the Gaia v27.4.0-rc0 upgrade and executed the provider chain upgrade, signing within the first blocks after restart ๐ŸŸ  @cosmoshub / testnet: migrated infrastructure to higher-capacity servers, including the RPC stack, reverse proxy, SSL, addrbook exporter, and Horcrux signer ๐ŸŸ  @cosmoshub / mainnet: voted NO WITH VETO on Props #1038, #1039, and #1040 due to fraudulent spam/phishing content, and voted YES on Prop #1041 for the Gaia v27.4.0 upgrade ๐Ÿ”ท @GenLayer / Bradbury: upgraded the validator to v0.5.12 with self-recovery fixes and security improvements ๐Ÿ”ท @GenLayer / Asimov: upgraded the validator to v0.5.12 with the same operational fixes and hardening ๐Ÿ“– @StoryProtocol / mainnet: executed the mandatory hardfork to Story v1.8.0 (Seneca) ahead of the scheduled height, with full post-upgrade verification โšก @Starknet / mainnet: enabled the staking pool for our strkBTC node, making it live and ready to receive delegation ๐ŸŒŒ @celestia / mainnet: upgraded nodes to celestia-app v8.0.8 during the scheduled maintenance window ๐ŸŒŒ @celestia / Mocha testnet: executed the upgrade to celestia-app v9.0.1-mocha with on-chain signaling for v9 ๐ŸŒŒ @celestia / Mocha testnet: upgraded the bridge node to celestia-node v0.31.1-mocha ๐ŸŒŒ @celestia / Mocha testnet: upgraded validator, RPC, and consensus nodes to celestia-app v9.0.2-mocha and celestia-node v0.31.1-mocha ๐Ÿ’ @monad / testnet: upgraded our full node to v0.14.5 within the required operational window ๐Ÿ’  XRPL EVM / mainnet: voted YES on Prop #32 to add a new validator to the network At Cumulo, we handle validation as production infrastructure work: upgrade readiness, governance monitoring, migration discipline, service continuity, observability, and controlled execution. Reliable validator operations are not just about keeping nodes online, but about managing critical systems with traceability, technical judgment, and professional standards. That is why we maintain our Activity Tracker: a public, JSON-backed record where we continuously document upgrades, migrations, deployments, and governance actions in an auditable format. ๐Ÿ“Follow our activity here: cumulo.pro/services/activityโ€ฆ
3
8
257
๐Ÿฆ RLUSD is now live on XRPL EVM. A major step for bringing regulated liquidity, XRP utility and multichain DeFi closer together. With RLUSD expanding through @wormhole NTT, builders on XRPL EVM can access new possibilities for: ๐Ÿ’ง Liquidity ๐Ÿ” Swaps ๐Ÿ“ฆ Collateral ๐Ÿ’ธ Payments ๐ŸŒ Cross-chain finance At Cumulo, as XRPL EVM validators weโ€™re proud to support the project and keep contributing to the infrastructure behind its growth. $RLUSD ร— $XRP is a big move for builders ๐Ÿ’ช.
The XRPL EVM Sidechain is now live with Ripple USD $RLUSD. A key part of RLUSD's multichain expansion, the XRPL EVM Sidechain combines compatibility with existing EVM developer tooling while remaining closely connected to the XRP Ledger, helping meet growing demand from developers looking to build with XRP. RLUSD has seen growing adoption across smart contract-based ecosystems, highlighting demand for regulated stablecoins within DeFi and multichain finance. As $RLUSD becomes available across these environments, $XRP can increasingly serve as a complementary asset for liquidity, settlement, swaps, collateral, and payments, thereby strengthening the utility of XRP and RLUSD across supported chains. This expansion is powered by @wormhole's NTT standard, enabling RLUSD to move natively across chains.
4
11
1,061
๐Ÿงต XRPL EVM May recap โšก May was a busy month for XRPL EVM. Lower fees, a new wallet, early use cases, and several important improvements on the way. Quick recap ๐Ÿ‘‡ ๐Ÿ’ธ Much lower fees Proposal #29 passed with 100% approval from 18 validators. A simple transaction now costs only 0.000016 XRP, matching the cost of XRPL mainnet. This is a big step for: โšก Micropayments, ๐Ÿงฉ Smart contracts, โฑ Fast-finality apps, ๐ŸŒฑ Real-world use cases with ripple:native More info: governance.xrplevm.org/propoโ€ฆ ๐Ÿ‘› New wallet for XRPL XRPL EVM A new unified wallet is now available at: wallet.xrplevm.org The goal is simple: manage XRPL and XRPL EVM from one interface using @MetaMask . Signatures are automatically routed depending on the action, making the experience much smoother. It also integrates XR Bridge, powered by @axelar, to move assets from Ethereum and other EVMs into XRPL EVM. Original post: x.com/Peersyst/status/205929โ€ฆ ๐Ÿ”ฎ First use cases taking advantage of the new fees @AxiomProtocol_ is already building on top of this new low-fee environment with a prediction market on XRPL EVM. Original post: x.com/AxiomProtocol_/status/โ€ฆ ๐Ÿ—บ Whatโ€™s next? ๐Ÿ’ธ A micropayments app as the first demo of low fees programmability ๐Ÿ”— Longer IBC channel bonding time for more stability ๐Ÿ›  Fund recovery from the Elys Network shutdown through governance ๐Ÿ‘› More wallet improvements, including custodian deposits and more EVM assets XRPL EVM by @Peersyst is moving into a more practical phase, with better infrastructure, better UX, and more reasons for builders to start experimenting on the network. At Cumulo, we keep supporting the network as validators and following closely what comes next โšก
LIVE: 18.1% chance for ripple:native to break ATH in 2026 Predict the future using XRP Only on Axiom Protocol
1
3
12
655
๐Ÿš€ Celestia Mocha v9 is getting closer! The upgrade signaling process for @celestia Mocha has reached the required voting power threshold โœ… Current status: ๐ŸŸข 57 / 78 validators signaling ๐Ÿ—ณ๏ธ 85.03% voting power ๐ŸŽฏ Threshold: 83.33% โš™๏ธ Target version: v9 This upgrade brings an important improvement to Mocha: blocks will move to 3-second block times, making the testnet faster and more aligned for future testing and development. As validators signal readiness through MsgSignalVersion, the community can follow the process in real time using our Upgrade Signal Tracker: ๐Ÿ‘‰ cumulo.pro/services/celestiaโ€ฆ Built by Cumulo to help the Celestia community track upgrades with more visibility ๐ŸŒŒ
7
49
1,455
๐Ÿš€ New article by Cumulo is live! Bitcoin apps are growing, but liquidity is still fragmented across multiple chains. In our latest Medium article, we recap the live workshop with @AvailProject, featuring @mayurrelekar from Avail and @yilmaz_btc from @citrea_xyz, focused on how Avail Nexus helps Bitcoin apps access cross-chain liquidity in a much smoother way. Main points covered ๐Ÿ‘‡ ๐Ÿ”น Why liquidity fragmentation is a major UX problem for Bitcoin apps ๐Ÿ”น How Avail Nexus enables N-to-1 cross-chain liquidity aggregation ๐Ÿ”น The live demo with Mystic Finance on Citrea ๐Ÿ”น How users can deposit into Bitcoin L2 apps without manual bridging ๐Ÿ”น Why this matters for developers building better onboarding flows Avail Nexus shows how complex cross-chain actions can be abstracted into a simple user experience, helping Bitcoin apps become more accessible, composable and ready for real adoption. ๐Ÿ“– Read the full article: English version: medium.com/cumulo-pro/bitcoiโ€ฆ Spanish version: medium.com/cumulo-pro/las-biโ€ฆ
6
11
286
๐ŸŒ Cumulo Live Peers: from static peer lists to real-time peer lists Cumulo Live Peers for @celestia is a live peer checker for Celestia mainnet and Mocha testnet, designed to help validators and infrastructure teams find peers that are actually reachable and useful right now. When a node starts having connectivity issues, a static list is often not enough. What operators need in that moment is simple: peers that are reachable from the outside, stable over time, and ready to use. Cumulo Live Peers checks peer availability every 30 minutes and builds updated lists using multiple sources: ๐Ÿ”Ž Our own Celestia nodes ๐ŸŒ RPC endpoints from validators in the ecosystem ๐Ÿ“š Addrbooks and public peer lists ๐Ÿค Peers contributed directly by operators Each candidate peer is tested through a direct TCP check against its P2P port. If a peer is not reachable from the outside, it does not make it into the published list. We also avoid publishing peers just because they appeared once. To be included, a peer needs to show consistent stability across several observation cycles. The goal is not to publish the biggest possible peer list. The goal is to publish a useful one. Peers are scored based on: โœ… Recent stability โœ… Outbound activity โœ… Confirmation from independent sources โœ… Geographic diversity You can use the live peer lists here: Mainnet: cumulo.pro/services/celestiaโ€ฆ Mocha testnet: cumulo.pro/services/celestiaโ€ฆ Full technical documentation: github.com/Cumulo-pro/Cumuloโ€ฆ We also maintain validator resource lists for Celestia mainnet and Mocha, so validators can contribute RPCs, addrbooks and peers via PR. The more validators contribute, the better the system becomes for everyone. We shared the full explanation on the Celestia Forum ๐Ÿ‘‡ forum.celestia.org/t/cumulo-โ€ฆ This is part of how we approach our role as @celestia validators at Cumulo: building tools that reflect our vision of solid, transparent and reliable infrastructure, while adding real technical value to the networks we support.๐ŸŒŒ
3
5
114
TL;DR ๐Ÿ‘‡ Static peer lists get outdated fast. Cumulo Live Peers keeps checking which Cosmos Hub peers are reachable, stable and useful for node operators. When you run a @cosmoshub node and connectivity starts failing, a static peer list is often not enough. What you need in that moment is simple: peers that are actually reachable from the outside right now. Not peers that were visible from one node a few days ago. That is why we built Cumulo Live Peers ๐ŸŒ A live peer checker for @cosmos Hub mainnet and testnet, updated every 30 minutes and available through both a public dashboard and API. The idea is simple: ๐Ÿ”Ž keep checking which peers are really reachable ๐Ÿงน filter out unstable ones ๐Ÿ› ๏ธ give node operators a list they can actually use How it works โš™๏ธ Every cycle, Cumulo Live Peers builds a candidate pool from several sources: ๐ŸŸข Our own Cosmos Hub node ๐ŸŸข RPC endpoints from validators in the ecosystem ๐ŸŸข Addrbooks and peer lists collected from validator resources ๐ŸŸข Peers contributed directly by operators Then we test each candidate with a direct TCP check against its P2P port. If a peer is not reachable from the outside, it does not make it into the published list. Simple rule: โœ… reachable peers stay in the process โŒ unreachable peers are filtered out Not just โ€œmore peersโ€ ๐Ÿ“ก The goal is not to publish the biggest possible list. The goal is to publish a useful one. Peers are scored based on recent stability, outbound activity, how many independent sources confirmed the same peer, geographic diversity. This helps avoid lists full of random peers that may not help much in practice, especially when an operator is trying to recover connectivity quickly. Ready to use ๐Ÿš€ You can use the live peer lists here: Mainnet: cumulo.pro/services/cosmos/pโ€ฆ Testnet: cumulo.pro/services/cosmos_tโ€ฆ Full technical documentation: github.com/Cumulo-pro/Cumuloโ€ฆ At Cumulo, we run validator infrastructure across Cosmos and modular networks. Cumulo Live Peers is our attempt to make that part of node operations a little more practical: ๐Ÿ” live checks ๐Ÿ“– public data โš™๏ธ reproducible logic โ™ป๏ธ a list that keeps updating without manual maintenance We hope this is useful for Cosmos Hub validators, node operators and teams running infrastructure. Feedback, suggestions and validator contributions are very welcome ๐Ÿค
2
2
5
133
Validator resource lists ๐Ÿค To make the external sources more useful, we also maintain public validator resource lists for Cosmos Hub mainnet and testnet. These include: ๐Ÿ”— RPCs ๐Ÿ“š addrbooks ๐Ÿ“ก contributed peers The more validators contribute their resources, the better the scoring becomes for everyone. Why? Because the system can compare more independent sources and build a more representative view of the network. If you are a @cosmoshub validator and want to add your resources, you can open a PR here: Mainnet validators: github.com/Cumulo-pro/cumuloโ€ฆ Testnet validators: github.com/Cumulo-pro/cumuloโ€ฆ
2
6
99
An important step for making XRPL EVM easier to use beyond the technical crowd ๐ŸŒฑ As XRPL EVM validators, weโ€™re excited to keep supporting this ecosystem as it grows ๐Ÿš€๐Ÿ’ช
๐ŸŒฑXRPL EVM infrastructure is getting ready for new exciting use cases: โšก๏ธNow supporting ripple:native micropayments, same fees as XRPL ๐Ÿ’ปAdding a programmability to combine logic micropayments 3s finality ๐ŸฆŠBrand new wallet.xrplevm.org allows multinetwork management in 1 wallet
2
1
6
161
โ‚ฟ New guide by @Cumulo_pro is live! โšก Weโ€™ve published a step-by-step guide on How to stake BTC on Starknet, designed for users who want to bring Bitcoin into Starknet DeFi and start making it productive. In the guide, we cover: ๐Ÿ”น How to get wrapped BTC on Starknet ๐Ÿ”น How to swap into strkBTC using @avnu_fi ๐Ÿ”น The main risks of BTC wrappers ๐Ÿ”น How to stake BTC through @endurfi ๐Ÿ”น How to choose a validator and delegate ๐Ÿ”น Why Starknet is becoming a powerful environment for BTC DeFi With low fees, fast confirmations and ZK-powered security, @Starknet is opening a new path for Bitcoin users who want more than just holding. At Cumulo, we are Starknet validators and one of the validators already supporting strkBTC staking. ๐Ÿ“– Read the full guide: ๐Ÿ‡ฌ๐Ÿ‡ง English version: medium.com/cumulo-pro/how-toโ€ฆ ๐Ÿ‡ช๐Ÿ‡ธ Spanish version: medium.com/cumulo-pro/cรณmo-โ€ฆ Weโ€™ll keep building infrastructure, guides and resources to make the @StarknetFndn ecosystem more accessible to users, builders and the wider community. ๐Ÿงฑ
2
2
8
179
Cumulo will be concluding validator operations on @StoryProtocol following the SIP-011 active set consolidation process. We want to thank the Story team for the opportunity to contribute as validators, from testnet operations to mainnet infrastructure. For our delegators: please redelegate or unstake your $IP as soon as possible. We will keep our node running during the notice period and until delegations are cleared. Although our validator operations and all the tools & service pages we developed for the protocol are coming to an end, Cumulo will continue building and operating strong and professional infrastructure across multiple networks. Thank you to everyone who supported us during this journey.
3
2
10
494
Who says there's not much going on?!! ๐Ÿ‘ฉโ€๐Ÿ”ง๐Ÿง‘โ€๐Ÿ”ง ๐Ÿš€ Cumulo weekly validator & infrastructure report: May 15โ€“23 Over the last week, our team executed validator operations, upgrades, governance actions, and incident-aware infrastructure work across multiple networks, check what we did? ๐Ÿ‘€๐Ÿ‘‡ โ˜• @EspressoSys / Mainnet: upgraded our mainnet node to 20260424, applying query and pruning optimizations and verifying healthy peer connectivity and consensus progression ๐Ÿ“– @StoryProtocol / Aeneid testnet: upgraded our validator to Story v1.7.0 (Seneca) ahead of the scheduled hardfork, with full sync and post-upgrade consensus validation ๐Ÿ›ก๏ธ @cosmoshub: voted NO WITH VETO on Prop #1037, a spam/scam proposal with no legitimate onchain purpose ๐ŸŸฃ @massachain / Mainnet: executed the mandatory MAIN.5.0 hard fork upgrade and rejoined the corrected network after the illegal minting fix ๐Ÿ”ท @GenLayer / Asimov: upgraded our validator to v0.5.11 ๐Ÿ’  XRPL EVM by @Peersyst / Mainnet: voted YES on Prop #31 to recover expired IBC light clients for Injective and Elys ๐ŸŸ  @cosmoshub Hub / Mainnet: executed the Gaia v27.3.0 upgrade at the scheduled height, covering validator, RPC, and backup infrastructure with post-upgrade verification ๐Ÿ”ท @GenLayer / Bradbury: upgraded our validator to v0.5.11 ๐Ÿ’ @monad / Testnet: upgraded our full node to v0.14.4 following the release window and verified full operational status At Cumulo, validator operations are handled as production infrastructure work: upgrade readiness, governance monitoring, incident response, controlled execution, and post-upgrade verification across live environments. That is also why we maintain our Activity Tracker: a public, JSON-backed operational log where we document upgrades, governance votes, incidents, and infrastructure actions in a transparent and auditable format. ๐Ÿ“Follow our activity here: cumulo.pro/services/activityโ€ฆ
1
4
177
Massive week @sedaprotocol
Massive week @ SEDA
4
391
๐ŸŒ Tokenization is moving from narrative to real institutional infrastructure. In our latest article, we analyze the Beyond Cosmoverse conversation with Anina Milanoviฤ‡ from the World Bank, and what it means for @cosmos, capital markets and the future of regulated digital assets. The key idea is clear: Tokenization is not here to replace traditional capital markets. It is here to upgrade them. In the article, we cover: ๐Ÿ”น How Serbia built one of the earliest digital asset regulatory frameworks before MiCA ๐Ÿ”น Why stablecoins pushed traditional finance to take blockchain infrastructure seriously ๐Ÿ”น The three institutional requirements for tokenized assets: legal certainty, trusted infrastructure and secondary liquidity ๐Ÿ”น Why emerging markets may have a unique opportunity to move faster ๐Ÿ”น How Cosmos-IBC architecture, sovereignty and interoperability fits naturally into this new financial landscape For the @cosmos community, this conversation matters. If regulated financial assets start moving across digital infrastructure, networks like Cosmos can play a key role in making those assets interoperable, auditable and usable across jurisdictions. At Cumulo, we are validators in @cosmoshub and we believe this is exactly the type of long-term infrastructure narrative that matters for the ecosystem. ๐Ÿ“– Read the full article: ๐Ÿ‡ฌ๐Ÿ‡ง English version: medium.com/cumulo-pro/regulaโ€ฆ ๐Ÿ‡ช๐Ÿ‡ธ Spanish version: medium.com/cumulo-pro/regulaโ€ฆ
1
4
152