We can do a lookup at the hub to see if it is in fact a CRC token.
There are two possible ways to add a Safe/Token to the PoH group currency:
a) A user adds their Token for the first time
b) A user adds a successor tokenIn the first scenario, the group currency just creates a new (Soul-ID → Token) mapping and the token is then added as member token.
In the second scenario, the group currency must check if there is already a token associated with the user’s soul-id. If that’s the case then the new token must have the already registered one as predecessor and must have been created after the predecessor was stopped.
Ok, I would have to understand more about the Soul-ID thing and Token mapping. So looking up the Hub makes sense, but what to look for exactly and how to make sure that the current user is actually “allowed” to do this, so how to trustlessly assign the Soul-ID to the old and new Token - there are some pieces missing for me.
Keeping the v1 trust connections vs. starting from scratch
This adds “clutter”… But I think overall benefits outweigh the clutter.
yes, but it’s true: this is not nice but could be included in some workflow and be transparant to the user, ie. “it could just work” without the user having to do something.