bip32 | A BIP32 compatible library | Cryptocurrency library

looking over https://github.com/iancoleman/bip39 I found I had to specify the correct ravencoin network specifications (don't really understand what this object means) but once I did, it worked perfectly.

After much research I have discovered that there is a simple way to extract the uncompressed public key by using the method serialize_uncompressed() on the public key, which is part of the same secp256k1 crate.

This provides a 65-byte output, where the first byte should be dropped to create the correct 64-byte public key.

junderw on Github answered this:

publicKey is a Buffer.

publicKey.toString('hex') will turn it into a hex string.

Similarly, for Base64, 'base64' can be used.

Assuming that "OTP" is a "one time password" as part of a 3D Secure flow, then you can trigger this in test mode by using the SCA regulatory test cards such as the 3155 or 3184 card.

It's not clear where your error is coming from, but if you can share more detail with reproduction in test mode then someone may be able to offer more suggestions.

The dart bip32 package doesn't seem to encode the signature in DER format, but rather in a simple (r, s) encoding. However DER is required for Bitcoin. For more information see:

https://bitcoin.stackexchange.com/questions/92680/what-are-the-der-signature-and-sec-format

You can either add the DER extra bytes yourself according to your r and s or check if there's a DER encoding in the dart bip32 library.

OK can solved this problem problem occur in the ecuve function bytes is less than 32 bytes just padding 0 in the left equal 32 bytes just solved it !

Public-key. Mathematically an elliptic curve public key is a point on the curve. For the elliptic curve used by Bitcoin, secp256k1, as well as other X9-style (Weierstrass form) curves, there are (in practice) two standard representations originally established by X9.62 and reused by many others:

• uncompressed format: consists of one octet with value 0x04, followed by two blocks of size equal to the curve order size containing the (affine) X and Y coordinates. For secp256k1 this is 1+32x2 = 65 octets

• compressed format: consists of one octet with value 0x02 or 0x03 indicating the parity of the Y coordinate, followed by a block of size equal tot he curve order containing the X coordinate. For secp256k1 this is 1+32 = 33 octets

The public key output by your trezor is the second form, 0x02 + 32 octets = 33 octets. Not 32.

I've never seen an X9EC library (ECDSA and/or ECDH) that doesn't accept at least the standard uncompressed form, and usually both. It is conceivable your python library expects only the uncompressed form without the leading 0x04, but if so this gratuitous and rather risky nonstandardness, unless a very good explanation is provided in the doc or code, would make me suspicious of its quality. If you do need to convert the compressed form to uncompressed you must implement the curve equation, which for secp256k1 can be found in standard references, not to mention many implementations. Compute x^3 + a*x + b, take the square root in F_p, and choose either the positive or negative value that has the correct parity (agreeing with the leading byte here 0x02).

The 'xpub' is a base58check encoding of a hierarchical deterministic key, which is not just an EC(DSA) key but adds metadata for the key derivation process. If you base58 decode it and remove the check, you get (in hex):