Skip to content
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.

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

[CHANGELOG] Deprecation warnings for privacy, permissioning, PoW, fast sync #7891

Merged
merged 4 commits into from
Nov 20, 2024

Conversation

macfarla
Copy link
Contributor

PR description

for more info - https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu

Thanks for sending a pull request! Have you done the following?

  • Checked out our contribution guidelines?
  • Considered documentation and added the doc-change-required label to this PR if updates are required.
  • Considered the changelog and included an update if required.
  • For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

  • unit tests: ./gradlew build
  • acceptance tests: ./gradlew acceptanceTest
  • integration tests: ./gradlew integrationTest
  • reference tests: ./gradlew ethereum:referenceTests:referenceTests

Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
@matthew1001
Copy link
Contributor

I think this is fine @macfarla, especially as it's currently just an announce. The one that I feel I could do with a bit more clarity on is the smart contract permissioning. The blog says "These features have existing and novel app-layer solutions" for tessera and smart contract permissioning, which I agree with for tessera, but I'm not as familiar with possible alternatives for smart contract permissioning.

@macfarla
Copy link
Contributor Author

I think this is fine @macfarla, especially as it's currently just an announce. The one that I feel I could do with a bit more clarity on is the smart contract permissioning. The blog says "These features have existing and novel app-layer solutions" for tessera and smart contract permissioning, which I agree with for tessera, but I'm not as familiar with possible alternatives for smart contract permissioning.

agree there is some work to do to get permissioning plugin-able eg #7835

@diega
Copy link
Contributor

diega commented Nov 20, 2024

Is it clear how plugin-able the PoW parts are?

@macfarla
Copy link
Contributor Author

Is it clear how plugin-able the PoW parts are?

some work needs to be done still to make the consensus mechanism plugin-able - @diega is this something you'd be interested to contributing to?

Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
@macfarla macfarla enabled auto-merge (squash) November 20, 2024 22:55
@macfarla macfarla merged commit ab12657 into hyperledger:main Nov 20, 2024
43 checks passed
@macfarla macfarla deleted the deprecate-privacy branch November 21, 2024 00:17
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.

4 participants