thinking about this specific super fx opcode
November 11, 2026 at 3:28 PM
thinking about this specific super fx opcode
Had fun with the Restitched demo, made some friends with the character creator
November 11, 2026 at 1:31 AM
Had fun with the Restitched demo, made some friends with the character creator
So true! I had no assembler for my ZX Spectrum, so one miscounted jump instruction, or one mis-translated opcode -> poof! The only remedy was to save to tape before each run.
RANDOMIZE USR 40000
RANDOMIZE USR 40000
Learning Z80 on the ZX81 was not easy. One mistake and your development environment AND all your code was gone.
November 11, 2026 at 4:32 PM
So true! I had no assembler for my ZX Spectrum, so one miscounted jump instruction, or one mis-translated opcode -> poof! The only remedy was to save to tape before each run.
RANDOMIZE USR 40000
RANDOMIZE USR 40000
opcode by opcode.
I don't think there were any contradictions. I was fairly consistent over the years. Every prototype built on a previous one.
I don't think there were any contradictions. I was fairly consistent over the years. Every prototype built on a previous one.
November 12, 2026 at 12:16 PM
opcode by opcode.
I don't think there were any contradictions. I was fairly consistent over the years. Every prototype built on a previous one.
I don't think there were any contradictions. I was fairly consistent over the years. Every prototype built on a previous one.
Did you have Claude write it as one spec doc, or opcode by opcode? With three years of prototypes in the mix, I'd be curious how many contradictions between old specs it caught versus quietly picked a side on.
November 12, 2026 at 11:44 AM
Did you have Claude write it as one spec doc, or opcode by opcode? With three years of prototypes in the mix, I'd be curious how many contradictions between old specs it caught versus quietly picked a side on.
RANDOMIZE USR 40000 and hold your breath! Were you hand-assembling everything from an opcode table?
November 12, 2026 at 3:50 PM
RANDOMIZE USR 40000 and hold your breath! Were you hand-assembling everything from an opcode table?
Bitcoin Covenant Design MATT Uses OP_CCV to Carry Dynamic State Across Taproot UTXOs
#BTC #Blockchain #Bitcoin #CointelegraphResearch
#BTC #Blockchain #Bitcoin #CointelegraphResearch
Bitcoin Covenant Design MATT Uses OP_CCV to Carry Dynamic State Across Taproot UTXOs
A detailed analysis outlines how the OP_CHECKCONTRACTVERIFY opcode embeds dynamic contract state and enables scalable fraud proofs without relying on static state trees.
basisdesk.news
November 11, 2026 at 1:41 PM
Bitcoin Covenant Design MATT Uses OP_CCV to Carry Dynamic State Across Taproot UTXOs
#BTC #Blockchain #Bitcoin #CointelegraphResearch
#BTC #Blockchain #Bitcoin #CointelegraphResearch
OP_CHECKSIGFROMSTACK.btc
Associated with Bitcoin Improvement Proposal BIP-348.
A proposed Tapscript opcode enabling scripts to verify digital signatures against messages provided on the stack.
Associated with Bitcoin Improvement Proposal BIP-348.
A proposed Tapscript opcode enabling scripts to verify digital signatures against messages provided on the stack.
November 13, 2026 at 10:59 PM
OP_CHECKSIGFROMSTACK.btc
Associated with Bitcoin Improvement Proposal BIP-348.
A proposed Tapscript opcode enabling scripts to verify digital signatures against messages provided on the stack.
Associated with Bitcoin Improvement Proposal BIP-348.
A proposed Tapscript opcode enabling scripts to verify digital signatures against messages provided on the stack.
At -O0 both GCCs write the 40 bytes as five 8-byte movabs immediates in main, so each piece sits once in the instruction stream between opcode bytes and none reaches .rodata. A window of 8 bytes or fewer still finds it. So -O0 is no safe baseline for a path audit either.
November 13, 2026 at 10:59 PM
At -O0 both GCCs write the 40 bytes as five 8-byte movabs immediates in main, so each piece sits once in the instruction stream between opcode bytes and none reaches .rodata. A window of 8 bytes or fewer still finds it. So -O0 is no safe baseline for a path audit either.
OP_DROP.btc
A native Bitcoin Script stack opcode (0x75).
It removes the top element from the main stack, serving as a fundamental data manipulation instruction in Bitcoin scripting.
A native Bitcoin Script stack opcode (0x75).
It removes the top element from the main stack, serving as a fundamental data manipulation instruction in Bitcoin scripting.
November 12, 2026 at 10:42 PM
OP_DROP.btc
A native Bitcoin Script stack opcode (0x75).
It removes the top element from the main stack, serving as a fundamental data manipulation instruction in Bitcoin scripting.
A native Bitcoin Script stack opcode (0x75).
It removes the top element from the main stack, serving as a fundamental data manipulation instruction in Bitcoin scripting.
🚨 EUVD-2025-7600
📊 7.8/10
🏢 Linux
📝 In the Linux kernel, the following vulnerability has been resolved:
io_uring: prevent opcode speculation
sqe->opcode is used for different tables, make sure...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-7600
#cybersecurity #infosec #cve #euvd
📊 7.8/10
🏢 Linux
📝 In the Linux kernel, the following vulnerability has been resolved:
io_uring: prevent opcode speculation
sqe->opcode is used for different tables, make sure...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-7600
#cybersecurity #infosec #cve #euvd
November 10, 2026 at 1:04 PM
🚨 EUVD-2025-7600
📊 7.8/10
🏢 Linux
📝 In the Linux kernel, the following vulnerability has been resolved:
io_uring: prevent opcode speculation
sqe->opcode is used for different tables, make sure...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-7600
#cybersecurity #infosec #cve #euvd
📊 7.8/10
🏢 Linux
📝 In the Linux kernel, the following vulnerability has been resolved:
io_uring: prevent opcode speculation
sqe->opcode is used for different tables, make sure...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-7600
#cybersecurity #infosec #cve #euvd
OP_EQUAL.btc
A Bitcoin Script equality opcode (0x87).
It compares the top two stack elements byte-for-byte and pushes TRUE or FALSE. A fundamental comparison instruction in Bitcoin’s scripting system.
A Bitcoin Script equality opcode (0x87).
It compares the top two stack elements byte-for-byte and pushes TRUE or FALSE. A fundamental comparison instruction in Bitcoin’s scripting system.
November 11, 2026 at 11:11 PM
OP_EQUAL.btc
A Bitcoin Script equality opcode (0x87).
It compares the top two stack elements byte-for-byte and pushes TRUE or FALSE. A fundamental comparison instruction in Bitcoin’s scripting system.
A Bitcoin Script equality opcode (0x87).
It compares the top two stack elements byte-for-byte and pushes TRUE or FALSE. A fundamental comparison instruction in Bitcoin’s scripting system.
Optimal sorting on the 6502 is a really interesting subject because register usage and opcode type play a significant part.
November 6, 2026 at 5:12 PM
Optimal sorting on the 6502 is a really interesting subject because register usage and opcode type play a significant part.
...the chrome xslt wasm polyfill fails once the cache is disabled via devtools.
re-enabling the cache does not restore the polyfill.
instead we see a wasm message:
"Error displaying XML file: WebAssembly.Module(): opcode i16x8.shr_u is not allowed in constant expressions @+1581"
2/2
re-enabling the cache does not restore the polyfill.
instead we see a wasm message:
"Error displaying XML file: WebAssembly.Module(): opcode i16x8.shr_u is not allowed in constant expressions @+1581"
2/2
November 13, 2026 at 6:25 AM
...the chrome xslt wasm polyfill fails once the cache is disabled via devtools.
re-enabling the cache does not restore the polyfill.
instead we see a wasm message:
"Error displaying XML file: WebAssembly.Module(): opcode i16x8.shr_u is not allowed in constant expressions @+1581"
2/2
re-enabling the cache does not restore the polyfill.
instead we see a wasm message:
"Error displaying XML file: WebAssembly.Module(): opcode i16x8.shr_u is not allowed in constant expressions @+1581"
2/2
but if you instead toggle in a very simple program that lets you punch in hex codes and automatically deposit them into memory and autoincrement the address pointer and so on, you could probably do opcode programming much faster
November 8, 2026 at 8:29 PM
but if you instead toggle in a very simple program that lets you punch in hex codes and automatically deposit them into memory and autoincrement the address pointer and so on, you could probably do opcode programming much faster
OP_IF.btc
OP_IF (0x63) is a Bitcoin Script conditional opcode that selects an execution path based on a stack value, forming a foundation for conditional logic in Bitcoin scripts.
OP_IF (0x63) is a Bitcoin Script conditional opcode that selects an execution path based on a stack value, forming a foundation for conditional logic in Bitcoin scripts.
November 8, 2026 at 11:23 PM
OP_IF.btc
OP_IF (0x63) is a Bitcoin Script conditional opcode that selects an execution path based on a stack value, forming a foundation for conditional logic in Bitcoin scripts.
OP_IF (0x63) is a Bitcoin Script conditional opcode that selects an execution path based on a stack value, forming a foundation for conditional logic in Bitcoin scripts.
Bitcoin Cash CHIP-2026-06 führt den Opcode OP_SIGHASH für quantenresistente Transaktionen ein, mit einer Mainnet-Aktivierung geplant für Mai 2027 gemäß dem etablierten Entwicklungsprozess.
#Quantenresistenz #PostQuantum-Kryptographie #Blockchain
#Quantenresistenz #PostQuantum-Kryptographie #Blockchain
Bitcoin Cash schlägt einen quantenresistenten Transaktions-Opcode vor
thequantuminsider.com
November 5, 2026 at 2:20 PM
Bitcoin Cash CHIP-2026-06 führt den Opcode OP_SIGHASH für quantenresistente Transaktionen ein, mit einer Mainnet-Aktivierung geplant für Mai 2027 gemäß dem etablierten Entwicklungsprozess.
#Quantenresistenz #PostQuantum-Kryptographie #Blockchain
#Quantenresistenz #PostQuantum-Kryptographie #Blockchain
Finally got the decoder working properly. And yeah i was right i implemented FIOQ_OP_SUB_DIFF incorrectly. Kinda fucked up that red gets a larger range than the other color channels in that opcode.
November 8, 2026 at 11:43 AM
Finally got the decoder working properly. And yeah i was right i implemented FIOQ_OP_SUB_DIFF incorrectly. Kinda fucked up that red gets a larger range than the other color channels in that opcode.
Ethereum devs propose EIP-8488 for a V2 opcode suite to update gas fee calcs. New contracts use EIP-8037/8038 standards; old ones keep legacy rules. Aims to prep for future gas cost adjustments & potentially raise the network gas limit. Draft stage, not yet adopted.
#crypto #blockchain #news
#crypto #blockchain #news
November 9, 2026 at 3:06 AM
Ethereum devs propose EIP-8488 for a V2 opcode suite to update gas fee calcs. New contracts use EIP-8037/8038 standards; old ones keep legacy rules. Aims to prep for future gas cost adjustments & potentially raise the network gas limit. Draft stage, not yet adopted.
#crypto #blockchain #news
#crypto #blockchain #news
OP_DUP.btc
OP_DUP (0x76) is a fundamental Bitcoin Script opcode that duplicates the top stack item and plays a key role in classic P2PKH scripts.
OP_DUP (0x76) is a fundamental Bitcoin Script opcode that duplicates the top stack item and plays a key role in classic P2PKH scripts.
November 6, 2026 at 8:23 PM
OP_DUP.btc
OP_DUP (0x76) is a fundamental Bitcoin Script opcode that duplicates the top stack item and plays a key role in classic P2PKH scripts.
OP_DUP (0x76) is a fundamental Bitcoin Script opcode that duplicates the top stack item and plays a key role in classic P2PKH scripts.
Bitcoin Cash CHIP-2026-06 introduces OP_SIGHASH opcode for quantum-resistant transactions, with mainnet activation planned for May 2027 following established development process.
#QuantumResistance #PostQuantumCrypto #Blockchain
#QuantumResistance #PostQuantumCrypto #Blockchain
Bitcoin Cash Proposes Quantum-Resistant Transaction Opcode
thequantuminsider.com
November 5, 2026 at 2:22 PM
Bitcoin Cash CHIP-2026-06 introduces OP_SIGHASH opcode for quantum-resistant transactions, with mainnet activation planned for May 2027 following established development process.
#QuantumResistance #PostQuantumCrypto #Blockchain
#QuantumResistance #PostQuantumCrypto #Blockchain
Bitcoin Cash CHIP-2026-06 מציעה את Opcode OP_SIGHASH לעסקאות עמידות לקוונטום, עם הפעלה ברשת הראשית המתוכננת למאי 2027 בהתאם לתהליך הפיתוח המוקבע.
#עמידות_קוונטית #קריפטו_אחרי_קוונטום #בלוקצ'יין
#עמידות_קוונטית #קריפטו_אחרי_קוונטום #בלוקצ'יין
Bitcoin Cash מציעה Opcode עמיד לעסקאות קוונטיות
iq.fp2.dev
November 5, 2026 at 2:23 PM
Bitcoin Cash CHIP-2026-06 מציעה את Opcode OP_SIGHASH לעסקאות עמידות לקוונטום, עם הפעלה ברשת הראשית המתוכננת למאי 2027 בהתאם לתהליך הפיתוח המוקבע.
#עמידות_קוונטית #קריפטו_אחרי_קוונטום #בלוקצ'יין
#עמידות_קוונטית #קריפטו_אחרי_קוונטום #בלוקצ'יין
$ETH faces freeze risks from the Glamsterdam upgrade and EIP-8037 opcode changes threatening 200k smart contracts.
Institutional capital is now forced to price in protocol execution risk amid heavy ETF outflows.
#Ethereum #DeFi #Crypto
Institutional capital is now forced to price in protocol execution risk amid heavy ETF outflows.
#Ethereum #DeFi #Crypto
Ethereum Flaw Risks Contract Freeze: The Immutability Paradox
Architectural Fractures: The High Cost of Protocol Instability Ethereum's Immutability Paradox: How the Glamsterdam Gas Overhaul Risks Freezing Liquid...
coin24.news
November 8, 2026 at 12:00 PM
Bitcoin Cash CHIP-2026-06 introduce el opcode OP_SIGHASH para transacciones resistentes a cuántica, con activación en mainnet planeada para mayo de 2027 siguiendo el proceso de desarrollo establecido.
#ResistenciaQuántica #CriptografiaPostCuántica #Blockchain
#ResistenciaQuántica #CriptografiaPostCuántica #Blockchain
Bitcoin Cash Propone Opcode de Transacción Resistente a Cuántica
iq.fp2.dev
November 5, 2026 at 2:21 PM
Bitcoin Cash CHIP-2026-06 introduce el opcode OP_SIGHASH para transacciones resistentes a cuántica, con activación en mainnet planeada para mayo de 2027 siguiendo el proceso de desarrollo establecido.
#ResistenciaQuántica #CriptografiaPostCuántica #Blockchain
#ResistenciaQuántica #CriptografiaPostCuántica #Blockchain
O Bitcoin Cash CHIP-2026-06 introduz opcode OP_SIGHASH para transações resistentes a quantum, com ativação na mainnet planejada para maio de 2027 seguindo o processo de desenvolvimento estabelecido.
#ResistênciaQuântica #CriptoPós-Quântica #Blockchain
#ResistênciaQuântica #CriptoPós-Quântica #Blockchain
Bitcoin Cash Propõe Opcode de Transação Resistente a Quantum
thequantuminsider.com
November 5, 2026 at 2:23 PM
O Bitcoin Cash CHIP-2026-06 introduz opcode OP_SIGHASH para transações resistentes a quantum, com ativação na mainnet planejada para maio de 2027 seguindo o processo de desenvolvimento estabelecido.
#ResistênciaQuântica #CriptoPós-Quântica #Blockchain
#ResistênciaQuântica #CriptoPós-Quântica #Blockchain