Christopher Allen

We've begun to draft some use cases for BIP-322 at https://hackmd.io/KR5ALrSSQO6eyrnUBJreeA — please feel free to add more, or add comments (in the view interface) if you have constructive criticism....

There is a thread starting today on Bitcoin-Lev list BIP-322: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-August/020844.html

@wolfmcnally has written up a research report on using a derivative of bech32 that we are calling bc32 at https://github.com/blockchaincommons/research and has been implemented in our bech32 library (which supports...

Recent commentary @kemitchell on this topic: https://writing.kemitchell.com/2019/11/07/BSD-Patents.html

Summary: That BSD-2-Clause Plus Patent License (spdx:BSD-2-Clause-Patent) is not the same license as the proposed Facebook BSD+Patent. The BSD-2-Clause Plus Patent License (spdx:BSD-2-Clause-Patent) is “gold”.

We likely will choose one Permissive and one Copyleft. For Permissive the BSD-2-Clause-Patent a good one for works derivative of BSD or MIT code, or one mostly of libraries that...

A number of our Patrons don’t want to financially support Copyleft, and much of Bitcoin is Permissive, so some repositories will need to be Permissive as well. It is a...

An issue with pubkeys is bitcoin uses 32 byte x-only, but multicodec uses 33-byte. Re: conversion see: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-July/020663.html

As far as signing, the best example we have is https://github.com/decentralized-identity/SchnorrSecp256k1Signature2019 but we don't actually know if it works.

BTW, I worked on a successor to BIP39 that turned keys into poetry a few years ago. Some of what we learned from that help create the better word-list for...