Closed Joseph-Gross closed 2 years ago
Hi @Joseph-Gross, David followed up with y'all in person about this grant. We'd love to work with y'all and figure out how we can get some funding for your project.
Please update the proposal scoped for how the team will be using Lit Protocol!
Milestone 1: Distributed Network of Orderbooks (secure, trust-less, encrypted)
Milestone 2: Personal Orderbook Explorer
Milestone 3: Executor Network
Milestone 4: Core SDK
encrypt(order: SlingOrder, signer: Signer)
and decrypt(order: EncryptedOrder, signer: Signer)
. While this component does not implement any novel lit protocol integration not previously detailed in milestones 1-3, it builds heavily on the work detailed above and includes building out various abstractions / tools for utilizing lit protocol.Milestone 5: PKP Exploration and integration
Total: $20,000
We are expecting to allocate a vast majority of our budget to salary and living expenses. We don't currently have any other overhead besides salaries and team expansion. However, depending on other funding leads that we are currently pursuing, we may outsource or hire UI / UX talent to help develop our brand as well as a comprehensive user experience and Sling design system. It is also important to note that we have been working since January so many of the deliverables above have already been started in some capacity. I want to emphasize that Lit Protocol is essential to our mission of maintaining a decentralized, secure, and private network of orders books. Without Lit Protocol, we would be required to either centralize our server or make all order books private.
Awesome. We really enjoyed reading through your project proposal and would like to fund milestones 1 and 2, then revisit funding for additional milestones as they get closer. Look out for an email to submit payment information!
Hey had a chat with the lit team. Actually we’re gonna do the following:
Build a PKP DEX SDK for calling common functions
Build an explorer / utils for Lit Actions
Build an explorer / utils for PKPs
Begin ideating how to integrate a generalized execution network with Lit Protocol (i.e. PKPs, access control conditions, Lit Actions, and more)
Propose a PKP + Lit Action Automation SDK
We are into our first milestone funding with Sling Protocol, thank you for working with Lit Protocol.
Open Grant Proposal:
Sling Protocol Grant Proposal
Name of Project: Sling Protocol
Proposal Category:
integration-adoption
Proposer:
Joseph-Gross
Do you agree to open source all work you do on behalf of this grant and dual-license under MIT, APACHE2, or GPL licenses?: Yes, but gradually over time. We intend to build a full decentralized automation network with an entire ecosystem of developers building on top of it, so while we do intend to open source all of our work at some point, we are planning on doing so gradually. The Lit Protocol component of our network, however, is one of the first components we intend to open source with the MIT license.
Project Description
We are building a decentralized and user-friendly automation network. In the long term, we envision a protocol layer that users, developers, and enterprises can use to automate any on-chain action(s) and compose these automations into complex transactional state machines. This is infrastructure for making highly composable and flexible new primitives.
Sling Protocol is composed of two elements: a secure, decentralized orderbook, and a competitive network of executors. Our SDK can be used to create programmable orders, which will be executed upon certain condition(s) being met. Once the order object has been created, it shall be encrypted and submitted to the orderbook. Access control conditions and a symmetric key will be submitted to Lit Protocol. When an executor verifies that an order’s condition has been met, its order data is decrypted using Lit and the executor may execute the order on chain, receiving a reward left by the user that placed the order.
Our plan is to open-source the contracts and SDK. To facilitate adoption, we will build protocols, tools, interfaces to demonstrate the power of Sling. Some examples:
The future of Sling is an established multichain hyperstructure facilitating trustless conditional transaction execution for its users. In a world where more and more software use cases and moving some component on-chain, we will enable users to take full control over their cryptographic assets.
Value
We believe we are building a new primitive in the blockchain ecosystem. By introducing a generalized, decentralized, automation layer, we can enable cross chain communication, complex trading strategies, on chain hedge funds, automated LP management, and so much work. We believe that if we get this right, Sling Protocol can be the gateway to most DeFi protocols as well as future use cases that we haven't yet thought of. The risks that we don't get it right are a lack of developer adoption, a lack of consumer adoption, and ultimately, it will mean that the protocol we spent months and maybe years building was unable to reach a high level of adoption.
The major risks we have identified for this project are developer adoption, UI / UX design and optimization, and prioritizing our time on the right use cases. We see our protocol as having a very wide range of use cases, but our team is currently very small, so finding the right use cases to hone in on and prioritize in these early stages will be extremely important. The primary difficulty of this project comes from the massive scope of what's possible as well as the technical and regulatory challenges that come with designing a distributed network.
Deliverables
We see what we're building as an evolving ecosystem to power the next wave of decentralized applications. At the infrastructure level, the first version of our network will have a decentralized private storage system (using Lit + IPFS), a network of executor bots, and deployed protocol contracts.
Once this is done we will get to work building sub-protocols, all created by the team, that use Sling's functionality. This serves to encourage development on Sling and also orgranically grow the volume of order executions on our network. These projects will likely look like the use-cases described above but as more innovative protocols come out and gain traction we will have a steady supply of new use-cases to focus on.
Development Roadmap
Note that these milestones are not sequential and we will be working on multiple tasks asynchronously depending on our bandwidth.
Milestone 1: Distributed Orderbook (secure, trust-less, encrypted)
Milestone 2: Orderbook Explorer
Milestone 3: Executor Network
Milestone 4: Core SDK
Milestone 5: Audited Smart Contract Layer
Milestone 6: Developer SDK v1
Milestone 7: Proxy Account Portfolio Page
Milestone 8: Sling dApp Component Library
Milestone 9: UI / UX Design System
Total Budget Requested
Total: $50,000
We are expecting to allocate a vast majority of our budget to salary and operational expenses. We don't currently have any other overhead besides salaries and team expansion. However, depending on other funding leads that we are currently pursuing, we may outsource or hire UI / UX talent to help develop our brand as well as a comprehensive user experience and Sling design system. It is also important to note that we have been working since January so many of the deliverables above have already been started in some capacity.
Maintenance and Upgrade Plans
We currently have 4 full time developers and intend on working full time throughout the summer. Though we are also planning on returning to school, we will continue working on Sling Protocol (reduced hours in the Fall). However, depending on our funding situation by the end of the summer, we will decide on whether to expand the team by hiring a full time developer, biz dev guy, or marketing / branding / UI and UX designer. We believe we can launch a functioning beta version of our ecosystem (i.e. the milestones listed above) by the end of the summer, and then continue to maintain, innovate, and develop new features throughout the rest of the year. It is also important to not that 3/4 team members will be graduating in a year and we all plan on continuing with Sling Protocol full time in between semesters (which for us in December - February).
Team
Team Members (and Linkedin Profiles)
Richter Brzeski
Joseph Gross
Will Seiple
Nick Ciepley
Team Website
Sling Protocol (landing page)
Relevant Experience
Richter Brzeski
Joseph Gross
Will Seiple
Nick Ciepley
Team code repositories
Though we intend to open source certain SDKs, our smart contracts, and executor bots at a certain point, we are still currently working towards a Beta version of our protocol, and as a result, are still closed source. However, we are happy to go over our code base while on a call or in person (we will be at EthNYC from Jun 24-26). Additionally, most of our personal GitHub have proprietary work.
GitHub Links:
Additional Information
We met with David in person at Consensus 2022 in Austin. He told us about the grant program and encouraged us to apply.
Contact Info: