Merge registry with factory + move transferOwnership
to registry
#81
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As discussed in #79, and alluded to in #80, this PR merges the registry with the factory, and moves the
transferOwnership
function to the registry so that the proxies mapping can get updated when ownership is transferred.This PR addresses the concern raised by @razgraf regarding the soundness of the
currentProxies
mapping. Now, the proxy returned bygetProxy
(the successor ofgetCurrentProxy
) is definitely a proxy owned byowner
.But this PR solves the problem in a non-disruptive way, i.e. it will still be possible to transfer ownership (via the registry).
Deployment Cost
The deployment cost has lowered a bit (by 12k gas).
In
v4.0.0-beta.1
, the cost was ~528,529, whereas with the version in this PR, it costs ~516,709.