prb-proxy
prb-proxy copied to clipboard
PaulRBerg
Proxy contract to compose Ethereum transactions
## Description There is a possibility to bypass the access-control check in `execute` function. The function itself performs a delegate call to the user-specified address with the specified data. As...
## Description If we already have a set of contracts deployed to a chain, and we modify only the `PRBProxyRegistry` contract, we run into trouble. The `PRBProxy` and `PRBProxyFactory` contracts...
See [common-changelog.org](https://common-changelog.org/).
As per @gakonst's comment [here](https://github.com/paulrberg/prb-proxy/issues/33#issuecomment-1129407690), the deterministic deployment proxy is now available on both Arbitrum and Optimism.
Gotta find a workaround for this: https://github.com/Zoltu/deterministic-deployment-proxy/issues/7.
The tree in [execute.ts](https://github.com/paulrberg/prb-proxy/blob/a9b60ce2bd2beb0068b8d4a95af61ba10e318add/test/integration/prbProxy/effects/execute.ts) has many leaves.
The `computeProxyAddress` is currently available only internally, via the `Base_Test` contract. I should make it publicly available via a `Utils.sol` file under `test/utils`.
done here: https://github.com/PaulRBerg/prb-proxy/pull/190 in the PR I describe the change that was made!
References: - https://github.com/sablier-labs/v2-core/issues/621 - https://github.com/sablier-labs/v2-core/discussions/647 - https://github.com/sablier-labs/v2-core/pull/642