-
Notifications
You must be signed in to change notification settings - Fork 522
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
[Bug]: AuctioneerExecuteSale
fails with Provided seeds do not result in a valid address
#1055
Comments
AuctioneerExecuteSale
fails with Provided seeds do not result in a valid address
@KartikSoneji I'm not sure how to write a test to duplicate this. If this is still an issue for you, let me know, and we can work to duplicate it and figure out what the bug is. If other people are experiencing this please upvote and drop a comment here with as many details as you can to allow me to try to write a test that can duplicate it. Otherwise, if there's no activity here I'm going to close it eventually as stale. |
Please let me know what information you need to help debug this. |
@samuelvanderwaal found another example: |
Hey @KartikSoneji, are you trying to use receipts? AFAIK that's currently not supported under Auctioneer. |
I don't think so, most other auctions handled by the same code have no issues. |
On a side note, can the IDL for Auctioneer please be published on-chain too? |
Yeah I can do that. |
It's weird that this is happening on ExecuteSale since every PDA should already have been utilized and successfully derived. I'll dig into the runtime on find_program_address but I assumed it was deterministic. The auctioneer PDA does look a little low on entropy so I'll also look into how hard it'd be to add more seeds in the future. |
For whatever it's worth, when I spoke to a colleague at Superteam about this issue, he checked the tx simulation that kartik provided said that the error in the log seems to imply that the listing_config account owned by the auctioneer program is not created yet which is created in the sell ix |
Sup Metaplex - Just wanted to drop by and let you guys know we finally figured out the issue for the auctioneer seeds error that was preventing token owners from finalizing the sale of a timed auction. The root cause of the issue was a deficient balance in the bidder’s escrow wallet. Basically, the bidders escrow wallet was deficient by .0009 SOL (likely either a miscalculation in the program or our BE logic at the time funds were transferred to the escrow wallet). Due to that deficiency, it caused the 1st instruction for the program to fail. Although the cause of the balance deficiency itself was a short coming on our end, it would definitely be helpful if the program returned a sensible error message instead of “Error processing Instruction 1: Program failed to complete.” Just a thought that might help anyone who comes across this issue in the future to more easily identify the problem. Have a good weekend! |
Thanks so much for the follow up! If you know exactly where this error should be raised and can make a PR I'll make sure it gets merged. |
@samuelvanderwaal @KartikSoneji Having same issue with ExecuteSale for PNFT, https://solscan.io/tx/3GbgNHFrQwqmeetnR2NnQfys2Jqse5sJB8dKQKsa4N744omvAhXZz6v5pCK8SeauP1bNLnKhwrWj6W6M7BVMos7w Issue: #1156 |
Having issue with ExecuteSale for PNFT |
Which package is this bug report for?
auction-house
Which Type of Package is this bug report for?
Rust Contract
Issue description
Trying to finalize the sale of a timed auction results in an error.
I'm not sure if this is an issue with the accounts used in the tx or very bad luck with the pda seeds and bumps.
It looks like the issue is in the
AuctioneerExecuteSale
instruction since the cpi succeedes.Here's the link to simulate the transaction:
https://explorer.solana.com/tx/inspector?signatures=%255B%25221111111111111111111111111111111111111111111111111111111111111111%2522%255D&message=AQAOGWJdA8E2UB0FUYnGqWSg%252BsgYXQDhtET1ULaTrOJUj5qcNzXQ4LhHNPFLhgPHhxr%252FDTC%252Fh5K50I5c6lcgR407VoM%252BQyIsDsJaq7zXt764XEDDeDKV7r72sGlgMioFTH5XGEZFeGSbzelgc1Ai7iTto6LERvKypouNwGzXJS%252FObsZEcL0%252FJ%252FY8CqdNNApRMWAdNchxz6x6vdYYapiNcxw%252BRMCE1kGNqyz6umt83ibJiLeKIZnOjmyurq2I0uS40mFWgIfNK9rmh9NIg5ZCi23GBKtokiFrU3TG6oNaBp544%252FyynbavCm%252BgrOdPCUmqyamJTnkih6ClFOsADdDRwlFvrG6xDYrywSQaxsIs%252FQSfNTx3WtQl4%252B8KfsDIwOPxhMJmA8AMwjCKVwGN6TzWxZCUwZ1zwQtugrqM58Iyzw%252FXjJaKx73P4SGOpq24xysmgJsXYbNyb8mLzxx94yUwLAClSNIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACtVHrtVhyribMnCf4V%252Ft3MdT%252FyRJSYAddc7h%252FYDk%252Fq7Wp3MsyAaW7l%252BIluuuNXFvKV%252Fo40Rif8inrVX55Ff%252FRpohL8LrGSXRiUvCHkZfyZrlkio%252Bls18yo11IuADvhHAIyXJY9OJInxuz0QKRSODYMLWhOZ2v8QhASOe9jb6fhZsVfveZ40NZ1%252BE6qrh4BvbEMYP2VglMhwPXEzJZ710uy6MBN05L7iGhlp9p8BsNoiaESRMjj6ddMZkIrFTIw5aN1ikNBEuIwB%252F9MIn3HSz3XCg5%252FLSAvDQz%252BC9oTzeAURCmWThjy6RhVk6uQTc3IVRusBUckwgna71K0qHDpCEHv0JF6XdZMSX7FZQbbAqSYK9EOLzRA1UpKkCwXfh%252FXVIAuxtdQOT6iste2ZYfITUcSiFoUZzPsWwL6WJkZZac7KBpuIV%252F6rgYT7aH9jRhjANdrEOdwa6ztVmKDwAAAAAAEGp9UXGSxcUSGMyUw9SvF%252FWNruCJuh%252FUTj29mKAAAAAAbd9uHXZaGT2cvhRs7reawctIXtX1s3kTqM9YV%252B%252FwCpzfiMzsZK7C%252B7K0%252FP1dyjb4XAwfX1yi79X5k6zlUH%252BAUBFRoTCQYAARENFgMABBIOBwoIBQIMEBgLDxQXABwlStmdTzEjBv7%252F%252F%252F4AXtCyAAAAAAEAAAAAAAAA
Relevant log output
Priority this issue should have
High (immediate attention needed)
The text was updated successfully, but these errors were encountered: