Skip to content

[Feature]: Event filtering for new Stacks blocks via /new_block is missing known eventsΒ #1460

@evonide

Description

@evonide

Event filtering for new Stacks blocks via /new_block is missing known events

1. Description

The webhook /new_block will observe new Stacks blocks once observed posted by stacks-core. The Stacks events are then extracted and actions executed depending on which events are observed as per
https://github.com/stacks-network/sbtc/blob/84948f2b7ec6cc5d7ac502ef68a6b496bb8e66a2/signer/src/api/new_block.rs#L162

Note that this list is not exhaustive and misses events such as update-protocol-contract which leads to:

            Err(error) => {
                tracing::error!(%error, %txid, "got an error when transforming the event ClarityValue");
                continue;
            }

being executed. This code has been patched via #1182 which replaced a return with the continue we now see.

However, it seems wrong to log errors for known events. This is a tracking ticket to add the missing update-protocol-contract event here, too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    flagged by ARIssue / bug / suggestion filed by Asymmetric Researchsbtc signer binaryThe sBTC Bootstrap Signer.

    Projects

    Status

    Needs Triage

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions