Thank-you @BaaSPoolLLC for the response. I appropriate the openness to reply to constructive feedback and critiques.
I’m still concerned with the lack of verifiable data provided in your responses. Let me elaborate by taking specific claims and ask for verifiable context.
Could you please provide verifiable data on the teams past experiences? This can be a combination of press releases, LinkedIn profiles, GitHub profiles, etc. Without ways to validate these claims, we are simply trusting this proposal at face value, which makes me very uncomfortable. That is what I mean by blind trust… we have to blindly trust the proposal that this team has the expressed experience.
This is a very general statement, and again, no verifiable context is given. Can you elaborate on the startups, their roles, and the time frame of their work?
Ah, I didn’t realize that you have relationships with core-team members. This could be a great way to put a lot of credibility towards this proposal if you expand on your history with the core-team and if they were able to vouch for this project.
It would also be great to have examples of how you have contributed to the ecosystem as a whole. That statement was very general, and specific would help with verifying.
I’m not sure what this means. If there is a commendable track history with the tech industry, why does it have to be secret from the voters? So far it sounds like this team has been with notable crypto startups and has a solid network… why now does the team require so much obfuscation?
Can you make that research open-source?
I’m concerned with the starting focus on designing and planning the UI, instead of infrastructure, node management, key security, and the entire backend. In any development project, the frontend typically is what is implemented last once the huge web3 engineering challenges are built and tested. UI is important, but for something like this, where POKT user funds are at stake, the backend is everything. Focusing on UI is putting the cart before the horse.
If you were to first provide the backend open-source materials you mentioned above that would be a good start for allowing the community to validate the security of this service, before investing this amount of POKT.