Custom Smart Contract Vault

Okay, so I scratched my previous idea about making my own MultiSig, decided to make my own Vault instead who's code won't be available on Etherscan for privacy reasons.

First of all I shared the call function at the bottom of this post so you can understand how I'll be interacting with the contract.

The idea is simple, I'll need a function to withdraw ETH, ERC-721 & ERC-20 Tokens, additionally I require this call function defined in order to claim future airdrop or whatever use-case I may need with the smart contract.

So here's what I'm thinking rn... Let's say the Owner Wallet (mine) of this Vault gets hacked right?

​

The wallet is empty and has nothing in it except $ETH for gas, so how on earth will the hacker know how to withdraw funds from this SC if I make the function names completely random and/or use a proxy to setup the SC?

I know this might NOT be the safest thing to do, however even if my key is compromised I can still send transaction using MEV relays to avoid my txns getting cancelled from the attacker monitoring the mempool..

​

So what do you guys think? Is this a viable option? The safest thing I'm counting on here is the hacker not knowing that this contract that I deployed is only accessible by its owner and he will also need to figure out which call function is the proper one. I think it might actually work.

​

Here's the call function I am looking to add:

function call(address payable _to, uint256 _value, bytes calldata _data) external onlyOwner payable returns (bytes memory) {

require(_to != address(0));
(bool _success, bytes memory _result) = _to.call{value: _value}(_data); require(_success);
return _result;

}