How the MUSHROOM ERC-20 example splits transfer fees—and what its tests check
A source article published November 12, 2026, at 16:07 UTC+8 presents a MUSHROOM (SHROOM) example contract built with…
-
Shaw Says Previously Posted pump.fun Code Was Not Open Source
-
Foundry Nightly (November 12, 2026): Forge, fuzzing, Anvil and Tempo changes
-
Binance to change order quantity increments for 23 spot pairs: what bot users should check
-
AI Formal Verification for Smart Contracts: What the Check Can Show
-
Foundry nightly of 10 November 2026 records forge, anvil, cast, and fuzz changes
-
Bitcoin’s Proposed Quantum Landmines: How Collateral Could Deter Key Theft
-
Base Denim upgrade: what changes for Flashblocks apps, timestamps and B20 tokens
-
Slang alpha for Hardhat 3: reported compile-time gains and current limits
Further reading
-
Solidus: What Paradigm’s Verified Solidity Compiler Proves—and What Remains Unfinished
-
Bitcoin PACTs explained: timestamping key control before a possible quantum sunset
-
Solidity Interview Repository Hid Malicious VS Code Terminal Profiles: What to Check
-
PHP2Shell: A Patch-and-Verification Checklist for Web3 Services
-
Fomo Bookmark Phishing: How a Fake CAPTCHA Targeted Embedded-Wallet Credentials
-
Lighthouse v8.3.3: High-priority security update for beacon nodes
-
Space and Time Enterprise: Verifying Private-Data Calculations Without Opening the Database
-
Ethereum gas: distinguish work, price, and spending caps
Read more
-
Smart contracts: inspect the rules and the people who can change them
-
Token approvals: understand the permission before the swap
-
Token supply: read minting, burning, vesting, and circulation separately
-
Token decimals: translate raw balances without changing value
-
Stablecoin mechanics: identify the route back to the target value
-
Stablecoin reserves: read the assets, liabilities, and access terms
-
DeFi collateral: calculate the buffer before borrowing
-
AMM liquidity: what a pool position actually owns
All articles
-
Oracle design: examine where a protocol gets its facts
-
Blockchain bridges: trace the claim on both sides
-
Rollups: separate execution speed from settlement guarantees
-
Data availability: why a valid commitment is not enough
-
Protocol governance: follow a proposal through to execution
-
Multisig wallets: a threshold is only the beginning
-
Wallet backups: test recovery before you need it
-
Crypto phishing: inspect the requested authority, not the urgency