Hi @supermagicien, @silvalau, @kaldata and @southklad,
We’re currently addressing this issue, which is mostly caused by your caching solutions. Cache plugins and server-side caching prevent comment forms from having dynamic “nonce keys” for security purposes. WordPress generates a unique key for each visitor, but caching solutions store it in the page HTML, resulting in the same “nonce key” for all visitors. This is a significant problem caused by cache plugins, and we’re actively working on a solution. Our plan is to resolve the issue and release a new version within the next 12-24 hours.