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

Create jekyll.yml #123

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
140 changes: 140 additions & 0 deletions .github/workflows/jekyll.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,140 @@
## AMPELChain Changelog and ROI Analysis

### High ROI Projects

**Project 1: Quantum Communication Network (APQ-CUZ-AP-GENSAI-CROSSPULSE-001)**
- **Description:** Secure communication leveraging quantum entanglement.
- **ROI Potential:** High

**Project 2: Quantum Algorithms for Aerodynamic Design (APQ-CUZ-AP-GENSAI-CROSSPULSE-002)**
- **Description:** Optimizing aircraft designs using quantum algorithms.
- **ROI Potential:** High

**Project 3: Quantum-Enhanced MRI Technology (APQ-CUZ-AP-GENSAI-CROSSPULSE-003)**
- **Description:** Improving MRI resolution and sensitivity using quantum mechanics.
- **ROI Potential:** Moderate to High

**Project 4: Quantum Financial Optimization (APQ-CUZ-AP-GENSAI-CROSSPULSE-004)**
- **Description:** Optimizing investment portfolios with quantum algorithms.
- **ROI Potential:** High

**Project 5: Quantum Environmental Monitoring (APQ-CUZ-AP-GENSAI-CROSSPULSE-005)**
- **Description:** Using quantum sensors for precise environmental monitoring.
- **ROI Potential:** Moderate

### Financial Integration and Automated Investment Strategy

**Weekly Investment Allocation (June to August):**
1. Ethereum (ETH): €50 per week
2. Solana (SOL): €50 per week
3. Binance Coin (BNB): €50 per week
4. Cardano (ADA): €50 per week
5. Ripple (XRP): €50 per week
6. PlayDoge (PLAY): €50 per week

**Additional Investment Allocation:**
- **July:** Reinforce positions in high-performing assets (ETH, SOL, BNB)
- **August:** Focus on emerging projects with high potential (Casper Network, SushiSwap)

### Automation and Validation

**Using Fin-AI Algorithms:**
- **DeltaOpt Function:** Dynamically adjust investments based on market trends.
- **Backtesting and Continuous Learning:** Validate the model with historical data and real-time adjustments.

### Portfolio Diversification

**Diversified Investment Strategy:**
- **Cryptocurrencies:** Ethereum, Solana, Binance Coin, Cardano, Ripple, PlayDoge
- **Stocks and ETFs:** Focus on technology and sustainable companies
- **Bonds:** ESG bonds for stable returns and reinvestment

### ESG Bonds and Reinvestment

**Reinvestment Plan:**
- **Initial Allocation:** 30% of gains to ESG bonds
- **Incremental Increase:** Increase reinvestment percentage as profits grow

### Automation Steps with Flask and PythonAnywhere

1. **Setup Flask Application:**
- Create endpoints for balance checks, price fetching, and order placements.
2. **Deploy on PythonAnywhere:**
- Utilize PythonAnywhere to host the Flask application and ensure it's accessible for automated scripts.

### Implementation Example

```python
from flask import Flask, request, jsonify
import requests
import alpaca_trade_api as tradeapi
from config import ALPACA_API_KEY, ALPACA_SECRET_KEY, ALPHA_VANTAGE_API_KEY

app = Flask(__name__)

# Initialize Alpaca API
api = tradeapi.REST(ALPACA_API_KEY, ALPACA_SECRET_KEY, base_url='https://paper-api.alpaca.markets')

def get_balance():
account = api.get_account()
balance = {
'cash': account.cash,
'portfolio_value': account.portfolio_value,
'equity': account.equity
}
return balance

def get_price(symbol):
endpoint = f'https://www.alphavantage.co/query?function=TIME_SERIES_INTRADAY&symbol={symbol}&interval=1min&apikey={ALPHA_VANTAGE_API_KEY}'
response = requests.get(endpoint)
data = response.json()
latest_time = list(data['Time Series (1min)'].keys())[0]
return float(data['Time Series (1min)'][latest_time]['1. open'])

def place_order(symbol, qty, side='buy'):
api.submit_order(
symbol=symbol,
qty=qty,
side=side,
type='market',
time_in_force='gtc'
)
return {'symbol': symbol, 'qty': qty, 'side': side}

@app.route('/balance', methods=['GET'])
def balance():
balance = get_balance()
return jsonify(balance)

@app.route('/prices', methods=['GET'])
def prices():
symbols = request.args.get('symbols').split(',')
prices = {symbol: get_price(symbol) for symbol in symbols}
return jsonify(prices)

@app.route('/place-order', methods=['POST'])
def order():
data = request.json
symbol = data['symbol']
qty = data['qty']
side = data['side']
order_response = place_order(symbol, qty, side)
return jsonify(order_response)

if __name__ == '__main__':
app.run(debug=True)
```

