Glossary
Transparent Proxy
An upgradeable-proxy pattern (OpenZeppelin TransparentUpgradeableProxy) where the admin can only upgrade, never call functions — preventing selector clashes.
In a transparent proxy, the admin address can call only the proxy's own admin functions (upgrade, change admin). Everyone else is delegated to the implementation. The split eliminates the "selector clash" risk where an admin function on the proxy might collide with a function on the implementation.
OpenZeppelin's TransparentUpgradeableProxy is the canonical
implementation. The trade-off is the gas cost of the admin check
on every call, which is why newer protocols often prefer the UUPS
pattern.