-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
1 parent
c274e5d
commit fde71fd
Showing
41 changed files
with
4,030 additions
and
171 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,25 @@ | ||
# unicorn-binance-suite Change Log | ||
|
||
All notable changes to this project will be documented in this file. | ||
|
||
The format is based on [Keep a Changelog](http://keepachangelog.com/) and this project adheres to | ||
[Semantic Versioning](http://semver.org/). | ||
|
||
[Discussions about unicorn-fy releases!](https://github.com/LUCIT-Systems-and-Development/unicorn-binance-suite/discussions/categories/releases) | ||
|
||
[How to upgrade to the latest version!](https://unicorn-binance-suite.docs.lucit.tech/readme.html#installation-and-upgrade) | ||
|
||
## 1.1.0.dev (development stage/unreleased/unstable) | ||
|
||
## 1.1.0 | ||
## Adding | ||
- unicorn-binance-trailing-stop-loss | ||
|
||
## 1.0.2 | ||
Testing azure pipe | ||
|
||
## 1.0.1 | ||
PYPI and Conda integration | ||
|
||
## 1.0.0 | ||
Initial release. |
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,76 @@ | ||
# Contributor Covenant Code of Conduct | ||
|
||
## Our Pledge | ||
|
||
In the interest of fostering an open and welcoming environment, we as | ||
contributors and maintainers pledge to making participation in our project and | ||
our community a harassment-free experience for everyone, regardless of age, body | ||
size, disability, ethnicity, sex characteristics, gender identity and expression, | ||
level of experience, education, socio-economic status, nationality, personal | ||
appearance, race, religion, or sexual identity and orientation. | ||
|
||
## Our Standards | ||
|
||
Examples of behavior that contributes to creating a positive environment | ||
include: | ||
|
||
* Using welcoming and inclusive language | ||
* Being respectful of differing viewpoints and experiences | ||
* Gracefully accepting constructive criticism | ||
* Focusing on what is best for the community | ||
* Showing empathy towards other community members | ||
|
||
Examples of unacceptable behavior by participants include: | ||
|
||
* The use of sexualized language or imagery and unwelcome sexual attention or | ||
advances | ||
* Trolling, insulting/derogatory comments, and personal or political attacks | ||
* Public or private harassment | ||
* Publishing others' private information, such as a physical or electronic | ||
address, without explicit permission | ||
* Other conduct which could reasonably be considered inappropriate in a | ||
professional setting | ||
|
||
## Our Responsibilities | ||
|
||
Project maintainers are responsible for clarifying the standards of acceptable | ||
behavior and are expected to take appropriate and fair corrective action in | ||
response to any instances of unacceptable behavior. | ||
|
||
Project maintainers have the right and responsibility to remove, edit, or | ||
reject comments, commits, code, wiki edits, issues, and other contributions | ||
that are not aligned to this Code of Conduct, or to ban temporarily or | ||
permanently any contributor for other behaviors that they deem inappropriate, | ||
threatening, offensive, or harmful. | ||
|
||
## Scope | ||
|
||
This Code of Conduct applies both within project spaces and in public spaces | ||
when an individual is representing the project or its community. Examples of | ||
representing a project or community include using an official project e-mail | ||
address, posting via an official social media account, or acting as an appointed | ||
representative at an online or offline event. Representation of a project may be | ||
further defined and clarified by project maintainers. | ||
|
||
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
reported by contacting the project team at https://www.lucit.tech/contact-unicorn-developers.html. | ||
All complaints will be reviewed and investigated and will result in a response that | ||
is deemed necessary and appropriate to the circumstances. The project team is | ||
obligated to maintain confidentiality with regard to the reporter of an incident. | ||
Further details of specific enforcement policies may be posted separately. | ||
|
||
Project maintainers who do not follow or enforce the Code of Conduct in good | ||
faith may face temporary or permanent repercussions as determined by other | ||
members of the project's leadership. | ||
|
||
## Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, | ||
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html | ||
|
||
[homepage]: https://www.contributor-covenant.org | ||
|
||
For answers to common questions about this code of conduct, see | ||
https://www.contributor-covenant.org/faq |
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,17 @@ | ||
# Contributing | ||
|
||
When contributing to this repository, please first discuss the change you wish to make via | ||
[issue](https://github.com/LUCIT-Systems-and-Development/unicorn-binance-suite/issues/new/choose) | ||
with the owners of this repository before making a change. | ||
|
||
Please note we have a | ||
[code of conduct](https://github.com/LUCIT-Systems-and-Development/unicorn-binance-suite/blob/master/CODE_OF_CONDUCT.md), | ||
please follow it in all your interactions with the project. | ||
|
||
## Pull Request Process | ||
|
||
1. Discuss with owners | ||
2. Fork | ||
3. Contribute | ||
4. Fulfill and confirm requirements of the pull request | ||
5. Trigger the pull request |
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,108 @@ | ||
LSOSL - LUCIT Synergetic Open Source License | ||
============================================ | ||
|
||
Version 1.0, November 2023 | ||
|
||
1. INTRODUCTION | ||
2. PROJECT INFORMATION | ||
3. LICENSE CONDITIONS AND VERIFICATION | ||
4. LICENSE PURCHASE | ||
5. CONTRIBUTING CODE | ||
6. USAGE AND DISTRIBUTION | ||
7. DATA COLLECTION AND LICENSE CONTROL | ||
8. THIRD-PARTY SOFTWARE | ||
9. DISCLAIMER OF WARRANTY AND LIABILITY | ||
10. CHANGES TO LICENSE TERMS | ||
|
||
------------------------------------------------------------------------------------------------------------------------ | ||
|
||
1. INTRODUCTION | ||
|
||
The "LUCIT Synergetic Open Source License" oversees the utilization and distribution of the UNICORN Binance Suite | ||
by LUCIT IT-Management GmbH. This API enables the effortless integration of Binance features into diverse applications. | ||
|
||
|
||
2. PROJECT INFORMATION | ||
|
||
- Project name: UNICORN Binance Suite | ||
- Project page: https://www.lucit.tech/unicorn-binance-suite.html | ||
- GitHub repository: https://github.com/LUCIT-Systems-and-Development/unicorn-binance-suite | ||
- PyPI repository: https://pypi.org/project/unicorn-binance-suite | ||
- Get a license: https://shop.lucit.services/software | ||
|
||
|
||
3. LICENSE CONDITIONS AND VERIFICATION | ||
|
||
The use of UNICORN Binance Suite requires a license key and an API secret. | ||
|
||
Licenses are available at: https://shop.lucit.services/software | ||
|
||
Verification is done via a client-side module that forwards the license details to our backend for validation. | ||
The software may be used and distributed without restriction, the only condition is that the execution requires a valid | ||
license from LUCIT (https://shop.lucit.services/software) and must be operated with such a license. | ||
|
||
For transparency, our licensing client module is available on GitHub: | ||
https://github.com/LUCIT-Systems-and-Development/lucit-licensing-python | ||
|
||
|
||
4. LICENSE PURCHASE | ||
|
||
Usage of the our software necessitates obtaining a license from the LUCIT Online Shop. | ||
|
||
More details can be found at: https://shop.lucit.services/software | ||
|
||
|
||
5. CONTRIBUTING CODE | ||
|
||
Contributions via GitHub pull requests are welcome. However, contributors should be aware that submitted code | ||
automatically becomes LUCIT IT-Management GmbH's property and copyright. | ||
|
||
|
||
6. USAGE AND DISTRIBUTION | ||
|
||
The LSOSL licensed projects of LUCIT IT-Management GmbH can be used and integrated into any application without | ||
restriction and distributed as desired. The only condition is that the execution of our software requires a valid | ||
license from LUCIT (https://shop.lucit.services/software) and must be operated with such a license. | ||
|
||
For information on library versions that do not contain a license requirement, please contact: [email protected] | ||
|
||
|
||
7. DATA COLLECTION AND LICENSE CONTROL | ||
|
||
For license adherence, test license misuse prevention, API rate monitoring, and service improvement, we gather: | ||
|
||
- User IP addresses | ||
- Instance log data | ||
- Used Python version | ||
- Operating system type | ||
- API usage rates | ||
- MAC addresses (for misuse detection) | ||
- Data volume processed (anonymously aggregated) | ||
|
||
This data is stored only for its intended purpose and duration, except for anonymous statistics. We commit to | ||
confidentiality and non-disclosure. Details are in our privacy policy. | ||
|
||
|
||
8. THIRD-PARTY SOFTWARE | ||
|
||
The software may embed third-party code or libraries, each governed by their respective licenses. Ensure awareness and | ||
compliance when using the software. | ||
|
||
|
||
9. DISCLAIMER OF WARRANTY AND LIABILITY | ||
|
||
The software is rendered "as is", sans any assurances. LUCIT IT-Management GmbH disclaims liability for any potential | ||
repercussions arising from software usage. | ||
|
||
|
||
10. CHANGES TO LICENSE TERMS | ||
|
||
LUCIT IT-Management GmbH reserves the right to modify, alter, or update the terms of this license at any time and at | ||
its sole discretion. Users are encouraged to review the license terms regularly to ensure compliance. | ||
|
||
------------------------------------------------------------------------------------------------------------------------ | ||
|
||
Thank you for selecting the UNICORN Binance Suite and products from LUCIT IT-Management GmbH. We deeply value | ||
your trust in our technologies. | ||
|
||
LUCIT IT-Management GmbH - Am Berg 391, 3970 Weitra, AUSTRIA - https://www.lucit.tech |
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,4 @@ | ||
unicorn_binance_suite | ||
============================= | ||
|
||
|
Oops, something went wrong.