# Enforcing that all kernels are different at consensus level?

**URL:** <https://forum.grin.mw/t/enforcing-that-all-kernels-are-different-at-consensus-level/7368>\
**Category:** Development and Technical Discussion\
**Created:** [May 26, 2020, 5:05pm UTC](https://forum.grin.mw/t/enforcing-that-all-kernels-are-different-at-consensus-level/7368 "2020-05-26T17:05:20Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Kurt](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/kurt/32/3361_2.png) [@Kurt](https://forum.grin.mw/u/Kurt)\
**Post date:** [May 27, 2020, 5:03am UTC](https://forum.grin.mw/t/enforcing-that-all-kernels-are-different-at-consensus-level/7368/6 "2020-05-27T05:03:08Z")

</div>

The correct term for these vulnerabilities is replay attack, and not rogue-key attack. Thank you Tromp for correcting me on keybase on this.

But it changes not the fact that UTXOs are moved against their owner’s will, and nobody likes the possibility and realization of things like that

---

_[View the full topic](https://forum.grin.mw/t/enforcing-that-all-kernels-are-different-at-consensus-level/7368)._
