Re: Regarding CBOR-LD Web Transports

At Blockchain Commons we too have been moving toward use of CBOR for
digital asset wallets, in particular for use with Bitcoin. Our
specifications are being adopted by more and more bitcoin wallets and
services, with half-a-dozen announced or in progress.

However, our digital asset wallet community has largely being moving toward
these specifications for security reasons, leveraging animated QRs for
AirGap, and uri-friendly CBOR for “TorGap” over secure or non-correlatable
channels. But not for decentralized identity reasons. But I do believe that
there can be synergy here.

Here is our video demo about animated QR:
https://youtu.be/t-GGZ9FyuT8

Here is a video of key creation & child key derivation using an offline
device and delegating the child key safely to a networked device via QR:
https://youtu.be/19GVOIZNedU

You can see an entire airgap multisig bitcoin process at:
https://youtu.be/FCJ9QcNXjoU

This week we’ll be releasing a video on our two-level sharded secret key
reconstruction (SSKR) specs leveraging Shamir, and our new “Crypto-Request”
feature where on wallet can ask for generic or specific keys or
cryptographic values from other devices.

The reference implementation libraries for these specs in C or C++, but we
have multiple implementations of many of them in Rust, Python, Swift, Java,
JavaScript and more. We have both cli tools for developer experiments & iOS
(Mac & iPhone) to try them out live.
https://github.com/BlockchainCommons/crypto-commons

In particular the seed and key management specs could be of immediate use
to the credentials community which largely does not currently have these
features.

We love to add too and ultimately move our informal CBOR registry to IETF
soon:
https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-005-ur.md
— we’d love your help.

We’d also like to be able to start adding symmetric encrypted & asymmetric
encrypted manifest CBOR & CBOR-LD functionality as well soon, in particular
for requests, metadata backup, did:onion / did:btcr, and P2P claims. Let me
know if you are interested in being involved.

— Christopher Allen