Abstract: A first smart contract references a second smart contract at a first address. A directory service, which may be implemented using one or more systems, smart contracts, non-fungible tokens, and so on, routes requests to execute the second smart contract from the first address to a second address where the second smart contract is stored. This enables the second smart contract to be moved, modified, replaced, and so on despite the reference to the first address in the first smart contract being fixed without requiring the first smart contract to be replaced.

Abstract: A first non-fungible token (NFT) may be created that is associated with an asset associated with a first address. A system and/or one or more smart contracts of one or more other NFTs may implement a directory service associated with the first address. The directory service may receive requests at the first address and route the request directly or indirectly to a second address. The directory service may be configurable such that the second address may be changed. In this way, the asset referenced by the first NFT may be changed. This may add the capabilities of allowing selection between multiple versions of the asset, failure protection through redundancy via multiple copies of the asset, providing of self-executing web microservices, providing storage location flexibility, access control, and so on.

Abstract: Automatic token wallet generation includes generating a token wallet generated for a unique identifier that is associated with a person. The unique identifier may be a communication identifier like an email address, a telephone number, a social media handle, and so on. Storage space may be allocated for the token wallet and may be associated with the unique identifier. One or more NFTs (non-fungible tokens) may then be associated with the token wallet. In some examples, the token wallet may be automatically created in response to a request to associate an NFT with it. In other examples, the token wallet may be created in response to a request to perform other actions related to the token wallet.

Abstract: A non-fungible token (“NFT”) document platform includes a host platform that is operable to create and/or perform one or more transactions related to one or more NFTs on behalf of and/or for one or more other entities. Creation of the NFTs may involve creation of one or more smart contracts, storage of the smart contracts and/or the NFTs in one or more blockchains, and so on. The NFT document platform may also be operable to mint one or more documents, such as one or more birth certificates, contracts and other signed documents, titles, prescriptions, licenses and/or identification documents, checks, money, gift cards, and so on. The smart contracts and/or NFTs may correspond to the one or more minted documents. The NFTs may be usable to authenticate the minted documents, evidence ownership of the minted documents, control the ability to perform transactions regarding the minted documents, and so on.

Abstract: A system uses one or more non-fungible tokens (NFTs) for authentication. An NFT and an associated smart contract may be generated and stored on a blockchain for authority that is to be delegated to a delegate on behalf of a delegator. The NFT may then be provided to the delegate, who may use the NFT to authenticate himself in order to act on the delegated authority. Subsequently, the NFT may be transferred, revoked, marked expired, and/or otherwise controlled by the delegator in order to control the authority delegated to the delegate.

Abstract: The present invention relates to a system and method for managing network delivery of media content to a client device and, more particularly, to processing a scheduler service request to determine to deliver to the user at least one asset by the digital video recorder (DVR), network DVR (nDVR) or network content storage systems utilizing one or more user characteristics so as to conserve bandwidth of the content delivery network.