You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any way to directly identify that a transaction contains a Rune commit? I couldn’t find any support for this in the ordinals-0.0.15 rust library and the commits are not Runestones. From what I’ve seen when processing transactions live, the only clear indicator is that the output must be a P2TR (Taproot) output.
Beyond that, it seems like the only reliable method is to detect a reveal transaction first, then trace back its inputs to validate the corresponding commit. Is that really the only approach?
If so, this means relying heavily on Bitcoin RPC calls for every rune etch reveal to backtrack commits, making it impractical to pre-index possible commit transactions in advance without constant RPC lookups.
Is there any alternative or recommended best practice to efficiently handle this? Thank you.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Is there any way to directly identify that a transaction contains a Rune commit? I couldn’t find any support for this in the ordinals-0.0.15 rust library and the commits are not Runestones. From what I’ve seen when processing transactions live, the only clear indicator is that the output must be a P2TR (Taproot) output.
Beyond that, it seems like the only reliable method is to detect a reveal transaction first, then trace back its inputs to validate the corresponding commit. Is that really the only approach?
If so, this means relying heavily on Bitcoin RPC calls for every rune etch reveal to backtrack commits, making it impractical to pre-index possible commit transactions in advance without constant RPC lookups.
Is there any alternative or recommended best practice to efficiently handle this? Thank you.
Beta Was this translation helpful? Give feedback.
All reactions