{"push_id":1647252303,"size":6,"distinct_size":6,"ref":"refs/heads/master","head":"671096a419f52869c4d6ccb810080162ffa45698","before":"23b3d809c34acc7703de643414504d74832c290c","commits":[{"sha":"351ea92a6b222730f3cfc0e39fcfc3bbaae77495","author":{"name":"Clark","email":"0c3dec305d7fe6df80564357a6a8d2d882973492@gmail.com"},"message":"Fix typo\n\nInstead of \"ensure the blockchain,\" it should be \"enter the blockchain\"","distinct":true,"url":"https://api.github.com/repos/clarkmoody/lightning-rfc/commits/351ea92a6b222730f3cfc0e39fcfc3bbaae77495"},{"sha":"9e0a0e893db389bfe392b2f4db8097949395fe28","author":{"name":"Olaoluwa Osuntokun","email":"69a12c6742ae5b3329f557d3da17697582c2d0a3@gmail.com"},"message":"BOLT 02: add a `chain-hash` field to the `open_channel` msg (#135)\n\nThis commit adds a `chain-hash` field to message that commences a\r\nfunding workflow. This field is used to specify a _target_ chain for the\r\nproposed channel. In order to uniquely identity blockchains in a manner\r\nthat doesn't require strict coordination between developers, the genesis\r\nhash of the target chain is used. For channels opened on the Bitcoin\r\nblockchain, the `chain-hash` field should _always_ be set to:\r\n000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f.\r\n\r\nIntroducing this new field _immediately_ allows nodes within the network\r\nto open a channel within any Satoshi-derived blockchain. Nodes can have\r\nchannels open across different blockchains globally, but also have many\r\nchannels open across distinct blockchains with the same peer.","distinct":true,"url":"https://api.github.com/repos/clarkmoody/lightning-rfc/commits/9e0a0e893db389bfe392b2f4db8097949395fe28"},{"sha":"a39b236e80f6e86d99eb0b312882f48b7cf56b01","author":{"name":"Rusty Russell","email":"69f5932eb9977dcad4aeec4104f9f99d5dd1ae66@rustcorp.com.au"},"message":"BOLT 2: require that we don't fulfill close to timeout either.\n\nIt was never mentioned, but fulfilling a timedout HTLC means a race\nbetween timing out and fulfilling, which is bad.\n\nSigned-off-by: Rusty Russell <rusty@rustcorp.com.au>","distinct":true,"url":"https://api.github.com/repos/clarkmoody/lightning-rfc/commits/a39b236e80f6e86d99eb0b312882f48b7cf56b01"},{"sha":"5ed243de2d3750121f9c0f1159f5d29369faca7d","author":{"name":"Rusty Russell","email":"69f5932eb9977dcad4aeec4104f9f99d5dd1ae66@rustcorp.com.au"},"message":"BOLT 3: fix labels on test vectors.\n\nAs per ElementsProject/lightning#134 Fabrice points out that to calculate\nour own commitment tx, we use the *other* side's revocation basepoint:\n\n\tThe revocationkey is a blinded key: the remote node provides the base,\n\tand the local node provides the blinding factor which it later\n\treveals\n\nThus, we fix the test vectors by renaming \"local_revocation_basepoint\"\nto \"remote_revocation_basepoint\", which is what we should be using.\n\nSigned-off-by: Rusty Russell <rusty@rustcorp.com.au>","distinct":true,"url":"https://api.github.com/repos/clarkmoody/lightning-rfc/commits/5ed243de2d3750121f9c0f1159f5d29369faca7d"},{"sha":"c3781c8938ee53f19aa3d87c8694af5cfb0209d7","author":{"name":"Fabrice Drouin","email":"063520b6f4661abc2a24cd8785e401455848285e@users.noreply.github.com"},"message":"Merge pull request #137 from rustyrussell/bolt3-use-remote-revocation-basepoint\n\nBOLT 3: fix labels on test vectors.","distinct":true,"url":"https://api.github.com/repos/clarkmoody/lightning-rfc/commits/c3781c8938ee53f19aa3d87c8694af5cfb0209d7"},{"sha":"671096a419f52869c4d6ccb810080162ffa45698","author":{"name":"Clark Moody","email":"0c3dec305d7fe6df80564357a6a8d2d882973492@gmail.com"},"message":"Merge pull request #1 from lightningnetwork/master\n\nCatch up to lightning-rfc","distinct":true,"url":"https://api.github.com/repos/clarkmoody/lightning-rfc/commits/671096a419f52869c4d6ccb810080162ffa45698"}]}
{"actor":{"display_login":"clarkmoody"}}