Guardian update unresolved

Price Feeds
1

Hi,
i have this error :

  "Program log: Instruction: WriteEncodedVaa",
  "Program HDwcJBJXjL9FpJ7UBsYBtaDjsBUhuLCUYoz3zr8SWWaQ consumed 2693 of 603000 compute units",
  "Program HDwcJBJXjL9FpJ7UBsYBtaDjsBUhuLCUYoz3zr8SWWaQ success",
  "Program HDwcJBJXjL9FpJ7UBsYBtaDjsBUhuLCUYoz3zr8SWWaQ invoke [1]",
  "Program log: Instruction: VerifyEncodedVaaV1",
  "Program log: AnchorError caused by account: guardian_set. Error Code: AccountNotInitialized. Error Number: 3012. Error Message: The program expected this account to be already initialized.",

Anchor:

pyth-solana-receiver-sdk = { git = "https://github.com/pyth-network/pyth-crosschain", branch = "main" }

SDK:

"@pythnetwork/client": "^2.22.0",
"pythnetwork/hermes-client": "^3.1.0",
"@pythnetwork/price-service-client": "^1.11.0",
"@pythnetwork/pyth-solana-receiver": "^0.14.0",

How do I resolve that, some people said I need to initialize the guardian, any ideas?

2

Context: I’m using Pyth historical prices with Hermes. At midnight, I fetch historical price data from Hermes for the previous day, onload those prices into Solana accounts using the Pyth Solana Receiver, run my competition, then offload the price accounts.

What’s happening: The transaction executes two Pyth Receiver instructions:

  1. WriteEncodedVaa — writes the encoded VAA (price update data) to an account. This succeeds.

  2. VerifyEncodedVaaV1 — verifies the VAA against Wormhole guardian signatures. This fails because the guardian_set account is not initialized.

Root cause: The Pyth Receiver program requires a Wormhole guardian set account to verify VAAs. This account must exist and be initialized before verification. On devnet (or when using historical prices), this account may not be set up.

Has anyone successfully initialized the guardian set on devnet, or is there a recommended approach for setting this up?

3

Hey @Biboux,

Good news — this should be resolved now.

The devnet guardian set upgrade was completed this morning. If you were testing on devnet, try again and it should work.

If you’re still seeing the AccountNotInitialized error after retrying, let us know which network you’re on and we can dig deeper.

4

We’re on Devnet yes,
I dont see some error messages since 2 hours last error is 2 hours and 10 mins ago.
I will investigate more in depth

5

Yes I confirm we don’t have anymore some errors.
Thanks you for fixing it