wannabehero/superhack

Shortcuts – The Public Good for onchain interactions

superhack's Issues

Add autocomplete and validation for templated values

Actions allow to use {argument} as a value when defining a shortcut.

Right now it's implied that {argument} exist among shortcut's inputs.

We need to validate that before creation, and also add autocomplete for the action fields (you either enter plain value or a {templated} one which should be displayed in some fancy way.

Add dynamic inputs

It's worth adding some dynamic and "system" inputs.

We can prefix them with $ (or other) to label them as "reserved"

Some of the simple ideas I had:

• current wallet (executor) address: {$executor}
• current chain id: {$chainId}
• current action's contract address: {$contract}

Create shortcuts from transactions

We should allow creating actions from my previous transactions (present an option and a list) or by referencing any onchain transaction (populate values from tx hash).

Handle struct inputs

Base "Stand with Crypto" NFT is minted via claim(...) call on this contract: 0x874ad7c13935f73c7bbe94efbd8e766de2a585eb

My tx: https://basescan.org/tx/0x02ea820ee2d81af4f58f44184a13d5736e4ecb68580c3a8a9689a7a3bc0ad0a8

One of the args is a struct (uint256, uint256, address) and we show it as a tuple:

We should allow to set individual values inside for all struct components and encode them accordingly both for Safe and EOA calls.

Bookmarks on iOS loose inputs on save

Explore gasless shortcuts

See how we can add gasless shortcut execution

Explore Cross-Chain calls

Explore and create new tickets for:

• execute shortcuts from other chains
• add cross-chain actions – shortcuts can contain actions from different chains

Allow to use results of `view` functions as action inputs

I imagined that we can define inputs for shortcuts not only by name: type as we do now, but also name: <view_function_result>.

<view_function_result> is another action that points to the contract and accepts arguments, but selects a view or pure function from the contract. It can also reference another view_function.

Before executing an action, all inputs should be resolved. Right now it works for ETH value and ENS names – view functions should work in a similar fashion: making an RPC call to set a value.

Batch simulation

Right now Simulate only works work with one action at a time.

We should fix it for complex shortcuts so all actions simulated in batch