Sun Microsystems, Inc.

Mydream Interactive, Inc.

Matthew Drew Birder

Allison Phuong Huynh

Mark Thomas Wallace

Andrew Jonathan Leker

Ronald A Ten-Hove

Techniques for updating blockchains using a proof of work determined serially include receiving a block of data for inclusion in a new block of a blockchain; deterministically determining an initial nonce, hashing a combination of the block of data and the initial nonce to create a hashed value; iteratively deterministically determining an updated nonce based on a combination of the hashed value and updating the hashed value by hashing the updated nonce until the updated hashed value satisfies a proof of work criteria; creating the new block based on the block of data, the initial nonce, and the updated hashed value that satisfies the proof of work criteria; and having the new block stored in the blockchain.

Systems and methods for blockchains with serial proof of work

A system and method for blockchains with serial proof of work includes a memory storing a blockchain, and a processor coupled to the memory. The processor is configured to receive a miner identifier, receive a block of data for inclusion in a new block of the blockchain, determine an initial nonce based on the miner identifier, hash a combination of the block of data and the initial nonce to create a hashed value, iteratively determine an updated nonce based on the hashed value and update the hashed value by hashing the updated nonce until the updated hashed value satisfies a proof of work criteria, create the new block based on the block of data, the miner identifier, and the updated hashed value that satisfies the proof of work criteria, and share the new block with one or more other computing devices hosting the blockchain.

A transformation document generation mechanism (TDGM) for automatically generating a transformation document given a source document and a target document is disclosed. The TDGM analyzes each document and builds a pattern dictionary for each that records the patterns found in that document. Thereafter, the TDGM processes the pattern dictionaries to automatically generate the transformation document. In doing so, the TDGM automatically generates pattern creation templates in the transformation document. These templates (when invoked by a transformation processor at a later time while processing a source document with the transformation document) will cause particular patterns to be created in a result document. In addition, the TDGM generates zero or more copy templates in the transformation document to copy identical elements, if any, from the source document to the result document. Once that is done, the transformation document is created and may be refined by a user. By performing much of the underlying document analysis for the user, and by generating an initial transformation document, the TDGM simplifies the transformation document creation process.

Enhanced mechanism for automatically generating a transformation document

In processing a source entity with a transformation entity, an action set forth in a portion of the transformation entity is executed. A portion of the source entity is the subject of this action. This action causes a particular portion of a result entity to be generated. After this portion of the result entity is generated, a set of history information is associated therewith, which comprises a reference to the portion of the transformation entity that gave rise to the action, and a reference to the portion of the source entity that was the subject of the action. Given this information, it is possible to perform backtracking at a later time, so that when this particular portion of the result entity is selected, those portions of the transformation and source entities that gave rise to the particular portion of the result entity can be indicated to a user.

Mechanism for facilitating backtracking

A mechanism for debugging a transformation document is disclosed, wherein a debugging mechanism interacts with a user interface to enable a user to specify one or more breakpoints. The user may specify a breakpoint at a particular location in the transformation document or a source document. In addition, the user may specify one or more breakpoints using an expression, or based upon XSL messages. In addition to interacting with the user interface, the debugging mechanism also interacts with a transformation processor, which is the mechanism that actually processes the source and transformation documents to derive a result document. Before and after each processing action, the transformation processor sends a pre-action and a post-action message, respectively, to the debugging mechanism. The debugging mechanism uses the information in these messages to determine whether a breakpoint has been reached. If a breakpoint has been reached, then processing of the documents is halted until further instruction is received from the user. In this manner, the user is able to see intermediate processing results, which aids in debugging the transformation document.

Growing community of inventors

San Francisco, CA, United States of America

Matthew Drew Birder