Transaction Presets or History

[sambarnes]

Describe the bug feature

Don't know if this would be out of scope or not, but your tweet a while back made me think about the difference between the two styles:

In general, I like the structured & strongly typed inputs much more. However a solid benefit in Etherscan style is being able to easily store presets in a text file and paste in the whole thing in one go. Something that's a lot more manual in blacksmith rn

I was thinking some sort of presets/bookmarks for recent calls made. Thoughts?

Curious if the "postman-for-contract-dev" is the route you're aiming for with the project? Or if it's more trying to target the scaffold-eth style of being a template/foundation to build your dapp off of? I imagine the functionality could be useful in either, but implementation different depending on usecase.

[unholypanda]

@sambarnes thanks for taking the time to write this up and sorry for the slow response!

However a solid benefit in Etherscan style is being able to easily store presets in a text file and paste in the whole thing in one go. Something that's a lot more manual in blacksmith rn

+1 I've been brainstorming different solutions to this problem for a while now, mostly from a UI/UX perspective. I really like your idea of "presets/bookmarks for recent calls made". I hadn't considered that and I think it could live alongside other solutions I had in mind. The trickiest part of this might be figuring out where this lives in the user interface. At one point in time I had a bottom drawer similar to the browser devtools where I intended to have transaction history, but I was encountering quite a few design limitations and decided to remove it for the initial release.

Curious if the "postman-for-contract-dev" is the route you're aiming for with the project

This aligns more with the long-term vision I had for Blacksmith, and I really like the framing of this as Postman for contract development.

Thanks for raising this question, its making me realize that I should probably document my roadmap for Blacksmith somewhere (possibly in the GitHub Discussions section of the repo).

Also for the sake of consistency and triaging purposes I'm going to label this as enhancement rather than bug.

[sambarnes]

and sorry for the slow response!

heh no worries at all! you've been super timely 🙏

The trickiest part of this might be figuring out where this lives in the user interface. At one point in time I had a bottom drawer similar to the browser devtools where I intended to have transaction history, but I was encountering quite a few design limitations and decided to remove it for the initial release.

yeah i was struggling to imagine exactly where it would live too -- initial thought was a second list in the side bar section, but felt that leaks kinda far outside of where transactions are made, so probably not great

best i could guess was some sort of dropdown inside a given method signature, organizing the presets under the relevant method... but I'm far from a good frontend/ux dev so its literally just a guess :)

I should probably document my roadmap for Blacksmith somewhere (possibly in the GitHub Discussions section of the repo).

would love to hear more of your thoughts on this, will be on the lookout for it!

A web3 postman definitely feels like an unfilled niche. I think the foundry x wagmi collab is supposed to be for bootstrapping dapps vs being a devtool, right? With that coming out sometime soonish, it'd probs be useful to lay out what blacksmith is/isn't, or where it can supplement other tooling.

---

ahh and yep i was looking to do an enhancement label but only saw bug/vuln in the new issue menu, completely missed the blank issue footnote

"Don’t see your issue here? Open a blank issue."