A method for maintaining state and event information for all of a user's devices associated in a common location using a blockchain where each block includes an event block and a device block within it, where each event and device block refers to an earlier block of the respective type, resulting in a blockchain-in-a-blockchain architecture. The device and event blocks store data regarding each device associated with a user and events related to the devices/user, respectively. Any time a new event occurs, or a device is registered or removed, a new set of blocks is created, where submissions regarding device changes or events can be made by any participant due to the decentralized and public nature of a blockchain. The result is a system where all data regarding a user's registered devices and events is kept in a common location in a manner that is auditable and verifiable.

A transceiver baseband hardware including an encryption-decryption block configured to encrypt and jumble intended transmission data or unjumble and decrypt received encrypted data, the encryption-decryption based on key coefficients generated based on a random key address, the encryption-decryption implemented via a cross logical operation of the encryption-decryption block. The cross logical operation includes when lower significant bytes of the key coefficients operating on most significant bytes of the intended transmission data and the encrypted data. The jumble and unjumble are implemented by a byte displacement/placement block based at least in part on the random key address.

A transceiver baseband hardware including an encryption-decryption block configured to encrypt and jumble intended transmission data or unjumble and decrypt received encrypted data, the encryption-decryption based on key coefficients generated based on a random key address, the encryption-decryption implemented via a cross logical operation of the encryption-decryption block. The cross logical operation includes when lower significant bytes of the key coefficients operating on most significant bytes of the intended transmission data and the encrypted data. The jumble and unjumble are implemented by a byte displacement/placement block based at least in part on the random key address.

Sharing data by defining a data encoding table, maintaining a data record database, defining a data encryption code, providing the data encryption code with an outgoing call, receiving an audio response including encrypted data, decrypting the encrypted data, and updating the data record database according to the data.

Sharing data by defining a data encoding table, maintaining a data record database, defining a data encryption code, providing the data encryption code with an outgoing call, receiving an audio response including encrypted data, decrypting the encrypted data, and updating the data record database according to the data.

An example operation may include one or more of generating an initial seed and allocating one or more authorized bits of the initial seed to a plurality of blocks in a distributed ledger, storing the initial seed and an identification of which authorized bits of the initial seed are allocated to each block of the distributed ledger, receiving a final seed value that is partially generated by each of a plurality of nodes configured to access the distributed ledger based on authorized bits of respective blocks updated by each respective node, and generating a random sequence value based on the final seed value and storing the random sequence value in a block of the distributed ledger.

An example operation may include one or more of generating an initial seed and allocating one or more authorized bits of the initial seed to a plurality of blocks in a distributed ledger, storing the initial seed and an identification of which authorized bits of the initial seed are allocated to each block of the distributed ledger, receiving a final seed value that is partially generated by each of a plurality of nodes configured to access the distributed ledger based on authorized bits of respective blocks updated by each respective node, and generating a random sequence value based on the final seed value and storing the random sequence value in a block of the distributed ledger.

An example operation may include one or more of connecting, by a processor of a transport, to a network comprised of a plurality of transports, receiving, by the processor of the transport, an access key request to the transport from a device, broadcasting, by the processor of the transport, the request to the network, collecting, by the processor of the transport, authorizations from a subset of the plurality of the transports, and sending a one-time access key to the device, if the authorizations are received from a minimal required number of the transports.

A method for providing and maintaining secure storage of data includes cloaking the data by retrieving, from a database and using a first set of user-specific cloaking sequences and a first mapping, a first set of hidden sequences, and applying the data and the first set of hidden sequences as inputs to a cloaking algorithm. The cloaked data is stored in a persistent memory. The method further includes, during a later, second time period, re-cloaking the cloaked data by uncloaking the cloaked data using the first set of hidden sequences, retrieving, from the database and using the first set of user-specific cloaking sequences and a different, second mapping, a second set of one or more hidden sequences, and applying the uncloaked data and the second set of hidden sequences as inputs to the cloaking algorithm. The re-cloaked data is stored in the persistent memory.

A system and method for block management of interactions comprising a network-connected block management computer connected to a plurality of connected devices and to one or more blockchains to enable an object compiler to receive a plurality of criteria from a requesting device. The compiler the receives a plurality of blocks from the blockchains based on the criteria. Each block corresponding to a preconfigured interaction object previously written by devices either during or after the completion of a transaction. The compiler analyzes the preconfigured interaction objects to determine if there is corresponding supplemental object. The compiler requests the supplemental blocks from the blockchains, and processes supplemental objects based on type, if no corresponding supplemental object it found, the associated interaction object is flagged.