A computing system (100, 200, 300, 400, 500) that is implemented in a decentralized network that implements a distributed ledger, the distributed ledger being configured to back one or more decentralized identities, DID, for one or more users of the computing system, the computing system comprising: one or more processors; and one or more computer-readable media having thereon computer-executable instructions that are structured such that, when executed by the one or more processors, cause the computing system to: attach delegation permissions (520, 521, 522, 523, 524, 525, 526) to one or more DID-related data objects (420A, 420B) that are to be provided by a DID owner to a first third-party entity, the delegation permissions at least specifying one or more interactions (546, 556, 566) that are to occur between the DID owner and one or more second third-party entities (540, 550, 560) that have received the one or more DID-related data objects from the first third-party entity before the one or more second third-party entities are able to use the one or more DID-related data objects; after attaching the delegation permissions, provide the one or more DID-related data objects to the first third-party entity; receive one or more interactions from the one or more second third-party entities when the one or more second third-party entities attempt to use the one or more DID-related data objects; and allow the one or more second third-party entities to use the one or more DID-related data objects when the received one or more interactions satisfy the delegation permissions. one or more processors; and one or more computer-readable media having thereon computer-executable instructions that are structured such that, when executed by the one or more processors, cause the computing system to: attach delegation permissions (520, 521, 522, 523, 524, 525, 526) to one or more DID-related data objects (420A, 420B) that are to be provided by a DID owner to a first third-party entity, the delegation permissions at least specifying one or more interactions (546, 556, 566) that are to occur between the DID owner and one or more second third-party entities (540, 550, 560) that have received the one or more DID-related data objects from the first third-party entity before the one or more second third-party entities are able to use the one or more DID-related data objects; after attaching the delegation permissions, provide the one or more DID-related data objects to the first third-party entity; receive one or more interactions from the one or more second third-party entities when the one or more second third-party entities attempt to use the one or more DID-related data objects; and allow the one or more second third-party entities to use the one or more DID-related data objects when the received one or more interactions satisfy the delegation permissions. attach delegation permissions (520, 521, 522, 523, 524, 525, 526) to one or more DID-related data objects (420A, 420B) that are to be provided by a DID owner to a first third-party entity, the delegation permissions at least specifying one or more interactions (546, 556, 566) that are to occur between the DID owner and one or more second third-party entities (540, 550, 560) that have received the one or more DID-related data objects from the first third-party entity before the one or more second third-party entities are able to use the one or more DID-related data objects; after attaching the delegation permissions, provide the one or more DID-related data objects to the first third-party entity; receive one or more interactions from the one or more second third-party entities when the one or more second third-party entities attempt to use the one or more DID-related data objects; and allow the one or more second third-party entities to use the one or more DID-related data objects when the received one or more interactions satisfy the delegation permissions.