The smart contract changes — Aave
Who can replace the code or create new tokens, and do the documents describe it?
For Aave, 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 | upgradeTo(address); upgradeToAndCall(address,bytes) | block 26454386, read 20 Nov 2026, 06:02 UTC |
| In the code: Create new tokens | Not found by our check | block 26454386, read 20 Nov 2026, 06:02 UTC |
| In the code: Hand over control | changeAdmin(address) | block 26454386, read 20 Nov 2026, 06:02 UTC |
| Contract code can be replaced (proxy) | Yes | block 26454386, read 20 Nov 2026, 06:02 UTC |
| Current code (implementation) | 0x5d4aa78b08bc7c530e21bf7447988b1be7991322 | block 26454386, read 20 Nov 2026, 06:02 UTC |
| Who can replace the code (proxy admin) | 0x86c3ffee349a7cff7ca88c449717b1b133bfb517 | block 26454386, read 20 Nov 2026, 06:02 UTC |
| Who controls the proxy admin | 0x17dd33ed0e3dd2a80e37489b8a63063161be6957 | block 26454386, read 20 Nov 2026, 06:02 UTC |
Contract and documents side by side
In the code: upgradeTo(address), upgradeToAndCall(address,bytes). The documents we archive do not answer “Upgrading the contract”. This needs an explanation, not a conclusion.
Requires explanation The contract is an upgradeable proxy: its code can be replaced at the same address. The documents we archive do not answer “Upgrading the contract”.
What stays unknown
Questions about Aave
Can the AAVE 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 AAVE tokens?
The archived documents do not answer this as of 20 Nov 2026; AsOf lists it as Unknown.
Can AAVE be frozen, and by whom?
The archived documents do not answer this as of 20 Nov 2026; AsOf lists it as Unknown.