Reject 117 (expired) #1008

1. 
   ysangkok commented at 4:41 pm on October 11, 2020: contributor

   Expired per BIP-0002 expiration rules. What do you say @maaku @btcdrak @kallewoof ?
2. Reject 117 (expired) 42e55930cc
3. 
   maaku commented at 6:48 am on October 12, 2020: contributor

   Tail-call script semantics provides a powerful mechanism for script execution, particularly when generalized to the recursive case (which BIP-117 does not include but is an explicit step along the path towards that goal). The passage of 3 years reflects the bitcoin development community’s priorities, not the viability or relevance of the proposal.
4. 
   gmaxwell commented at 7:15 am on October 13, 2020: contributor

   ACK.
5. 
   murchandamus commented at 8:18 pm on April 30, 2024: contributor

   This proposal did appear to have a working implementation, but I am not aware of community plans to progress it to the Final status. Since the proposal appears to not have garnered community interest and to not have made progress in almost seven years, per my understanding of BIP2, its status should be changed to Rejected. Should this BIP at a later time gain momentum again, its status should be updated to Draft or Proposed at such a time.

   ACK 42e55930cc4bf92fe65fd087635cb9e5fde41442

6. 
   murchandamus commented at 8:24 pm on April 30, 2024: contributor

   After reading the discussion on #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.
7. 
   maaku commented at 8:32 pm on April 30, 2024: contributor

   “Tail-call script semantics provides a powerful mechanism for script execution, particularly when generalized to the recursive case (which BIP-117 does not include but is an explicit step along the path towards that goal). The passage of 3 years reflects the bitcoin development community’s priorities, not the viability or relevance of the proposal.”

   This is as true now as when I wrote it a further 3 1/2 years ago. There is no reason to transition this BIP out of the Draft state. Please close this PR.

8. murchandamus added the label Process on May 10, 2024
9. 
   ysangkok commented at 8:50 pm on January 20, 2026: contributor

   Closing this since the “Rejected” status no longer exists in BIP-0003
10. ysangkok closed this on Jan 20, 2026

    ---

11. 
    ysangkok commented at 8:56 pm on January 20, 2026: contributor

    @maaku Per BIP-0003:

    BIPs that have had Draft status for extended periods will be moved to Complete or Deployed as applicable in collaboration with their authors.

    Would you like this BIP to be Complete or Deployed? I will then submit a separate PR for that.

12. 
    maaku commented at 11:03 pm on January 20, 2026: contributor

    I no longer have anything to do with bitcoin or the BIP process. I will be turning off notifications from this repository.
13. 
    murchandamus commented at 6:55 pm on January 21, 2026: contributor

    @ysangkok: I don’t think Deployed applies, since this is not used on mainnet. It could be moved to Complete, as it seems to me that all planned work has concluded and it has reference implementation and tests. If the last comment by @maaku were to be interpreted as the authors no longer pursuing this proposal, it could alternatively now be moved to Closed after all. :shrug:

Contributors
ysangkok maaku gmaxwell murchandamus

Labels
Process