Sei executes transactions in parallel and resolves the collisions afterward Sei (Sei) executes transactions concurrently instead of one at a time, working from an estimate of the state each will touch and skipping the usual locks. A conflict means two transactions wrote to the same state key, or one... read state that another had just written. The engine compares the read and write sets recorded during execution. Clashing transactions are re-run until nothing collides, with a fixed resolution order preventing loops. The final state matches sequential processing exactly. Sei's documentation notes the overhead stays low when conflicts are infrequent, so blocks crowded onto one contract benefit the least. The engine covers EVM and CosmWasm on sei-network:native.show more

BSCN

1,376,418 subscribers

Teilen Herunterladen