o1-labs / o1-labs/Archive-Node-API

mesa-mut archive node has zero indexed actions for a live zkApp account

Open
#201 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
19
Forks
9
Avg merge
14h 20m
Merged PRs (30d)
8

Description

Account: B62qmMvzQNSCnZ4qH1N9uJByov9EyGushzv1jV7Cqg8UwS6BrRgHGzk
Network: mesa-mut

Summary: the account's live actionState (from the plain GraphQL node) shows 5
non-trivial checkpoint values, proving it has genuine dispatched-action
history. The archive node, queried for the same account, returns zero
actions. Any zkApp call that builds a proof via the reducer (getActions +
reduce over the action window) against this archive will fail its
actionState precondition every time, because it can never fold to the real
on-chain checkpoints below.

--- 1) Live node: account has real action history ---

curl -s https://plain-1-graphql.mesa-mut.minaprotocol.com/graphql \
  -H 'Content-Type: application/json' \
  --data-binary '{"query":"{ account(publicKey: \"B62qmMvzQNSCnZ4qH1N9uJByov9EyGushzv1jV7Cqg8UwS6BrRgHGzk\") { actionState } }"}'

Result:

{"data":{"account":{"actionState":[
  "11458356342759438541738573545169597086675027729527248375916260588605121581293",
  "17586986046166294258830928060876012965208590900444248935753527009853595352328",
  "13837801268417440190225600024460171302089933907320929190650982698721074902359",
  "11698221125984846111284980357655256601121460624292826388540328477116370830899",
  "2224141281896578534795846560567363169197624904962533988426166532576061498362"
]}}}

Non-zero, non-initial values -> the account has genuinely dispatched actions.

--- 2) Archive node: nothing indexed for the same account ---

curl -s https://archive-node-api.mesa-mut.minaprotocol.com/ \
  -H 'Content-Type: application/json' \
  --data-binary '{"query":"{ actions(input: { address: \"B62qmMvzQNSCnZ4qH1N9uJByov9EyGushzv1jV7Cqg8UwS6BrRgHGzk\" }) { blockInfo { distanceFromMaxBlockHeight } actionState { actionStateOne actionStateTwo } actionData { accountUpdateId data transactionInfo { sequenceNumber zkappAccountUpdateIds } } } }"}'

Result:
{"data":{"actions":[]}}

--- Observed downstream effect ---

Included-but-failed transaction, failure reason
Account_action_state_precondition_unsatisfied:
Hash: 5JuapscdEj6YbUktGRMQxAv3UcRL55ud8kpsN4ACJsicP2PcAWjc
Block: 3NKmxXWuY5eZ5Em2SfwERuZb8c2dusdXBnVQtVut6N4S3ngsNRm8

--- Ask ---

The mesa-mut archive at https://archive-node-api.mesa-mut.minaprotocol.com/
appears to have stopped indexing (or never indexed) this account's actions.
Please check/resync its indexing — every transaction that depends on the
action reducer will keep failing on-chain until it reflects the real
actionState history shown above.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the live-node and archive-node GraphQL queries for the specified mesa-mut account, then trace the archive action-indexing and resync entry points. Compare the indexed actionState history with the live account values and the reported failed transaction. Done means the archive query returns the account's actions and reducer-dependent transactions can obtain the correct history.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, typescript
Domain
api, backend, data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.