Foundry

can someone explain how forge's vm.parseJson works bc i do not get this shit at all

prev: /nook, protocol @ opensea, co-author seaport & stuff.
professional @slokh and @0xalexander fanboy

building /nook – farcaster & more. prev: protocol @ opensea, co-author seaport & stuff. professional @slokh and @0xalexander fanboy

ok, sorted, i think
issues i was running into:
- treats all props that start with a 0x-prefixed hex string of length 42 as type address when decoding, get fucked otherwise
- this means it also breaks if any prop starting with a 0x-prefixed hex string of length 42 has extra trailing non-hex chars (bc get fucked)

i dared to store an address as a string in a field that i always want to be parsed as a string and never as an address

Tricks with polynomials and Riemann-Roch spaces. Breaking into the platonic realm to pillage forbidden abstractions. Starknet grantee.

i dared to store an address as a string in a field that i always want to be parsed as a string and never as an address https://warpcast.com/emo.eth/0x9e177eec