Polymarketbecause i was once chatting with a guy and he told it doesn't really reflects how clob engine processed the requests
because i was once chatting with a guy and he told it doesn't really reflects how clob engine processed the requests
Ravdes参与话题 5消息总数 258
该用户的聊天记录定位。
聊天记录
共 258 条，显示第 201-250 条or <@1335736302808727562>
or <@1335736302808727562>
i mean if somebody has lower position in the block than me i can assume his request was processed before mine on same token id in same block right?
i mean if somebody has lower position in the block than me i can assume his request was processed before mine on same token id in same block right?
same block different block positions
same block different block positions
means clob prioritized my request faster?
means clob prioritized my request faster?
i am before somebody 2 positions in the same block
i am before somebody 2 positions in the same block
on the same market lets say same token
on the same market lets say same token
by the way is position in the block reflects how matching engine consumed requests? <@624575779023355904>
by the way is position in the block reflects how matching engine consumed requests? <@624575779023355904>
so it does make sense to spam it for some interval
so it does make sense to spam it for some interval
but yeah fak not
but yeah fak not
gtc would grab it
gtc would grab it
that's a good take thanks, because its a fak not resting gtc though so i might miss the price range entry in certain timestamp but literally after 1ms there can be ask order hanging thath matches it
that's a good take thanks, because its a fak not resting gtc though so i might miss the price range entry in certain timestamp but literally after 1ms there can be ask order hanging thath matches it
because it's not a resting gtc though
because it's not a resting gtc though
if i got your logic right
if i got your logic right
so i think you're right
so i think you're right
that in the particular moment of orderbook there might not be the ask in the price range i did set it in my fak order limit but like 1ms after it can be though
that in the particular moment of orderbook there might not be the ask in the price range i did set it in my fak order limit but like 1ms after it can be though
am i getting it right? <@1335736302808727562>
am i getting it right? <@1335736302808727562>
lets say
lets say
it might not be initially
it might not be initially
i have opportunity to catch the moment where there is going to be exact ask in my price range right?
i have opportunity to catch the moment where there is going to be exact ask in my price range right?
because if i spam
because if i spam
ok i get what you're saying i guess
ok i get what you're saying i guess
yeah those are faks
yeah those are faks
so with my understanding the first request should grab it all and is the most important one though
so with my understanding the first request should grab it all and is the most important one though
but how does it make the sense if clob engine is fifo then my first initially sent request is the fastest one so he should be prioritized as first if i spam others afterwards they are the later ones entering the fifo
but how does it make the sense if clob engine is fifo then my first initially sent request is the fastest one so he should be prioritized as first if i spam others afterwards they are the later ones entering the fifo
same order
same order
or spam from one account
or spam from one account
do i get it right
do i get it right
you say to not spam from one account but have 2-3 and send concurrently for example?
you say to not spam from one account but have 2-3 and send concurrently for example?
ah
ah
what does it change then though
what does it change then though
though
though
if clob engine is fifo
if clob engine is fifo
if spamming makes a difference?
if spamming makes a difference?
i was thinking
i was thinking
let me check
let me check
hm ok
hm ok
sometimes probably im late though
sometimes probably im late though
so that's not an issue
so that's not an issue
like 2-3ms i guess
like 2-3ms i guess
my processing time from receiving event to submitting tx is fairly low
my processing time from receiving event to submitting tx is fairly low
yeah yeah get it
yeah yeah get it
assuming i am the fastest one it will be processed prioritely
assuming i am the fastest one it will be processed prioritely
that my request is going to be processed in kind of
that my request is going to be processed in kind of
because i cannot control response time
because i cannot control response time
that's good take tough
that's good take tough
yeah
yeah
excluding response coming back from api right?
excluding response coming back from api right?
from receiving information to sent tx?
from receiving information to sent tx?
because usually its 30-50ms
because usually its 30-50ms