About version of Prysm and Go-etherrum

**About version of Prysm**
I would like to know in order to run a relay node in my local blockchain, which version of Prysm beacon node should be used? And which version of go-etherum should I use?
I must use the prysm in flashbots (i.e. https://github.com/flashbots/prysm) or I can use Prysm by prysmaticlabs?

**Steps to reproduce**
Steps to reproduce the behavior:
1. Use commad to initialize the genesis state of go-ethereum
`./geth --datadir=gethdata init genesis.json`
2. Run go-ethereum
`./geth --http --http.api eth,net,web3 --ws --ws.api eth,net,web3 --authrpc.jwtsecret jwt.hex --datadir gethdata --nodiscover --syncmode full --allow-insecure-unlock --unlock 0x123463a4b065722e99115d6c222f267d9cabb524`
3. Run flashbots's Prysm(https://github.com/flashbots/prysm) beacon node
`./beacon-chain --datadir beacondata --min-sync-peers 0 --genesis-state genesis.ssz --bootstrap-node= --interop-eth1data-votes --chain-config-file config.yml --contract-deployment-block 0 --chain-id 32382 --accept-terms-of-use --jwt-secret jwt.hex --suggested-fee-recipient 0x123463a4B065722E99115D6c222f267d9cABb524 --minimum-peers-per-subnet 0 --enable-debug-rpc-endpoints --execution-endpoint gethdata/geth.ipc`
4. Get two main errors
ERROR blockchain: could not process new slot error=0x0000000000000000000000000000000000000000000000000000000000000000: unknown finalized root
ERROR powchain: Could not log ttd status error=got an unexpected error in JSON-RPC response: expected `totalDifficulty` field in JSON response

**Question**
I think the problem is the version of prysm and go-etherum can not match, but in order to run relay, must I run the prysm provided by flashbots or I can use the newest version provided by prysmaticlabs?

**Version I am using:**
- OS: Ubuntu 22.04
- Geth: newest (install by `git clone https://github.com/ethereum/go-ethereum`)

No repository files or tests are named. Start by reviewing the reported Geth and flashbots Prysm commands, the stated environment, and both error messages; determine which supported client versions and Prysm distribution are expected, then document the compatible setup or the missing configuration needed to reproduce the issue.

Written by the indexing model from the issue text.