Control & evidence · 2016 onward
DAO governance: follow the vote all the way to execution
A public vote can be transparent while power remains concentrated in delegation, proposal rights, upgrade keys or execution.
Research · History · Reference
All entries A–Z · 5 / 15
438 · Articles and references
DeFi & governance
DAO governance: transparent votes can still concentrate power
Proposal rights, quorum, delegation and execution determine who can direct the assets.
Blockchain fundamentals
Data availability
Participants need transaction data to reconstruct state and exit.
Infrastructure & ownership · Modular blockchain design
Data availability, historical storage and the limits of a hash
A commitment can authenticate data without supplying it. Publishing data now and preserving it for years are related but different jobs.
Blockchain fundamentals
Data availability: can the state be independently reconstructed?
A commitment identifies data; availability determines whether the required data can be obtained.
Scam patterns
Deepfake executive livestreams
Generated video or copied broadcasts impersonate a public figure.
Origins & history · 2018–2021
DeFi’s expansion: pooled liquidity, collateral and rented activity
Automated markets and token incentives changed how users could provide capital, and made headline growth harder to interpret.
Wallets & security
Delegatecall authority
Delegatecall runs another contract's code in the caller's storage context.
Scam patterns
Discord account takeovers
A compromised team or moderator account publishes an emergency link.
KOLs & promotion
Discounted OTC tokens promoted at market price
An influencer buys below market and promotes into public demand.
Market structure
Divergence loss: what a liquidity position gives up relative to holding
Fee income and inventory changes must be evaluated together.
Crypto history
DMM Bitcoin, 2024: a recruitment lure reached a custody workflow
The official attribution follows a fake coding test through session impersonation to a manipulated transaction request.
Scam patterns
DNS hijacking
Domain records are changed so a real name resolves to attacker infrastructure.
Web fundamentals
DNS: the name is part of the security boundary
A familiar domain must still resolve to the intended service.
Names, identity and web content
DNSSEC and HTTPS: two checks behind a wallet website
Authenticated name resolution and encrypted transport do not certify a financial application.
Scam patterns
Dust-token message scams
A token name, NFT description or tiny transfer contains a malicious URL.
Blockchain fundamentals
Economic and protocol finality
Finality defines when reversal becomes impossible or economically exceptional.
Blockchain fundamentals
EIP-1559 base fees
Ethereum burns a protocol base fee that adjusts with block utilisation.
Smart accounts and governance
EIP-4788: a beacon root is a commitment, not the whole beacon state
Ethereum exposes a consensus-layer commitment to contracts; the proof and interpretation still need work.
Smart accounts and governance
EIP-6963: choosing between browser wallets without trusting the icon
Provider discovery solves a coordination problem; names and icons remain self-reported.
Wallets & security
EIP-712 domains: what stops a signature travelling to another application?
Readable fields help, but the signed domain and replay controls still matter.
Wallets & security
EIP-7702: delegation deserves its own review
An account upgrade can change the code used when your address is called.
Names, identity and web content
ENS names: why a reverse record needs a forward check
A readable name improves navigation only when the address relationship is verified.
Wallets & security
ERC-1155: one operator approval can cover many token IDs
An approval for a collection contract is broader than permission for the item pictured on a page.
Wallets & security
ERC-1271: a contract decides whether a signature is valid
Smart-wallet signatures depend on validation logic and state, not only public-key recovery.
Research methods
ERC-165: interface support is a claim, not a security certificate
A contract recognising a function set does not prove that its implementation behaves honestly.
Wallets & security
ERC-1967: finding the implementation behind a proxy address
The address users recognise can remain unchanged while the code they execute changes.
Wallets & security
ERC-2612: a permit deadline is not an allowance expiry
The time limit governs submission of the signature, not necessarily the life of the resulting approval.
Wallets & security
ERC-4337: programmable accounts without assuming one private key is enough
Bundlers, account validation and optional paymasters split a transaction flow into distinct responsibilities.