# txstream workgroup

## Participating in this Workgroup

- Alex
- Dave (overview)
- Diego
- Evaldas (not actively building this, consultant role)
- Julius
- Karolis
- Max
- Thibault

## Main Goals

- Main goal: Get the node software to properly communicate both ways with Wasp.
- We already have this with GoShimmer (https://github.com/iotaledger/goshimmer/tree/develop/plugins/txstream), now we need it for StarDust/Chrysalis. Wasp imports this module from GoShimmer as well.
- Create a specification for `txstream` - TIP (Karolis)
- Improve TIP based on feedback node teams (Thibault, Alex, Max)
- Implementation of `txstream` in Hornet, Bee and Wasp
- Cluster testing environment for Wasp using `txstream`
- Testing and docs

> No TIP but just a HackMD if only connecting to existing Event/API instead of creating a new plugin.

## Requirements

- Draft: https://hackmd.io/@Evaldas/HkPjaLt3t
- Open question: Wrap around existing Event/API or completely seperate (implement in both Wasp and Nodes)? To be investigated
- Security?
- To be discussed

## References

- Node API endpoints: https://editor.swagger.io/?url=https://raw.githubusercontent.com/iotaledger/tips/main/tips/TIP-0013/rest-api.yaml
- Node events endpoints: https://playground.asyncapi.io/?load=https://raw.githubusercontent.com/iotaledger/tips/main/tips/TIP-0016/event-api.yml

## Further discussion

- #stardust-txstream-wg

## Next steps:

- Initial spec from Karolis
- Changes to API/Events by Alex/Thibault
- Implement it all (mainly Wasp wrapper around events/api)
- Cluster tests and docs
- Done!

## Merging strategy

- To be discussed for wasp, either PR to `stardust-vm` to avoid further merging drama's or a seperate branch to be merged at a later point in time. -> Use existing stardust branch for PRs for this.