Bill Laboon | Web3 Foundation

Reminder that this is disingenuous, and Chainspect knows it is incorrect, since it measuring one chain out of dozens, and the one DESIGNED to have as few txs as possible (since it just coordinates other chains). They keep making mistakes understanding the chain, and keep writing these misleading tweets that they know are misleading. It‘s fine if you don’t understand how Polkadot works, but if that‘s the case simply don‘t write about it. x.com/BillLaboon/sta…

🎉 Big day for @Polkadot The network reached its highest TPS of the past 7 days on Thursday. 0.01 TPS That's 971 transactions across the entire day 📊 chainspect.app/chain/polkadot

No servers. No cloud providers. No infrastructure to provision. At @Web3Summit 2026, attendees paid for food and drinks, proved their humanity, published .dot domains, deployed apps, and interacted with decentralized services across two days. Every front end is hosted on Levity. Every person verified as human through HUMANITY without revealing who they are. Every deployment handled by the Product SDK. All of it on-chain. Most people in the room never thought about the infrastructure. It was beneath the experiences it enabled. That is the shift. Developers should not start by thinking about chains. They should start with users. The infrastructure is there to make that possible.

One of the cool things about Web3 Summit was that everything - payment, scheduling, chat, coding, proof-of-personhood, tickets - could be done on-chain. Very cool to see.

All @kusamanetwork vision bounties are open for new teams to apply to. Build some crazy stuff!

This dashboard does not include any unsigned transactions (including system transactions) by default. You can see that some of the parachains only show 1 or 2 transactions per day, which would not be the case if it were showing system transactions like timestamp.set. I understand Polkadot is a bit different than the way most chains operate, and thus more difficult to track. Tracking only the relay chain, however, which is _designed_ to have fewer and fewer transactions over time, doesn't really make sense for Polkadot. I am not sure who you talked to working on Polkadot, or what information you need, but all this information is publicly available and I can show you the endpoints to get it. Just let me know.

The relay chain is tracked, but not the rest of the parachains. We tried to make it happen with the Polkadot team, but despite multiple attempts, the Polkadot team was against it. But happy to revisit it. As for the Polkadot dashboard, built by the Polkadot team to track Polkadot metrics exclusively, it includes system transactions, such as timestamp.set and parachainsystem.set_validation_data, which are present in every block. As a result, the total number is heavily inflated. On Chainspect, all chains are tracked in the same way, so we don't count system- or consensus-related transactions. You can read more about it on our platform.

📉 Polkadot's on-chain activity has nearly disappeared On Tuesday, @Polkadot processed just 21 transactions, a 99.5% decrease from the 3,924 recorded on June 12 Is anyone still using Polkadot? 📊 chainspect.app/chain/polkadot…

You can see here that there around 450k transactions per day on average on Polkadot: data.parity.io/parachain-stat… There are numerous errors on this page, probably because it is looking at the relay chain (whose job is to do as little as possible other than coordinate parachains). It also shows that there no validators and no stake, which is incorrect. This is likely due to not updating when staking moved off the relay chain to the Hub parachain.

Check out the presentations from @Web3summit!

Here's an excellent overview of the technologies used to run the Web3 Summit 26. Most didn't know that the event ran on 100% decentralized services, and that was the point. From the conference app, maps, and agenda through to payments. forum.polkadot.network/t/polkadot-pro…

@yaydotoi It‘s failing with something like 20 million ACA against and 100 in favor.

@BillLaboon Hopefully people are paying attention to the fake runtime upgrade ref on Acala right now that's trying to updateBalance 99K DOT acala.subsquare.io/democracy/refe…

We saw a few governance attacks in the Polkadot ecosystem, as well. There are some additional safeguards (e.g. takes longer to pass more powerful referenda, minimum support, etc.), but the key preventative measure is almost always people paying attention.

I should thank this scammer, I literally laughed out loud at this

@cao_lab @alice_und_bob The discussion he is referring to is here: forum.polkadot.network/t/brave-wallet…

@alice_und_bob that's great, I missed that, I should be more active in the forum obviously, thank you @alice_und_bob

Back in 2024, the Polkadot Treasury approved a $3M USDC proposal to integrate Polkadot into Brave Wallet！ I'm genuinely curious if anyone has recent usage metrics or progress updates from this integration. If I've missed them, please share them! It was described as a strategic ecosystem investment, but it raises an important governance question: What measurable outcomes have been achieved? Are there public KPIs or adoption metrics? Is the integration actively maintained? Should the Treasury receive more than just implementation for investments of this scale? If the ecosystem spends millions to accelerate adoption, the community should be able to evaluate the long-term return. Going forward, should large Treasury-funded strategic partnerships include: • Milestone-based payments? • Public performance reports? • Revenue sharing or equity/warrants when appropriate? • Long-term maintenance commitments? This isn't about criticizing Brave or polkadot. It's about improving how the Polkadot Treasury allocates capital and measures success. I'd love to hear the community's thoughts. Curious to hear thoughts from @BillLaboon @shawntabrizi @alice_und_bob @joepetrowski @giottodf — are there any recent public updates or metrics on the Brave Wallet integration funded by the Polkadot Treasury?

@unholywrath1 @PolkadotDevs Correct. The era extended longer than normal. However, when the long era ended, a proportionally larger number of rewards were distributed.

@PolkadotDevs Is this the reason am not reciving any stacking rewards for the past 48hrs?

⚠️ We're aware of an issue that's currently preventing validator elections from rotating to the next validator set, and we're actively working on a fix. The issue was identified following the rollout of recent governance-approved changes to validator eligibility. Under specific conditions, the resulting validator set no longer met the requirements needed for validator rotation to complete. For validators, the current validator set will remain active until the issue is resolved. For nominators, new nominations and reward payouts for the current era will be delayed until the extended era ends. Aside from staking operations related to era transitions, the network continues to operate normally. No staking rewards are being lost. Validators continue earning rewards throughout the extended era, and nominators will receive their rewards once the era concludes. Because the era is longer than usual, both validators and nominators will receive proportionally larger rewards. The rewards are delayed, not reduced. We're currently targeting a fix within 2.5 to 4 days and will continue providing updates as work progresses. A full postmortem will be published once the issue has been resolved. Follow the Referenda: polkadot.subsquare.io/referenda/1914

@Asu41578538 For a very good reason - Web3 Foundation has nothing to do with the Polkadot App (or this code - Parity made it publicly available, I am just sharing it because I thought people would find it interesting).

@BillLaboon Why not publish the Polkadot app ?

If you couldn't make it to Web3 Summit, and are curious about the software demoed there, Parity open-sourced the entire stack - chains, UI, infrastructure - and include full instructions for running your own. paritytech.github.io/w3s-architectu…

@Hiraweb3 It explains it in the link. The election stalled because a good enough solution could not be found after a number of validators were chilled.

@BillLaboon glad the chain stayed safe, what caused the delay?

A post-mortem on the recent validator election issue (which caused a longer era than normal on Polkadot) has been released. forum.polkadot.network/t/2026-06-30-s…

NB: "The chain itself was never at risk: block production, finality and all non-staking functionality continued normally. No user funds were at risk or lost, and no emission was lost to the stall. Unbonding was delayed, not forfeited, and resumed once the era rotated."