A few years ago, [Smashcat] ported a ZX Spectrum game called Manic Miner to the Arduino Uno. The Arduino has less memory than the original Spectrum did, so doing all this on an 8-bit microcontroller was no easy lift. Since then, parts of this original port have been adapted to produce a game engine, allowing [Smashcat] to port several other games to the Arduino Uno as well.

The engine is able to host a 2D map with the ability to scroll, at a resolution of 256×256, as well as up to nine sprites at the same time. The graphics are locked to 50 FPS, but only with a real Arduino Uno that has a crystal oscillator. Some replica boards do not have a timekeeping chip accurate enough to replicate the video signal, which is done without a framebuffer. That signal, as well as two PWM audio channels, are still generated directly as well, with only a few resistors needed to hook everything up to a monitor and a controller, including the option of using an NES controller.

With all of that running on the Arduino and it hooked up to the daughterboard that provides the controller interface as well as the resistors for the video signal to function and a driver for a speaker, the system now runs the original Manic Miner as well as three other games: Scramble, Space Invaders, and Pac Man.

The engine and the rest of the code are available on a GitHub page as well, and there’s even a WebAssembly version available to run various pieces of the software without the specific hardware. The original ZX Spectrum was an interesting machine too that still inspires builds like this, despite it being well over 40 years old now.

Fhenix launches CoFHE on Ethereum and Arbitrum mainnets, enabling encrypted smart contract computation for confidential DeFi and tokenized assets.

Electrum disclosed a wallet flaw on October 24 that could turn a Bitcoin fee adjustment into an unintended payment. Its advisory explains how an apparently routine approval became dangerous.

TL;DR

• Version 4.8.3 fixes the flaw.
• Downloads are available from Electrum’s official site.
• Each transaction approval still needs its destinations and amounts checked.

The dangerous moment came after the original payment

The developer advisory describes malicious servers substituting an unconfirmed wallet-history entry. A user who then approved a replacement transaction to raise its fee could authorize payment to an attacker. Developers reported two affected users, including one who lost money; the disclosure does not establish a total loss figure.

That distinction makes the incident different from someone simply stealing a private key. The wallet owner could make the correct initial payment and still encounter a dangerous second signing request. Checking an address once does not authenticate every transaction a wallet might subsequently ask the owner to approve.

Electrum’s documentation explains the underlying trade-off. Its lightweight client uses servers to retrieve transaction information, including unconfirmed activity, while confirmed transactions receive separate verification. Users avoid running a complete node, but the interface still needs to treat remote data carefully.

The issue adds a practical consumer example to the software-maintenance questions raised in NewsBTC’s coverage of Bitcoin Core’s changing disclosure rules. A security update is useful only once the software people actually use incorporates it.

Version 4.8.3 closes the wallet-history weakness

The official Electrum site now lists 4.8.3 and signed downloads. The project specifically directs users to its own domain and signature-verification process. Downloading an alleged fix from an unsolicited message would introduce a separate risk at precisely the moment users are trying to remove one.

Updating does not reverse a Bitcoin transfer already confirmed to the wrong recipient. Nor should an unexplained transaction-history entry be treated as proof that a legitimate recipient has received funds. The practical task is to establish what was actually broadcast and authorized before taking further action.

NewsBTC’s reporting on shared-key Bitcoin collateral and insured custody arrangements addresses other ways of controlling asset risk. This incident concerns the signing workflow itself: even strong custody arrangements need an accurate description of what a signature will authorize.

The broader lesson is concrete. A fee increase is still a new transaction approval, with recipients and amounts that deserve a fresh check. The patched wallet reduces the danger from this specific deception; it does not make transaction review unnecessary.

Written by the News Desk and edited by Samuel Rae.

Czech company KBP International has unveiled GRYF, a long-endurance drone designed to carry interceptor drones and small missiles aloft so it can hunt down hostile unmanned aircraft, presenting the aircraft on Oct. 21, 2026, at the Future Forces Forum in Prague in the presence of Czech President Petr Pavel. GRYF works as a flying weapons […]

TL;DR: Arbitrum representatives have presented the network’s infrastructure and revenue model to European financial institutions managing substantial assets. The meetings should not be confused with confirmed investment commitments to ARB.

Arbitrum is increasingly pitching itself as a blockchain infrastructure business rather than simply another cryptocurrency ecosystem.

During institutional meetings reported on October 16, representatives discussed the network’s commercial potential with European banks, wealth managers and other professional investors. The participating organisations were said to represent more than €800 billion in assets under management.

That figure describes the institutions attending the presentations. It does not represent money invested in Arbitrum or its native token.

Explaining The Business Behind The Blockchain

The discussions placed particular emphasis on how blockchain infrastructure can earn fees through licensing, network services and support for financial applications.

Research presented alongside WisdomTree material explored Arbitrum’s financial performance and the possibility of building sustainable revenue rather than relying on speculative token trading.

Institutional projects using Arbitrum technology are one possible route toward such a model. They demonstrate how a financial business might adopt blockchain infrastructure without requiring its customers to trade ARB directly.

Arbitrum’s community has also discussed new ways to generate revenue for its DAO treasury.

Interest Is Not Adoption

The meetings do not confirm that any participating bank has committed to deploy the technology, purchase tokens or establish a product.

For Arbitrum, the next task is converting conversations into actual commercial integrations. Banks will demand clear answers about reliability, compliance, privacy and the economics of using blockchain rails.

Still, the change in emphasis is notable. Blockchain companies increasingly want to be assessed on the value of the services they provide, not simply the price of their coins.

Written by the News Desk and edited by Samuel Rae.

In the 8-bit home computer boom of the early 1980s, Sir Clive Sinclair’s machines were always among the cheapest on the market, often packing a surprising level of sophistication in their limited hardware. If there was one component that was key to their success it was the Ferranti ULA, or Uncommitted Logic Array, a clever way to make an ASIC from a chip containing a library of logic parts ready made. The Sinclair ULAs have been reverse engineered, but their full details have remained a mystery. Until now it seems, because here’s [Happy Little Diodes] with a treasure trove of original Ferranti design documents covering all the Sinclair parts.

The documents were picked up on eBay, and contain folders with printouts, engineering drawings, and hand written design notes. They cover the full range of Sinclair products of the era, including the ZX81 and Spectrum, the ZX printer, the Microdrive, the Spectrum Interface 1, and even the curious little flat screen TV. Oddly the IP is now held by the satellite broadcaster Sky as the holder of Amstrad’s portfolio, but fortunately Sky have recognised their historical importance and allowed their sharing with minimal changes. They’re all catalogued with download links in a Google spreadsheet, so dig in and see what you can find. Of particular interest are the ULAs that haven’t been reverse engineered yet, and the subtle differences between different versions of the same ULA as the engineers tried to fix bugs. The video is below the break.

If you’re curious about the ULA and Ferranti, we linked to a period film about it.

As cloud environments grow more complex and agencies manage increasingly sensitive data, how can they strengthen security, mitigate risk and maintain mission readiness?