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

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

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?

If the allowlist is changing frequently, it’s pretty common to use a server-provided signature in place of the merkle tree altogether. Essentially the oracle pattern

Here’s a sample implementation:

A token airdrop claimer in 48 lines of Solidity. 
This is the power of the EVM. https://t.co/wuxZW0krQ1

vectorized.eth

If the allowlist is changing frequently, it’s pretty common to use a server-provided signature in place of the merkle tree altogether. Essentially the oracle pattern

Here’s a sample implementation: https://x.com/optimizoor/status/1878595257941803381?s=46

Ooo that’s an interesting approach, might look into that