8000 feat(connector-besu): remove tessera support · Issue #3883 · hyperledger-cacti/cacti · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat(connector-besu): remove tessera support #3883

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
petermetz opened this issue Apr 29, 2025 · 2 comments
Open

feat(connector-besu): remove tessera support #3883

petermetz opened this issue Apr 29, 2025 · 2 comments
Labels
Besu Breaking_V2 Changes that can only be made with the release of v3.0.0 due to them being breaking changes.
Milestone
v3.0.0

Comments

@petermetz
Copy link
Contributor
petermetz commented Apr 29, 2025 •
edited
Loading

BREAKING CHANGE

Besu has deprecated privacy features and since we are coming up on a major release we should also use this opportunity to reduce complexity in the Besu connector by eliminating the associated features from the connector itself and from the testing infrastructure as well (Besu AIO container image).

Tessera-based privacy is deprecated in Besu version 24.12.0 and later. Please read this blog post for more context on the rationale behind this decision as well as alternative options.

Source 1: https://besu.hyperledger.org/private-networks/concepts/privacy
Source 2: https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu

Implementation Notes

You can search for .priv. in your favorite IDE and filter the results to .ts file extensions which then will give you a (probably/hopefully) comprehensive list of places in the code where privacy features are being used.
These all need to be removed and the corresponding public API surface features removed as well.

cc: @hyperledger-cacti/cacti-maintainers
@petermetz petermetz added Besu Breaking_V2 Changes that can only be made with the release of v3.0.0 due to them being breaking changes. labels Apr 29, 2025
@petermetz petermetz added this to the v3.0.0 milestone Apr 29, 2025
@petermetz petermetz self-assigned this Apr 29, 2025
petermetz added a commit to petermetz/cacti that referenced this issue Apr 29, 2025 8000
@petermetz
feat(connector-besu): remove tessera support
66c40b7 
WORK IN PROGRESS

Fixes hyperledger-cacti#3883

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz added a commit to petermetz/cacti that referenced this issue Apr 29, 2025
@petermetz
feat(connector-besu): remove tessera support
d0262b8 
WORK IN PROGRESS

Fixes hyperledger-cacti#3883

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
@outSH
Copy link
Contributor
outSH commented Apr 30, 2025 •
edited
Loading

Since privacy features in besu were main differentiator from geth and other standard ethereum implementations, maybe it'd be better to consolidate this connector with cactus-plugin-ledger-connector-ethereum? Sadly I didn't have any time to work on my connector inheritance idea (that would be great for this scenario), but I think if there are little differences and JSON-API is basically the same I don't think there's a strong need for duplicated code

@petermetz
Copy link
Contributor Author

@outSH I agree. We could retire one or the other connector as of v3.0.0 (where we can make breaking changes) just have to make sure the features are merged all together so nobody gets left behind in that sense.

@petermetz petermetz removed their assignment May 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Besu Breaking_V2 Changes that can only be made with the release of v3.0.0 due to them being breaking changes.
Projects
None yet
Milestone
v3.0.0
Development

No branches or pull requests
2 participants
@petermetz @outSH
0