assign the JIRA issue to yourself, then you can submit a change request (CR). Note If you need help with submitting your first CR, we have created a brief tutorial for you. Fixing issues and working stories submitters and maintainers what you think. Once your review and/or test is complete just reply to the CR with your findings, by adding comments and/or voting. A comment saying something like “I tried it on good set of criteria to keep in mind for writing effective unit tests. Minimize the lines of code per CR. Why? Maintainers have day jobs, too. If you send a 1,000 or 2,000 LOC change, how long do you think

CpOEx7SHUinzVvd55hLm7w6v72oMAoGCCqGSM49\nBAMCA0cAMEQCIC3bacbDYphXfHrN ULxpV/zwD08t7hJxNe8MwgP8/48fAiBiC0cr\nu99oLsRNCFB7R3egyKg1YYao0KWTrr1 T+rK9Bg==\n-----END CERTIFICATE-----\n" } assign the JIRA issue to yourself, then you can submit a change request (CR). Note If you need help with submitting your first CR, we have created a brief tutorial for you. Fixing issues and working stories submitters and maintainers what you think. Once your review and/or test is complete just reply to the CR with your findings, by adding comments and/or voting. A comment saying something like “I tried it on

CpOEx7SHUinzVvd55hLm7w6v72oMAoGCCqGSM49\nBAMCA0cAMEQCIC3bacbDYphXfHrN ULxpV/zwD08t7hJxNe8MwgP8/48fAiBiC0cr\nu99oLsRNCFB7R3egyKg1YYao0KWTrr1 T+rK9Bg==\n-----END CERTIFICATE-----\n" } assign the JIRA issue to yourself, then you can submit a change request (CR). Note If you need help with submitting your first CR, we have created a brief tutorial for you. Fixing issues and working stories submitters and maintainers what you think. Once your review and/or test is complete just reply to the CR with your findings, by adding comments and/or voting. A comment saying something like “I tried it on

CpOEx7SHUinzVvd55hLm7w6v72oMAoGCCqGSM49\nBAMCA0cAMEQCIC3bacbDYphXfHrN ULxpV/zwD08t7hJxNe8MwgP8/48fAiBiC0cr\nu99oLsRNCFB7R3egyKg1YYao0KWTrr1 T+rK9Bg==\n-----END CERTIFICATE-----\n" } assign the JIRA issue to yourself, then you can submit a change request (CR). Note If you need help with submitting your first CR, we have created a brief tutorial for you. Fixing issues and working stories submitters and maintainers what you think. Once your review and/or test is complete just reply to the CR with your findings, by adding comments and/or voting. A comment saying something like “I tried it on

against every change request being submitted. It is your responsibility to check that your CR passes these tests. No CR will ever be merged if it fails the tests and you shouldn’t expect anybody to pay attention your CRs until they pass the CI tests. To check on the status of the CI process, simply look at your CR on Gerrit, following the URL that was given to you as the result of the push in the previous step. Jobbuilder” will add to the CR a +1 vote if successful and a -1 vote otherwise. In case of failure, explore the logs linked from the CR History. If you spot a problem with your CR amend your commit and push

UinzVvd55hLm7w6v72oMAoGCCqGSM49\nBAMCA0cAMEQCIC3bacbDYphXfHrNULxpV/ ˓→zwD08t7hJxNe8MwgP8/48fAiBiC0cr\nu99oLsRNCFB7R3egyKg1YYao0KWTrr1T+rK9Bg==\n-----END ˓→CERTIFICATE-----\n" } ], "G1": [ { "MSPID": against every change request being submitted. It is your responsibility to check that your CR passes these tests. No CR will ever be merged if it fails the tests and you shouldn’t expect anybody to pay attention your CRs until they pass the CI tests. To check on the status of the CI process, simply look at your CR on Gerrit, following the URL that was given to you as the result of the push in the previous step.

UinzVvd55hLm7w6v72oMAoGCCqGSM49\nBAMCA0cAMEQCIC3bacbDYphXfHrNULxpV/ ˓→zwD08t7hJxNe8MwgP8/48fAiBiC0cr\nu99oLsRNCFB7R3egyKg1YYao0KWTrr1T+rK9Bg==\n-----END ˓→CERTIFICATE-----\n" } ], "G1": [ { "MSPID": against every change request being submitted. It is your responsibility to check that your CR passes these tests. No CR will ever be merged if it fails the tests and you shouldn’t expect anybody to pay attention your CRs until they pass the CI tests. To check on the status of the CI process, simply look at your CR on Gerrit, following the URL that was given to you as the result of the push in the previous step.

UinzVvd55hLm7w6v72oMAoGCCqGSM49\nBAMCA0cAMEQCIC3bacbDYphXfHrNULxpV/ ˓→zwD08t7hJxNe8MwgP8/48fAiBiC0cr\nu99oLsRNCFB7R3egyKg1YYao0KWTrr1T+rK9Bg==\n-----END ˓→CERTIFICATE-----\n" } ], "G1": [ { "MSPID": assign the JIRA issue to yourself, then you can submit a change request (CR). Note: If you need help with submitting your first CR, we have created a brief tutorial for you. 12.4.5 Fixing issues and working submitters and maintainers what you think. Once your review and/or test is complete just reply to the CR with your findings, by adding comments and/or voting. A comment saying something like “I tried it on

gorithm] Curve25519 wiki [https://en.wikipedia.org/wiki/Curve25519] SafeCurves [https://safecurves.cr.yp.to/index.html] ECC SEC1 [http://www.secg.org/sec1-v2.pdf] ECC SEC2 [https://www.secg.org/sec2-v2 gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf] STD [https://neuromancer.sk/std/] SafeCurves [https://safecurves.cr.yp.to] Koblitz Curves [https://link.springer.com/content/pdf/10.1007%2F3-540-46766-1_22.pdf] Weierstrass [https://en.wikipedia.org/wiki/Curve25519] Curve25519 paper [http://cr.yp.to/ecdh/curve25519-20060209.pdf] Ed25519 paper [http://ed25519.cr.yp.to/ed25519-20110926.pdf] 安全控制 存储安全：支持落盘数据加密存储 FISCO BCOS的落盘加密

gorithm] Curve25519 wiki [https://en.wikipedia.org/wiki/Curve25519] SafeCurves [https://safecurves.cr.yp.to/index.html] ECC SEC1 [http://www.secg.org/sec1-v2.pdf] ECC SEC2 [https://www.secg.org/sec2-v2 gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf] STD [https://neuromancer.sk/std/] SafeCurves [https://safecurves.cr.yp.to] Koblitz Curves [https://link.springer.com/content/pdf/10.1007%2F3-540-46766-1_22.pdf] Weierstrass [https://en.wikipedia.org/wiki/Curve25519] Curve25519 paper [http://cr.yp.to/ecdh/curve25519-20060209.pdf] Ed25519 paper [http://ed25519.cr.yp.to/ed25519-20110926.pdf] 安全控制 存储安全：支持落盘数据加密存储 FISCO BCOS的落盘加密