The mentality of wondering why you have to ask for permission to build on permissionless stacks... is the problem? Would have been a lot easier to just answer the question with an example rather than saying I'm the problem. I'm not the problem, I assure you.
You are viewing a single comment's thread from:
it is not the permissionless stacks and asking for permission.
it is asking the chain for technical help to onboard a project.
Say a project wants to come on and connect and needs help building a HAF server and an API endpoint for there in house systems.
Let's say a current project has that working and I go. "hey can I see that code and ask you some questions" and they go no. FK off.
they have the right to do that but it sure as hell doesn't look good.
Too many people around here are focused on themselves and not the chain. Which they have the right to do, but the world does not work that way.
Yeah I understand perfectly.
What I fail to understand is how forking the chain could possibly help.
This is not an on-chain problem.
It's an infrastructure and documentation problem.
let's use this an example.
Microsoft / wotc / nintendo / sony / 30 smaller studios want to use Hive but don't like the lack of support, but love the tech.
They can fork and set themselves up as the top witnesses.
or just spin up a new chain with themselves as the top witnesses and set up a dev team made up of people from each company to help with tech.
This makes them feel better.
If we had the tech and onboarding support. 10 smaller studios could onboard to hive and show the benefits and bring the larger one's onboard.
I am working on the latter but the first option is gaining a lot of traction. the IMX presentation is going to be interesting.
Fun week next week for sure.
Fascinating... good luck with that!
Sounds like it would be REALLY easy to port tech to and from sister chains created in this way.
I think so. interesting days ahead.