G6 Networks' second and final milestone proposal (developed by CCTF DAO)
The community's vote of confidence in May was a significant achievement for us when our proposal, which included the project's initial phase, was approved. We deeply appreciate this support. This trust drives our dedication, and we want to demonstrate our commitment with a transparent Milestone 1 delivery and achievement report which you can find here. We propose that our second milestone focuses on integrating the developed products into the institutions with which we have initiated collaboration, connecting them to Polkadot. Additionally, we aim to advance the development of an enterprise SDK that facilitates easy connection to Polkadot from managed and private blockchains, along with our public chain dashboard, the Citizens of Polkadot.
Link to full proposal
Our proposal is divided into three chapters, taking an unconventional approach. Instead of following the usual structure of problem statement, solution, and product, we will explore a different narrative. Our first proposal already covered the concept in detail, along with comprehensive research work. This time, we focus on a journey through our past achievements, present status, and future outlook.
Chapter 1: The Past In this chapter, we reflect on our journey so far. We share the collaborations and our achievements, a detailed report of our development milestones and our MVP.
Chapter 2: The Present This is where we stand now. We will discuss our current development status and we'll introduce the exciting concept for the G6 SDK and the “Citizens of Polkadot” dashboard — a vision becoming reality.
Chapter 3: The Future Looking forward, this chapter is our canvas. We'll paint a picture of our development outlook, our vision for the future and our sustainability efforts.
Also at the end of this proposal, we will provide again a detailed budget breakdown for the next milestone, outlining the specific implementations we plan to undertake.
Short Summary of Budget
Path Tracing (to prove without reveal):
- zk-SNARK ZK transfers
- Path-tracing features
- Extending Legal Teleport with ZK
Enterprise SDK:
- Tooling
- Rust tools for development on Substrate G6
- Python tools for development on Substrate
- G6 and MW APIs G6 Development space
- Middleware APIs
- Smart contract space
Live Integrations - Ecosystem and institutions:
- TownHalls and Pallet Pass
- Coretime public CA chain with Decentralized Meetup platform
- Private networks (currently under NDA)
I'll dive in further and provide a more in-depth review before actually voting, but in the meantime I'd just like to share that my absolute favorite dashboard to use in the Polkadot ecosystem today is the Staking Dashboard by JKRB - the team at https://jkrb.io/. I have no affiliation with JKRB but hot dang, not only is their UI beautifully designed, but it's actually easy to use without any instructions what-so-ever. It makes Polkadot feel slick and it's exciting to log in daily to track staking earnings the way they laid it out. So why am I saying this?
I took a look at the proposed design direction you included and couldn't help but cringe a little to be honest, as it feels like a rather big downgrade in terms of design quality as well as UX and especially readability (which I understand can be fixed in time, but still). Certain things are glaringly wrong in the preview image that would never be shown by a real UI/UX design firm, even in a 'preview' image (e.g., padding/spacing that makes no sense, unreadable fonts, alignment issues, etc), so I'm naturally concerned given you are asking for nearly half a million dollars to provide governments around the world with a dashboard that needs to be well thought out and highly customizable.
With all of that said, two quick questions:
Can you share your team's full website and portfolio so that we can look through your previous work to get a sense of experience you have in this area, and who from your team will be leading the design direction - specifically the look and feel of the UI - moving forward?
Would you be willing to include the JKRB team in your budgeting and let them run with the front-end etc (assuming they were up for the task?)