聊天记录
共 493 条，显示第 201-250 条
It will send an update any time a field changes, so most commonly on price changes. For slow moving markets you might not get an update for minutes or maybe even hours. For fast moving markets like crypto you can get multiple updates per second regularly
It will send an update any time a field changes, so most commonly on price changes. For slow moving markets you might not get an update for minutes or maybe even hours. For fast moving markets like crypto you can get multiple updates per second regularly
Just order book. The ticker subscription is always a full set of fields, not deltas, so you're effectively always getting a snapshot
Just order book. The ticker subscription is always a full set of fields, not deltas, so you're effectively always getting a snapshot
Now if you want asymmetrical yes/no markets for volatility/arbitrage then...tough luck. This ain't that place
Now if you want asymmetrical yes/no markets for volatility/arbitrage then...tough luck. This ain't that place
It might not look exactly how you have it in your head but the money would be identical in the end
It might not look exactly how you have it in your head but the money would be identical in the end
I think we've all exhausted ourselves explaining how you can do this effectively right now if you want
I think we've all exhausted ourselves explaining how you can do this effectively right now if you want
You want it to act like calls and puts where there can be asymmetrical movement on each side
You want it to act like calls and puts where there can be asymmetrical movement on each side
And in your proposed scenario you would STILL have a net 0 position, just with more fees and less liquidity
And in your proposed scenario you would STILL have a net 0 position, just with more fees and less liquidity
At step 1 you have done absolutely nothing
At step 1 you have done absolutely nothing
+10 or -30 or whtever
+10 or -30 or whtever
Stop thinking of it as holding a yes or no contract. You have a positive or negative position
Stop thinking of it as holding a yes or no contract. You have a positive or negative position
Literally semantics
Literally semantics
You can enter and exit positions as often as you'd like. The point is selling yes and buying no are identical operations
You can enter and exit positions as often as you'd like. The point is selling yes and buying no are identical operations
Short selling effectively
Short selling effectively
Except paying fees
Except paying fees
The math all evens out in the end
The math all evens out in the end
But you CAN
But you CAN
So you want less liquidity
So you want less liquidity
This is fundamentally not how the exchange works. This would require separate liquidity pools for each side
This is fundamentally not how the exchange works. This would require separate liquidity pools for each side
This is the game! No one is making anyone play
This is the game! No one is making anyone play
Every person in here has something different they'd like a UI to provide. They can't make it that customizable. Franky I dint know why anyone building a system off of the api WOULDN'T want to build their own UI
Every person in here has something different they'd like a UI to provide. They can't make it that customizable. Franky I dint know why anyone building a system off of the api WOULDN'T want to build their own UI
The mods have been explicit here that the UI is and will be geared towards casual users
The mods have been explicit here that the UI is and will be geared towards casual users
What do you want? An apology? It's a startup that has grown 200x in the last year. If you want to play the game you roll with it
What do you want? An apology? It's a startup that has grown 200x in the last year. If you want to play the game you roll with it
I expect serious api users to have their own UI
I expect serious api users to have their own UI
Nothings been downgraded. They're just expecting api users to interact with the matching engine the way it natively works. You're used to the semantics of the UI? Well that's not how the api works. It really isn't that complicated. Pull up your big boy pants and figure it out
Nothings been downgraded. They're just expecting api users to interact with the matching engine the way it natively works. You're used to the semantics of the UI? Well that's not how the api works. It really isn't that complicated. Pull up your big boy pants and figure it out
I make good money in that market. Not on this cycle...
I make good money in that market. Not on this cycle...
Lol...care to guess which side I was on?
Lol...care to guess which side I was on?
Maybe you got some taker fills immediately, maybe it's a UI bug, maybe it's a fee assessment error. It could be a lot of things
Maybe you got some taker fills immediately, maybe it's a UI bug, maybe it's a fee assessment error. It could be a lot of things
It has maker fees and taker fees listed. It's hard to know exactly what the time line was on your order from those screenshots
It has maker fees and taker fees listed. It's hard to know exactly what the time line was on your order from those screenshots
Yes. Get Orders
Yes. Get Orders
Check your orders. The answer to the question "could the UI be buggy" is always yes
Check your orders. The answer to the question "could the UI be buggy" is always yes
Unless the UI is displaying maximum possible fees
Unless the UI is displaying maximum possible fees
Someone posted a UI shot of resting orders recently with fees reported and it would be impossible to calculate them without an actual fill
Someone posted a UI shot of resting orders recently with fees reported and it would be impossible to calculate them without an actual fill
It might be fees on partial fills from the same order
It might be fees on partial fills from the same order
Easiest way is to just use the naming conventions. I leave a couple seconds between expiration and subscribing to the incoming market just to avoid race conditions but they go live immediately. Hourlies are created days in advance
Easiest way is to just use the naming conventions. I leave a couple seconds between expiration and subscribing to the incoming market just to avoid race conditions but they go live immediately. Hourlies are created days in advance
Check the orders. It's not unheard of for Kalshi to mess up fees occaiso nally. You can get them reimbursed if it was a mistake
Check the orders. It's not unheard of for Kalshi to mess up fees occaiso nally. You can get them reimbursed if it was a mistake
Orders has maker fees separate from taker fees
Orders has maker fees separate from taker fees
Get Fills or Get Orders
Get Fills or Get Orders
Yes he confirmed that was how batch orders are processed but has anyone actually seen individual orders executed out of the order they were submitted?
Yes he confirmed that was how batch orders are processed but has anyone actually seen individual orders executed out of the order they were submitted?
I'm still a little unclear how batching would guarantee order of execution any better than individual order posts. Has anyone actually tested it? From the discussion the other week it sounded like it was just hypothetical
I'm still a little unclear how batching would guarantee order of execution any better than individual order posts. Has anyone actually tested it? From the discussion the other week it sounded like it was just hypothetical
The issue is that everyone has their own specific use cases. What I gather from people with this particular gripe is that they want the api to confirm whether they are adjusting an already open position versus opening a new one. That shouldn't be a hard thing to handle client side if you're tracking your positions and doing proper trade logging. At that point you can write buy/sell in your trade log if it helps for your strats but there's no need to keep tacking on extra api parameters for every new specific use case
The issue is that everyone has their own specific use cases. What I gather from people with this particular gripe is that they want the api to confirm whether they are adjusting an already open position versus opening a new one. That shouldn't be a hard thing to handle client side if you're tracking your positions and doing proper trade logging. At that point you can write buy/sell in your trade log if it helps for your strats but there's no need to keep tacking on extra api parameters for every new specific use case
The whole point of v2 is weening api users off the habit of thinking in terms of buy/sell yes/no. It sucks for a few days and then you get used to it. There's no point in inching the api back towards the old semantics at this point. If you really want to you can tailor your own UI/record keeping to use the old semantics pretty easily
The whole point of v2 is weening api users off the habit of thinking in terms of buy/sell yes/no. It sucks for a few days and then you get used to it. There's no point in inching the api back towards the old semantics at this point. If you really want to you can tailor your own UI/record keeping to use the old semantics pretty easily
the UI should be ACCURATE but there shouldn't be an expectation that it is infinitely customizable or even that useful for heavy API trading
the UI should be ACCURATE but there shouldn't be an expectation that it is infinitely customizable or even that useful for heavy API trading
Yeah I don't know of any channel that's sends out a message on order cancelation besides the actual update to the order status. But I would imagine it is almost always balance or time in force related
Yeah I don't know of any channel that's sends out a message on order cancelation besides the actual update to the order status. But I would imagine it is almost always balance or time in force related
OK man. It is what it is
OK man. It is what it is
That isn't what buy_max_cost. It was always confusing. Fact of the matter is the UI is simply not for any kind of sophisticated trading. That feature is for gamblers on slow moving markets with high liquidity who aren't thinking about the server side functionality at all
That isn't what buy_max_cost. It was always confusing. Fact of the matter is the UI is simply not for any kind of sophisticated trading. That feature is for gamblers on slow moving markets with high liquidity who aren't thinking about the server side functionality at all
like bruno said, it would be nice to have but it's asking the matching engine to do more work as opposed to doing it client side and in general that's not where kalshi's priorities are right now
like bruno said, it would be nice to have but it's asking the matching engine to do more work as opposed to doing it client side and in general that's not where kalshi's priorities are right now
even the function in the UI is just a brute force fill or kill order type
even the function in the UI is just a brute force fill or kill order type
because the potential slippage you're describing is essentially a rounding error for most automated systems
because the potential slippage you're describing is essentially a rounding error for most automated systems
i'm sure there might be ways to mitigate it, but if i'm putting myself in kalshi's shows and looking at API users there's just so many different usecases/individual needs per user. they've said the UI is a one size fits all platform for casual users and i just don't know how worth it it would be on their end to try to make it customizable to the point where heavy API users could dial it in exactly how they want
i'm sure there might be ways to mitigate it, but if i'm putting myself in kalshi's shows and looking at API users there's just so many different usecases/individual needs per user. they've said the UI is a one size fits all platform for casual users and i just don't know how worth it it would be on their end to try to make it customizable to the point where heavy API users could dial it in exactly how they want
yes, especially since they completely removed the action parameter from the order posts
yes, especially since they completely removed the action parameter from the order posts
Kalshi