# UX of distributing multiple binaries \[take 2\]

**URL:** <https://forum.polkadot.network/t/ux-of-distributing-multiple-binaries-take-2/2854>\
**Category:** Tech Talk\
**Tags:** security, validators, ux\
**Created:** [May 14, 2023, 4:54pm UTC](https://forum.polkadot.network/t/ux-of-distributing-multiple-binaries-take-2/2854 "2023-05-14T16:54:23Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![burdges](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/burdges/32/172_2.png) [@burdges](https://forum.polkadot.network/u/burdges)\
**Post date:** [May 14, 2023, 5:08pm UTC](https://forum.polkadot.network/t/ux-of-distributing-multiple-binaries-take-2/2854/2 "2023-05-14T17:08:34Z")

</div>

We’d represent node version and PVF worker version separately in libp2p info, and later in the [slashing resistant session key certificates](https://github.com/paritytech/substrate/issues/7398)? Or would they always be aligned?

Or should this question be asked in [UX implications of PVF executor environment versioning](https://forum.polkadot.network/t/ux-implications-of-pvf-executor-environment-versioning/2519) ?

---

_[View the full topic](https://forum.polkadot.network/t/ux-of-distributing-multiple-binaries-take-2/2854)._