shazow/callthis

Build a transaction, send a link for someone else to execute it.

callthis.link

Build a transaction and send it as a link for someone else to execute.

---

Latest version is available on callthis.link and on IPFS via callthis.eth.

✨ Automagic proxy resolving and ABI detection is powered by WhatsABI!

Developing

If you're a fellow Nix-user, run nix develop. Otherwise, make sure you have nodejs and pnpm installed.

Run make run to serve locally, make build to build a ready-to-deploy static site.

License

MIT

callthis's Issues

Dark mode

Add footer, link to repo

Deploy!

Save a long link as an IPFS object, load IPFS object links

Would be nice to be able to save long links as an IPFS object, to support longer calldata and to create shorter links.

This opens up other usecases, like adding more metadata into the IPFS object such as proofs/signatures/branding/etc.

Reflect State Mutability

Disable value when non-payable, etc.

Feature: Multicall batching

Detect if sender is a multisig with multicall support, support batching multiple transactions?

Could even offer to bolt on an optional tiny fee?

Also useful for view multicalls.

Feature: Deploy contracts

https://warpcast.com/jayden/0x3921ee44

cc @jaydenwindle

Add Safe Support

• Add Safe App Provider

• Create a manifest.json

Additional requirements here: https://docs.safe.global/safe-core-aa-sdk/safe-apps/get-started#basic-requirements

Deploy on ENS+IPFS so that callthis.eth.link works

Will eventually be on https://callthis.eth.link

Add loading throbbers

Right now there's a bunch of things that load async with no indication

Generate QR code for sharing

MVP should work for sufficiently short links.

Improve Dark Mode

Continuation from #19:

• Check prefers-color-scheme media query to set correct mode on load
• Maybe: Save the selection via cookie/localstorage?
• Bonus: Refactor so that the relevant colorscheme variables are in one place, making it easy to create additional themes.

This site has some good code snippets: https://scriptraccoon.dev/blog/darkmode-toggle-sveltekit

Decode results

If ABI is available

Pull previous transactions from sender to generate example links

• https://twitter.com/wilsoncusack/status/1728617424801481082
• https://warpcast.com/maurelian/0xdf1af97f

Feature: Complex contract argument types

Right now tuples/arrays aren't supported, just haven't written the code for it.

Settle on a new name

Not sure I love callthis.eth

😐

Handle simple arguments

Oops, no arguments are being included in the calldata yet.

Bring your own ABI

Sometimes WhatsABI can't get the full ABI, or missing some type annotations. Would be nice to be able to bring your own ABI annotation.

Would be hard to encode this in the link (maybe just the called function hint?).

Feature: Override calldata

Maybe an advanced mode where you can override the calldata with something specific, the rest of the decoding becomes readonly?

(Right now it's the reverse: Calldata is readonly, generated from the inputs)

Improve the Trust Experience (TX)

Context: https://stark.mirror.xyz/rkLEVz9p4r3ouusD-WCkWP_iVZYkZ0K7TFkzeRfiXCU

Some ideas specific to callthis:

• Signed link shares (so you can verify that a linked transaction is from shazow.eth, not some rando)
• Show and summarize recent transactions to target address/contract
• Warn when target address is new (<1 month?) or has no prior activity
• Would be neat to have a list of addresses that can attest to the trustworthiness of another address (like a curation list) which people can subscribe to. Kinda like "community notes" for transactions?
• Link out to contract source code if available, using contractreader so it's more readable.
• ... what else?

Feature: Use hint to preload ABI

We a simple function signature in the hint are, can preload that before whatsabi is done.

Support contracts with unresolved selectors

Let people specify their own calldata for them.

E.g. 0x0000f00000627D293Ab4Dfb40082001724dB006F has a few unresolved selectors.

Explicit network switching

Right now the network is assumed from your wallet but not sure how reliable that is. We should set the network explicitly somewhere, could even force it on saved transactions.

Retain WalletConnect state across reloads

Not sure what we need to do here, maybe store a connection string?

Submit transactions

Right now it's just doing a read-only call

Add default readonly provider

Right now we don't do any default providers, just whatever you bring to the wallet.

It's nice but UX suffers. Not sure if it's worth keeping the purity.