### Deployment on PythonAnywhere

1. Upload `app.py` and `config.py` to PythonAnywhere.
2. Setup Virtual Environment: `mkvirtualenv my-virtualenv --python=python3.8`
3. `pip install flask requests alpaca-trade-api`
4. Configure Web App: Set up the web app on PythonAnywhere to run the Flask application.
5. Monitor and Adjust: Use PythonAnywhere’s logs and monitoring tools to ensure the application runs smoothly.

### Conclusion

By integrating your financial situation, leveraging your projects, and using advanced algorithms, you can achieve your financial goals while maintaining a diversified and sustainable investment strategy. This plan ensures you are maximizing returns and reinvesting in ESG bonds, contributing to both personal growth and societal impact.

For more details, please visit [GitHub Project](https://github.com/users/AmePelliccia/projects/2/views/1?visibleFields=%5B%22Assignees%22%2C%22Title%22%2C%22Status%22%2C%22Repository%22%2C118224757%5D&layout=board&pane=issue&itemId=68914068).
170 changes: 94 additions & 76 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -1,76 +1,94 @@
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to make 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 within all project spaces, and it also applies when
an individual is representing the project or its community in public spaces.
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 [email protected]. 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
# Citizen Code of Conduct

## 1. Purpose

A primary goal of //Ampel||.GitHub is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).

This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.

We invite all those who participate in //Ampel||.GitHub to help us create safe and positive experiences for everyone.

## 2. Open [Source/Culture/Tech] Citizenship

A supplemental goal of this Code of Conduct is to increase open [source/culture/tech] citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.

Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society.

If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know.

## 3. Expected Behavior

The following behaviors are expected and requested of all community members:

* Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
* Exercise consideration and respect in your speech and actions.
* Attempt collaboration before conflict.
* Refrain from demeaning, discriminatory, or harassing behavior and speech.
* Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
* Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.

## 4. Unacceptable Behavior

The following behaviors are considered harassment and are unacceptable within our community:

* Violence, threats of violence or violent language directed against another person.
* Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
* Posting or displaying sexually explicit or violent material.
* Posting or threatening to post other people's personally identifying information ("doxing").
* Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
* Inappropriate photography or recording.
* Inappropriate physical contact. You should have someone's consent before touching them.
* Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
* Deliberate intimidation, stalking or following (online or in person).
* Advocating for, or encouraging, any of the above behavior.
* Sustained disruption of community events, including talks and presentations.

## 5. Weapons Policy

No weapons will be allowed at //Ampel||.GitHub events, community spaces, or in other spaces covered by the scope of this Code of Conduct. Weapons include but are not limited to guns, explosives (including fireworks), and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. Community members are further expected to comply with all state and local laws on this matter.

## 6. Consequences of Unacceptable Behavior

Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.

Anyone asked to stop unacceptable behavior is expected to comply immediately.

If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event).

## 7. Reporting Guidelines

If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible. 4. Contact Info: This is for the contact information where issues or breaches of the Code of Conduct can be reported..

1. Link to Reporting Guidelines: This is where you should provide a URL to the guidelines or a document where community members can learn how to report violations of the code of conduct.

Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.

## 8. Addressing Grievances

If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify 6. Governing Body: If your project or community is managed by a specific organization or committee, you can provide that information here. with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies. 2. Link to Policy: This could be a URL to the full Code of Conduct document or a related policy document.

3. Note: You might want to include any additional notes or specific instructions relevant to your community or project.

## 9. Scope

We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues--online and in-person--as well as in all one-on-one communications pertaining to community business.

This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.

## 10. Contact info

4. Contact Info: This is for the contact information where issues or breaches of the Code of Conduct can be reported.

## 11. License and attribution

The Citizen Code of Conduct is distributed by [Stumptown Syndicate](http://stumptownsyndicate.org) under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/).

Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy).

_Revision 2.3. Posted 6 March 2017._

_Revision 2.2. Posted 4 February 2016._

_Revision 2.1. Posted 23 June 2014._

_Revision 2.0, adopted by the [Stumptown Syndicate](http://stumptownsyndicate.org) board on 10 January 2013. Posted 17 March 2013._
Loading