That kind of certainty has a beauty to it.
1,415 karma · joined January 4, 2013
Founder of Folkvang: folkvang.io
https://mvr.com/ https://github.com/askmike
That kind of certainty has a beauty to it.
If you want to sell this much you really do not do it on screen (and definitely not at once). You get a big OTC desk to sell in tranches.
What do they say about correlation and causation?
Folkvang is a high frequency, quantitative trading firm active in the cryptocurrency markets. With a backing from Alameda Research, we’ve become a major player in the markets; powered by our fully proprietary technology and infrastructure, we trade billions of dollars a day across a variety of exchanges. We boast a team with years of experience in varied backgrounds and notably developed the open source project, Gekko.
We are looking to expand our team with a full stack developer with a deep understanding of nodejs and experience with quant trading, cryptocurrencies and (cloud) devops.
If you fit the bill, we should talk. Please email to hr at company domain and add:
- Your CV
- Github JS repo link / links to a JS code project
Really at this point it's too late to do anything else, instead of trying to dos your dev machine he can instead do simpler things like delete your ssh key from the machine. But let's play along:
> The attackers also take advantage of several of these RegEx DoS vulnerabilities to prevent you from quickly fixing the problem. When you discover the issue, you’ll first see that your build machine is unresponsive
There is nothing any attacker can do with the static files on the server that will trigger and RegEx DoS in your local development. Aside from the fact that you wouldn't download whatever is on the server back to your machine, even if you did it would never trigger such a DoS since (in the examples in the link) these are modules related to running a dev version of a frontend project based on the raw source files.
Your scenario is only true when an attacker pwned both your production server and your laptop. A regex DoS is really the last thing you worry about at that stage.
Folkvang is a high frequency, quantitative trading firm active in the cryptocurrency markets. With a backing from Alameda Research, we’ve become a major player in the markets; powered by our fully proprietary technology and infrastructure, we trade billions of dollars a day across a variety of exchanges. We boast a team with years of experience in varied backgrounds and notably developed the open source project, Gekko.
We are looking to expand our team with a full stack developer with a deep understanding of nodejs and experience with quant trading, cryptocurrencies and (cloud) devops.
If you fit the bill, we should talk. Please email to hr at company domain and add:
- Your CV
- Github JS repo link / links to a JS code project
I would love to play around with this, but the docs are a little light at the moment (unless I missed them). Would definitely recommend pushing docs and content on how to build custom strats, extend the main framework with custom reporting or new exchanges.
It does Binance but it's unclear to me what product types (I'm assuming spot markets).
Things I recommend exploring: (high latency) arbitrage between derivs and spot (for example cash and carry arbitrage). Or super simple funding arb on coinmargined perps (short 1x into synthetic usd). Pure directional is hard, and besides that there is a ton of alpha in more market neutral stuff.
----
A long while back I created a framework with a lot of overlapping functionality called Gekko (not trying to shill, I haven't maintained it for years). It took what I learned from that experience and build a prop trading firm called Folkvang. Crypto has a sea of opportunities ready to seize and in a bull market like we've seen in the last few months there is plenty of fish for everyone (yes there is a free lunch, even for those without a decade of quant/HFT experience from wall street).
----
play, build and have fun - can easily grow into a career
Folkvang is a high frequency, quantitative trading firm active in the cryptocurrency markets. With a backing from Alameda Research, we’ve become a major player in the markets; powered by our fully proprietary technology and infrastructure, we trade billions of dollars a day across a variety of exchanges. We boast a team with years of experience in varied backgrounds and notably developed the open source project, Gekko.
We are looking to expand our team with a full stack developer with a deep understanding of nodejs and experience with quant trading, cryptocurrencies and (cloud) devops.
If you fit the bill, we should talk - please email to hr@folkvang.io: - Your CV or relevant presentation - Github links (related repos or profile)
> Or rather, what most people in the industry pretend doesn't exist, because they know it's a systemic risk and everyone's in way too deep at this point.
Are you referring to the NYAG here?
They don't refuse this, instead they fail to find an auditor that people actually trust that wants to work on a big crypto project. They are very open about this.
The big problem about Tether is the amount of FUD and misinformation going around as common knowledge.
> I think the currently most plausible answer for how Tether works is
As someone who deals with Tether as well as all the big exchanges that run Tether markets, this is about as real as Alice in wonderland.
> Tether has been responsible for multiple bitcoin bubbles now
No one in the space actually believes this.
I think many people are trying to figure these questions for them out right now, as there is very little information yet on ARM support from many tools.
- If I buy an Apple I buy into this developer unfriendly ecosystem with a big gatekeeper.
- If I buy an Android I pay with all my privacy, on top of that Google is also a big bully to small app developers.
- Besides Google or Apple, what choices are there?
It wasn't, it was stored in a third party database.
> Genuine question - if mall had deployed people whose job was to look at people to guess their gender, age and then jot it down in a notebook, then would it have been a problem?
I don't think these notes would ever come close to "a biometric representation of their face" which can tell you with certainty someone was there or not (when, what time, who they were with).