Looking for a way to stay connected with friends while staying active? 🚶‍♀️🚶‍♂️ With #Moverse# Engage-To-Earn mechanism, you can enjoy the benefits of exercising & socializing combined 💪👟 A truly unique & synergistic experience 💫 #M2E# #Engage2Earn# #GetFit# #ML# #Exercise# #Socializing# #AI#

I’m glad to be in the JAPAN TEAM squad for the World Cup 2026🇯🇵 It’s an honor to lead this Japan team as the captain. It wasn’t an easy way to recover from the injury but I believed in myself to make this happen and will keep working hard to get fit for the games. Thank you all my teammates,staff and the fans for always being with and supporting me. I hope to see you all the @LFC fans on the pitch at Anfield next week before going to the World Cup.YNWA❤️ W杯メンバーに選出されたこと、キャプテンとしてこのチームを引っ張っていけることを非常に嬉しく思います。 まずは自分自身が引き続きしっかり良い準備をしてW杯に挑んでいきます。 5月31日に国立でファンの皆さんにお会いできるのを楽しみにしています。 日本がまだ見たことのない景色をみんなで見ましょう！！ #worldcup2026# #worldcup# #ynwa#

ethrex v30.0.0 schedules Glamsterdam on Hoodi. If you run ethrex on Hoodi, this is the release you need to follow the fork. Hoodi activates Glamsterdam at timestamp 1793036568, which is 2026-10-26 17:42:48 UTC. This is the first ethrex release with the fork scheduled on Hoodi, so earlier releases stop following the chain at that point, and it needs to be paired with a consensus client release that ships the Hoodi Gloas config. Mainnet has no Glamsterdam time scheduled. ⚠️ L2: the prover and the SP1 guest move to SP1 6.9.0, and SP1 6 proofs need the SP1 v6.1.0 Groth16 verifier. An existing deployment's SP1 5 verifier rejects them whatever key is registered, so the order matters. Let every committed batch be verified before the upgraded sequencer commits anything, then upgrade the OnChainProposer and replace the verifier in a single Timelock call, upgradeToAndCall(newImplementation, upgradeSP1Verifier(newVerifier)), and register this release's verification key. Full procedure: Aligned mode is unavailable until Aligned ships SP1 6 support, and the OpenVM L2 prover backend is removed. L1 node operators are unaffected. The rest of the release is mostly hardening, on the paths where something outside the node decides how much work it does. JSON-RPC parsing is bounded in memory and the Auth-RPC token is checked before the request body is read. eth_getLogs and log filter polls are bounded in cost, serving eth/72 cells to peers is bounded in CPU, and what a peer's transaction announcements can make the node track is bounded. Maps keyed by contract- or block-chosen values are seeded, and MODEXP gas is charged before its operands are sized. Also in v30.0.0: - RPC: eth_getFilterChanges reports each new log once, and the receipts of blocks still held in memory come back in full. - Sync: snap/2 catch-up charges peers that cannot serve block access lists, and accounts left with no storage slots get the empty storage root. - Performance and zkVM guests: calldata, CALL arguments and CREATE initcode are no longer copied per call, so zkVM guests stop running out of heap. Finality pruning no longer piles up overlapping range deletes, and state-history journaling skips layers that are already final. - L2: the committer generates the prover input for batches another build sealed, so a sequencer that takes over, or batches committed again after a revert, can still be proven. If you run ethrex on Hoodi, upgrade before 26 October. Everyone else, upgrade at your convenience. No resync is needed.