Permission Evaluation Applied to Copy Trading

When delivering an action of type “Action” from @alice to @bob, the Lux platform first checks to see if @alice has defined a permission mapping for @bob.groupa.subgroup.Action. If nothing is found, then a mapping for @bob.groupa.subgroup, then @bob.groupa and lastly @bob will be checked. If no further match is found, then the assumed mapping will be to the named permission group @alice.active.

Once a mapping is identified, then the signing authority is validated using the threshold multi-signature process and the authority associated with the named permission. If that fails, then it traverses up to the parent permission and ultimately to the owner permission, @alice.owner.