public inbox for gccadmin@sourceware.org help / color / mirror / Atom feed
From: Lior <lhirschfeld@kalshi.com> To: gccadmin@gcc.gnu.org Subject: We’re building a new exchange for quants and would love your thoughts Date: Wed, 19 Apr 2023 21:45:41 +0000 [thread overview] Message-ID: <20230419214541.5407a128516edb7d@cio73255.kalshi.com> (raw) [-- Attachment #1: Type: text/plain, Size: 1570 bytes --] Good afternoon! It’s nice to meet you - my name is Lior, and I’m a software engineer at Kalshi ( https://kalshi.com/quant?utm_source=quant-04-17-23&utm_medium=email&utm_campaign=growth-free&utm_content=for-quants&utm_term=for-quants ). I saw that you’d starred the MachineLearningStocks repo on GitHub, and thought based on your interest in quant trading you might enjoy our platform. We’re a federally-regulated options exchange that was established in 2020. We’ve tried to structure the platform with programmatic traders in mind - our markets are volatile and settle daily, which means that a small edge can be extremely profitable. Trading is fully-cash collateralized, so you can never lose more than you put into a trade, and contracts can be purchased for as little as $0.01. It’s very easy to get started - we support trading through our native app, website, and API. For the latter, we provide extensive documentation, open-sourced sample code, and live technical support. Installing our package is as easy as `pip3 install kalshi_python`. We also run a Discord community for our members, which is a great place to get started if you have any questions. If you’re interested in joining the exchange, you can sign-up using the link above. If you do, I’d be happy to give you $50 of credit to get started with, and I’d love to hear your thoughts. Sincerely, Lior Community & Engineering at Kalshi unsubscribe ( http://track.customer.io/unsubscribe/dgTYlwcAAJnmE5jmEwGHm3iYuEmXUrZH1uFh6eE= )
reply other threads:[~2023-04-19 21:45 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230419214541.5407a128516edb7d@cio73255.kalshi.com \ --to=lhirschfeld@kalshi.com \ --cc=gccadmin@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).