Hi Polkadot Community,
My team Peranto SSI NA LLC and I currently have an unfunded/bonded proposal in OpenGov, Ref 1789. We understand that we are in a bind with the most recent post from Kilt https://x.com/Kiltprotocol/status/1988220030623117742?s=20 . Please know as part of our exploration work to find a pathway for our clients FlyAdvanced for FlyGateway flight schools and Chilian Mountaineers we have found some options, in addition to reaching out to Kilt directly to understand liabilities of taking over the chain.
First course of action is the initial proposal; to test the technology and remove the bugs, we are proposing to make this effort on Kreivo via Kusama. Once proven our goal is to stand-up Highlander Chain, this is our own deployment (over time) for our custom runtime and multiple applications/verticals listed within our proposal. Please see comprehensive options after phase 1 here; https://aura.peranto.app/
Right now, my team is requesting feedback from the community on funding request directive.
-
We can leave up 1789 put down our deposit for the proposal, fix the verbiage to indicate Krevio is our host for testing (next 7 months), plus adjust our financial numbers for this new direction.
-
Let 1789 end without a deposit and open a new referendum on Kusama for this request?
I have read the feedback and have opened a telegram room for any questions https://t.me/+CkDiXA9-GnFhZDIx and the above, plus our website should address any current questions regarding the sunset of Kilt, as we look to move to Highlander.
Best Regards,
Peranto SSI NA LLC
3 Likes
More than anything, it seems like these client focused referenda will need a clear path to revenue. Not only for self-sustainability but also towards the ecosystem it belongs to and not just use of the chain.
Based on conversations recently in BsAs with other blockchain governance bodies, DAOists and DAO participants, the trend seeks to be revenue focused. Prove that you can create revenue for yourself and for the ecosystem and you and your team should be considered for long term incubation. Else, it’ll just add minor metrics to the ecosystem without creating actual value or activity (which in itself is also a form of value).
Concretely, 1789 requires polishing on two areas. Obviously the DID provider as well as the acceptance of said credentials in the outside world. While the former is more or less clear the latter also bears a heavy weight as many are betting on identity as their main development venue. The main characteristic that pretty much everyone on Ethereum has agreed upon is that this identity has to be accepted and recognized by others consistently and long term. Otherwise, it only becomes an experimental use case of identity on x-y or z platform (Be Kilt, Kreivo, ZKPassport, etc.) These are only the 0.002c that can be brought into this referendum that certainly has tons of interesting parts as well as hard issues that may even have no answer still. It’s just what we would like to see in a referendum right now.
1 Like
If you’re looking for feedback here is the REF REEEEEEEEEEPORT
1 Like
Appreciate this comprehensive write-up. Will look to address what we can from this going forward.
Thank you for the feedback. On our next proposal we will address these with Letter of Intent, or we will not continue. Please note that we have seen deployment of DID but not adoption in the world. Our model driven on solving problems to gain adoption, not deploy and pray it gets used. Through or approach we’re removing bugs and proving to the client our solution is proven for thier needs.
Looking forward to further engagment on this Product alignment for Polkadot.
I think the logical next step here is to let that referendum expire and submit a new one on Kusama.
It might be a good idea to include in that proposal:
– a brief explanation of your new technical direction (Kreivo), and
– a clear roadmap with deliverables.
Best of luck!
1 Like
Appreciate you taking the time Lily and giving us feedback! It was a pleasure meeting you in person!!! Plus spending time exploring BA together.
Me & my team have some work to do & it may not fit in a pretty box! The Goal is to Solve Problems and to deploy, for this partnerships are required, otherwise this is just a use case that may sit on a shelf. I have always been here to help and try to solve problems. My team and I will put out something well versed when we forward. 
1 Like