🚧 Dev ➾ Support for external TZkT Instances that are not managed by the Flextesa plugin to the VScE UI

[hu3man]

🔗 Epic|Feature Link

No response

🚥 Definition of Done

• [x] 🎯 Planning and Design
• [ ] 🏎️ Dev Implementation (PR merged)
• [ ] ✍️ Release Notes Added
• [ ] 🏆 Product Acceptance

✅ To Do

Sliced tickets:

• Move all polling to subscriptions
• Implement filtering that only query data that matters (contracts with aliases)
• Refactor local indexing functionality to use aliases
• Support pagination or filtering to support real-world usage where large datasets can be added

No response

⚖️ Acceptance Criteria

✨ Functional:

• [ ] The TZkT UI component in VScE can be pointed at a public TZkT instance (ghostnet indexer for example)
• [ ] The UI should only listen for contracts/operations known by Taqueria (populated from aliases/state)
• [ ] Replacing the use of polling with subscriptions
• [ ] Upon switching environments, the UI should switch to the correct TZkT source
• [ ] Reduce/filter input to cover only data relevant to the current Taqueria project
• [ ] Only query the contracts that are known to Taqueria (aliases)

• [ ]

  📐 Non-Functional:

• [ ] ...

🔭 Scope

🙅‍♂️ Out of Scope:

• ...

🧰 Work Description

Currently, the VScE TzKT indexer only works on a sandbox. We want to expand this so that the UI in VScE can show relevant contracts and operations on testnets as well

🦄 Sizing

7

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[jevonearth]

Notes from today's standup;

Some blockers around tzkt for @MichalLytek , @AlirezaHaghshenas are helping unblock that. Some or all of the filtering is implemented

Work on changing polling to subscriptions is underway. We need to talk about this when @hu3man is back in the fold.