Appreciate the answer!
Looking back over the proposal; it's sadly a huge text-wall - technical important stuff, mixed with marketing/ELI5 text. It would certainly help to get your point across if you'd keep things short and to the point. I'm already reading code all day, man :D
I'd appreciate it if you could quickly answer the following questions:
- Do you already have a code-base or existing architecture that can be "forked"?
- BSC and BNB have both native gateways. Are you planning the same for HIVED and HSC?
- What tech-stack/language are you going to use? JS/Node would be kinda slow.
- What's your current status? Research?
- What's the current funding amount going to pay for? And what amount do you expect for the project to cost in total?
- Do you have a timeframe when we can expect an Alpha product?
I've not got a working code-base yet sadly. Was doing most of the initial research and tinkering on a custom "Geth" version. Will work on getting a repository online for this before the end of the weekend.
By native gateways do you mean the ERC-20 <-> BEP2 bridging that's been worked out for it? Was certainly something that I came across in research and bookmarked but haven't fully looked into how it all works. It would be silly not to have something like this eh?
Started using GOlang although ideally something like C++ would be used down the road. Have looked briefly into NodeJS implementations of Ethereum but given Javascript number handling is basically aids likely going to shy away from that side of things..
Current project status: Exploring multiple implementations of the Ethereum protocol on a handful of languages in comparison and also as exploratory research. Awaiting bobinson to get back to me to look at an example of an already EVM stack running on graphene. Had a number of different node types built and running locally trying to find optimal block times.
The current funding will be going towards compensating developers putting active hours into the project development. Total cost to get the side chain running should not exceed the value of the proposal. As for cost of hardware to run nodes initially it should be low, although might become larger assuming developers use it like a DB as seems to be the case with ETH.
Absolute earliest I'd dare speculate the beginning of alpha testing occurring is a month and a half or two months from now. Might have something working earlier than that, likely will be running testnets during developing within the next 2-3 weeks.
Bah, you said it! Needs more pictures and TL:DR's.. Noted!
Thank you for the questions. I know you're a busy man but if once I get a repository up and running here you want to hop in and throw some code around would certainly be grateful. More the merrier and in a day or so I'll have a better overview of who all is interested in giving the project development a hand then we can start attacking this thing to get it running and ready for testing.
I completely agree with the sentiment. I feel like you're waaay underestimating the difficulty of the task.
The fact that you're using "simply" and almost thinking of it as putting two existing lego bricks together. shows that you don't see how hard it is to build it. You mentioned that you want to fund it with other devs but which other devs are on board ?
I think wolf is right that a poc would go a long way before requesting funding.
Also overall I think there is no point in funding 50 different side chains at the same time, @blocktrades is building one, hive engine is there, decentralized fiat has one etc.
There is just no need for yet another one, imho we should just converge together to work on one or two instead of spreading thin.
I looked at the 6 or so different sidechains being built and asked myself "are any of these offering what ETH, BnB and countless other chains that are attracting millions and millions of dollars volume daily doing?"..
As far as I know no one was making a side chain that was going to be compatible with all existing popular smart contract code and also use HIVE as it's utility currency.
If a bunch of people are building side chains to add functionality to HIVE that is great, will certainly try to build interfaces with all of them to support the community and be inclusive.
For Devs on board officially it's lapingvino and myself although a few of the other guys have expressed some interest in helping. Even if it's just small things like helping run nodes on testnet or auditing code when it gets pushed will help out immensely.
Also lol, The usage of the word simply in that context is hella sarcastic. Obviously if it was simple someone would have done it 3 years ago. Quite confident though that development of this chain will result in a net positive for the community as a whole.
The convergence idea is cool, but who's project to focus on?
If the entire developer community focused on one project and smashed it out you figure development cycles would take weeks instead of months? It would be cool to have all the devs working together on projects to turbocharge things, but to overcome the different schools of thought and personality quarrels within our group may take a truly worthy cause or a time of incredible chaos. If you want to work on this sidechain you are welcome to. The helping eachother idea is neat but most of us developer types seem to stick to ourselves. :/ Been lucky to have a few developers express interest in aiding this project along.
Personally I'm focused on building this as a means of decentralizing my lending contracts in v2.0 of Hive.Loans.
Sadly haven't got time for atleast the next 3 or so months to dive into other peoples sidechains here on HIVE in any serious fashion.