add support to v2 schema #9
Conversation
| StakingTimeLock uint64 `json:"staking_timelock"` | ||
| StakingOutputIndex uint64 `json:"staking_output_index"` | ||
| StakingTxHex string `json:"staking_tx_hex"` | ||
| IsOverflow bool `json:"is_overflow"` |
There was a problem hiding this comment.
@jeremy-babylonlabs @gusin13 i think we need to review the msg events needed for phase-2.
For example, IsOverflow, StakingStartTimestamp, stakingTimeLock, stakingOutputIndex, and stakingTxHex don’t seem to be necessary.
If I’m not mistaken, we only need the staking transaction hash and its new state. Theoretically, this means we could significantly simplify the current messaging system.
We should align the msg with state changes in the indexer and only emit the fields that needed for performing the stats calculation
There was a problem hiding this comment.
hmm right, needs investigation.
let me check, @jeremy-babylonlabs this pr is not urgent correct as you already have local copy of schema in api-service?
is it ok if we close this pr, will open a new one later once i have clarity on schema.
closes #8