Turn-control rewritable blockchain
First Claim
Patent Images
1. A system including:
- memory configured to store a blockchain; and
blockchain phase circuitry configured to;
initiate a rewrite-permissive phase for a selected trusted party by obtaining, on behalf of the selected trusted party, access that allows combination of a turn-control portion of a key secret with a first portion of the key secret,the first portion controlled by the selected trusted party;
combine the turn-control portion and the first portion to generate the key secret;
receive a first command to perform a first validity-preserving rewrite to the blockchain,the first command received during the rewrite-permissive phase for the selected trusted party, andthe first validity-preserving rewrite coding-consistent with an existing integrity output stored within the blockchain;
responsive to receiving the first command during the rewrite-permissive phase, cause execution of the first validity-preserving rewrite to the blockchain using the key secret;
after the rewrite-permissive phase for the selected trusted party, initiate a rewrite embargoed phase by altering the access in response to request for write privileges from a specific trusted party different from the selected trusted party;
after altering the access, fail to combine the first portion and the turn-control portion during a rewrite-embargoed phase for the selected trusted party;
receive a second command to perform a second validity-preserving rewrite to the blockchain,the second command received during the rewrite-embargoed phase for the selected trusted party; and
responsive to receiving the second command during the rewrite-embargoed phase, fail to cause execution of the second validity-preserving rewrite to the blockchain.
2 Assignments
0 Petitions
Accused Products
Abstract
A system includes circuitry for rewriting blockchains in a non-tamper-evident or tamper-evident operation by a selected trusted party during a rewrite-permissive phase for the selected trusted party. During a rewrite-embargoed phase for the selected trusted party, rewrite access may pass to at least one second trusted party in a turn-based scheme. In some implementations, rewrite access may be implemented by controlling access to combination of a turn-control key secret portion with respective key secret portions controlled the by the individual trusted parties. Using the access to combination with the turn-control key secret portion, the trusted parties may preform rewrites to the blockchain.
-
Citations
20 Claims
-
1. A system including:
-
memory configured to store a blockchain; and blockchain phase circuitry configured to; initiate a rewrite-permissive phase for a selected trusted party by obtaining, on behalf of the selected trusted party, access that allows combination of a turn-control portion of a key secret with a first portion of the key secret, the first portion controlled by the selected trusted party; combine the turn-control portion and the first portion to generate the key secret; receive a first command to perform a first validity-preserving rewrite to the blockchain, the first command received during the rewrite-permissive phase for the selected trusted party, and the first validity-preserving rewrite coding-consistent with an existing integrity output stored within the blockchain; responsive to receiving the first command during the rewrite-permissive phase, cause execution of the first validity-preserving rewrite to the blockchain using the key secret; after the rewrite-permissive phase for the selected trusted party, initiate a rewrite embargoed phase by altering the access in response to request for write privileges from a specific trusted party different from the selected trusted party; after altering the access, fail to combine the first portion and the turn-control portion during a rewrite-embargoed phase for the selected trusted party; receive a second command to perform a second validity-preserving rewrite to the blockchain, the second command received during the rewrite-embargoed phase for the selected trusted party; and responsive to receiving the second command during the rewrite-embargoed phase, fail to cause execution of the second validity-preserving rewrite to the blockchain. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. A method including:
-
initiating a rewrite-permissive phase for a selected trusted party by obtaining, on behalf of the selected trusted party, access that allows combination of a turn-control portion of a key secret with a first portion of the key secret, the first portion controlled by the selected trusted party; combining the turn-control portion and the first portion to generate the key secret; receiving a first command on behalf of the selected trusted party, the first command to perform a first validity-preserving rewrite to a blockchain, the first command received during the rewrite-permissive phase for the selected trusted party; responsive to receiving the first command during the rewrite-permissive phase, causing execution of the first validity-preserving rewrite to the blockchain using the key secret, the first validity-preserving rewrite coding-consistent with a first existing integrity output stored within the blockchain; after the rewrite-permissive phase for the selected trusted party; initiating a rewrite-embargoed phase for the selected trusted party by altering the access to allow combination of the turn-control portion with a second portion of the key secret, the second portion of the key secret controlled by a target trusted party different than the selected trusted party; after altering the access, failing to combine the first portion and the turn-control portion during the rewrite-embargoed phase for the selected trusted party; receiving a second command on behalf of the selected trusted party, the second command to perform a second validity-preserving rewrite to the blockchain, the second command received during the rewrite-embargoed phase for the selected trusted party; responsive to receiving the second command during the rewrite-embargoed phase, failing to cause execution of the second validity-preserving rewrite to the blockchain; receiving a third command on behalf of the target trusted party, the third command to perform a third validity-preserving rewrite to the blockchain, the third command received during the rewrite-embargoed phase for the selected trusted party; and responsive to receiving the third command during the rewrite-embargoed phase, causing execution of the second validity-preserving rewrite to the blockchain using the key secret, the second validity-preserving rewrite coding-consistent with a second existing integrity output stored within the blockchain. - View Dependent Claims (16, 17, 18)
-
-
19. A system including:
-
memory configured to store a blockchain; and blockchain phase circuitry configured to; initiate a rewrite-permissive phase for a selected trusted party by obtaining, on behalf of the selected trusted party, access that allows combination of a turn-control portion of a key secret with a first portion of the key secret, the first portion controlled by the selected trusted party; combine the turn-control portion and the first portion to generate the key secret; receive a first command on behalf of the selected trusted party, the first command to perform a first validity-preserving rewrite to the blockchain, the first command received during the rewrite-permissive phase for the selected trusted party; responsive to receiving the first command during the rewrite-permissive phase, cause execution of the first validity-preserving rewrite to the blockchain using the key secret, the first validity-preserving rewrite coding-consistent with a first existing integrity output stored within the blockchain; after the rewrite-permissive phase for the selected trusted party; initiate a rewrite-embargoed phase for the selected trusted party by altering the access to allow combination of the turn-control portion with a second portion of the key secret, the second portion of the key secret controlled by a target trusted party different than the selected trusted party; after altering the access, fail to combine the first portion and the turn-control portion during the rewrite-embargoed phase for the selected trusted party; receive a second command on behalf of the selected trusted party, the second command to perform a second validity-preserving rewrite to the blockchain, the second command received during the rewrite-embargoed phase for the selected trusted party; responsive to receiving the second command during the rewrite-embargoed phase, fail to cause execution of the second validity-preserving rewrite to the blockchain; receive a third command on behalf of the target trusted party, the third command to perform a third validity-preserving rewrite to the blockchain, the third command received during the rewrite-embargoed phase for the selected trusted party; and responsive to receiving the third command during the rewrite-embargoed phase, cause execution of the second validity-preserving rewrite to the blockchain using the key secret, the second validity-preserving rewrite coding-consistent with a second existing integrity output stored within the blockchain. - View Dependent Claims (20)
-
Specification