# Publishing vetting status of nodes by satellites

**URL:** <https://forum.storj.io/t/publishing-vetting-status-of-nodes-by-satellites/22987>\
**Category:** Node Operators\
**Created:** [June 17, 2023, 10:07am UTC](https://forum.storj.io/t/publishing-vetting-status-of-nodes-by-satellites/22987 "2023-06-17T10:07:18Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [June 17, 2023, 11:33am UTC](https://forum.storj.io/t/publishing-vetting-status-of-nodes-by-satellites/22987/2 "2023-06-17T11:33:04Z")

</div>

The vetting state here is for a reason. It actually could be a completely different node, than when you started it: you may migrate it any time.

I support the idea, that node should gain a reputation on each satellite independently (and vice versa), I do not like an idea of preferences only because you stored data for other satellites. Because it also requires that the system should have a memory, and each new node started after the failed one must be considered as unreliable in this extreme case.

---

_[View the full topic](https://forum.storj.io/t/publishing-vetting-status-of-nodes-by-satellites/22987)._
