[PROPOSAL 819][APPROVED] Re-allocate Prop 72 funding from P2P to Neutron
Change log • 2023-07-24 Created initial post Summary Re-allocate funding granted by the Cosmos Hub community for the development of Neutron via Prop 72 to the Neutron Foundation. This requires authorising P2P to transfer the 25K ATOM received as part of Proposal 72 proposal, and authorising the Funding Committee to transfer the remaining 25K to the relevant address. Context In July 2022, the Cosmos Hub community voted in favour of Prop 72 , and allocated 150k ATOM to fund the development of consumer chains to be launched on Replicated Security of which 50k ATOM were earmarked for Neutron. The first portion (50%) will be sent once the Funding Committee votes to support the project, and the second portion (50%) will be sent at a maximum 2 weeks after the project enables Interchain Security. P2P received the first portion, 25 000 ATOM, in August last year. The transaction can be seen here . The second portion is pending transfer. Past use of funds As a validator, builder and investor, P2P.org has been committed to the success of the Cosmos Hub since genesis. As a result, instead of liquidating the tokens, P2P shouldered Neutron’s development cost, held and…
Excerpt (1196 of 4581 characters). Read the whole post on the forum ↗
According to the original Prop 72: ‘2/3 of funds (100 000 ATOMs) will go towards CosmWasm and smart contract projects that either decide to launch on the DeFi Hub, or as their own appchain. The Managing Committee will vote on which projects to fund on a case by case basis.’
This draft proposal is about 1/3 of the funds (50k ATOM) from Prop 72, but what about the other 2/3 (100k ATOM)? So this means that 100k ATOM were to fund projects building on Neutron or launching as consumer chains (Stride, Duality). Is there any transparency about this? @zaki_iqlusion have you funded Stride, Duality or other projects with this 100k? Wouldn’t this also overlap with the proposed Neutron grants program since these funds are to fund projects building on Neutron?
I believe the remaining 100K were used to fund other consumer chain projects. As far as I know, no Prop 72 ATOM was used to fund applications on Neutron. I’ve asked the committee members to confirm.
Hi @cosmic_validator Jelena here, who was previously part of the Prop 72 committee. As Im no longer employed with Informal Systems, I am no longer part of the committee, as my role on the committee was tied to my employment at Informal and advancing the goals of ICS / Cosmos Hub. However, I’m sharing some relevant historical information as it pertains to your question: As you note, the intention of Prop72 was to use 1/3 of the funds to fund Neutron. We transferred half of the grant upfront, 50K ATOM and the committee will be transferring the remaining half, 50K ATOMs, to the team, as per the governance proposal. The remainder 2/3 of the funds (100K) was earmarked towards supporting other projects that want to launch as a consumer chain of the Cosmos Hub. The only other project that the committee has formally voted on has been Fairblock. The Fairblock team made their case as to why they should launch as a consumer chain on the forum. As such, the committee transferred their initial grant and since then, the team has been leveraging the funds to build out the Fairblock infrastructure and to explore using ICS. If Fairblock decides to launch as a consumer chain, their remaining…
Excerpt (1199 of 1775 characters). Read the whole post on the forum ↗
Half of Neutron’s grant: Interchain Explorer by Cosmostation
Half of Fairblock’s grant: Interchain Explorer by Cosmostation
Fairblocks case to be consumer chain: Fairblock: A Consumer Chain of the Cosmos Hub
Cheriton School of Computer Science – 17 Oct 22FairBlock, start-up founded by recent master’s graduate Peyman Momeni,...
FairBlock, a start-up founded by recent master’s graduate Peyman Momeni, has received the equivalent of $400k USD funding from Cosmos, an ecosystem of apps and services that exchange digital assets and data using inter-blockchain communication...
Hey, Peyman from Fairblock here:
also please check this:
Fairblock: Update for community [image] We’ve been fortunate to start our journey in the Cosmos ecosystem which has proven to be an ideal ecosystem for the most innovative ideas in the industry. We really appreciate the endless support from all teams in the Cosmos ecosystem since the announcement of Prop 72. We would love to share some updates with the community about Fairblock during the last six months: What’s Fairblock? Fairblock’s current focus is bringing “pre-execution privacy” to the …
Thanks for the update, according to this update you mention: “While our current library works fine for up to 50 validators, we are not sure that it will work fine for ~150+ validators of the hub. Due to the design of ICS, we don’t have the option to run it with top 50 Cosmos hub validators and we should make sure that it’s possible before making the final call (we are going to test and optimize for this soon). We were not aware of this limitation at the time of the announcement and there was no clear documentation about this; however, we think that we can still make it work with ICS.”
It seems that you should have researched about this limitation preventing you to launch as a consumer chain before asking for, and receiving a $400k grant in ATOM from Prop 72 funds as funding to build and launch a consumer chain? Moreover, Jelena mentions that ‘The Fairblock team made their case as to why they should launch as a consumer chain on the forum. As such, the committee transferred their initial grant’, shouldn’t the committee also had done due diligence to realize as well about that limitation before awarding the grant?
Thanks for the comment, there are a few things to consider. • First of all, we haven’t received 400K, we received 16250 atoms (50% of the grant) which was valued at ~160000 at the time of payment (payment was delayed hence the article is out-dated) • It’s not a theoretical limitation, it’s an engineering challenge that needs more research and optimization basically like all of the scalability challenges for ZK projects, or even Ethereum. We haven’t been told about the fact that we can’t use a subset of validators, and there was no decent documentation at the time of application. We haven’t told that we are not doing it anymore, we just mentioned some of the technical challenges that may make it harder. It’s still in our roadmap and we will try our best to make it work. • A grant doesn’t mean that there is 0 risk for that project, it means that the project is supported to conduct research, explore and do their best to implement it. Many big projects in the blockchain industry are trying to do the impossible, or have already done that after years of experimenting, we wouldn’t have many of them if VCs or grant committees only fund the next easy and guaranteed project.…
Excerpt (1195 of 1376 characters). Read the whole post on the forum ↗
Pememoni: We haven’t been told about the fact that we can’t use a subset of validators, and there was no decent documentation at the time of application. If you are applying for a large grant from Prop 72 to build and launch a consumer chain in the Cosmos hub, it would be expected that you would do research to understand what is a consumer chain, and what is replicated security, opt-in security and mesh security? I mean even the name says ‘replicated’ meaning consumer chains benefit from the same security of the Cosms hub which is the total value staked in all validators (the soft opt-out only affects liveness, not safety: ‘It is important to note that the small validators who are not being slashed will still be present in the validator set of the consumer chain. In other words, we are sacrificing liveness, not safety. The economic security of the consumer chain is the same, but it may be more likely to halt.’). I think saying that ‘you were not told that you couldn’t launch your consumer chain with replicated security with 50 validators instead of 150’ is not a valid excuse, I assume the committee was expecting you to understand how replicated security works if you…
Excerpt (1194 of 1270 characters). Read the whole post on the forum ↗
• We are still planning to use replicated security as it makes a lot of sense for us and we are currently testing/experimenting with our DKG library. We think it’s possible and we need to implement some optimization techniques. We think we have a complex architecture so it’s important to test and ship each part carefully. We are closely working with the Informal team and the community to discuss the best approach and possible solutions to address these problems and are actively making an effort to onboard as an ICS consumer chain. • It is not possible to guess any engineering challenge before actually implementing it (in our case implementing cryptography libraries, building the chain etc) and testing it. So no one could predict any numbers just based on papers and ideas. Also, the details of mesh security, opt-in security, and replicated security, opt-in are all new, and evolving; and there was no documentation or implementation for researching them other than the high-level idea. You are defining the term “replicated” but it was not used at that moment it was ICS. The opt-out for 10% of the validators and the details were discussed later and so it wouldn’t be possible to…
Excerpt (1192 of 1276 characters). Read the whole post on the forum ↗
This doesn’t seem like fair criticism to me, given the timeline.
When Prop 72 happened (in May last year), ICS was not built out to the point that an incoming project could possibly know that we were going to do ‘replicated’ security and that the engineering challenges they would face would be so significant. Soft opt-out certainly didn’t exist at the time. That’s an incredibly recent development.
“We weren’t told” is more like…“There literally wasn’t any information about this because it didn’t exist yet”. Hard to blame a team for not being able to see the future ![]()
When Prop 72 happened (in May last year), ICS was not built out to the point that an incoming project could possibly know that we were going to do ‘replicated’ security and that the engineering challenges they would face would be so significant.
Fairblock’s case to be a consumer chain in the Cosmos Hub forum, as @Spaydh indicated with the link above, was in October 2022, not May 2022 (although Prop 72 passed in July not May, not sure why you mentioned that it happened in May) and this case presented in the forum as Jelena indicated was used to decide the funding allocation by the committee. October 2022 was after Sunny’s talk in Cosmoverse Medellin for example about Mesh Security (ICS v3) where he clearly described and explained ICS v1 (replicated security) and ICS v2 (Opt-in security) and compared them to Mesh security. The soft opt-out is not related to Fairblock’s limitation of not being able to launch with the full Cosmos Hub validator set but only with up to 50 validators
Thank you all for the feedback to this proposal. Since no strong objection was raised, we propose to prepare the signalling proposal to be published on-chain soon.
Aren’t Neutron and P2P closely tied together? Could you elaborate a bit more on why this is necessary? Is it because development will move faster if the proposed multisig is in charge? How many people in the new multisig have the same amount of influence when the funds were going to P2P?
They are. One was launched by the other (cutting some bureaucratically edged here)
Proposal 819 has been approved by governance.
https://www.mintscan.io/cosmos/proposals/819
The Foundation will verify the mutlisig’s integrity and collaborate with P2P and the Prop 72 committee to re-allocate the tokens.