bips
bips copied to clipboard
Reject 199 (expired)
This BIP is expired according to BIP-0002 expiration rules.
It is linking an ZKCP implementation (pay-to-sudoku). But ZKCP is broken.
It is not mentioned that PTLC's are superior for many applications.
The HTLC's are discussed and explained in the lightning-rfc documents, and they are subtly different.
It is not explained how an optimal construction can be achieved using miniscript.
Tagging @ebfull
The claim the ZKCP is broken is outright false. That paper is about issues with particular implementation using snarks.
I don't see any issue moving this proposal to rejected, as you note there are other more efficient constructions and AFAIK this particular one isn't used as a freestanding thing. ACK.
ACK
(Waiting on https://github.com/bitcoin/bips/pull/1016 to clarify the rejection criteria but I'm happy with @gmaxwell rationale here. Plus author has been cc'd and has not opposed)
@kallewoof What is needed for this to move forward?
@ysangkok: I'm working on a revised BIP process (BIP 3) that will propose an update to the 3 year rejection rule. But it isn't completed, will need review and will take time to become active if it is accepted. In the meantime BIP 2 is clearly active so in this particular case with the BIP author not opposing this change I have ACKed. It is obviously up to the BIP editors whether they merge this or not though.
The HTLC's are discussed and explained in the lightning-rfc documents, and they are subtly different.
Would it then be more correct to update this BIP with the subtle differences (and then change it to Final)?
After reading the discussion on https://github.com/bitcoin/bips/pull/1012, it may be better to hold off on merging this PR, as there is currently an on-going discussion about revising the BIP process per a successor to BIP2.