> Except from article. ​ Nigeria received approximately $59 billion in crypto-asset inflows between July 2023 and June 2024, according to an International Monetary Fund (IMF) report published June 16. The country has accounted for 60% of all stablecoin inflows across sub-Saharan Africa since 2019. Dollar-pegged tokens have grown from a niche product into a primary channel for cross-border transfers among households and small businesses. Conventional remittance services charge Nigerian senders an average of 9% of the transaction value to move $200 abroad, compared to a global average of 6%, according to World Bank data. Stablecoins have offered a faster and cheaper alternative. Smartphone access and digital wallets have made adoption easy to scale across income levels. submitted by /u/zesushv [link] [Kommentare]

Welcome to the Daily Crypto Discussion thread. Please read the disclaimer and rules before participating. Disclaimer: Consider all information posted here with several liberal heaps of salt, and always cross check any information you may read on this thread with known sources. Any trade information posted in this open thread may be highly misleading, and could be an attempt to manipulate new readers by known "pump and dump (PnD) groups" for their own profit. BEWARE of such practices and exercise utmost caution before acting on any trade tip mentioned here. Please be careful about what information you share and the actions you take. Do not share the amounts of your portfolios (why not just share percentage?). Do not share your private keys or wallet seed. Use strong, non-SMS 2FA if possible. Beware of scammers and be smart. Do not invest more than you can afford to lose, and do not fall for pyramid schemes, promises of unrealistic returns (get-rich-quick schemes), and other common scams. Rules: All sub rules apply in this thread. The prior exemption for karma and age requirements is no longer in effect. Discussion topics must be related to cryptocurrency. Behave with civility and politeness. Do not use offensive, racist or homophobic language. Comments will be sorted by newest first. Useful Links: Beginner Resources Intro to r/Cryptocurrency MOONs 🌔 MOONs Wiki Page r/CryptoCurrency Discord r/CryptoCurrencyMemes Prior Daily Discussions - (Link fixed.) r/CryptoCurrencyMeta - Join in on all meta discussions regarding r/CryptoCurrency whether it be moon distributions or governance. Finding Other Discussion Threads Follow a mod account below to be notified in your home feed when the latest r/CC discussion thread of your interest is posted. u/CryptoDaily- — Posts the Daily Crypto Discussion threads. u/CryptoSkeptics — Posts the Monthly Skeptics Discussion threads. u/CryptoOptimists- — Posts the Monthly Optimists Discussion threads. u/CryptoNewsUpdates — Posts the Monthly News Summary threads. submitted by /u/AutoModerator [link] [Kommentare]

I wanted to share an ICML 2026 spotlight position paper on a failure mode in image-generation alignment: aesthetic preference optimization may override explicit user intent when the requested output is anti-aesthetic or outside mainstream visual taste. The paper frames this as **reversed alignment**. Instead of the model aligning to the user's stated preference, the output is pulled back toward the model's learned aesthetic prior. We test generation and reward models on prompts asking for blurry, distorted, low-fidelity, negative-emotion, and other anti-aesthetic images. GitHub repo: https://github.com/weathon/icml2026_position Paper: https://arxiv.org/abs/2512.11883 OpenReview: https://openreview.net/forum?id=1gQ4zc1Q8I I would be interested in feedback on the framing and on evaluation designs for separating prompt understanding from preference override. submitted by /u/Striking-Warning9533 [link] [Kommentare]

Move would be ‘embarrassing’ for the EU, Patrick O’Donovan says

Static types and shovels I have a simple theory about why static typing became much less popular in the 2000s to early 2010s and started to get more popular again around the mid to late 2010s. It isn't because programming is a fashion led industry, but because the quality of the static type systems that were widely available improved. Here's an analogy: say you want to dig a hole, would you rather use a shovel or your hands? If the shovel is any good then obviously you'd use the shovel. But what if the only shovel available to you was made of paper? You'd just be flailing uselessly at the ground with it. You'd be better off digging barehanded. With a dynamic type system, you have to do all of the thinking about the states and contents of the variables and fields in your program yourself, with your own brain. The computer doesn't help you at all, nor does it hinder you. It's analogous to digging with your hands. On the other hand, if you're given a poor static type system like the ones that were popular in the 90s and early 00s, such as the ones in early Java or C++98, it's analogous to a paper shovel. These static type systems fail to even help you with simple things like distinguishing nullable from non-nullable pointers. They don't have sum types, only product types. Meanwhile they require you to spend a lot of effort manually writing out type names all over the place. BufferedReader bufferedReader = new BufferedReader(new FileReader(filename)); is a small disaster. If you contrast this to a modern type system like the one in say TypeScript, Haskell, MyPy, Swift or Rust, you'll always get: Some way of distinguishing nullable from non-nullable types. Haskell has Maybe t. TypeScript has T | null. Swift has T?. Rust has Optional. The type system can easily tell you where all the null checks need to be and if you missed one. In practice you almost never see null pointer errors at runtime. At least one of sum types or union types, which let you follow the "Make invalid states unrepresentable" practice. This means you can have objects representing state machines, they have multiple fields, and each field exists when and only when the system is in a relevant state. Some kind of type inference. We don't need to write let x: number = 5; when the compiler can just work out that let x = 5; is definitely a number. Another thing which made static type systems more useful is that IDE features like method name completion have become more widespread. In the 90s Intellisense was a killer feature in Visual Studio, whereas in the 2020s similar features are available in just about every IDE and editor. So information you put into a static type system yields extra productivity benefits, entirely aside from its usefulness for checking programs for errors. In conclusion: A good dynamic type system is better than a bad static type system. But now we have much better static type systems than we used to. © Copyright 2026 Richard Barrell

Don't rent your future, own it with Ruby