From 1d131ba42dcccaa5443684e3fcf92d34e94fa236 Mon Sep 17 00:00:00 2001 From: VinceKLDN Date: Fri, 3 Nov 2023 18:23:52 +0000 Subject: [PATCH] kaladin grant application --- applications/Kaladin.md | 194 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 194 insertions(+) create mode 100644 applications/Kaladin.md diff --git a/applications/Kaladin.md b/applications/Kaladin.md new file mode 100644 index 00000000000..3e39d42faa3 --- /dev/null +++ b/applications/Kaladin.md @@ -0,0 +1,194 @@ +# Name of your Project + +> This document will be part of the terms and conditions of your agreement and therefore needs to contain all the required information about the project. Don't remove any of the mandatory parts presented in bold letters or as headlines (except for the title)! Lines starting with a `>` (such as this one) should be removed. Please use markdown instead of HTML (e.g. `![](image.png)` instead of ``). +> +> See the [Grants Program Process](https://github.com/w3f/Grants-Program/#pencil-process) on how to submit a proposal. + +- **Team Name:** Kaladin LLC +- **Payment Address:** +0x06293bA89A49bD5279705250F16b2c72ef4a1600 for ETH or USDT on ERC20 +- **[3](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** + +> :exclamation: *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* + +## Project Overview :page_facing_up: + +If this application is in response to an RFP, please indicate this on the first line of this section. + +If this is an application for a follow-up grant (the continuation of an earlier, successful W3F grant), please provide name and/or pull request of said grant on the first line of this section. + +### Overview + +Please provide the following: + +Kaladin's cross-chain protocol allows the exchange of assets between blockchains without an intermediary or bridge. The Kaladin protocol can enable to direct transfers and exchanges between any blockchain asset with <0.1% transaction fees and in <0.25 seconds without using a bridge or a central third party. Swaps between Bitcoin variants, ETH chains, Stellar and Algorand can be done in less than 1 second, and we can support over 6,000 tps for exchanges. + +### Project Details + +We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant): + +- Kaladin.com +- swap.kaladin.com +- Python, Javascript, HTML, CSS, Solidity +https://kaladin.gitbook.io/api-docs/quick-start + + +Things that shouldn’t be part of the application (see also our [FAQ](../docs/faq.md)): + +- The (future) tokenomics of your project +- For non-infrastructure projects—deployment and hosting costs, maintenance or audits +- Business-oriented activities (marketing, business planning), events or outreach + +### Ecosystem Fit + +Help us locate your project in the Polkadot/Substrate/Kusama landscape and what problems it tries to solve by answering each of these questions: + +- Where and how does your project fit into the ecosystem? + Our project would create trustless cross-chain infrastructure which would create a bridge to trade without just trading on an exchange where your funds could be compromised. We support Moonbeam at the moment for polkadot to be able to trade into eth or btc or any other chain we currently support. + +- Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? + Our target audience are large liquidity providers and daily users +- What need(s) does your project meet? + Our project meets the needs of cross chain swaps without having to trust an exchange or brokerage. +- Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem? + - If so, how is your project different? + - If not, are there similar projects in related ecosystems? + No, lightning would be closest but they are bitcoin only. + +## Team :busts_in_silhouette: + +### Team members + +- Name of team leader. Sean Costello +- Names of team members. Caia Costello, Jake Koffman, Vincent Truong + +### Contact + +- **Contact Name:** Full name of the contact person in your team + Sean Costello +- **Contact Email:** Contact email (e.g. john@duo.com) + sean@kaladin.com +- **Website:** Kaladin.com + swap.kaladin.com + + +### Legal Structure + +- **Registered Address:** Address of your registered legal entity, if available. Please keep it in a single line. (e.g. High Street 1, London LK1 234, UK) +- **Registered Legal Entity:** Name of your registered legal entity, if available. (e.g. Duo Ltd.) + +### Team's experience + +Please describe the team's relevant experience. If your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. + +If anyone on your team has applied for a grant at the Web3 Foundation previously, please list the name of the project and legal entity here. + +### Team Code Repos + +- https://github.com/Kaladinn/stormLibrary +- we have some others that are privitized + +Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. + +- https://github.com/seanaocostello +- https://github.com/Jake-Koffman +- https://github.com/caiacostello +- https://github.com/VinceVT + +### Team LinkedIn Profiles (if available) +- https://www.linkedin.com/company/kaladin-inc/ +- https://www.linkedin.com/in/sean-costello-090a7620b/ +- https://www.linkedin.com/in/jake-koffman-743084150/ +- https://www.linkedin.com/in/caia-costello-5b4064216/ +- https://www.linkedin.com/in/vincevtruong/ + + +## Development Status :open_book: + +If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be: + +- links to improvement proposals or [RFPs](https://github.com/w3f/Grants-Program/tree/master/docs/RFPs) (requests for proposal), +- academic publications relevant to the problem, +https://www.kaladin.com/Kaladin_Whitepaper.pdf +- links to your research diary, blog posts, articles, forum discussions or open GitHub issues, +- references to conversations you might have had related to this project with anyone from the Web3 Foundation, +- previous interface iterations, such as mock-ups and wireframes. + + + +## Development Roadmap :nut_and_bolt: + +This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/Support%20Docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe *the functionality we should expect in as much detail as possible*, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. + +Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Substrate, Kusama or Polkadot. We *recommend* that teams structure their roadmap as 1 milestone ≈ 1 month. + +> :exclamation: If any of your deliverables is based on somebody else's work, make sure you work and publish *under the terms of the license* of the respective project and that you **highlight this fact in your milestone documentation** and in the source code if applicable! **Projects that submit other people's work without proper attribution will be immediately terminated.** + +### Overview + +- **Total Estimated Duration:** 2 years, 6 months duration left. +- **Full-Time Equivalent (FTE):** 4 Average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), e.g. 2 FTE) +- **Total Costs:** 100,000 Requested amount in USD for the whole project (e.g. 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#level_slider-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in Bitcoin, the amount will be calculated according to the exchange rate at the time of payment. + +### Milestone 1 Example — Basic functionality + +- **Estimated duration:** 3 +- **FTE:** 4 +- **Costs:** 30,000 + +Push for mainnet launch, already on testnet, developing a wasm smart contract for polkadot. Push for filing of money transmitter license. + +> :exclamation: **The default deliverables 0a-0d below are mandatory for all milestones**, and deliverable 0e at least for the last one. + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| **0a.** | License | Apache 2.0 / GPLv3 / MIT / Unlicense | +| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works. | +| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | +| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | +| 0e. | Article | We will publish an **article**/workshop that explains [...] (what was done/achieved as part of the grant). (Content, language and medium should reflect your target audience described above.) | +| 1. | Substrate module: X | We will create a Substrate module that will... (Please list the functionality that will be implemented for the first milestone. You can refer to details provided in previous sections.) | +| 2. | Substrate module: Y | The Y Substrate module will... | +| 3. | Substrate module: Z | The Z Substrate module will... | +| 4. | Substrate chain | Modules X, Y & Z of our custom chain will interact in such a way... (Please describe the deliverable here as detailed as possible) | +| 5. | Library: ABC | We will deliver a JS library that will implement the functionality described under "ABC Library" | +| 6. | Smart contracts: ... | We will deliver a set of ink! smart contracts that will... + + +### Milestone 2 Example — Additional features + +- **Estimated Duration:** 3 +- **FTE:** 4 +- **Costs:** 40000 + +Finish up algorand and start development test wasm chains. Start deployment to watch tower, add more order types, work on advanced trading UI. + + + + +## Future Plans + +Please include here + +- how you intend to use, enhance, promote and support your project in the short term, and +- the team's long-term plans and intentions in relation to it. + +## Referral Program (optional) :moneybag: + +You can find more information about the program [here](../README.md#moneybag-referral-program). + +- **Referrer:** Name of the Polkadot Ambassador or GitHub account of the Web3 Foundation grantee +- **Payment Address:** +0x06293bA89A49bD5279705250F16b2c72ef4a1600 for ETH or USDT on ERC20 + + +## Additional Information :heavy_plus_sign: + +**How did you hear about the Grants Program?** Web3 Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. +medium article + +Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: + +- Work you have already done. +- If there are any other teams who have already contributed (financially) to the project. +- Previous grants you may have applied for.