{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":214236899,"defaultBranch":"main","name":"fabric-rfcs","ownerLogin":"hyperledger","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2019-10-10T16:50:57.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/7657900?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1693494180.0","currentOid":""},"activityList":{"items":[{"before":"29dfe1e0c945dfd9d7bc8866421a4f7b798b0690","after":"52f8d6543ea6a73b84d3718c998f5836b1ad26f9","ref":"refs/heads/main","pushedAt":"2023-12-06T03:09:35.000Z","pushType":"pr_merge","commitsCount":4,"pusher":{"login":"denyeart","name":"Dave Enyeart","path":"/denyeart","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20165681?s=80&v=4"},"commit":{"message":"Update RFC for extend chaincode lifecycle API to query all approved chaincodes\n\n- Fix the format\n- Update some information\n\nSigned-off-by: Tatsuya Sato ","shortMessageHtmlLink":"Update RFC for extend chaincode lifecycle API to query all approved c…"}},{"before":null,"after":"29dfe1e0c945dfd9d7bc8866421a4f7b798b0690","ref":"refs/heads/AA","pushedAt":"2023-08-31T15:03:00.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"ryjones","name":"Ry Jones","path":"/ryjones","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/466142?s=80&v=4"},"commit":{"message":"BFT signatures: update (#57)\n\nThe RFC currently calls for adding a gRPC service for getting the Header+Signature stream (Block attestation).\r\n\r\nAfter reviewing the current (SmartBFT fabric v2.3) and proposed solution, it is clear that adding a gRPC service\r\nand multiple new proto messages needlessly duplicates code and bloats the code base. The task is realised in the\r\ncurrent implementation by 6 lines of code - 3 in the orderer (set nil to the block payload, depending on the\r\ncontent type requested) and 3 in the peer (set the required content type).\r\n\r\nWe therefore revert this part of the proposal and will simply migrate the code from SmartBFT fabric v2.3 for this functionality.\r\n\r\nSigned-off-by: Yoav Tock ","shortMessageHtmlLink":"BFT signatures: update (#57)"}},{"before":"8ebea2f8fb54bdc6444229049e75eef98240cd0a","after":"29dfe1e0c945dfd9d7bc8866421a4f7b798b0690","ref":"refs/heads/main","pushedAt":"2023-05-29T11:58:39.699Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"tock-ibm","name":"Yoav Tock","path":"/tock-ibm","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15885305?s=80&v=4"},"commit":{"message":"BFT signatures: update (#57)\n\nThe RFC currently calls for adding a gRPC service for getting the Header+Signature stream (Block attestation).\r\n\r\nAfter reviewing the current (SmartBFT fabric v2.3) and proposed solution, it is clear that adding a gRPC service\r\nand multiple new proto messages needlessly duplicates code and bloats the code base. The task is realised in the\r\ncurrent implementation by 6 lines of code - 3 in the orderer (set nil to the block payload, depending on the\r\ncontent type requested) and 3 in the peer (set the required content type).\r\n\r\nWe therefore revert this part of the proposal and will simply migrate the code from SmartBFT fabric v2.3 for this functionality.\r\n\r\nSigned-off-by: Yoav Tock ","shortMessageHtmlLink":"BFT signatures: update (#57)"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"startCursor":"Y3Vyc29yOnYyOpK7MjAyMy0xMi0wNlQwMzowOTozNS4wMDAwMDBazwAAAAPCOa1r","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wNS0yOVQxMTo1ODozOS42OTk4MjBazwAAAAM2O1eB"}},"title":"Activity · hyperledger/fabric-rfcs"}