Timeline for solana block delay
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 16 at 8:00 | vote | accept | yan liu | ||
| Jan 15 at 16:45 | comment | added | Jon C | If you want to ask more questions, please create new questions! No one will be able to find the answers otherwise. | |
| Jan 15 at 3:57 | comment | added | yan liu | I tried use confirmed in blocksub ws methed ,delay is still 2000ms~3000ms,and I have 2 questions here 1、In Solana, is local state modification of obtained blocks done after the processed state or after the commitment state? If Solana's apply block occurs after commitment, then regardless of the method used, the latest block state can only be obtained after 2000 milliseconds. 2、In Ethereum, non-validators only need to receive blocks sent by validators without waiting for the voting process. In Solana, is the process of collecting votes necessary for both validators and non-validators? | |
| Jan 13 at 10:09 | comment | added | Jon C |
1. It depends on the commitment that you provide, finalized or confirmed. It's technically possible for a confirmed block to get rolled back in the protocol, but we haven't seen it in practice. 2. You can probably safely use confirmed blocks, but as I mentioned in my previous answer, it's technically possible for them to get rolled back / reorganized.
|
|
| Jan 13 at 4:39 | comment | added | yan liu | Thank you for your response. After seeing your reply, I have two questions: 1、On Solana, when subscribing to blocks, am I getting blocks that are finally confirmed, meaning blocks before this block won't be subject to reorganization? 2、Can the currently provided official Solana API perform similar actions to Ethereum, where I can use the block state for price predictions immediately upon receiving the block, without waiting for final confirmation? | |
| Jan 11 at 0:57 | history | answered | Jon C | CC BY-SA 4.0 |