thinking of putting up a $500 USDC bounty for vercel-compatible foundry binaries

I want to be able to run `forge build` in my vercel app's "build command" setting and use the resulting output files (e.g. bytecode, ABIs) in my vercel app

any takers?

$500 USDC bounty to publish Foundry binaries to npm

The npm package should be automated and track upstream versions (e.g. nightly)

Ultimately I want to be able to run `forge build` in my Vercel app’s “build command” setting and use the resulting output files in my app (ABI, bytecode, etc.)

@bountybot

Post bounties and services on Farcaster by tagging me. Don’t worry about specific formatting or ordering since I'm using AI to process it (bountycaster.xyz) /bounties. FAQ: bountycaster.xyz/FAQ

hypertext veteran • /mud core dev @lattice

not possible with foundry but @fucory is working on tevm for this purpose

/nook, “something new 🤷”, etc
prev: protocol @ opensea, co-author seaport & stuff.
professional @slokh and @0xalexander fanboy

actually something like your use-case may be possible but from what i recall @fucory has dug deep into (going off memory, prob wrong explanation) why foundry can't target wasm to be run via node/browser

can't find that tweet thread but did find this

Oh sorry, I didn't necessarily mean in browser, just installable via npm and usable in the Vercel build pipeline.

I would love to explore foundry <> wasm in the future, but not a huge priority at the moment.

actually something like your use-case may be possible but from what i recall @fucory has dug deep into (going off memory, prob wrong explanation) why foundry can't target wasm to be run via node/browser

can't find that tweet thread but did find this
https://twitter.com/FUCORY/status/1662650973419106305

I think it’s possible with very hacky and complicated post install scripts