Smart contracts (blockchains, distributed ledgers) and rights management broadly construed are the themes of today's Spotlight Applications. Assigned to tZERO, the first application discloses techniques for deploying a second smart contract based on a first smart contract. Assigned to Factom, the second application discloses techniques for smart contracts in blockchain environments.
20220374870, “Deploying a second smart contract based on a first smart contract,” assigned to tZERO IP, LLC.
A network node that includes at least one processor, at least one memory, and at least one network interface. The network node is configured to be within a plurality of network nodes communicatively coupled in a peer-to-peer network of network nodes implementing a distributed ledger. The network node is communicatively coupled to at least one remotely located computing device through the at least one network interface. The at least one processor is configured to deploy a second smart contract at a second address on the distributed ledger; set an address field in the first smart contract to reference the second address; subtract a particular number of tokens from a first respective value corresponding to a first respective address in the first table of balances; and add the particular number of tokens to a second respective value corresponding to the second address in the first table of balances.
20200044857, “Smart contracts in blockchain environments,” assigned to Factom, Inc.
Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a blockchain. Because there may be many digital contracts offered as virtual services, the contract identifier uniquely identifies a particular decision table and/or the digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the decision table and/or the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.