Skip to content

chore(vendors|approaches):add fairblock and update private payment approach#91

Merged
Meyanis95 merged 2 commits intoethereum:masterfrom
YadlaMani:approaches/purpose-built-confidential-layer
Feb 24, 2026
Merged

chore(vendors|approaches):add fairblock and update private payment approach#91
Meyanis95 merged 2 commits intoethereum:masterfrom
YadlaMani:approaches/purpose-built-confidential-layer

Conversation

@YadlaMani
Copy link
Contributor

What are you adding?

  • Vendor/Protocol
  • Enterprise Use Case
  • Update to existing content
  • Other

Description

Fairblock is a purpose-built confidential layer combining lightweight homomorphic encryption + ZK to enable confidential transfers for existing EVM assets, with public counterparty relationships and scoped selective disclosure.

Checklist

  • I've checked this doesn't duplicate existing content
  • All links work
  • Info is accurate

Copy link
Contributor Author

@YadlaMani YadlaMani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed the Purpose-Built Confidential Layer from this pr

Copy link
Collaborator

@Meyanis95 Meyanis95 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@YadlaMani
Copy link
Contributor Author

@Meyanis95 whenever you get a chance, could you open the issue so we can continue the discussion there? I’ll follow up with a detailed response and address your questions in that thread.
Appreciate your time on this.

@Meyanis95
Copy link
Collaborator

Hey @YadlaMani, I think you're in the best position to write the issue.

I'd suggest writing it as a new ./pattern to add to the map. Ideally, the issue should motivate that this technical pattern isn't mapped yet, as well as describe it thoroughly in the proposed pattern card.

Also mention that once done, it could be approved as one of the building blocks for a proposed approach to the private payments use case.

Also, we're good to merge this PR, and the newly created issue could be addressed in a new one.

@YadlaMani
Copy link
Contributor Author

@Meyanis95 thank you for clairfication.I will be working on the issue please merge this pr if everyting is good to go with this pr

@Meyanis95 Meyanis95 merged commit e73331d into ethereum:master Feb 24, 2026
5 checks passed
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.

2 participants