Wurstkloppi

@typhalive yeah absolutely. especially the younger ones are really exciting lately.

@WFA_Archive yeah i don’t want to mention the younger ones till they become full u19 players but we have A LOT of talent in the pipeline rn. broich gaining more control would be my dream

bvb players on this call-up sheet #soon. we are manifesting

@typhalive @Randy20_ yeah thats a crucial thing which will decide winners and losers sadly when they get 17/18/19 nowadays

@Randy20_ @WFA_Archive none of the 08s/09s are physically there yet tbh

@typhalive interesting. Fahrenhorst most still underrate sadly. Riedl simply has to stay healthy for a longer period, same for Kaba. THe other candidates I had are though a tad younger, so would be for different youth teams ^^. I would just love if the U23 finally goes under Broich fully

@WFA_Archive kaba, fahrenhorst, riedl

Ripple USD $RLUSD Now Available at iTrustCapital! ► Learn more here: itrustcapital.com/learn/what-is-… @Ripple

@typhalive So he was good as CB so far?

TONY REITZ. i doubted you but you’re a better emre can than emre can ever was

@daxooo_ Reitz really CB? Didnt know he can play that

Dortmund U21 vs Everton in the Premier League International Cup at 20:00. Line-up: Ostrzinski - Krevsun, Reitz, Benkara, Kabar - Duarte, Fahrenhorst, Inacio - Diallo, Hoy, Albert Subs: Held, Ritter, Degener, Faust, Zarqelain, Wessels, Tazemeta youtube.com/live/dYSvSKlXn…

Cross-border payments don’t have to be painful. PYUSD is rolling out to the PayPal wallet across 70 markets — enabling faster settlements, lower costs, and built for everyday global commerce. Learn more: bit.ly/4uwNwCs

@PlayGOALS is there a known issue that controllers not get recognized (and I see also no way to select a specific controller in the settings) ?

If the game lags, you're not in control. You're just watching. GOALS is built differently. Here’s how our netcode works ↓

@_Roman_R_ @shxrkFNBR @FrayFN I hope you got a good transfer amount for him.

Today we say goodbye. @shxrkFNBR is one of the biggest Fortnite talents of the last few years and @FrayFN spotted that right away. It has been a great pleasure to being part of his journey. During our time together, he showed not only how much talent he has, but also the dedication and passion with which he pursues his dream. I’m certain that we will see a lot more from him and that he has what it takes to become one of the very best in Fortnite. I wish him nothing but the best for the future, in&outside the game.

Digital assets are entering a new phase. What once ran in parallel to existing financial systems is increasingly being applied to solve practical, real-world needs — often behind the scenes – from cross-border remittances to B2B money transfers. This creates new opportunities to add value in how money moves globally. Today, we introduced the Mastercard Crypto Partner Program — a global initiative that brings together more than 85 crypto-native companies, payments providers, and financial institutions. Together, we're creating a forum for meaningful dialogue and collaboration as this space continues to mature.

Xaman wallets now have chat. Self custody messaging with @evergramhq

Evergram is now available through @XRPLWin Self-custodied communication for the XRPL ecosystem. Your wallet. Your identity. Your messages. evergram.app

Evergram is live. Fully encrypted messaging for Web3. No central message database. End-to-end encryption by default. Try it via Xaman xApp or web: evergram.app

A historic moment for crypto. Kraken Financial has been granted a Federal Reserve master account, making us the first digital asset bank with direct access to the U.S. payments system. A major step toward connecting crypto infrastructure with the core rails of global finance. blog.kraken.com/news/federal-r…

