Did not recv blocks #315
Replies: 15 comments 5 replies
-
|
Sorry for delays, |
Beta Was this translation helpful? Give feedback.
-
|
why do I need to set an rpc server? wouldn't lite-rpc connect to the validator like normal rpc do? |
Beta Was this translation helpful? Give feedback.
-
|
It defaults to |
Beta Was this translation helpful? Give feedback.
-
Lite-rpc aims to provide scalability to RPC infrastructure. It will depend on one or more Solana RPC to do load balancing on several functionality. Lite-RPC cannot replay blocks to confirm and finalize itself, but it takes block stream from a RPC and implements sending and confirming transactions based on it. |
Beta Was this translation helpful? Give feedback.
-
|
it needs an rpc to get the information! Is the transaction sent to the RPC or directly to the validators? |
Beta Was this translation helpful? Give feedback.
-
|
I would presume the RPC connections are just for the data the lite-rpc needs in order to function - I would also presume it then proceeds to send transactions directly to the validators. But who knows honestly, not sure why everything solana related has such poor documentation. |
Beta Was this translation helpful? Give feedback.
-
Yes it is sent directly to the validators. And then confirmation is done over data that comes from the rpc. |
Beta Was this translation helpful? Give feedback.
-
Yes transactions are sent directly to the validators. |
Beta Was this translation helpful? Give feedback.
-
|
Good thanks - so what is the ideal setup here? Im trying to use my Helius RPC url to test the client - I see the default is to connect to "solana-validator" locally but what is that exactly.. a full node? Also how are configs actually passed in the run command: doesnt seem to work as it doesn't read the string |
Beta Was this translation helpful? Give feedback.
-
|
Not exactly.
Other wise you can also use the env variables. Please refer to the README for all the key-values. env RPC_ADDR="https://mainnet.helius-rpc.com/?api-key=blabla" cargo run --release # -- pass any arguments if desiredNote: env > config You can find the example config in the {
"rpc_addr": "http://0.0.0.0:8899",
"ws_addr": "ws://0.0.0.0:8900",
"lite_rpc_http_addr": "[::]:8890",
"lite_rpc_ws_addr": "[::]:8891",
"fanout_size": 18,
"identity_keypair": null,
"prometheus_addr": "[::]:9091",
"maximum_retries_per_tx": 40,
"transaction_retry_after_secs": 3,
"quic_proxy_addr": null,
"use_grpc": false,
"calculate_leader_schedule_form_geyser": false,
"grpc_addr": "http://127.0.0.0:10000",
"grpc_x_token": null,
"postgres": {
"pg_config": "your_postgres_config",
"ssl": {
"ca_pem_b64": "your_base64_encoded_ca_pem",
"client_pks_b64": "your_base64_encoded_client_pks",
"client_pks_pass": "your_client_pks_password"
}
}
} |
Beta Was this translation helpful? Give feedback.
-
|
cargo run --release -- -c ./.json Are you sure this is correct: error: unexpected argument '-c' found |
Beta Was this translation helpful? Give feedback.
-
|
which branch are you on ? I just tried it cargo run --release -- -c ./config.example.json Consider pulling the branch if you are on main |
Beta Was this translation helpful? Give feedback.
-
|
Which branch - i did think that as i was using the release version so i redownloaded the main branch just now but still no look, i see you are working on the production branch shall i try that? |
Beta Was this translation helpful? Give feedback.
-
|
I am using the main branch. I'll simplify this for you. Steps:
cargo --version # Mine is cargo 1.73.0 (9c4383fb5 2023-08-26)
cargo install --git https://github.com/blockworks-foundation/lite-rpc lite-rpc --lockedRun with logs Attach config Note: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for that, I have indeed got that working now. I used the example config json file - i only changed the rpc_addr to the helius one and the ws_addr to the helius web socket address. Do you know what connection string this is complaining about? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
I think check with helius, you can also use grpc with helius. Usually it is helius endpoint as grpc_addr and your API key as grpc_x_token. |
Beta Was this translation helpful? Give feedback.
-
|
Update config.example.json accordingly as you are using mainnet you should point everything to mainnet. |
Beta Was this translation helpful? Give feedback.
-
|
did you ever figure this out? I'm getting the exact same error "unexpected EOF" |
Beta Was this translation helpful? Give feedback.
-
|
use |
Beta Was this translation helpful? Give feedback.
-
|
I reached the same stage, and looks like everything connected as I can see the logs from alchemy dashboard. problem is alchemy is returning errors like - { there are many of these, so it looks like lite-rpc is giving strange parameter requests |
Beta Was this translation helpful? Give feedback.
-
Running the latest version, I am getting the follow error on startup:
I have confirmed my RPC and WS connection.
Here is a full stacktrace if needed:
Beta Was this translation helpful? Give feedback.
All reactions