rosetta reports some stx unlock at incorrect heights

[rafaelcr]

The stacks rosetta node generates stx_unlock operations at scheduled heights even when balance already unlocked earlier.

Example (SP3MCAXZWZRCEW3HRKA8B08HB4HWBP2SN1YJKKD5Z):

• Block 140307: Lock 100,043,319,874 STX → scheduled unlock at burn height 836150 (block 143989)
• Block 140628: Actually unlocks (balance → 0)
• Block 143989: Rosetta shows unlock operation, but balance unchanged

Unlock Operation Returned in Block 140628

{
  "operation_identifier": {
    "index": 4
    "type": "stx_unlock"
    "status": "success"
    "account": {
      "address": "SP3MCAXZWZRCEW3HRKA8B08HB4HWBP2SN1YJKKD5Z"
    }
  }
  "amount": {
    "value": "100043319874"
    "currency": {
      "decimals": 6,
      "symbol": "STX"
    }
  }
  "metadata": {
    "tx_id": "0xc512c01981d015d276f4eca230e7c9543706b22ee57c765f81558c1ca1bfc8c5"

Unlock Operation Returned in Block 143989 (Duplicated, balance unchanged)

{
  "operation_identifier": {
    "index": 5886
  }
  "type": "stx_unlock"
  "status": "success"
  "account": {
    "address": "SP3MCAXZWZRCEW3HRKA8B08HB4HWBP2SN1YJKKD5Z"

[rafaelcr]

Reason for early unlock was that they were stacking 102,500 STX, 100,166 STX, and 100,043 STX and they feel below the threshold for that cycle. The minimum ended up at 120,000. The unlock happened when the next stacking cycle was about to begin.

https://api.hiro.so/extended/v1/tx/0xe619b5fbdccbf2c2e489bbce11cfe614e6e39ed0a1c2472b3abf98d5e1003654