-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
95 additions
and
130 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,95 @@ | ||
# LIGO - CMTAT-Ligo - #1 | ||
## Current Status: Open for application | ||
* Open for application (13/12/2023) | ||
* Assigned | ||
* In Review | ||
* Closed | ||
|
||
## Bounty Details | ||
* Total Bounty Amount (without bonus): 2500 xtz | ||
* Time Left: Expires 15/03/2024 | ||
* Project Type: Single Contributor | ||
* Opened: 13/12/2023 | ||
* Time Commitment: Weeks | ||
* Type: Library creation | ||
|
||
## Description | ||
### Goal : | ||
Creation of a library using LIGOLang for Tezos. The library must implement the [CMTA Token](https://cmta.ch/standards/cmta-token-cmtat) developed by CMTA to tokenise securities in compliance with the Swiss law. | ||
|
||
After completion of the bounty, the library may be made available in the ligo [registry](https://packages.ligolang.org/packages). | ||
|
||
### Scopes : | ||
- Creation of library | ||
- Has to be compliant with [CMTAT guidelines](https://cmta.ch/standards/cmta-token-cmtat) | ||
- Code constraint have to be available as [here for TZIP12](https://github.com/ligolang/contract-catalogue/blob/main/lib/fa2/common/tzip12.interfaces.jsligo) | ||
- Implemented function can be called as [here for NFT](https://github.com/ligolang/contract-catalogue/blob/main/lib/fa2/nft/nft.impl.jsligo) | ||
- Has to be tested with LIGO tests. | ||
- Creation of the documentation related to the library. | ||
|
||
## Bounty Bonus | ||
- Clean open-source project using your library is available (+600xtz) | ||
- Blog post on how to use your library is published. (+400xtx) | ||
|
||
## Acceptance Criteria | ||
- Interface code has to be documented | ||
- Current LIGO version has to be used | ||
- Resources are in english | ||
- Readme is available and explains how to use the library (will be posted into registry) | ||
- User experience to use the library has been validated by the LIGO team | ||
- Security audit has been done and accepted by the LIGO team | ||
- If bonus have been done, they have been validated by the LIGO team | ||
|
||
## To apply for this bounty you should: | ||
- Understand Tezos and at least one syntax of LIGO | ||
- Understand the [CMTA Standard](https://cmta.ch/standards/standard-for-the-tokenization-of-shares-of-swiss-corporations-using-the-distributed-ledger-technology) | ||
- Understand the [CMTAT Token](https://cmta.ch/standards/cmta-token-cmtat) | ||
|
||
## Selection Process | ||
LIGO core team will examine your profile. If you are selected we will contact you. The bounty will ideally attributed to 1 person. If bonus are not done, other bounties may be created to handle them. | ||
LIGO core team or Tezos core team are not available to participate to the bounty. | ||
|
||
## To help you on bounty completion | ||
- You will have a special channel on slack where you can contact members of the LIGO core team. They will try to answer to your questions quickly | ||
- You can use the already existing [FA library](https://packages.ligolang.org/package/@ligo/fa) | ||
- You can follow the structure of [FA library](https://github.com/ligolang/contract-catalogue) | ||
- An [example implementation exist in Smartpy](https://github.com/CMTA/CMTAT-Tezos-FA2) | ||
- An [example implementation exist in Solidity](https://github.com/CMTA/CMTAT) | ||
|
||
## Development process | ||
- Keep your ongoing code in a public repository (a fork of the [CMTAT-Ligo](https://github.com/ligolang/CMTAT-Ligo) repository). | ||
- Provide weekly updates through Discord or slack channel. | ||
- Code commits count as updates if you link to your branch/fork from the bounty thread. We just need to be able to see that you are making progress. | ||
- The code is merged in [CMTAT-Ligo](https://github.com/ligolang/CMTAT-Ligo) repository. | ||
|
||
## Legal conditions | ||
### Payment condition | ||
|
||
- Your identity must be verified. | ||
- The balance will be paid out upon completion. | ||
|
||
### Copyright and Licensing: | ||
- Copyright: All work produced within the scope of this bounty is subject to copyright laws. Any creations, code, documentation, or other works produced initially belong to Ligolang (Accélérateur de Blockchain). We reserve the right to modify, distribute, and use these works freely as per our requirements. | ||
- MIT License: By submitting your work for this bounty, you agree to apply the MIT License to the deliverables. All submitted work must be licensed under the MIT License to allow free use, distribution, and modification without restrictions, while acknowledging the copyright. | ||
|
||
### Rights of Use: | ||
- By submitting your work, you grant Ligolang (Accélérateur de Blockchain) a non-exclusive, worldwide, royalty-free, and irrevocable license to use, reproduce, modify, distribute, and publicly display the delivered works for internal or public purposes. | ||
|
||
- Your identity have to be verified. | ||
- The balance will be paid out at completion. | ||
|
||
## Bounty Abandonment and Re-awarding | ||
If work on the bounty is paused for an extended period, or if the quality of work deteriorates to a level where it's deemed appropriate for someone else to take over, we might consider reassigning the bounty. We will maintain transparency throughout this process and make efforts to collaborate with you to overcome challenges and successfully finish the project. However, there might be situations where it becomes essential to either proceed in a different direction or enhance your efforts with additional resources, leading to a divided bounty. | ||
|
||
## Funding | ||
The bounty is funded by the LIGO team. | ||
|
||
# Bounty Process | ||
## Open for application | ||
Developers can submit applications through Discord / Slack. | ||
## Assigned | ||
A defined number of developers are assigned to the bounty. | ||
## In Review | ||
The LIGO core team is reviewing the submission. | ||
## Awarded | ||
The award has been given and the bounty is closed. |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.