Let me say that, outside of my continued concern in having David interacting with the community on THIS forum, clearly something that is not working for most of the year now, (though things are usually better in the official IOTA channels), that I'm also worried about the constant "last claim didn't count but the next one will". If I'm not mistaken, we already claimed last year, then once MORE last year then again under the new GUI earlier this year (then were also asked to create a new ultra secure account/seed - which most did)... now, we have been asked to claim AGAIN.

This doesn't inspire too much confidence and is perhaps why many people (myself included) have deciding to wait until later in the year (or next year since we have a one year deadline) to make this "new" claim. It feels kind of shitty to have been part of three or four snapshots and secured seeds and jumped through hoops only to find out "it didn't really count". This is doubly worrisome when the CEO of the company comes out with aggressive demands that a customer forcibly accept a refund (at an economic disadvantage at that) - a refund, mind you, that should have already been impossible four times over, as most people have already claimed multiple times only to have the entire network re-set.

To be clear, I'm not too upset about re-setting and optimizing the network (or waiting generally)... but, to wait and be told: "STFU or you will have your seed and account excluded from the genesis snapshot" is extremely disturbing.

As a last point, it would suck to claim - go away for two years for x reason, come back and be told "well, sorry, that claim didn't count because we re-set everything 4-5 more times after we opened the claim process". That has legal and PR trouble written all over it and I would tread carefully here to make sure no one is excluded for things which were not part of the software sale.

**meaning, I don't assume that there was a clause in the sale that said you were forced to keep up with development on a weekly/monthly basis after getting your software released to you. If anything, the re-setting of the network, if it left a member who participated in the software sale on the outside looking in, would look to constitute a breach. This can, of course, all be avoided with some careful planning and understanding from the dev group. I hope this is thought over carefully.

Best,
rtrt