EIP-712 (typed data signing)
Related service Blockchain & smart contracts
DEFINITION
Ethereum standard for signing structured data · MetaMask renders it human-readably (not a hex string). Foundation of gasless meta-transactions.
- Smart contract→
Code running on a blockchain (Solidity, Rust) that auto-executes an agreement. A single bug can cost nine figures · why we audit, fuzz, and threat-model before deploy.
- Solidity→
The primary language for EVM-compatible blockchains (Ethereum, Arbitrum, Base). Pascal-like syntax, low-level memory handling, TS-compatible toolchain (Foundry, Hardhat).
- EVM (Ethereum Virtual Machine)→
The shared execution environment across Ethereum and compatible chains (Arbitrum, Base, Polygon, Optimism). Writing a contract here means it runs on all of them.
- L2 (Layer 2)→
A secondary network (Arbitrum, Base, Optimism, zkSync) settling on Ethereum (L1) but much faster and cheaper. Rollups bring 10-100× lower gas.
- Invariant test→
A test that verifies a universal rule ('sum of user balances always equals total supply'). Feeds the contract random transaction sequences; the rule must hold in every state.
- Fuzz test→
Running millions of pseudo-random inputs through a function to find a combination that breaks it. Echidna or Foundry fuzz campaigns.
- 0114 May 2026The 2026 smart contract security checklist before you ship→
- 0214 May 2026Blockchain Without the Hype: Where It Actually Helps→
- 0330 Apr 2026Smart contract audit pricing in 2026: €4k vs €15k vs €60k→
- 0429 Apr 2026NIS2 readiness for EU SaaS · the 90-day playbook→
- 0526 Apr 2026OWASP LLM Top 10 v2 · what changed and what to ship→
- 0626 Apr 2026The CSP we ship · with notes on why each directive is there→
- 0722 Apr 2026Signed-firmware OTA pipeline · the 2026 default we ship→
- 0822 Apr 2026Agentic AI · the safe tool-use pattern we ship by default→