KalshiYeah, I was torn between being helpful and being adversarial.
Yeah, I was torn between being helpful and being adversarial.
Bumbling Bayesian参与话题 33消息总数 209
该用户的聊天记录定位。
聊天记录
共 209 条，显示第 151-200 条You have a queue of infinite capacity?
You have a queue of infinite capacity?
You still have to have the same amount of compute to process the messages.
You still have to have the same amount of compute to process the messages.
I'm at ~27k and no errors.
I'm at ~27k and no errors.
That is, by not very strict, I mean that they could easily add some more constraints to the property definitions that would match what the documentation says.
That is, by not very strict, I mean that they could easily add some more constraints to the property definitions that would match what the documentation says.
Their schema isn't very strict. But it would catch at least some problems if they validated requests and responses against it.
Their schema isn't very strict. But it would catch at least some problems if they validated requests and responses against it.
That makes sense and is a smaller ask.
That makes sense and is a smaller ask.
They need a way for `add_markets` to accept a market filter predicate rather than simply explicit tickers.
They need a way for `add_markets` to accept a market filter predicate rather than simply explicit tickers.
Nice!
Nice!
I took a semester off in 1993. Never went back.
I took a semester off in 1993. Never went back.
I don't know. I hit my big red button immediately upon receipt of Noah's message.
I don't know. I hit my big red button immediately upon receipt of Noah's message.
It is a shame that Kalshi is not more eager for bug reports.
It is a shame that Kalshi is not more eager for bug reports.
I figured that someone had already figured this out as a way to DoS the exchange given the number of problems we have seen since.
I figured that someone had already figured this out as a way to DoS the exchange given the number of problems we have seen since.
On July 16, 2025, Noah reached out to me. I had a bug that was creating dumb orders. Noah said I had the majority of resting orders on the exchange and it was causing problems.
On July 16, 2025, Noah reached out to me. I had a bug that was creating dumb orders. Noah said I had the majority of resting orders on the exchange and it was causing problems.
Looks like the 200,000 order limit was added no later than 2025-12-02, which is when I first committed a version of openapi.yaml which had that note.
Looks like the 200,000 order limit was added no later than 2025-12-02, which is when I first committed a version of openapi.yaml which had that note.
I do not remember seeing a limit before.
I do not remember seeing a limit before.
No, v2 is v2. There is now a v2 of v2.
No, v2 is v2. There is now a v2 of v2.
There was also that time period when v2 provided an endpoint for yet another version number.
There was also that time period when v2 provided an endpoint for yet another version number.
And Kalshi has a history of remaining silent on questions explicitly asked. It is entirely reasonable that engineers and support have been instructed to not be honest or candid on some topics.
And Kalshi has a history of remaining silent on questions explicitly asked. It is entirely reasonable that engineers and support have been instructed to not be honest or candid on some topics.
Some days I feel a little mischievous and consider encouraging people to do dumb things.
Some days I feel a little mischievous and consider encouraging people to do dumb things.
Is Trump Jr. not helping these companies he advises on compliance?
Is Trump Jr. not helping these companies he advises on compliance?
That makes sense. Maybe not so much thinking about international users specifically as just needing an SSN for reporting.
That makes sense. Maybe not so much thinking about international users specifically as just needing an SSN for reporting.
You should bring this up directly with support. There is no guarantee they will see this conversation.
You should bring this up directly with support. There is no guarantee they will see this conversation.
Only via API, as far as I know.
Only via API, as far as I know.
But in Kalshi’s defense, I would have no idea how to handle reporting requirements for international users.
But in Kalshi’s defense, I would have no idea how to handle reporting requirements for international users.
Just a guess. I have no idea. But don’t be surprised that Kalshi is behind on what is expected of fintech companies in general.
Just a guess. I have no idea. But don’t be surprised that Kalshi is behind on what is expected of fintech companies in general.
The web UI.
The web UI.
Interesting. I am wondering if this is because of compliance/KYC requirements. If they cannot figure out who your interest should be reported to, maybe they don’t pay it.
Interesting. I am wondering if this is because of compliance/KYC requirements. If they cannot figure out who your interest should be reported to, maybe they don’t pay it.
It makes sense to me also that it should be deposited to subaccount 0 because maybe it is hard to tell which subaccount(s) provided the liquidity. But it shouldn’t show up on the history of other subaccounts.
It makes sense to me also that it should be deposited to subaccount 0 because maybe it is hard to tell which subaccount(s) provided the liquidity. But it shouldn’t show up on the history of other subaccounts.
Yeah, it is hokey.
Yeah, it is hokey.
Try https://api.elections.kalshi.com/trade-api/v2/historical/markets/KXGOVSHUT-26JAN31. Looks like it has been archived.
Try https://api.elections.kalshi.com/trade-api/v2/historical/markets/KXGOVSHUT-26JAN31. Looks like it has been archived.
Are liquidity incentives just going to subaccount 0? I see the same values reported under Credit for every subaccount.
Are liquidity incentives just going to subaccount 0? I see the same values reported under Credit for every subaccount.
I got one at 2026-06-09T08:48:27.586097Z.
I got one at 2026-06-09T08:48:27.586097Z.
U.S. fintech is so dumb. It feels like the banks I work with are deliberately dragging their heels on FedNow. So much duct tape and Rube Goldberg plumbing could go away.
U.S. fintech is so dumb. It feels like the banks I work with are deliberately dragging their heels on FedNow. So much duct tape and Rube Goldberg plumbing could go away.
I have code that works with my business bank to pay vendors via ACH and Nacha formatted files SFTP'd to my bank. Some businesses use Plaid for that. It is just table stakes for any modern business of scale. Kalshi will eventually support this if they want more institutional users.
I have code that works with my business bank to pay vendors via ACH and Nacha formatted files SFTP'd to my bank. Some businesses use Plaid for that. It is just table stakes for any modern business of scale. Kalshi will eventually support this if they want more institutional users.
I think it makes sense that from Kalshi's perspective they might think of CloudFront as a shared resource versus having their own load balancer.
I think it makes sense that from Kalshi's perspective they might think of CloudFront as a shared resource versus having their own load balancer.
I think this is just imprecise terminology for CloudFront (shared) versus the load balancer they are now using.
I think this is just imprecise terminology for CloudFront (shared) versus the load balancer they are now using.
I am not answering for James or in any official capacity, but will try to help: The API has been hosted on AWS CloudFront. That is the legacy/deprecated https://elections.api.kalshi.com/. The API now is also now being served up at https://external-api.kalshi.com/ and that is where we are directed to go now. So "dedicated external trade api hosts" is the new host, external-api.kalshi.com (and related), and "existing shared hosts" is the deprecated hostname(s), which might stop working at some point.
I am not answering for James or in any official capacity, but will try to help: The API has been hosted on AWS CloudFront. That is the legacy/deprecated https://elections.api.kalshi.com/. The API now is also now being served up at https://external-api.kalshi.com/ and that is where we are directed to go now. So "dedicated external trade api hosts" is the new host, external-api.kalshi.com (and related), and "existing shared hosts" is the deprecated hostname(s), which might stop working at some point.
(that is, sometimes the collection only has one item)
(that is, sometimes the collection only has one item)
From the POV of my client SDK, I pass in a collection of orders and it decides how to batch them. I agree that everything should just be either one or a collection.
From the POV of my client SDK, I pass in a collection of orders and it decides how to batch them. I agree that everything should just be either one or a collection.
When I first started with the API, it seemed promising to minimize latency and there was the decreased cost against the rate limit. I have since discovered it is not that simple, so wouldn't care if batch was deprecated.
When I first started with the API, it seemed promising to minimize latency and there was the decreased cost against the rate limit. I have since discovered it is not that simple, so wouldn't care if batch was deprecated.
My system noticed this morning that `category` disappeared from the event object. (https://discord.com/channels/871819895443189862/927686720990892032/1511333667803238470)
My system noticed this morning that `category` disappeared from the event object. (https://discord.com/channels/871819895443189862/927686720990892032/1511333667803238470)
If you have never had an auth request work before, you have likely not yet correctly implemented the signing algorithm.
If you have never had an auth request work before, you have likely not yet correctly implemented the signing algorithm.
Got another one of these at 2026-06-02T13:11:36.156316Z.
Got another one of these at 2026-06-02T13:11:36.156316Z.
"single market" or "single event"?
"single market" or "single event"?
It seems pretty clear to me after the last round of collateralization checks was implemented.
It seems pretty clear to me after the last round of collateralization checks was implemented.
I do. And I think it would be great to have a feature to check that my model of how that works matches Kalshi's.
I do. And I think it would be great to have a feature to check that my model of how that works matches Kalshi's.
It is not as simple as "available balance less all resting orders" when taking MECNET/DIRECNET into account, right?
It is not as simple as "available balance less all resting orders" when taking MECNET/DIRECNET into account, right?
Yes. There is the blunt feature. It sounds to me like Melon wants another feature that surfaces the result of the collateralization checks.
Yes. There is the blunt feature. It sounds to me like Melon wants another feature that surfaces the result of the collateralization checks.
Yes, the exchange keeps track of how much you can actually spend. It is reasonable to want a way to retrieve this.
Yes, the exchange keeps track of how much you can actually spend. It is reasonable to want a way to retrieve this.