Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kaladin grant application #2086

Closed
wants to merge 3 commits into from
Closed

kaladin grant application #2086

wants to merge 3 commits into from

Conversation

VinceKLDN
Copy link

Project Abstract

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.

Grant level

  • Level 1: Up to $10,000, 2 approvals
  • Level 2: Up to $30,000, 3 approvals
  • Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

  • The application template has been copied and aptly renamed (project_name.md).
  • I have read the application guidelines.
  • Payment details have been provided (bank details via email or Polkadot (USDC & USDT) or BTC address in the application).
  • The software delivered for this grant will be released under an open-source license specified in the application.
  • The initial PR contains only one commit (squash and force-push if needed).
  • The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
  • I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @CryptoKaladin:matrix.org (change the homeserver if you use a different one)

Copy link
Contributor

github-actions bot commented Nov 3, 2023

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. Please submit the following text as a separate comment:


I have read and hereby sign the Contributor License Agreement.


You can retrigger this bot by commenting recheck in this Pull Request

@semuelle semuelle self-assigned this Nov 3, 2023
Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your interest in our grants program. However, the application at the moment contains very little information, and the milestones are simply based on the template. Could you please update this?

@Noc2 Noc2 added changes requested The team needs to clarify a few things first. details missing Not enough technical details. labels Nov 6, 2023
Copy link
Contributor

github-actions bot commented Nov 6, 2023

Thank you for submitting a grant application.

We've assessed your submission and have found that it requires a higher level of technical detail in order to be considered for review. We encourage you to expand on it by providing a more precise specification/technical details. The section on project details in the application template is a good reference as to what type of information we expect applicants to provide, and these category-specific requirements contain more precise guidelines depending on what type of software you're building.

An area of the application that we often find to be insufficiently elaborated are the milestone deliverables. At a minimum, please indicate what languages/technologies you will be using to implement each deliverable, and provide a technical summary of its expected functionality. Note that deliverables should be tangible, reusable by other teams and in most cases not already present in the ecosystem. If they are, you will need to provide a comparison to existing implementations and explain why it makes sense to fund your approach. Also see our FAQ for a breakdown of what we fund and what we don't.

Let us know as soon as you're done with your changes, and we'll give your application another look!

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update. Let us know once we should take another look at the application. But just be aware that, for example "We are currently developing a wasm smart contract for Polkadot." doesn't contain any technical details. (e.g., programming language). The milestone table represents the technical requirements of our contracts.

@VinceKLDN
Copy link
Author

We have just updated the information, let us know if there is anything else that needs to be changed

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update. However, the formatting of the application seems to be wrong. The tables don't render correctly. Could you fix this? Also what is the reason for the additional price increase? Why is the smart contract repo that you shared archived? Additionally, the estimated duration seems very high to me, especially given that you want to reuse an existing solution developed in solidity. Could you comment on this?

@Noc2
Copy link
Collaborator

Noc2 commented Nov 23, 2023

I'm closing this application due to inactivity. Let me know if I should reopen it.

@Noc2 Noc2 closed this Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changes requested The team needs to clarify a few things first. details missing Not enough technical details.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants