revoked delegation still shows up in delegations endpoint

[rafaelcr]

extended/v1/pox4/{pool_principal}/delegations

We see one of our test delegations from a few cycles ago:

    {
      "stacker": "SP3PMNSRKWYJ48XZXPZC8KCH01Z2TK7MB03BD3SNV",
      "amount_ustx": "25000000000",
      "block_height": 189384,
      "tx_id": "0x66f5613313c7d6b82e15aaa9f8beb4660887062fb3e07117de91590faa8d3f26"
    },

That transaction was made via LockStacks and we selected Indefinite as duration. The address keeps showing in the API output even after a revoke-delegate-stx was broadcasted and confirmed.
https://explorer.hiro.so/txid/0x6cadecc2a20124bd5b36e59f27ef0efcc31985265173eddc251088fff9416980?chain=mainnet

[rafaelcr]

The Hiro API started parsing the print events generated by the pox4 contract to determine if a stacker has delegated, revoked, etc. However, when this endpoint was created, no such events existed so revokes were simply not reflected in the API endpoint.

We can add revoke support for that endpoint now, but there's still this open issue in Stacks core about revokes coming from the burnchain that I'm not sure is still even an issue we should consider for the API. Reaching out to core devs to get the best course of action here.

[hirosystems-release-bot]

🎉 This issue has been resolved in version 8.13.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