Practical overview
When it fits
Use DSProxy when a smart-contract workflow needs owner-controlled execution through a proxy or needs custom script contracts to make multiple actions atomic.
Who it is for
- Ethereum developers building smart-contract workflows that need proxy-based execution.
- Application teams that want to group contract actions into an all-or-nothing transaction.
- Developers using Solidity with Dapphub's dapp and seth tools.
Documented uses
- Execute a contract function through an owner-controlled proxy identity.
- Bundle a sequence of contract actions into one atomic transaction.
- Use a proxy-level ownership model for internal calls that authorize the proxy.
Requirements & limits
- Execution uses Solidity contract bytecode, calldata and delegatecall.
- The repository's example uses dapp, seth and solc.
- A DSProxy can be deployed directly; deploying a DSProxyFactory and building a proxy is another documented route.
- The repository metadata lists the GPL-3.0 license.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare a custom contract call for DSProxy
Compile a custom contract and prepare the bytecode and calldata to submit to a deployed DSProxy.
Before you start
- A deployed DSProxy, or a DSProxyFactory if using the factory route.
- Dapphub's dapp and seth tools.
- solc to compile the custom contract.
Steps
Deploy DSProxyFactory, or deploy DSProxy directly.
If using the factory, call its build function to create a proxy.
Create and compile the custom contract with dapp.
Use seth calldata to encode the target function and arguments.
Submit the contract bytecode and calldata to the deployed proxy's execute function.
Expected outcome
The example's inputs for invoking a custom contract function through DSProxy are prepared and submitted.
Guide limitations
- The example assumes use of dapp and seth and requires a compiled contract and deployed proxy.
- The factory route is optional; the README does not provide a complete application-specific script contract.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- dapphub/ds-proxy · Official homepage title · retained in its source language

