abandoned because of threats from some Kerbal, ICF opacity. Not one alone, the combination.
Change log
- 2023-01-19 Created initial post
target on chain date
- 2023-01-26
Funding date range
This is funding for maintainership of the variety described here for 365 days from the date of passage.
Summary
Fund Notional with 120,000 atoms for work across the cosmos stack:
- Cosmos Hub
- Cosmos SDK
- Consensus
- tm-db
- cosmos-db
- ibc-go
- Relaying
- IBC client update governance proposals
- Pre-upgrade code reviews
âŠincluding on security issues like the one that affected Quicksilver recently, which our team member Khanh Nguyen patched in fall of 2022.
We cannot and will not disclose security items until they are fixed, so we will rely on teams like ICF, Informal, IG, Iqlusion, Strangelove and Binary Builders to confirm for the community that we are actively working in that space.
Details
Above is our work to date, which we will attempt to seek a retroactive grant, which will also be held for a period of at least 2 years and not sold on open or closed markets, from the interchain foundation for.
Looking at the document above from a technical perspective, it is possible to see that our work falls into numerous categories, and covers the entire cosmos stack.
- Maintainership
- Fixes of both critical and non critical issues
- Ease of use improvements
- Software integration
- Performance improvements
- Security
We wish to continue that line of work.
Specific deliverables to be completed by EOY:
-
Account rekeying
-
Validator operator transfers
https://twitter.com/pupmos/status/1611472847821758464
Additionally, for the cosmos hub, our team has made contributions to:
- Liquidity module
- Packet forward middleware
Members of the ICF and itâs TAB have recognized that our contributions to the stack from a technical perspective are exponentially greater than any other organization without a grant or contract from the ICF.
- Our team led the development of cosmos-db, an evolution of tm-db that follows design ideas from Notional
- Our team wrote IBC v5, and it passed review from the IBC-go team at IG
- We are major contributors to the cosmos hub
- We have contributed important security patches, including a patch that would have prevented the issues encountered by Quicksilver
- We have supported design and development processes on consumer chains in both a hands on and consultative manner
- We have a team capable of working on every layer of the cosmos stack, including subject matter experts for each layer.
- We fixed entirely non-functional pieces of the continuous integration systems of:
- Gaia
- Cosmos-sdk
- Ibc-go
The continuous integration system in each of the above repositories was, for several tasks, always passing, because it was misconfigured. This was allowing pull requests that had issues that could be automatically identified to pass CI regardless of those issues.
what we arenât doing
- We are not asking for product ownership of any of the above named repositories, the current product owners are excellent.
- We are not Implying that we will not seek funding for specific initiatives that go beyond the scope of maintenance.
- We are not Implying that only the cosmos hub should fund this work.
- We are not Expressing to the community that we can find or solve every possible issue in security
- We are not taking a wait and see stance on possible public goods funding from the proposed cosmos hub grants program
- We are not silently accepting continued opacity and inaction on the part of the Interchain Foundation.
Recipient
We will be making a multisig with members of our team to receive this and will post the address here.
Oversight and reporting
We will continuously report work here:
For work that affects security, we will report privately in the channels that we have established to the product owners of the repositories mentioned.
We invite any technical organization with sufficient technical capabilities to contact us during the next week to be formally listed as participating in oversight.
These organizations include but are not limited to:
Founding Orgs:
- Interchain Foundation
- Allinbits, inc
note: we strongly condemn the recent seizure of the tendermint GitHub org by AIB, and the opacity and inaction we have observed from ICF. As enormous stakeholders in the hub, both deserved a place on a list of possible overseers.
Prominent technical orgs:
- Informal Systems
- Iqlusion
- Strangelove Ventures
- Binary Builders
Validators with high technical capability:
- CryptoCrew
Amount
120,000 atoms
Note: we will not sell these atoms for a period of at least two years, and intend to hold those atoms for longer than two years.
Forum post link
https://twitter.com/notionaldao/status/1615927081443160064
Governance votes
The following items summarize the voting options and what it means for this proposal:
YES - fund notional with 120,000 atoms that wonât be sold for two years to sponsor work across the cosmos stack for the benefit of the hub and her consumer chains
NO - donât fund notional with 120,000 atoms to work across the cosmos stack for the benefit of the hub and her consumer chains
NO WITH VETO - A âNoWithVetoâ vote indicates a proposal either (1) is deemed to be spam, i.e., irrelevant to Cosmos Hub, (2) disproportionately infringes on minority interests, or (3) violates or encourages violation of the rules of engagement as currently set out by Cosmos Hub governance. If the number of âNoWithVetoâ votes is greater than a third of total votes, the proposal is rejected and the deposits are burned.
ABSTAIN - You wish to contribute to quorum but you formally decline to vote either for or against the proposal.