- Yeah that sounds more realistic.
- I don't think that's a real problem in the end, stakeholders can remove their vote at any time if the project drags for too long and stops adding value. Ofc, each stakeholder can judge of that independently, just my two cents. As a proposal leader, I'd rather spend my time working on development than being constantly campaigning; that's also a waste of resources.
- Agreed on that
- Your last paragraph > I'd actually think that what you said on 3/ makes more sense to me, identifying waste and cutting it rather than trying to cut everywhere. Big projects cannot really be completely switched off and on at will. Talents will leave, and it's not easy to find good devs who know how to develop on Hive. Training others takes time and costs resources. Having crypto-related Apps on iOS and Android also requires a company to publish the Apps. Just adding these things here because I'm not sure everyone would necessarily think about that.
It's good to talk about these things, glad we're having this discussion.
1/ maybe, though I've done this many times it's a long and thankless task when you don't have the support of the biggest whales. I guess I'll just have to get back to it since we've just lost our funding.
3/ I was mostly talking about devs being employed by the projects, not project owners.
1/ seems ur funded again
3/ im referring to both. stake holders diluted to keep "talent" around is a totally unacceptable scenario to both the reputation of Hive builders and stake holders. Like i say, DHF outflows must be cut, and we can maybe find a balance where everyone can win and the people both voting for and receiving DHF outflows may have a chance to save their reputations as people who can avoid Zumbabwe style money printing into oblivion. Have no doubt that the votes and DHF outflows are on chain and everyone can see who is contributing to the situation.