Thanks for the quick reply ! I must admit I think in business terms rather than being technically competent when it comes to coding. My guess is that it might be easier to code on layer 2 - after all, we've got Hive Engine already.
But if it's on Hive Engine things we'd need to think about are anti-extraction mechanisms that still help people to build their actual HIVE (and the anti-extraction still works), and we'd still need to find a way to fund it and keep the price of the token used stable or pegged to HIVE. Tribe tokens are notorious for losing value !
The additional issue of doing it on layer 2 is that it adds complexity, and I think unnecessary over-complexity combined with poor information provision is a key driver in pushing new users away.
Layer 2 tokens are a difficult puzzle, but they are also a lot easier to deploy. They don't need consensus from the whole chain.
Soon (I hope), I'm going to be hosting a podcast with some Hivens that have solved tokenomics on top of Hive. It's the bricks one would need to then implement anything else on top of.