FIX update spent claims bug where nothing gets updated
FIX bug where claim_id was never getting set on the output when processed
ADD run command to run individual chainquery jobs instead of the whole application
ADD new columns to track against the latest utxo applied to a claim
CHANGE name of transaction value sync function name for alignment
CHANGE owner of claims to be the first output that creates it instead of the latest output that updates it
CHANGE claim trie sync to consider the latest utxo for whether its spent
This is a breaking change (2.0) to the Chainquery database schema. The transaction_hash_id and the vout column on a claim now refer to the transaction and output of its origination. Any updates to the claim, include its origination will update the transaction_hash_update and vout_update columns respectively.
@tzarebczan (anything else you can think of?), @akinwale (explorer), @jessopb (spee.ch)
FIX update spent claims bug where nothing gets updated FIX bug where claim_id was never getting set on the output when processed ADD run command to run individual chainquery jobs instead of the whole application ADD new columns to track against the latest utxo applied to a claim CHANGE name of transaction value sync function name for alignment CHANGE owner of claims to be the first output that creates it instead of the latest output that updates it CHANGE claim trie sync to consider the latest utxo for whether its spent
This is a breaking change (2.0) to the Chainquery database schema. The
transaction_hash_id
and thevout
column on a claim now refer to thetransaction
andoutput
of its origination. Any updates to the claim, include its origination will update thetransaction_hash_update
andvout_update
columns respectively.@tzarebczan (anything else you can think of?), @akinwale (explorer), @jessopb (spee.ch)