ELIP: Silent Payments with Confidential Transactions on Liquid#38
Closed
Ferryx349 wants to merge 1 commit into
Closed
ELIP: Silent Payments with Confidential Transactions on Liquid#38Ferryx349 wants to merge 1 commit into
Ferryx349 wants to merge 1 commit into
Conversation
Signed-off-by: ABHAY PANDEY <pandeyabhay967@gmail.com>
Member
|
Appears to be slop. Blocked from org. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This ELIP specifies Confidential Silent Payments on Liquid, BIP-352's unlinkable static addresses combined with CT's hidden amounts and assets.
The BIP-352 core (input aggregation, shared secret, partial tweaks, labels,
K_max) is imported without modification. Liquid-specific additions are the CT envelope: confidential P2WPKH outputs, per-output blinding keys derived fromSin a separate hash domain,lsp/tlspaddresses (distinct fromlqCT addresses), anelspdescriptor, optional PSET fields, normative scan/recovery procedures, and a tweak-server receive profile with a concrete REST API.Includes worked test vectors. No consensus or relay changes.
Highlights vs. a minimal adaptation
lsp/tlspHRP:- avoids collision with existing confidential addressesk, label handling, BIP-352 increment rulesm/352'/coin'/account'/1'/0(scan),.../0'/0(spend)Status
Draft. Reference implementation (LWK) and final
lsp1...test vector pending.