[Draft] Auto reassignment fail

[jarekr-da]

No description provided.

[meiersi-da]

Yes, the unreassignability of the TokenRules is why I'm pushing for guidelines where the workflows tell the token standard registry what the target synchronizer is. See this conversation: #1622 (review)

For that to work cleanly we'll need a small amendment to the token standard off-ledger APIs. However, until then we can funnel the information in an additional field in the choiceArgument submitted to the factory endpoints; e.g. a top-level _targetSynchronizerId field, which you then parse in the TestTokenV1 registry handlers.

[jarekr-da]

I do not understand this :-(
I tried to play around - but do not get how would this additional field help in fundamental problem, that contract cannot be reassigned automatically

[meiersi-da]

The trick is that the TestTokenV1 registry maintains TokenRules contract on every synchronizer it supports and selects the right one based on the communicated target synchronizer. This guarantees that TokenRules contracts never need to be reassigned by the client submitting a token standard action.