{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":57929990,"defaultBranch":"master","name":"bips","ownerLogin":"TheBlueMatt","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2016-05-03T00:30:51.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/649246?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1713749072.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"4ee106096a4b5b31b27ab4f0a98972cae250f24b","ref":"refs/heads/2024-04-not-a-dumping-ground","pushedAt":"2024-04-22T01:24:32.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"TheBlueMatt","name":"Matt Corallo","path":"/TheBlueMatt","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/649246?s=80&v=4"},"commit":{"message":"Require BIPs be \"beyond the ideation phase\" before being merged\n\nAs the BIP process restarts, one general risk in the BIPs is that\nthey become (even more of) a dumping ground for half-baked ideas\nwhich even the BIP champion does not work on after the BIP is\nassigned. While simply never merging new BIPs addresses this issue,\nthis isn't particularly sustainable, and we should instead have\nsome concrete criteria here.\n\nBIPs generally fall into a few categories with respect to when they\nshould be considered ready for merge:\n * they're not particularly controversial (and not about consensus)\n   and move forward towards adoption in several ecosystem projects\n   relatively quickly or,\n * they generate lots of discussion, lots of feedback, the champion\n   actively pushes the BIP forward and makes sustained arguments for\n   adoption over some extended time period (this generally applies\n   to consensus changes).\n\nAs long as the BIP champion is relatively actively pushing for\nadoption (i.e. active on the BIP outside of the BIP text itself)\nand actively addressing feedback on the BIP, the BIP should be\nmerged, however if the BIP hasn't seen any adoption anywhere\n(outside of maybe one project the author wrote) and the BIP\nchampion is off doing other things, I'd argue it clearly should\nsimply be closed.\n\nThis commit adds some trivial but flexible text to that effect,\nrequiring roughly the above criteria for merge.","shortMessageHtmlLink":"Require BIPs be \"beyond the ideation phase\" before being merged"}},{"before":"09db33a98a6ed4a9b60cf430356dbe85c9ae4ec7","after":"d618202ed00b1481d4938bcbcd0d6b27753df6f5","ref":"refs/heads/2024-02-dns-payment-instructions","pushedAt":"2024-03-06T15:24:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TheBlueMatt","name":"Matt Corallo","path":"/TheBlueMatt","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/649246?s=80&v=4"},"commit":{"message":"minor grammar fixes and additional clarification on resolver selection","shortMessageHtmlLink":"minor grammar fixes and additional clarification on resolver selection"}},{"before":"8ba00663f7370fb9391f217affa89c00e93b20f5","after":"09db33a98a6ed4a9b60cf430356dbe85c9ae4ec7","ref":"refs/heads/2024-02-dns-payment-instructions","pushedAt":"2024-03-05T21:29:34.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"TheBlueMatt","name":"Matt Corallo","path":"/TheBlueMatt","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/649246?s=80&v=4"},"commit":{"message":"Add a BIP which resolves human readable names into payment info\n\nUser behavior has clearly indicated a strong demand for the\nresolution of human-readable names into payment instructions. This\nBIP defines a protocol to do so using only the DNS, providing for\nthe ability to query such resolutions privately, while utilizing\nDNSSEC to provide compact and simple to verify proofs of mappings.","shortMessageHtmlLink":"Add a BIP which resolves human readable names into payment info"}},{"before":"83c1343a03ac83dea87841fbe6294a6797e5387e","after":"8ba00663f7370fb9391f217affa89c00e93b20f5","ref":"refs/heads/2024-02-dns-payment-instructions","pushedAt":"2024-03-05T21:26:42.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"TheBlueMatt","name":"Matt Corallo","path":"/TheBlueMatt","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/649246?s=80&v=4"},"commit":{"message":"Add a BIP which resolves human readable names into payment info\n\nUser behavior has clearly indicated a strong demand for the\nresolution of human-readable names into payment instructions. This\nBIP defines a protocol to do so using only the DNS, providing for\nthe ability to query such resolutions privately, while utilizing\nDNSSEC to provide compact and simple to verify proofs of mappings.","shortMessageHtmlLink":"Add a BIP which resolves human readable names into payment info"}},{"before":null,"after":"039f1e7a07edd69fe3bf942c91a1fd31f24d413f","ref":"refs/heads/2024-03-uris-without-bodies","pushedAt":"2024-03-01T17:10:28.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"TheBlueMatt","name":"Matt Corallo","path":"/TheBlueMatt","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/649246?s=80&v=4"},"commit":{"message":"Update BIP 21 with information about more modern usage of it\n\nAs Bitcoin has grown, the introduction of new address formats\ndescribing new forms of payment instructions has become\nincreasingly fraught with compatibility issues. Not only does there\nexist traditional on-chain addresses, but some recipients wish to\nreceive Lightning (when the sender supports it) or newer formats\nsuch as Silent Payments.\n\nThis has led to increasing use of the BIP 21 query parameters to\nencode further optional payment instructions.\n\nLooking forward, as new payment instructions get adopted, it makes\nmuch more sense to include them in query parameters rather than\nreplace the existing address field, ensuring compatibility with\nsenders and recipients who may or may not be upgraded to support\nall the latest payment instructions.\n\nThis updates BIP 21 to suggest that future address formats do this.\n\nFurther, it updates BIP 21 to allow an empty bitcoin address in\ncases where new payment instructions have moved to becoming\nmandatory. This isn't a backwards-incompatible change any more than\nswitching to a new address format is, so doesn't impact existing\nBIP 21 implementations in a new way, however provides a nice\nconclusion to the query-parameter-based upgrade path - once a form\nof payment instructions has broad adoption, senders can simply drop\nthe existing address field, keeping their existing query parameter\nencoding, rather than replace the existing address field. It also\naddresses the question of what to do if a wallet no longer wishes\nto receive some legacy on-chain address, but has multiple payment\ninstruction formats that they wish to include - deciding which one\nto place in the address field would be a difficult task.","shortMessageHtmlLink":"Update BIP 21 with information about more modern usage of it"}},{"before":"05abc54f695a2700b6653f420daa175be55258c9","after":"83c1343a03ac83dea87841fbe6294a6797e5387e","ref":"refs/heads/2024-02-dns-payment-instructions","pushedAt":"2024-02-12T19:43:50.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TheBlueMatt","name":"Matt Corallo","path":"/TheBlueMatt","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/649246?s=80&v=4"},"commit":{"message":"f add note about user enumeration","shortMessageHtmlLink":"f add note about user enumeration"}},{"before":"ac7302c57ac4ff6a17190b5cb0326118d8fecadd","after":"05abc54f695a2700b6653f420daa175be55258c9","ref":"refs/heads/2024-02-dns-payment-instructions","pushedAt":"2024-02-12T19:07:34.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TheBlueMatt","name":"Matt Corallo","path":"/TheBlueMatt","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/649246?s=80&v=4"},"commit":{"message":"f document recipient formatting is user@domain","shortMessageHtmlLink":"f document recipient formatting is user@domain"}},{"before":"d46a29ff4b4ac27210bc81474ae18e4802141324","after":"ac7302c57ac4ff6a17190b5cb0326118d8fecadd","ref":"refs/heads/2024-02-dns-payment-instructions","pushedAt":"2024-02-12T18:51:19.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TheBlueMatt","name":"Matt Corallo","path":"/TheBlueMatt","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/649246?s=80&v=4"},"commit":{"message":"f various super minor tweaks","shortMessageHtmlLink":"f various super minor tweaks"}},{"before":"0849fe35b1ee19eee0adad76b3206d528e9d2c3d","after":"d46a29ff4b4ac27210bc81474ae18e4802141324","ref":"refs/heads/2024-02-dns-payment-instructions","pushedAt":"2024-02-11T00:10:52.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TheBlueMatt","name":"Matt Corallo","path":"/TheBlueMatt","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/649246?s=80&v=4"},"commit":{"message":"f list bastien as tentative co-author","shortMessageHtmlLink":"f list bastien as tentative co-author"}},{"before":"2d9c172cddd6eaf2b1dedea66595fb33fa987fef","after":"0849fe35b1ee19eee0adad76b3206d528e9d2c3d","ref":"refs/heads/2024-02-dns-payment-instructions","pushedAt":"2024-02-11T00:01:53.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TheBlueMatt","name":"Matt Corallo","path":"/TheBlueMatt","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/649246?s=80&v=4"},"commit":{"message":"f note lack of adoption","shortMessageHtmlLink":"f note lack of adoption"}},{"before":null,"after":"2d9c172cddd6eaf2b1dedea66595fb33fa987fef","ref":"refs/heads/2024-02-dns-payment-instructions","pushedAt":"2024-02-10T22:49:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"TheBlueMatt","name":"Matt Corallo","path":"/TheBlueMatt","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/649246?s=80&v=4"},"commit":{"message":"Add a BIP which resolves human readable names into payment info\n\nUser behavior has clearly indicated a strong demand for the\nresolution of human-readable names into payment instructions. This\nBIP defines a protocol to do so using only the DNS, providing for\nthe ability to query such resolutions privately, while utilizing\nDNSSEC to provide compact and simple to verify proofs of mappings.","shortMessageHtmlLink":"Add a BIP which resolves human readable names into payment info"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAENoZeWwA","startCursor":null,"endCursor":null}},"title":"Activity · TheBlueMatt/bips"}