-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AttributeError: 'solders.rpc.errors.InvalidParamsMessage' object has no attribute 'value' #49
Comments
Hey there @VeryBoredPanda
I think you forgot to provide the error.
It could very well be. Have a look at our docs:Limits. This bot isn't using any Limits from any specific/exception methods, so double check these:
That looks like a slippage value issue? |
Thanks for replying. The error appears in like this |
A fixed one? As a hardcoded value? Try looking into the transactions adjacent to the one where you expect to have done the sell transaction. See here Analyzing adjacent transactions for priority fees. Could be related to a priority fee not high enough. Also, if you are willing to spend a few cents or a dollar, try with a Warp transaction and a priority. Do note that each Warp transaction (not all requests, just the transaction itself) costs $0.15, so don't let it run wild. But just for an experiment. |
Yeah priority fee is fixed for now, I check recent fees and set a high number just to make sure, something in between 2-6 lamports per cu depending on current situation (I wanted to make sure bot works before adding |
Hi again, async def get_token_balance(conn: AsyncClient, associated_token_account: Pubkey): The result is like this: Buy transaction went ok, tokens are in my wallet and ATA is Initialized. |
Hi,
I was often getting this error while using this bot stock.
I've been working on it few days to set some rules so it only buys some coins and sell based on price instead of fixed time.
Now I get this error i would say 9 times out of 10 when selling.
I'm using Chainstack Growth plan.
Maybe i'm wrong but i don't think it's a code problem because some transaction still goes through.
Could be my plan limit? Or maybe if the coin is getting lot of transaction?
Thank you
edit: looks like it happens when the price of the coin goes up or down very fast.
The text was updated successfully, but these errors were encountered: