Sjors Provoost

Results 247 issues of Sjors Provoost

Currently (pending #5) you can get the `address` for a `HDKey` instance, but in order to get the `scriptPubKey`, you have to parse the address. This adds complexity when generating...

See suggested improvements here: https://github.com/ElementsProject/libwally-core/pull/349#issuecomment-1326916051

Hopefully this works again after #61.

As of #69 Xcode is handling the building of libwally-core. This reveals a number of warnings: We should ideally resolve these upstream rather than suppress the warnings. That is, assuming...

Since #54 the [build script](https://github.com/Sjors/libwally-swift/blob/master/build-libwally.sh) switches from `libsecp256k1-zkp` to vanilla `libsecp256k1` (and matching the commit used by Bitcoin Core). This uses libwally-core's `--enable-standard-secp` configure flag (introduced in https://github.com/ElementsProject/libwally-core/pull/301). The problem...

For example in order to call `bip39_mnemonic_from_bytes` and convert `Data` to `String`: ```swift precondition(entropy.data.count

See e.g. https://github.com/blockchain/libwally-swift/pull/14/files#r363318690

Although Bitcoin signatures are deterministic thanks to [RFC6979](https://tools.ietf.org/html/rfc6979), adding entropy to libwally using `wally_secp_randomize` helps it protect against side-channel attacks. https://wally.readthedocs.io/en/latest/core/#c.wally_secp_randomize

See upstream https://github.com/ElementsProject/libwally-core/issues/116 It would enable this:

nginx config for https needs: ``` proxy_set_header X-Forwarded-Proto https; ```

provisioning