Closed dubuqingfeng closed 4 months ago
# Save the atomicals hash for the current block
current_height_atomicals_block_hash = self.coin.header_hash(b''.join(concatenation_of_tx_hashes_with_valid_atomical_operation))
put_general_data(b'tt' + pack_le_uint32(height), current_height_atomicals_block_hash)
self.logger.info(f'height={height}, atomicals_block_hash={hash_to_hex_str(current_height_atomicals_block_hash)}')
Atomicals block hash generate by all of the concatenation_of_tx_hashes_with_valid_atomical_operation
in this height, from the log, It seems found_parent_mint_info
get error caused this wrong. I will try to fix it.
Should be fixed by https://github.com/atomicals/atomicals-electrumx/pull/180.
During our process of running the indexer, we have recently encountered some issues with mismatched atomicals block hashes
The phenomenon is as follows:
In the past two days, I have been running data from scratch. In version 1.3.7.5, starting from a certain height, the atomic block hash does not match with other nodes, nor does it match with third parties,
The other nodes were already running before.
The specific blocks and hash are as follows:
block height: 826309
tx hash: 14c04cda9d6ea6e84e0143871c9a8e495be346a428091555b6af72b1cb1d2a90
error hash:
normal:
normal: 6cf66e08c81fbca2639fd624a6bb5c5ead2bf177c730c2b19527eb02e7697bb4 error: 6510639a449461bc0fd43c741cdc5b5f1cfab65a1c3bd7c0db77bc9dc5855584
txhash log: