kylefang/bitcoin-indexer
1
0
Fork 0
mirror of https://github.com/alexgo-io/bitcoin-indexer.git synced 2026-01-12 22:43:06 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix: simulate ord numbering bug

Browse Source
This commit is contained in:
Ludo Galabru
2024-01-25 10:49:47 -05:00
parent 4141fd6cca
commit 5828f820a7
1 changed files with 12 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
components/ordhook-core/src/core/protocol/inscription_sequencing.rs
View File

@@ -757,9 +757,20 @@ fn augment_transaction_with_ordinals_inscriptions_data(
// Compute satpoint_post_inscription
inscription.satpoint_post_inscription = satpoint_post_transfer;
inscription_subindex += 1;
match destination {
OrdinalInscriptionTransferDestination::SpentInFees => {}
OrdinalInscriptionTransferDestination::SpentInFees => {
// Inscriptions are assigned inscription numbers starting at zero, first by the
// order reveal transactions appear in blocks, and the order that reveal envelopes
// appear in those transactions.
// Due to a historical bug in `ord` which cannot be fixed without changing a great
// many inscription numbers, inscriptions which are revealed and then immediately
// spent to fees are numbered as if they appear last in the block in which they
// are revealed.
sats_overflows.push_back((tx_index, op_index));
continue;
}
OrdinalInscriptionTransferDestination::Burnt(_) => {}
OrdinalInscriptionTransferDestination::Transferred(address) => {
inscription.inscription_output_value = output_value.unwrap_or(0);
@@ -767,14 +778,6 @@ fn augment_transaction_with_ordinals_inscriptions_data(
}
};
if traversal.ordinal_number == 0 {
// If the satoshi inscribed correspond to a sat overflow, we will store the inscription
// and assign an inscription number after the other inscriptions, to mimick the
// bug in ord.
sats_overflows.push_back((tx_index, op_index));
continue;
}
// The reinscriptions_data needs to be augmented as we go, to handle transaction chaining.
if !is_cursed {
reinscriptions_data.insert(traversal.ordinal_number, traversal.get_inscription_id());
@@ -798,7 +801,6 @@ fn augment_transaction_with_ordinals_inscriptions_data(
} else {
sequence_cursor.increment_pos_classic(ctx);
}
inscription_subindex += 1;
}
tx.metadata
.ordinal_operations