Wildberries and Ozon to Accept Digital Rubles from September 1, 2026
Wildberries and Ozon will enable payments using digital rubles starting September 1, 2026. Home users, corporations, fraud protection, payment security, and compliance with Russian legislation are among the key aspects highlighted in the announcement.
Marketplaces have confirmed preparations for the new payment method. Ozon will first activate the digital ruble in test mode, placing it next to bank cards and other payment options. The company then intends to open the feature gradually to all customers, according to RIA Novosti. Wildberries shared no additional details but stated it will meet the requirements of the Bank of Russia and applicable regulations.
From the same date, the largest banks must allow clients to open digital wallets, transfer funds, and pay for goods. Users will access the new currency form through their usual banking application connected to the Central Bank platform. For citizens, operations with digital rubles will stay free of charge.
Mandatory Implementation Timeline
The marketplaces' launch is not a voluntary crypto experiment. Per Bank of Russia rules, from September 1 trading companies with revenue above 120 million rubles must accept digital rubles if serviced by major banks. In 2027 the requirement will extend to sellers with annual revenue over 30 million rubles, and in 2028 to all remaining businesses. Companies with turnover below 5 million rubles are exempt from mandatory connection.
The digital ruble will become the third form of Russian currency alongside cash and regular bank account money. Buyers will not be forced to switch; cards and other payment methods will remain available. The Bank of Russia has also promised banking secrecy for digital ruble holders.
Related articles
Google Developing Voice-Activated Emergency SOS Feature for Android Devices
Google is working on a voice-activated Emergency SOS function for Android that would allow users to summon help without touching their smartphone. The feature, discovered in the Personal Safety app code by Android Authority, appears to trigger after the user says the word 'Help' three times in sequence. Once activated, the system would automatically determine location, begin emergency video recording, and place a call to emergency services. The current method requires pressing the power button five times, which can be impractical in certain situations. Additional code strings suggest optional voice confirmation with phrases such as 'Say yes to continue' and 'Say cancel to dismiss Emergency SOS'. The function is not yet available to users and may eventually reach non-Pixel devices running the Personal Safety app, though supported languages and models remain undisclosed.
How the Lorenz SZ 42 Teleprinter Cipher Machine Worked: Nazi High Command Encryption and Its 1941 Breakthrough
The Lorenz SZ 42 was a teleprinter attachment used by the German high command for encrypting top-secret communications during World War II, operating on the Vernam cipher principle with twelve wheels generating a keystream. Unlike the portable Enigma, Lorenz integrated directly between teletypes for automatic five-bit ITA2 encryption. British interceptors at Knockholt first encountered its signals in 1940, later named Tunny. A critical operator error on 30 August 1941 allowed cryptanalysts at Bletchley Park to deduce the machine's structure. This led to the development of the Colossus computer in 1944 for automated decryption. The article details the χ, ψ, and μ wheel groups, the stuttering psi mechanism, and Python implementations of ITA2 encoding and XOR operations.
Inside the Fortress: Why Perimeter Security Tools Fall Short and How Microsegmentation Protects Networks Internally
Companies invest heavily in perimeter defenses such as firewalls and intrusion detection systems, yet these measures no longer guarantee safety as attackers increasingly operate from within networks. Traditional L2 domains leave virtual machines unisolated, enabling traffic interception, lateral movement, and malware spread similar to an apartment building with poor soundproofing. Microsegmentation powered by SDN divides VLANs into isolated microsegments down to individual VM ports, enforcing granular policies based on ports, IP addresses, and protocols. This approach implements Zero Trust by placing virtual packet filters directly at VM network interfaces on the hypervisor, independent of guest OS actions. Performance remains high because filtering runs on powerful virtualization servers, and scaling occurs naturally as additional hypervisors absorb new workloads without extra configuration. A real-world case from the oil and gas sector shows one customer creating up to 5,000 new microsegmentation rules per week via open REST API. The technology complements rather than replaces perimeter firewalls, delivering both strict internal controls and operational agility.
Good Bear 1.0 Released: Firefox-Based Browser with Isolated Russian PKI Trust Container
Good Bear 1.0 is a Russian-language browser built on Firefox 156.0 that provides an isolated container for handling Russian PKI certificates without mixing trust contexts or user data with the standard browsing session. The release includes .deb packages for Ubuntu 24.04 LTS amd64 and Windows x64 installers, using Mozilla Public License 2.0 and reproducible build processes from pinned Firefox sources. Instead of globally importing root certificates, the browser performs secondary chain validation only inside a dedicated userContextId container with strict OriginAttributes isolation for caches, storage, and connections. Password autofill and sensitive session data are disabled in the container when separation cannot be guaranteed, and POST requests trigger explicit user choice before reopening in the isolated context. The interface shows both a persistent container marker and a separate RU indicator only when Russian PKI is actively used, along with detailed security panels explaining the trust source. Updates, crash reporting, and automatic MAR mechanisms are intentionally omitted to avoid creating unverified trust chains for the distribution itself.