Are Merkle trees still the best way to handle onchain allowlist? Anything simpler or a service to manage them?

Warpcash

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links

That's what I used for /warpcash. Found it pretty straightforward

Onchain startups. /rebase, /basedjobs and more

Yea, it doesn't seem optimal for dynamic trees. 

If you didn't want to update the contract state every time the merkle tree updates, you could have users supply a root each time they also supply a proof, and verify in the contract that the root is signed by (one of) a trusted set of addresses?

I’ve used them once before and it was ok, but for something dynamic it can be tricky because your client/server and the contract state have to stay synced, which was a pain I don’t look forward to dealing with again 😅 lol

oh, you are behind warpcash? i didn't know. will pay attention