Skip to content
No description, website, or topics provided.
Branch: master
Clone or download

README.md

Wall-Street-Bets-Master-Doc

Hey, guys. Welcome to the GitHub page. We'll be splitting it up into a few different sections, depending on area of research.

The workflow of this project is largely going to be dictated by its main purpose, which is identifying vulnerable assets, in particular, corporate debt. There are a few subtopics that we might explore that lie a bit outside the scope of that, but by and large, the thrust is debt. Here's a rough outline of the game plan, broken down into steps:

  1. FA team will identify at-risk market demographics, including foreign banks and distressed debt generally.
  2. They'll be crosschecked by other FA members until a consensus is reached on risk levels; justifications for each in a writeup would be great
  3. Tickers will then be passed on to the TA/data guys, who can set up a bunch of indicators and alerts and generally work their computer magic to best predict the window in which these will fail; graphs and math are appreciated

We now have a list of vulnerable target securities that we're going to work on exploiting: CMBS; Shadow bank bonds (like Quicken); Oil bonds; Tech bonds

We need to begin identifying BTOs (if possible (BTOs are just CLO/CDOs, because of course they are)) that target these assets. They're going to fail. Stay tuned, I'm just writing this down so I don't forget it.

Some tentative deadlines I'd like to set for each of the steps are

  1. 3/20/20 for a comprehensive (not exhaustive) list of at-risk targets and tickers
  2. 4/3/20 for completed analysis and approval of a list of tickers
  3. 4/3/20 for a set of agreed-upon tracking strategies for the targets.

I'd like regular check-ins with progress. Say, a minimum of once every day or two. Either post your research directly or relay it to your team lead post-haste.

TechnicalANALyst is your TA team lead; Cannabiz-420/Ti-84/Wa ge is your FA team lead; Jellyra is your macro team lead. Lelouch_lamperouge is master-of-all-trades, jack-of-none. He's kind of like a magic 8-ball, except he's always right. Be nice to him and you might be rewarded.

If you have any concerns, comments, questions, or suggestions, please feel free to hit me up on discord or bring them to the attention of your team lead.

I really appreciate your time and enthusiasm, guys. I'm stunned that I was met with such a flood of excited talent; you guys are experts and actual powerhouses in each of your fields. It's impressive, and I'm really happy to be a part of this. I'm going to do my best here to keep morale up and attention focused; the death of this project will be waning enthusiasm. I don't want to act like a boss or a manager, but I do want to keep everyone working towards this goal. Expect to put at least an hour or two of work into this every week to keep the wheels turning. As long as everything keeps flowing, I'll be here nonstop to keep things moving and handle anything that needs handling. I don't know how this is going to turn out, but between the lot of you, there's an incredible pool of potential to tap into and use to our advantage. Let's make some tendies, guys.

Contributing to the Github Repository

  1. Create a branch by selecting the branch dropdown, typing a name, and click Create.
  2. Navigate to the folder or file you want to change.
  3. Upload files or edit the file you want, and at the bottom, commit it directly to the branch you just created.
  4. Navigate back to the home page of the repository
  5. You should see the option to create a New Pull Request. Click that, and submit a Pull Request from your new branch into master.
  6. Your changes will be approved and merged in shortly.
You can’t perform that action at this time.