like, guys, be real. enable the full automation support via embedded wallets. let us get the private keys of them.
like, guys, be real. enable the full automation support via embedded wallets. let us get the private keys of them.
该用户的聊天记录定位。
like, guys, be real. enable the full automation support via embedded wallets. let us get the private keys of them.
like, guys, be real. enable the full automation support via embedded wallets. let us get the private keys of them.
because it does ecdsa client-side and sends it onchain which gets indexed 100x slower than directly sending to the CLOB api.
because it does ecdsa client-side and sends it onchain which gets indexed 100x slower than directly sending to the CLOB api.
oh i checked the messages it seems like u force users to use EOAs. but how am i supposed to use API via EOA if its going to be extremely slow?
oh i checked the messages it seems like u force users to use EOAs. but how am i supposed to use API via EOA if its going to be extremely slow?
hi, how do i get the private ke of embedded wallet? i get this: "Signer does not match - you should use embedded address for smart wallet"
hi, how do i get the private ke of embedded wallet? i get this: "Signer does not match - you should use embedded address for smart wallet"