Skip to content

Zsa integration with upstream main#52

Closed
PaulLaux wants to merge 268 commits intomainfrom
zsa-integration-demo-ag
Closed

Zsa integration with upstream main#52
PaulLaux wants to merge 268 commits intomainfrom
zsa-integration-demo-ag

Conversation

@PaulLaux
Copy link

This PR represents the difference between the current working version of the ZSA-enabled Zebra and the upstream Zebra.

This version is very raw at this point and does not include state management.

Expect significant changes as we fo further.

…(without unit tests fixing for now).

- Refactored `ShieldedData` and `Action` structures to be generics parameterized by Orchard flavor
  (`OrchardVanilla` or `OrchardZSA`), enabling support for both Orchard protocols in Tx V6.
- Introduced a `burn` field in `ShieldedData` to support ZSA, with unit type for Tx V5 and a vector of burn items for Tx V6.
- Modified `Transaction` enum methods (orchard_...) to handle generics properly, ensuring compatibility with both Orchard flavors.
- Implemented serialization and deserialization for Tx V6 while avoiding code redundancy with Tx V5 wherever possible.
… with the upstream halo2/librustcash/orchard/sapling versions
dmidem and others added 29 commits February 17, 2025 13:56
## Motivation

<!--
- Describe the goals of the PR.
- If it closes any issues, list them here.
-->
We want to deploy the Zebra node on an ECS service in AWS to be able to
communicate with it.
This PR adds the TF code needed for deploying a full ECS service, with
Terragrunt code to drive it in an AWS account.
This also adds the Lambda function for viewing the logs publicly, and
all the Lambdas supporting resources.
@dmidem dmidem closed this Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants