The management utility allows users to create (x) key pairs and (y) Ethereum transactions. The Ethereum transactions fall into three types, namely declarations of (i) delegation of signing authority, (ii) revocation of signing authority, and (iii) permanent invalidation of a key pair. The first type of transaction records in an Ethereum block a declaration in which key pair X says that it delegates signing authority to another key pair Y. The second type records in an Ethereum block a declaration in which key pair X says that it revokes signing authority from another key pair Y. The third type records in an Ethereum block a declaration in which key pair X says that it should from now on be treated as invalid, i.e. unable to enter into any further transactions in the future. After declarations of this kind have been recorded on Ethereum, the Inkan client then has the ability to fetch these declarations from Ethereum for key pairs the user has chosen to track. The client then uses the fetched declarations as a basis for calculating time periods during which a key pair delegated signing authority to another key pair. These delegation relationships can be both direct or indirect through chains of delegation (i.e. if key pair X directly delegates to key pair Y and key pair Y directly delegates to key pair Z, this will be interpreted by the client as key pair X indirectly delegating to key pair Z). You can see these calculated delegation relationships in the tables / backup data that is displayed by the client when you click on the green "D"s on the avatars. I'll leave it at this for now. There is more to be explained, but it may be better to do so in smaller chunks as one gets used to it. Please feel free to ask questions and I can further explain any part of Inkan that you're looking at.