What & Why
Many protocols handle the native token through the IWETH interface.
Thus making SETH compatible with that interface could facilitate integration of the native token wrapper.
Also, there's currently no canonical way to query if a SuperToken is the native token wrapper.
How
Since the SETH specific methods are implemented in the proxy contract itself (which we can't change for existing deployments), this would require a variant of the SuperToken logic containing the wanted methods. To be considered in the tooling for supertoken upgrades.
Note: the ancient deployments on Polygon and Gnosis Chain may be different from more recent ones.
What & Why
Many protocols handle the native token through the IWETH interface.
Thus making SETH compatible with that interface could facilitate integration of the native token wrapper.
Also, there's currently no canonical way to query if a SuperToken is the native token wrapper.
How
Since the SETH specific methods are implemented in the proxy contract itself (which we can't change for existing deployments), this would require a variant of the SuperToken logic containing the wanted methods. To be considered in the tooling for supertoken upgrades.
Note: the ancient deployments on Polygon and Gnosis Chain may be different from more recent ones.