thoughts on positioning two secp256k1 public keys

0 replies 257 views
Posts: 2 · Reputation: 51
#1Jan 2, 2026, 05:13 PM
Hey everyone, I'm working on a feedback system to evaluate the positioning of two secp256k1 public keys. Based on my attempts, I found that the best indicator is the ETA. Like, if it takes 5 minutes to go from 100 to 1, then it should take about 2.5 minutes for 50 to reach 1. I've noticed this holds true when the initial number increases and the ETA changes. I did try something, but it didn’t quite work out and I’m unsure why. Any guidance would be super appreciated if I'm going down the wrong path. Here's what I tried: 1. Convert Public Keys to Coordinates: First, I took the public keys in hex format and converted them to coordinates on the elliptic curve (x, y). 2. Perform Point Comparison: Next, I compared the x-coordinates of the two public keys to see if they point to the same location on the secp256k1 elliptic curve. If the x-coordinates match, there's a good chance they represent the same public key. 3. Measure Execution Time: To track how long the comparison takes, I figured I'd use a programming language like Python, which has libraries for elliptic curves, or maybe a specialized cryptography library like OpenSSL. I needed functions for secp256k1 point comparison and timing the process. I even whipped up a Python example using the pycoin library to compare two secp256k1 public keys and check the time it takes. The code converts the public keys to coordinates and compares their x-coordinates. It should print out if the public keys are identical or not, along with the execution time.
6 Reply Quote Share

Related topics