Batch 17: Approved Grants

Skip will solidify their long-term partnership with Osmosis by developing a number of in-protocol features. Similar to ProtoRev, the deliverables detailed below stand to further differentiate Osmosis from other DEX’s and appchains in terms of UX, security, and value capture. These deliverables represent a subset of the work that Skip will perform under the recently executed 2-year contributor agreement between Skip and the Osmosis Foundation. While the vesting $OSMO compensation that Skip receives from the Foundation aims to ensure long-term incentive alignment, this proposed grant aims to provide the working capital required for resource staffing. For each milestone, Skip will receive 50% of the allocated amount upon testnet integration, and the remaining 50% upon mainnet integration. Milestone 1: Protocol Owned Builders (POB) v0. In POB v1, Skip will develop a new Cosmos SDK module (x/auction) that hosts a top-of-block auction. The proceeds from this auction will help Osmosis recapture value from CEX/DEX arbitrage and other top-of-block MEV opportunities; Milestone 2: POB v2 (also referred to as Block SDK). In POB v2, Skip will implement a standardized framework for a laned mempool. The top-of-block auction developed for POB v1 will become the MEV lane of the Osmosis mempool; Milestone 3: Oracle implementation. Skip will develop and integrate an in-protocol Oracle module and sidecar process that allows validators to query prices and load them into on-chain state. This Oracle update mempool lane will allow Osmosis to update prices every block without the risk of front-running or critical 3rd party dependencies; Milestone 4: EIP-1559+. Similar to EIP-1559, Skip will integrate a transaction fee market that dynamically adjusts fees to improve user experience and manage transaction load. This potentially could also include a base fee burn mechanism that stands to improve value capture for Osmosis.

After completing Phase 1 of back-end development for Mesh Security, which involved 1) a detailed overview of the various components of Mesh Security and 2) the integration of the Mesh Security MVP into the Osmosis and Juno codebases, demonstrating functionality on devnet, we have finalized the scope of Phase 2. The goals of this phase will be to launch V1 of Mesh Security, which is meant to be deployed with low-cap chains (e.g. Chihuahua or Eve) as consumers and possibly Juno/Osmosis as providers. Milestone 1: at completion of the integration of the uni-directional V1 version of Mesh Security into low-cap chains to field test the solution in a low-risk environment; Milestone 2: at completion of the integration of the already field-tested V1 version of Mesh Security into the partner chain's and Osmosis' codebases and demonstrating functionality on a devnet.

As part of this grant, Nabla will extend cli.osmosis.zone to also support signing, by building a version of the CLI keyring that uses Cosmoskit, so that developers can make CLI txs and sign them using Keplr. Nabla will also add informational token pages to the Osmosis frontend, which will include relevant descriptions and metrics. Milestone 1 = at completion of the CLI improvements; Milestone 2 = at completion of the token info pages for both desktop and mobile.