secp256k1 | Optimized C library for EC operations on curve secp256k1 | Cryptography library

As kelalaka pointed out in a comment on the original post, I was confusing the the order of the group and the finite field F_p. I was getting values modulo the Group Order, when I should've been using the values modulo prime p used to define the finite field.

The new and correct result I get is:

When signing, not the data itself is signed, but the hash of the data. This is necessary on the one hand to be able to sign longer messages and on the other hand for security reasons (s. here).

For secp256k1 typically a digest with an output size of 256 bit is used (s. here), e.g. SHA256.

If you take a digest with a larger output size, the leftmost n bits of the hash are considered according to NIST FIPS 186-4 (s. here, where n is the key size, i.e. bit size of the generator order, 256 bit for secp256k1).

This is the reason why in the posted example the verification is successful: Only the first 32 bytes are considered, which are identical.

If the hashed value of the data is used instead, the verification fails as expected:

As stated in the documentation of the standard library:

Julia also provides the RandomDevice RNG type, which is a wrapper over the OS provided entropy.

Note that the word "entropy" is abused here. The OS will - with high likelihood - not directly return entropy, it will return random bytes from it's own seeded pseudo random number generator.

The implementation of a function usable with serde's with-attribute is mostly boilerplate and looks like this. This only differentiates between human-readable and other formats. If you need more fine-grained control, you could branch on a thread-local variable instead.

The fix is to the issue is to add --permissions-nodes-contract-version=2 to your besu command line.

This is because in v 2.0.0 of permissioning smart contracts repo we changed the interface as per the changelog https://github.com/ConsenSys/permissioning-smart-contracts/releases/tag/v2.0.0 It is in the besu docs here https://besu.hyperledger.org/en/stable/HowTo/Limit-Access/Specify-Perm-Version/ but I have already reported this issue and it has been fixed on the documentation of on-chain permissioning tutorial.

you can find more details here

1. Github issue
2. Besu Docs

Turns out, the solution is rather simple. When adding another extension directory to the java command, the connection works:

I managed to solve it.

1. Generate keys using ecdh.generateKeys and export public key as compressed.
2. Use ASN1.js and create schema for RFC5480 and RFC59159.
3. Encode as DER generated keys using created ASN1.js schemas.

In my case, downgrading the version of @truffle/hdwallet-provider in package.json from 1.2.4 to 1.2.3 helped:

Yes, you can. The library has support for compression and decompression of points. During the decompression, the library must find y if it can.

The header of the DecodePoint