# TTIG Registration Guidance

**URL:** <https://www.thethingsnetwork.org/forum/t/ttig-registration-guidance/47629>\
**Category:** Migrating Gateways to V3\
**Created:** [May 12, 2021, 1:28pm UTC](https://www.thethingsnetwork.org/forum/t/ttig-registration-guidance/47629 "2021-05-12T13:28:41Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\
**Post date:** [May 12, 2021, 4:01pm UTC](https://www.thethingsnetwork.org/forum/t/ttig-registration-guidance/47629/6 "2021-05-12T16:01:35Z")

</div>

How would it be if all 15k users came on and asked the same question? And needed an answer formatted specifically for them? We are a community with collective responsibility, we all run off the hive mind that is the documentation supplemented by the forum posts.

There are no announcements for TTIG v3 to find because there are no announcements for TTIG v3.

From that, Schrodinger’s Cat style, we have to infer if the TTIG is should be deployed on v2 or v3. At present, it is suitable for both, but if we open the box, we will cause it to take up one state. However at that point Heisenburgs Uncertainty principle cuts in and we alter the measurement by taking it. As Heisenburg was mostly looking at speed & direction, I’d posit that we can assume that the TTIG is moving towards v3, so we are likely to alter the speed. So if we ask TTI each day, we a likely to cause the speed to change and as we are interrupting the developers, I think it is likely to slow things down.

In the absence of any announcement, I’m working to this:

> [@TTN V2 to V3 migration](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration-migrate-your-gateways-last/43445):
>
> Packet Broker currently routes traffic from gateways connected to The Things Network V2 to V3. That is, gateway coverage of V2 is available in V3. But not the other way around : gateways already connected directly to V3 will not be available for applications in V2. As a friendly request, both as a user of TTN and as the maintainer of TTN Mapper, please keep your gateways on TTNv2, until as late as possible. People in your city that have not yet migrated their application from v2 to v3 will…

But you need to make a decision yourself, nothing written on this forum should be considered legally binding, it is your responsibility to make the final decision based on the information or lack there of that is available.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/ttig-registration-guidance/47629)._
