The smart contract changes — Lido DAO Token
Who can replace the code or create new tokens, and do the documents describe it?
For Lido DAO Token, the documents we archive answer none of the 3 questions that matter for this event.
What the contract shows
| In the code: Replace the code | Not found by our check | block 26454387, read 20 Nov 2026, 06:02 UTC |
| In the code: Create new tokens | generateTokens(address,uint256) | block 26454387, read 20 Nov 2026, 06:02 UTC |
| In the code: Hand over control | changeController(address) | block 26454387, read 20 Nov 2026, 06:02 UTC |
| Contract code can be replaced (proxy) | Not detected by our standard checks | block 26454387, read 20 Nov 2026, 06:02 UTC |
Contract and documents side by side
In the code: generateTokens(address,uint256). The documents we archive do not answer “Issuing new tokens”. This needs an explanation, not a conclusion.
In the code: destroyTokens(address,uint256). The documents we archive do not answer “Freezing and blocking”. This needs an explanation, not a conclusion.
What stays unknown
Questions about Lido DAO Token
Can the LDO smart contract be changed?
The archived documents do not answer this as of 20 Nov 2026; AsOf lists it as Unknown.
Who can create new LDO tokens?
The archived documents do not answer this as of 20 Nov 2026; AsOf lists it as Unknown.
Can LDO be frozen, and by whom?
The archived documents do not answer this as of 20 Nov 2026; AsOf lists it as Unknown.