Thanks @Jaguar0625 and others
Opt In vs Opt Out
As stated above, there are options being investigated and discussed to see what is an isn’t possible at present. One of those is to allow an Opt Out process instead of an Opt In process, difference being below:
Opt In - NIS1 token holders make an active interaction to signal they want to receive tokens on Catapult
Opt Out - All NIS1 token holders are allocated tokens on Catapult UNLESS, they actively Opt-Out, if they do decide to Opt Out, they can still claim their tokens later via an Opt In process similar to the above.
Both of these would occur on-chain in NIS1 and both would allow NIS1 token holder to claim tokens post launch. The exact duration of that is being investigated still but as noted above is likely to be several years and that is being planned for, legal advice is also being taken to ensure we are taking legally compliant approaches. Opt Out alters a couple of other elements to the recommended approach (particularly around Multi Sig) which are still being scoped, that is the primary reason nothing has been released publicly on it just yet.
It is likely an updated communication will be issued in the next few days covering this.
Wallets
Current thinking is that either Opt In or Opt Out will be actioned by sending a transaction to a known account with a specific message. A NEM Wallet (Nano Wallet) plugin has been scoped to make this simple and easy, but there is no reason any other wallet couldn’t do the same, or that it couldn’t be sent programmatically. Once the decision is firm on what is happening and how it is to happen, guides I’m sure can be produced quite easily, similar to the above, I would expect this to be wallet agnostic, it just might be easier on the official desktop wallet.
Supernode Group
Regarding the SuperNode holders engagement. Contrary to intimations about closed door decisions, this approach has been taken to provide a way to allow members of the community who feel less able voice their opinions publicly for various reasons to have a way in which to express them. The “consensus” referred to above is acknowledged as not being community consensus but only consensus of that specific group. The group also generally includes a lot of longer standing members of the community and those who understand the technology and ecosystem well so serves as a useful challenge to assumptions by the committee.
That is not to say we don’t expect the wider community to also challenge assumptions, express preferences etc - we definitely do, it is just one more way to allow people to do that.