Kalshiprobably not good for their data selling business
probably not good for their data selling business
brunoBowser参与话题 12消息总数 209
该用户的聊天记录定位。
聊天记录
共 209 条，显示第 151-200 条yeah - I estimated off of Greed's numbers yesterday but those were like half of what is shown (which confirmed my suspicion that Greed is missing a good deal of transaction data)
yeah - I estimated off of Greed's numbers yesterday but those were like half of what is shown (which confirmed my suspicion that Greed is missing a good deal of transaction data)
AWS is pretty granular but it is honestly a pain - I prefer it over Azure tho - Azure is slightly more user friendly (slightly) but is not as granular and can be clunky for certain use cases. I've never used DigitalOcean but assume it is a similar to services like Heroku, in which case it is 10x easier to use than AWS. Basically if you don't have an infrastructure background you will have a painful learning curve with AWS. I don't have an infra background but was too stubborn to switch course - I like AWS for the most part but there are still days when I wish Borders had won the book wars
AWS is pretty granular but it is honestly a pain - I prefer it over Azure tho - Azure is slightly more user friendly (slightly) but is not as granular and can be clunky for certain use cases. I've never used DigitalOcean but assume it is a similar to services like Heroku, in which case it is 10x easier to use than AWS. Basically if you don't have an infrastructure background you will have a painful learning curve with AWS. I don't have an infra background but was too stubborn to switch course - I like AWS for the most part but there are still days when I wish Borders had won the book wars
Thats a broad question - there are all kinds of factors including (but not limited to) latency to your signals, latency to the exchange, infrastructure requirements, budget, and your own technical ability - you will want to answer those for yourself and then start measuring metrics to find an optimal location baesd on your needs. I know (from previous comments) there are bots in Azure, AWS and DigitalOcean. AWS seems to be the most common but it does tend to have a higher learning curve than others
Thats a broad question - there are all kinds of factors including (but not limited to) latency to your signals, latency to the exchange, infrastructure requirements, budget, and your own technical ability - you will want to answer those for yourself and then start measuring metrics to find an optimal location baesd on your needs. I know (from previous comments) there are bots in Azure, AWS and DigitalOcean. AWS seems to be the most common but it does tend to have a higher learning curve than others
have you restarted your own runtime? Seems OK for me but I don't have that detailed logging turned on so could be missing the issue
have you restarted your own runtime? Seems OK for me but I don't have that detailed logging turned on so could be missing the issue
Because when my bot tries to buy them, they aren’t there but are consistently showing on the WS feed after resubs. If they were being flickered by another bot at the same price, they would fill my resting orders. This happened earlier in the week as well
Because when my bot tries to buy them, they aren’t there but are consistently showing on the WS feed after resubs. If they were being flickered by another bot at the same price, they would fill my resting orders. This happened earlier in the week as well
Showing contracts on offer that do not exist
Showing contracts on offer that do not exist
Congrats - may be a bit concerning tho that your bot works when the data is bad but wasn’t profitable when the data was good
Congrats - may be a bit concerning tho that your bot works when the data is bad but wasn’t profitable when the data was good
WS giving out some bad data right now - looks like maybe cached/stale data. Y'all have good luck with that - I'm not exposing capital to this yet again - hopefully your PnLs work out.
WS giving out some bad data right now - looks like maybe cached/stale data. Y'all have good luck with that - I'm not exposing capital to this yet again - hopefully your PnLs work out.
Wait - did just my TV freeze at the exact same time?
Wait - did just my TV freeze at the exact same time?
It’s kinda their MO
It’s kinda their MO
Just table stakes at this point
Just table stakes at this point
Oh yeah - another thing to be aware of - during major outages, often the first restart doesn’t take - best to just let your bot take a well earned vacation until they are back up for a bit (if your strat allows)
Oh yeah - another thing to be aware of - during major outages, often the first restart doesn’t take - best to just let your bot take a well earned vacation until they are back up for a bit (if your strat allows)
There are a lot of things one can do to mitigate the issues. It’s tough and expensive to figure those out unfortunately
There are a lot of things one can do to mitigate the issues. It’s tough and expensive to figure those out unfortunately
Kicking him when he is down - not very nice
Kicking him when he is down - not very nice
We could avoid freakouts (that each of us has done in their own turn) when this type of thing happens (as it does rather regularly)
We could avoid freakouts (that each of us has done in their own turn) when this type of thing happens (as it does rather regularly)
Someone should really write a best practices post - some kind of “shit will hit the fan - here’s how to protect yourself” manual
Someone should really write a best practices post - some kind of “shit will hit the fan - here’s how to protect yourself” manual
Not guaranteed
Not guaranteed
They often do that
They often do that
First timer I am guessing - welcome
First timer I am guessing - welcome
For all the folks experiencing their first critical outage - welcome to the club - looks like you got some new code to write tomorrow
For all the folks experiencing their first critical outage - welcome to the club - looks like you got some new code to write tomorrow
Commodore64s take some time to reboot - patience is required
Commodore64s take some time to reboot - patience is required
Better than the 10 gb it used to be (for me). I literally could only use the desktop site on a gaming machine
Better than the 10 gb it used to be (for me). I literally could only use the desktop site on a gaming machine
That’s most likely due to non-auth limits based on IP - not account limits. I notice the issue when I am doing testing locally but my cloud deployment does not experience it. If your bot is running local then you will encounter it unless you run either your browser traffic or your bot through a proxy/VPN
That’s most likely due to non-auth limits based on IP - not account limits. I notice the issue when I am doing testing locally but my cloud deployment does not experience it. If your bot is running local then you will encounter it unless you run either your browser traffic or your bot through a proxy/VPN
Yeah - it might make sense to reduce rate limit token cost for certain markets - granted doing so will just create a rush of everyone wanting the cost to be reduced on their preferred markets. They would probably need to restrict it to markets below a certain volume to not clog the exchange (eg exclude certain sports markets from such a program since those are the ones that tend to be linked to exchange latency)
Yeah - it might make sense to reduce rate limit token cost for certain markets - granted doing so will just create a rush of everyone wanting the cost to be reduced on their preferred markets. They would probably need to restrict it to markets below a certain volume to not clog the exchange (eg exclude certain sports markets from such a program since those are the ones that tend to be linked to exchange latency)
That sucks
That sucks
Would you even get to a higher tier with the 15 minute markets? Seems like thats gonna bleed out your rate limit without getting to the exchange percentages needed
Would you even get to a higher tier with the 15 minute markets? Seems like thats gonna bleed out your rate limit without getting to the exchange percentages needed
I don’t think anyone grabs (or cares about) them that early though so it seems to be overkill - if they can’t do dynamic then they should list closer to start
I don’t think anyone grabs (or cares about) them that early though so it seems to be overkill - if they can’t do dynamic then they should list closer to start
I assume they mean for order management - but if they are getting price data from the API then ouch
I assume they mean for order management - but if they are getting price data from the API then ouch
Yeah - that’s a pain - better if they dynamically added them instead of spamming
Yeah - that’s a pain - better if they dynamically added them instead of spamming
For some
For some
Everyone knows that knockoff beanie babies are where it is at
Everyone knows that knockoff beanie babies are where it is at
So you REALLY like your money to be overrated
So you REALLY like your money to be overrated
Money is overrated
Money is overrated
Let’s not get to hasty - coding errors put food on the table
Let’s not get to hasty - coding errors put food on the table
Not for numbat
Not for numbat
Yeah - $10 is pretty limiting - altho I started with $100 so its doable
Yeah - $10 is pretty limiting - altho I started with $100 so its doable
Just let it rip - no one here will complain of your model loses money
Just let it rip - no one here will complain of your model loses money
Just make sure that when you find out I was right, that you loosen up your model so I can pick off a few layup trades 😀
Just make sure that when you find out I was right, that you loosen up your model so I can pick off a few layup trades 😀
The model is only "dynamically picking" one or two markets to trade in at any one given time (probably based on how your criteria is set) - hence the bands - those bands are tracking your profitability in singular markets - color code by market ticker and I put good money it is correct.
The model is only "dynamically picking" one or two markets to trade in at any one given time (probably based on how your criteria is set) - hence the bands - those bands are tracking your profitability in singular markets - color code by market ticker and I put good money it is correct.
Actually, simpler than that - each band represents a single market and you are only targeting one market at a time (sometimes two) - the band itself is the change in price of the band as you buy it represented as your profit/loss.
Actually, simpler than that - each band represents a single market and you are only targeting one market at a time (sometimes two) - the band itself is the change in price of the band as you buy it represented as your profit/loss.
Did you look it in comparison to the actual underlying? For example, did you overlay your chart over the BTC price and price change velocity? A quick glance tells me that it is likely your bands are explained in there - but I'll let you do that work.
Did you look it in comparison to the actual underlying? For example, did you overlay your chart over the BTC price and price change velocity? A quick glance tells me that it is likely your bands are explained in there - but I'll let you do that work.
changelog says 11th
changelog says 11th
Also a good way to test if your kill switches work properly when the exchange “hiccups” - not gonna happen in demo
Also a good way to test if your kill switches work properly when the exchange “hiccups” - not gonna happen in demo
It allows you to compartmentalize funds. For many (unfortunately) it is just a way to be lazy about position management. (Not saying it isn’t used properly by some, just not most) If you are using one strat and are limiting your money on the exchange it is likely overkill and will lead to more headaches. I would recommend keeping it simple but be aware of their basic mechanics and look to expand your code later to leverage if appropriate. There is a lot to be learned in position management (eg force cancels) that will keep you busy and sub accounts will make it more difficult.
It allows you to compartmentalize funds. For many (unfortunately) it is just a way to be lazy about position management. (Not saying it isn’t used properly by some, just not most) If you are using one strat and are limiting your money on the exchange it is likely overkill and will lead to more headaches. I would recommend keeping it simple but be aware of their basic mechanics and look to expand your code later to leverage if appropriate. There is a lot to be learned in position management (eg force cancels) that will keep you busy and sub accounts will make it more difficult.
Back when the Kalshi server was just a single Commodore64 (now they have hundreds)
Back when the Kalshi server was just a single Commodore64 (now they have hundreds)
I think the last time I used the demo API was back when we used a password to access the API. Maybe even back in the day of V1 api and the old endpoints.
I think the last time I used the demo API was back when we used a password to access the API. Maybe even back in the day of V1 api and the old endpoints.
And, yes, we all test in Prod. I don't even think my demo credentials are even stored anywhere anymore
And, yes, we all test in Prod. I don't even think my demo credentials are even stored anywhere anymore
You couldn't test that anyway even if demo had activity - only test that is in prod with gradual scaling. Make sure you have settings accessible outside of your runtime to change on the fly and ramp up and you should be fine
You couldn't test that anyway even if demo had activity - only test that is in prod with gradual scaling. Make sure you have settings accessible outside of your runtime to change on the fly and ramp up and you should be fine
I would also recommend you hook it up to prod and test the full route stopping just before sending trades if you haven't tested your runtime on prod yet - a lot more data coming through - a lot more things that you may have missed hooked to demo.
I would also recommend you hook it up to prod and test the full route stopping just before sending trades if you haven't tested your runtime on prod yet - a lot more data coming through - a lot more things that you may have missed hooked to demo.