KalshiAh ok ty!
Ah ok ty!
𝓛𝓮𝓸参与话题 5消息总数 31
该用户的聊天记录定位。
聊天记录
共 31 条，显示第 1-31 条Maybe I'm dumb but I don't see how this differs from normal activity? Wasn't the quoter already a maker and the other side already a taker? Is there a specific edge case here I'm unaware of?
Maybe I'm dumb but I don't see how this differs from normal activity? Wasn't the quoter already a maker and the other side already a taker? Is there a specific edge case here I'm unaware of?
Maybe you should ask the AI that produced these numbers if it's fast 🤣 (fwiw I simply don't believe these numbers are even real, maybe check what it's actually measuring under the hood? feels like it's looking at the wrong thing)
Maybe you should ask the AI that produced these numbers if it's fast 🤣 (fwiw I simply don't believe these numbers are even real, maybe check what it's actually measuring under the hood? feels like it's looking at the wrong thing)
I think the question was more for a min price, i.e. betaclone wants to avoid trading at all if there is a maker willing to give him too good of a price (this doesn't exist natively on the exchange, so there's always a bit of a race here)
I think the question was more for a min price, i.e. betaclone wants to avoid trading at all if there is a maker willing to give him too good of a price (this doesn't exist natively on the exchange, so there's always a bit of a race here)
I'm out of the loop - why's that?
I'm out of the loop - why's that?
Not really: only in super narrow cases where the legs have the exact same set of events and they're all mutually exclusive (And you can check for this by seeing if the combo event is mutually exclusive)
Not really: only in super narrow cases where the legs have the exact same set of events and they're all mutually exclusive (And you can check for this by seeing if the combo event is mutually exclusive)
Why would you ever want to hold both sides vs having them net out?
Why would you ever want to hold both sides vs having them net out?
I'm not entirely sure if `Markets not found` is going to even accomplish the intended load reduction on Kalshi's servers. Instead of sending batched subscribes I now have to do them one by one to even detect which is closed :/
I'm not entirely sure if `Markets not found` is going to even accomplish the intended load reduction on Kalshi's servers. Instead of sending batched subscribes I now have to do them one by one to even detect which is closed :/
I'm seeing this too
I'm seeing this too
Hmm don't know if it's documented anywhere, I just observed the same thing as you haha
Hmm don't know if it's documented anywhere, I just observed the same thing as you haha
The ticker channel updates at a 1s frequency (and only if there is a change to report), not every delta
The ticker channel updates at a 1s frequency (and only if there is a change to report), not every delta
Entire RFQ system down rn?
Entire RFQ system down rn?
Contests are legally different than trading, so it's more restricted
Contests are legally different than trading, so it's more restricted
Earlier today I subscribed to orderbook deltas for `KXINTLFRIENDLYGAME-26JUN09LBRSLE-LBR` and received an initial snapshot that was ~20m out of date, followed by deltas that were similarly out of date (when compared to another websocket I already had running, and the website's chart). How could this be? It was a fresh connection so no backlog/backpressure by definition, and it was internally consistent (not crossed) leading me to believe that it was replaying a correct sequence of deltas but just 20m late. It feels like this must be a Kalshi server-side bug and I have no clue how to plausibly correct for this happening outside of running multiple websockets in parallel and having a voting process or something like that. Has anyone seen something similar and/or know how to get a Kalshi dev to look into it? While I don't have the raw deltas recorded and can't repro it (the market is closed), I have side by side logs of bbos and such that are definitely mismatched
Earlier today I subscribed to orderbook deltas for `KXINTLFRIENDLYGAME-26JUN09LBRSLE-LBR` and received an initial snapshot that was ~20m out of date, followed by deltas that were similarly out of date (when compared to another websocket I already had running, and the website's chart). How could this be? It was a fresh connection so no backlog/backpressure by definition, and it was internally consistent (not crossed) leading me to believe that it was replaying a correct sequence of deltas but just 20m late. It feels like this must be a Kalshi server-side bug and I have no clue how to plausibly correct for this happening outside of running multiple websockets in parallel and having a voting process or something like that. Has anyone seen something similar and/or know how to get a Kalshi dev to look into it? While I don't have the raw deltas recorded and can't repro it (the market is closed), I have side by side logs of bbos and such that are definitely mismatched
"Bumbling Bayesian told me to full port Spencer Pratt YES!!!" 😱
"Bumbling Bayesian told me to full port Spencer Pratt YES!!!" 😱
We all have root, that's a moot point if you read the agreement though
We all have root, that's a moot point if you read the agreement though
The owner of the API key sshes in and uses it in their own process when necessary
The owner of the API key sshes in and uses it in their own process when necessary
They don't want people making a frontend/app that induces users to input an API key or password, but that's very clearly not what I'm describing
They don't want people making a frontend/app that induces users to input an API key or password, but that's very clearly not what I'm describing
If you can point to a single mod message saying so I'd happily forfeit my claims!
If you can point to a single mod message saying so I'd happily forfeit my claims!
I'm saying that the letter, as I have read it, does not prohibit it. And nothing Kalshi has ever said would lead me to believe they don't want people doing it.
I'm saying that the letter, as I have read it, does not prohibit it. And nothing Kalshi has ever said would lead me to believe they don't want people doing it.
My read of the agreement is that using the API as someone else is prohibited, not that having the ability to go snoop (but not doing so) if I were nefarious and have root access to a shared server is prohibited In the same way that it's not prohibited/illegal for me to log into my own bank account on a shared family computer
My read of the agreement is that using the API as someone else is prohibited, not that having the ability to go snoop (but not doing so) if I were nefarious and have root access to a shared server is prohibited In the same way that it's not prohibited/illegal for me to log into my own bank account on a shared family computer
Did you place your bet to win $19 at 5:15pm? Because if so, then I and literally any one of the thousands of other members of the public who record trade logs can verify what bet you placed and that it doesn't match your claim
Did you place your bet to win $19 at 5:15pm? Because if so, then I and literally any one of the thousands of other members of the public who record trade logs can verify what bet you placed and that it doesn't match your claim
Hmm I'm just simply 100% certain that what I'm describing doesn't break the rules in any way and isn't even a grey area. We are all traders+coders who are writing code and running it using our own API keys in totally separate processes. There isn't overlap beyond being on the same physical server. Not trying to tell you how to do your thing - just trying to make it known to newcomers here that there's no need to be scared of doing something similar to save on hosting costs / ops overhead
Hmm I'm just simply 100% certain that what I'm describing doesn't break the rules in any way and isn't even a grey area. We are all traders+coders who are writing code and running it using our own API keys in totally separate processes. There isn't overlap beyond being on the same physical server. Not trying to tell you how to do your thing - just trying to make it known to newcomers here that there's no need to be scared of doing something similar to save on hosting costs / ops overhead
I hate to say it but this was surely a mistake when making the trade originally. All trading activity is public and verifiable so there simply isn't a way for this to have changed after the fact. It sounds like you placed your bet on KXMVESPORTSMULTIGAMEEXTENDED-S2026C54E3C21A0A-0C9AB70D74C and I can clearly see a record of someone putting down $8.66 to win $19 at 5:15pm ET yesterday, was that you? This is in my logs that I recorded at the time of the trade and there is no way Kalshi could've changed my logs later on.
I hate to say it but this was surely a mistake when making the trade originally. All trading activity is public and verifiable so there simply isn't a way for this to have changed after the fact. It sounds like you placed your bet on KXMVESPORTSMULTIGAMEEXTENDED-S2026C54E3C21A0A-0C9AB70D74C and I can clearly see a record of someone putting down $8.66 to win $19 at 5:15pm ET yesterday, was that you? This is in my logs that I recorded at the time of the trade and there is no way Kalshi could've changed my logs later on.
I don't see anything in https://kalshi.com/developer-agreement forbidding that? FWIW I share a VPS with others and it's fine... like we just run our different stuff separarely but it's all from the same IP and has never once caused an issue. One note is that we do sign all API requests even those that don't require it so that it counts against the account's rate limit and not the IP's rate limit.
I don't see anything in https://kalshi.com/developer-agreement forbidding that? FWIW I share a VPS with others and it's fine... like we just run our different stuff separarely but it's all from the same IP and has never once caused an issue. One note is that we do sign all API requests even those that don't require it so that it counts against the account's rate limit and not the IP's rate limit.
I trade MVE markets but just listening to rfqs and trades gives a comprehensive enough view imo. Can't imagine going through 1400 pages of markets gets you any additional value?
I trade MVE markets but just listening to rfqs and trades gives a comprehensive enough view imo. Can't imagine going through 1400 pages of markets gets you any additional value?
ooc is this out of idle curiosity or do you have a legit reason to need to walk all open markets?
ooc is this out of idle curiosity or do you have a legit reason to need to walk all open markets?
I'd put money on your implementation dropping deltas somehow - but ooc which markets are you seeing this on?
I'd put money on your implementation dropping deltas somehow - but ooc which markets are you seeing this on?
Ohhh ty you just made me go back and re-read the assertion and I'd gotten it wrong: the failure was not a nonnull cursor but a completely missing cursor 🤦♂️ Still weird that it's the first time it's occurred in forever hah
Ohhh ty you just made me go back and re-read the assertion and I'd gotten it wrong: the failure was not a nonnull cursor but a completely missing cursor 🤦♂️ Still weird that it's the first time it's occurred in forever hah
Like I don't use server-side pagination, I just have my system manually send out batches <100 markets at a time, and it's been completely stable for months until today
Like I don't use server-side pagination, I just have my system manually send out batches <100 markets at a time, and it's been completely stable for months until today
I just had a GET to `/trade-api/v2/markets` with `tickers` set to <100 individual tickers return a response with a nonnull `cursor` (i.e. != `""`). Is that ever expected? Has anyone ever seen anything like it? It tripped an assertion I have for the first time in months of trading but I can't repro it lol
I just had a GET to `/trade-api/v2/markets` with `tickers` set to <100 individual tickers return a response with a nonnull `cursor` (i.e. != `""`). Is that ever expected? Has anyone ever seen anything like it? It tripped an assertion I have for the first time in months of trading but I can't repro it lol