BLOCKCHAIN TOKEN NATURE

Brand Owner (click to sort) Address Description
DREAMCOIN Koach Capital Holdings 2565 Kilo Way Laguna Beach CA 92651 Blockchain token in the nature of downloadable electronic data files featuring transferrable virtual currency units used to execute transactions and record transactional information relating to registration, storage and digital streaming of creative works;DREAM COIN;Financial services, namely, providing a blockchain token in the nature of a virtual currency for use by members of an on-line community used to execute transactions and record transactional information relating to registration, storage and digital streaming of creative works via a global computer network;
DREAMIUM DREAMCHAIN CORPORATION 5509 Paseo Del Lago West #B Laguna Woods CA 92637 Blockchain token in the nature of downloadable electronic data files featuring transferrable virtual currency units used to execute transactions and record transactional information relating to registration, storage and access rights of creative works;Financial services, namely, providing a blockchain token in the nature of a virtual currency for use by members of an on-line community used to execute transactions and record transactional information relating to registration, storage and access rights of creative works via a global computer network;
 

Where the owner name is not linked, that owner no longer owns the brand

    
Technical Examples
  1. A method and computer program to revoke and update a token (130) having several encryption, signature and role certificates/private keys contained in the token (130). The certificates/private keys in the token 130 are transmitted wrapped by a public key and may only be activated by a private key contained in the token (130). The activation of any certificate/private key requires the entry of a passphrase by a user (132). Further, all certificates/private keys contained in a token (130) are stored in an authoritative database 104. In the event that a token (130) is lost then all certificates/private keys associated with the token (130) are revoked. Further, when new certificates/private keys are issued to a user (132) these certificates/private keys are encrypted using the token's (130) public key and downloaded to the token (130).