I'm not sure if EllipticCurve.lift_x has well-defined Y coordinate or not, but at least my current version of Sage computes the wrong G. Fix this.
Fix G.y parity in sage code #996
pull sipa wants to merge 1 commits into bitcoin-core:master from sipa:202110_evengy changing 1 files +3 −0-
sipa commented at 2:16 PM on October 20, 2021: contributor
-
Fix G.y parity in sage code 044d956305
- real-or-random approved
-
real-or-random commented at 2:24 PM on October 20, 2021: contributor
ACK 044d95630556dda5492a70af056bc277f0b79ebc
Crazy that I missed this (or it really has changed in sage?)
- real-or-random merged this on Oct 20, 2021
- real-or-random closed this on Oct 20, 2021
- sipa referenced this in commit f727914d7e on Oct 28, 2021
- sipa referenced this in commit 440f7ec80e on Oct 31, 2021
- sipa referenced this in commit d057eae556 on Dec 2, 2021
- fanquake referenced this in commit c4a1e09a8c on Dec 3, 2021
- sipa referenced this in commit 86dbc4d075 on Dec 15, 2021
- jonasnick cross-referenced this on Jan 2, 2022 from issue Sync Upstream by jonasnick
- real-or-random referenced this in commit 21e2d65b79 on Jan 5, 2022
- gwillen referenced this in commit 35d6112a72 on May 25, 2022
- janus referenced this in commit 879a9a27b9 on Jul 10, 2022
- patricklodder referenced this in commit 21badcf9d2 on Jul 25, 2022
- patricklodder referenced this in commit 03002a9013 on Jul 28, 2022
- backpacker69 referenced this in commit 77186f4a04 on Jan 18, 2023
- str4d referenced this in commit 6de4698bf9 on Apr 21, 2023
- vmta referenced this in commit e1120c94a1 on Jun 4, 2023
- vmta referenced this in commit 8f03457eed on Jul 1, 2023
Contributors