该用户的聊天记录定位。
TP/SL are best-effort. we could maybe add it to the API but would make the create order path slower since it isn't happening atomically in the exchange
TP/SL are best-effort. we could maybe add it to the API but would make the create order path slower since it isn't happening atomically in the exchange
and what Yes + No looks like
and what Yes + No looks like
I would encourage you to draw the payoff curves for Yes, No, -Yes, -No
I would encourage you to draw the payoff curves for Yes, No, -Yes, -No
1) buy Yes at .50 and No at .50 --> do nothing 2) market (yes) goes up 3) sell Yes at .75, still holding No at .25 --> sell 1 contract at 75c 4) market goes down 5) sell No at .75 (or hold until close) --> buy 1 contract at 25c
1) buy Yes at .50 and No at .50 --> do nothing 2) market (yes) goes up 3) sell Yes at .75, still holding No at .25 --> sell 1 contract at 75c 4) market goes down 5) sell No at .75 (or hold until close) --> buy 1 contract at 25c
in your example:
in your example:
changing that behavior doesn't let you do anything you can't already do
changing that behavior doesn't let you do anything you can't already do
but so does "buying no"
but so does "buying no"
yeah you can do that
yeah you can do that
but if you're buying yes and buying no at 50 cents, and the market drops to 25c, then yes you make 25c on the no, but you lose 25c on the yes so you're "even"
but if you're buying yes and buying no at 50 cents, and the market drops to 25c, then yes you make 25c on the no, but you lose 25c on the yes so you're "even"
and then rebuy it at 25 cents
and then rebuy it at 25 cents
you can sell yes at 50 cents if you want
you can sell yes at 50 cents if you want
no I understand what you're saying but it's incorrect
no I understand what you're saying but it's incorrect
"buying yes and no at 50 cents" is equivalent to doing nothing
"buying yes and no at 50 cents" is equivalent to doing nothing
because you're doing exactly the same thing
because you're doing exactly the same thing
the play is exactly the same
the play is exactly the same
this is exactly the same as selling yes at 0.75 and then buying yes at 0.25
this is exactly the same as selling yes at 0.75 and then buying yes at 0.25
sorry what
sorry what
the matching engine has no concept of buy no being different from sell yes. that's just a cosmetic field for the frontend. separately, there is still the reduce only flag in the v2 order create. expressiveness from v1 hasn't changed. but reduce only is a little bit strange, because it's only used when the order is aggressing. like what would you expect if you're +30, you place an order for -20. then, you place a new order for -20 that fills. so now you're +10, but you have a resting order for -20 that's "reduce only". you'd expect us to cancel that order (or decrease it?)
the matching engine has no concept of buy no being different from sell yes. that's just a cosmetic field for the frontend. separately, there is still the reduce only flag in the v2 order create. expressiveness from v1 hasn't changed. but reduce only is a little bit strange, because it's only used when the order is aggressing. like what would you expect if you're +30, you place an order for -20. then, you place a new order for -20 that fills. so now you're +10, but you have a resting order for -20 that's "reduce only". you'd expect us to cancel that order (or decrease it?)
when you place an API order, you're asking us to invent whether this order was a buy yes or a sell no (or vice versa).
when you place an API order, you're asking us to invent whether this order was a buy yes or a sell no (or vice versa).
not quite; yes and no doesn't exist. buy and sell still does
not quite; yes and no doesn't exist. buy and sell still does
the backlog there was actually very short, it just wasn't quite as transparent about when users could be promoted as we would've liked
the backlog there was actually very short, it just wasn't quite as transparent about when users could be promoted as we would've liked
you can subscribe to the changelog RSS feed
you can subscribe to the changelog RSS feed
https://docs.kalshi.com/changelog
https://docs.kalshi.com/changelog
the changelog
the changelog
going to be deprecating v1 order endpoints in the near near future!
going to be deprecating v1 order endpoints in the near near future!
create, at least, don't know the others off the top of my head but would recommend just checking
create, at least, don't know the others off the top of my head but would recommend just checking
the request is slightly different too
the request is slightly different too
the payloads are slightly different
the payloads are slightly different
create order v2 currently uses "side", but that's an interesting point; I can add a synonym for book_side or something like that
create order v2 currently uses "side", but that's an interesting point; I can add a synonym for book_side or something like that
yes you cannot have multiple accounts
yes you cannot have multiple accounts
<@1307399713108135956> ^ since you send the original msg
<@1307399713108135956> ^ since you send the original msg
oops, I had cherry picked a config change that didn't make it into the release. we're going to be cutting off the v1 endpoints entirely soon, so would not suggest using them
oops, I had cherry picked a config change that didn't make it into the release. we're going to be cutting off the v1 endpoints entirely soon, so would not suggest using them
what notification would you like? we've added a bunch of updates to the changelog (like 3-4) about this, and the idea of the rate limiting is precisely this; to give you a gentle notification that something has changed rather than just having everything not work at once
what notification would you like? we've added a bunch of updates to the changelog (like 3-4) about this, and the idea of the rate limiting is precisely this; to give you a gentle notification that something has changed rather than just having everything not work at once
you should be seeing Sell Yes, but the fees do not depend on whether you see Buy No or Sell Yes
you should be seeing Sell Yes, but the fees do not depend on whether you see Buy No or Sell Yes
its exactly the same with v1 endpoints as v2 endpoints, the two paths merge like as soon as you make the request
its exactly the same with v1 endpoints as v2 endpoints, the two paths merge like as soon as you make the request
I just send it here as well to give additional heads up
I just send it here as well to give additional heads up
it will be on the changelog too!
it will be on the changelog too!
will be bumping v1 order endpoint costs today once again
will be bumping v1 order endpoint costs today once again
(those are the only two I was thinking of)
(those are the only two I was thinking of)
what other ones are you thinking of
what other ones are you thinking of
there's only batch create/cancel, no?
there's only batch create/cancel, no?
prob all
prob all
<@1318254066752552991>
<@1318254066752552991>
totally separate
totally separate
just submit the application again
just submit the application again
do you have any volume? if you do, then just submit it again
do you have any volume? if you do, then just submit it again
that has both the old and the new endpoints (and is also the demo server)
that has both the old and the new endpoints (and is also the demo server)
you're probably still using the old endpoints
you're probably still using the old endpoints
but i am trying to space out changes so focusing on the order endpoint v2 migration for now
but i am trying to space out changes so focusing on the order endpoint v2 migration for now
still on the chopping block
still on the chopping block
Kalshi