Polymarketnot yet
not yet
tehnoobkiddo参与话题 23消息总数 565
该用户的聊天记录定位。
聊天记录
共 565 条，显示第 401-450 条hahaahah yes they did it this morning
hahaahah yes they did it this morning
only one way to find out 😈
only one way to find out 😈
probably different clob engines handling different orderbooks and sometimes we're not getting routed to the right instance
probably different clob engines handling different orderbooks and sometimes we're not getting routed to the right instance
they usually do updates at 12 UTC so...
they usually do updates at 12 UTC so...
there was no announcement so we can only assume it's delayed
there was no announcement so we can only assume it's delayed
i mean if they're scaling down despite those latencies it'd be outrageous
i mean if they're scaling down despite those latencies it'd be outrageous
but have you observed that at any given time t, if you send a post and cancel, do you get the ack at the same time or cancel is way more delayed?
but have you observed that at any given time t, if you send a post and cancel, do you get the ack at the same time or cancel is way more delayed?
55s AHHA
55s AHHA
-10k as of now
-10k as of now
i mean we can all agree that poly's getting attacked/exploited all the time right? there's no way things break that fast, it must be spammers/ddos of some sort or perhaps latency was good because people held off from turning on their bots after the update
i mean we can all agree that poly's getting attacked/exploited all the time right? there's no way things break that fast, it must be spammers/ddos of some sort or perhaps latency was good because people held off from turning on their bots after the update
they didn't schedule the maintenance right?
they didn't schedule the maintenance right?
the update was good for 3 days
the update was good for 3 days
kek
kek
otherwise you're telling ppl you want to trade at that price (making an offer)
otherwise you're telling ppl you want to trade at that price (making an offer)
BID limit order on best ask or above is a taker, because you want to bid (buy) at a price that other people are trying to sell at, so your order is marketable and you are a taker (taking someone's order) (vice versa for ASK limit order on best bid or below)
BID limit order on best ask or above is a taker, because you want to bid (buy) at a price that other people are trying to sell at, so your order is marketable and you are a taker (taking someone's order) (vice versa for ASK limit order on best bid or below)
it's been enforced almost since forever
it's been enforced almost since forever
you can dm mustafa he'll give you a delay bypass if you're nice enough
you can dm mustafa he'll give you a delay bypass if you're nice enough
if you're posting with a limit price of best ask + 1, or selling at best bid - 1, then you're a taker hence you get the taker delay
if you're posting with a limit price of best ask + 1, or selling at best bid - 1, then you're a taker hence you get the taker delay
taken directly from their doc
taken directly from their doc
but you might be referring to the huge latency spikes on cancels
but you might be referring to the huge latency spikes on cancels
no cancel and post have no delay
no cancel and post have no delay
you submit an order and it only gets processed 250ms after
you submit an order and it only gets processed 250ms after
since EOA don't show on poly
since EOA don't show on poly
are we sure it's not confounding their EOA/proxy/deposit wallets?
are we sure it's not confounding their EOA/proxy/deposit wallets?
just asking for a friend
just asking for a friend
thanks!
thanks!
<@&1485393752645173399> yo get this dude out of here
<@&1485393752645173399> yo get this dude out of here
funny to change your nickname after being so damn disrespectful mr security researcher
funny to change your nickname after being so damn disrespectful mr security researcher
nah you're just dumb
nah you're just dumb
```auth = AuthConfig( builder_config=None, relayer_headers={ "RELAYER_API_KEY": relayer_api_key, "RELAYER_API_KEY_ADDRESS": relayer_api_key_address, }, ) relayer = RelayClient(relayer_url, args.chain_id, private_key, auth.builder_config)```
```auth = AuthConfig( builder_config=None, relayer_headers={ "RELAYER_API_KEY": relayer_api_key, "RELAYER_API_KEY_ADDRESS": relayer_api_key_address, }, ) relayer = RelayClient(relayer_url, args.chain_id, private_key, auth.builder_config)```
there's only one way to be sure
there's only one way to be sure
but i'll let <@1335736302808727562> flex even more
but i'll let <@1335736302808727562> flex even more
rookie numbers
rookie numbers
we comparin genital sizes now? ajhahah but yes indeed all comes back to skill issue
we comparin genital sizes now? ajhahah but yes indeed all comes back to skill issue
there are even faster alternatives if you know what to look for
there are even faster alternatives if you know what to look for
been capturing poly market data since oct never had any issue
been capturing poly market data since oct never had any issue
haahah well i can only say skill issue
haahah well i can only say skill issue
then fanout to whichever listeners need the data
then fanout to whichever listeners need the data
dedupe on ts|type|hash
dedupe on ts|type|hash
just run many connections and you won't lose data
just run many connections and you won't lose data
skill issue
skill issue
<@&1485393752645173399>
<@&1485393752645173399>
you just get processed 250ms later
you just get processed 250ms later
arrival time priority
arrival time priority
skill issue
skill issue
yes there is
yes there is
user WS or clob WS?
user WS or clob WS?
tf was that
tf was that
seems like it
seems like it