On duty, still 🙃

No drama, no luck, just pure football royalty. La Roja is flying to New York to claim the crown. ¡Vamos! La Roja 🇪🇸

Hahaha, Polkadot is so hilarious🤣 while in 2026 other chains compete for institutional liquidity, deliver enterprise, institution level privacy infrastructure for capital markets, tokenized deposits and securities you are flexing around some archaic app & paper rock scissors

Another list of useless things. Another half year of „products for the people” wasted time, efforts and resources. We were promised usefull dapps, products, a breakthrough. And this is what they been working on 🤣 Polkadot is officially done.

Most teams building their first cross-border payment product assume that picking a provider now is a reversible decision. If the FX desk underperforms, swap them. If the ramp gets expensive, change it. If the KYC vendor frustrates the ops team, find another. By the time you want to swap, you're not swapping a provider. You're rewriting your payment core. The first corridor is usually built around one set of choices: one FX partner, one payout provider, one ledger setup, one KYC vendor, one ramp. The decisions feel local - pick what fits the first market - and the integration is direct, because there's no reason yet to abstract anything. That shape works fine until the second market. Then the third. Then the corridor that needs a different liquidity provider, or the regulator that requires a different KYC partner, or the FX desk that quotes 80 bps tighter on the same pair. The cost surfaces when you try to add or replace one of those. Provider-specific assumptions are wired into status handling, retry logic, the reconciliation layer, the ledger schema, the way exceptions get classified. The "swap" is not a swap. It's a partial rewrite of the payout core, with every other corridor exposed to regression risk during the change. The mistake compounds... In conventional software, a bad early dependency is annoying. In a payment system booking real money against a ledger, every uncontrolled rewrite is a reconciliation incident waiting to happen. The migration window has to coexist with live settlement, and the team writing the migration is the same team running production. By the time you realize the first provider became your architecture, the cost to undo it is no longer the cost of an integration. It's the cost of a refactor while the system is live, multiplied by the number of corridors built on the same assumption. The decision worth making early is not which provider. It's where the seam between your payment core and any specific provider lives, whether ledger, FX, custody, ramp and KYC sit behind interfaces that treat each provider as a swappable implementation, or whether they're wired directly into the workflow. What is your bet on the orchestation framework?

Welcome home Yukon 🇦🇺🇨🇦🐶

No one cares about Nakamoto numbers if one entity can single-handedly change the whole protocol rules, tokenomics, freeze the funds, or spend all the treasury with governance proposal and votes.

W Dubaju można płacić krypto za usługi rządowe a u nas składają propozycje całkowitego zakazu kryptowalut… Świat pędzi do przodu a my jesteśmy w dupie. A najgorsze jest to że powoli zaczynamy się w tej dupie urządzać…

W Dubaju można płacić krypto za usługi rządowe a u nas składają propozycje całkowitego zakazu kryptowalut… Świat pędzi do przodu a my jesteśmy w dupie. A najgorsze jest to że powoli zaczynamy się w tej dupie urządzać…

Congrats Centrifuge! Huge!

JAM wont happen at all. They realised it has no chance of wider adoption, there is total mess, teams are frustrated because there is no any leadership, only changes of delivery path, noone been paid inspite of many delivered the M1. Just check the element chat, absolute cinema

A goldmine of a report for anyone building new stablecoin financial rails. Seeing the landscape evolve like this, @neti_soft's decision to build NetiRails - the stablecoin rails for cross-border payments - wasn't a guess. It was a read. Congrats @slawek_neti and the whole team.

I've spent 7 years in the Polkadot, building community, running validators, representing at events, watching Web3 grow up. Now as the next chapter, it's time to channel all of that into helping serious teams ship serious products. Joining @neti_soft as BD Manager, one of the top blockchain dev houses in the world, quietly shipping great work out of Poland. If you're building in web3 and need a tech partner who actually delivers, let's talk.