Statement on dUNL Responsibilities and my position following the Batch amendment incident (XLS-56) Over the past weekend, in spaces and in several DM conversations regarding the recent Batch amendment issue (widely referred to as BatchGate), I have seen widespread confusion about the actual role and responsibilities of dUNL validators. I want to provide clarity from my perspective as a long-standing operator, along with the conclusions I have reached. The role of dUNL validators is specific and limited: We coordinate the activation (or rejection) of amendments by casting “Yay” or “Nay” votes once an amendment is proposed. We are supposed to judge pending amendments. That is our primary governance function. The baseline expectations for anyone on the dUNL are straightforward technical competencies: - Deep understanding of how rippled works - Operational experience running and maintaining rippled nodes - Solid knowledge of decentralised network principles - Ability to debug issues quickly - Proactive mindset to identify risks before they materialise Importantly, dUNL participation is uncompensated. The principle “no incentive is the best incentive” has always guided consensus security, and I fully support it. I run my validator as a service to the network because I believe I am well-positioned to help protect its long-term health and uptime, better than the vast majority of voices in the ecosystem. I have repeatedly pushed back against Ripple when I believed it was in the network’s best interest, and I will continue to do so. Ripple’s corporate objectives are not always aligned with the XRPL’s security and decentralisation priorities. My success metric is simple: 100% uptime and preventing issues, not their resolution after the fact. The dUNL is not a free code-review or protocol-auditing body. Expecting validators to spend dozens of unpaid hours reviewing complex amendment code was never part of the design and never will be. Instead, parties proposing amendments should be required to deliver comprehensive documentation, test suites, security analyses, and formal proofs upon request. If you want my vote, prove the change is safe and beneficial. I have applied this standard consistently for years. However, requiring proposers to ask them to review their own code is simply not enough. We need more eyes and hands on the code. Past warnings ignored. Over the last five years, I have publicly flagged serious concerns with several high-impact amendments, including XLS-20 (NFTs), XLS-30 (AMM), and now XLS-56 (Batch). In every case, my concerns proved valid. Despite this track record, the pattern has not changed: proposals continue to advance with insufficient scrutiny, and public discourse rarely engages with the actual technical risks. The recent critical vulnerability in XLS-56, which could have allowed unauthorised transaction execution and potential fund drainage, is the latest and most serious example. The fact that it reached the voting stage on mainnet before being caught, and that public disclosure by an independent researcher and an AI tool was ultimately required to prevent harm, highlights a systemic failure in review processes. By public opinion, this issue rests with the amendment’s authors and the dUNL. Meanwhile, formal verification and AI are being pitched as the complete solution, as the holy grail. This is unacceptable. My actions moving forward, effective immediately: - Withdrawing all current “Yay” votes on every amendment under consideration (excluding pending fixes) - Refusing to upgrade to rippled 3.1.1 (unless staying on the prior version risks removal from the network) I will not vote in favour of any future amendments until Ripple makes a credible, concrete commitment to substantially increase investment in XRPL core protocol engineering, security review, and long-term sustainability. I am pinning this on Ripple as no well-funded alternative exists in the ecosystem as of today. If XRP is truly Ripple’s “North Star,” as repeatedly stated, then the network’s foundational security and decentralisation must receive the attention and resources they deserve. A fintech company positioning itself at the centre of future finance cannot afford to under-invest in the very ledger that powers its vision. A fancy blogpost with made-up numbers is not enough. I remain fully committed to the XRPL’s success and will continue to operate my validator to the highest standards of reliability. However, I will no longer participate in a governance process that repeatedly accepts elevated risk without corresponding accountability. The network’s security and longevity must come first. Always.

@daxooo_ Finally. That should be a standard every game hopefully going forward (next season onwards) by removing a few more of the "regio" players.

Luca Reggiani, Mussa Kaba, Samuele Inacio, and Mathis Albert start for Dortmund U23. 8 out of the 11 players come from our U19 or youth categories, that’s exactly ehat we want from a U23, and having great talents in the lineup, as is the case today, is exactly what we aim for.

New xApp in @XamanWallet: Flare XRPFi Yield! $XRP yield. One wallet. One signing flow. Your keys. Your wallet in control. Built by @FlareNetworks. Accessible through Xaman. Read all the details: xaman.app/blog/flare

@niklasborglund @songsofconquest great to hear. happy this helped out.

@WFA_Archive @songsofconquest Thank you! I think I found the issue - and hopefully a fix will be out later today!

We just launched a new spell for Wielders of the Essence! (SoC-lovers, please know that we'll tone down the Wielders talk as soon as Next Fest is over!) And thanks for your patience! 🙏 Devblog is linked in 🧵

@niklasborglund @songsofconquest here a small snippet. For me it seems like certain audios-bits are randomly played and much loader than usual. It happened after the last update in steam from I think yesterday or the night before. And on camp screen as mentioned often the sound was completely off as well.

@WFA_Archive @songsofconquest A video would be great! Thank you! We've had some reports about audio issues, but not any good reproduction case yet