Delegated SAFEs show incorrect history
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 7
- Avg merge
- 4h 1m
- Merged PRs (30d)
- 6
Description
`0xE983D60dE7E40fea4b2c878c21CD88AaFE5CD16d` is a multisig SAFE wallet that is staked to @stronk-dev. [The explorer reports that correctly](https://explorer.livepeer.org/accounts/0xE983D60dE7E40fea4b2c878c21CD88AaFE5CD16d/delegating):
But that account has nothing in the "history" tab. When did it delegate?
[That history is instead attributed to iameli.eth](https://explorer.livepeer.org/accounts/0x70CAb68009e9545f8bebcD20469b8d3bAab5DB8F/history) (`0x70CAb68009e9545f8bebcD20469b8d3bAab5DB8F`), which is the account that _performed the delegation_ using authorizations from the multisig, but it was not the actual delegate.
The error appears to be coming from the subgraph aggregation rather than anything on-chain, thankfully
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies subgraph aggregation as the likely source of the incorrect history attribution. Start by tracing how delegated SAFE events are attributed to accounts, then verify the affected multisig history against the delegation performed through authorizations; done means the history appears under the actual delegate account rather than the authorizing account.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100