Latest white paper from September’s #RWOT12. Goal is to understand & tie together various decentralized #web3 identity efforts with W3C Verifiable Credentials. For instance, how various on-chain proofs are used to help in the verification of claims. Team led by @by_caballero. https://twitter.com/RWOTEvents/status/1642957657177997312
If you’d like to attend, please join our Signal channel and/or announcements list to get all the latest info. [3/5] https://www.blockchaincommons.com/subscribe.html#gordian-developers
April’s topics include: Blockchain Commons Goes to IETF Dispatch; UR/CBOR Updates; Evolving Internet-Drafts for dCBOR and Gordian Envelope; SSKR sharing for JavaCard, and QuickConnect for #Nostr. Agenda evolving at https://github.com/BlockchainCommons/Gordian-Developer-Community/discussions/106 [2/4]
Our next monthly Gordian Developer meeting is on April 5th at 4pm PT. These meetings are for talking about the cooperative progress on all of our wallet interoperability projects, such as URs, SSKR, Gordian Envelope, CSR, and more. Details in 🧵…[1/4]
If the creation of open, interoperable, secure, and compassionate digital infrastucture is important to you, please also become a Blockchain Commons sponsor at GitHub. [4/4] https://github.com/sponsors/BlockchainCommons
Replying to @kimdhamilton, @vinayvasanji, @crabbylions and @slowburnxyz
Though I’m not a fan of abusing volunteer bitcoin full-node storage by Ordinal Inscriptions, the technique behind is sound (I’d prefer core just allowed larger op_return). Combined with #GordianEnvelope’s elision privacy & proof of inclusion could be good option for did:btcr 2.0.
Replying to @kimdhamilton, @vinayvasanji, @crabbylions, @slowburnxyz and @vinayvasanji
There is a lot more context on BTCR past & BTCR future in the @Rubric_Podcast at https://rubric.cc/podcast/the-granddaddy-of-dids/
RT @ChristopherA: @kimdhamilton @vinayvasanji @crabbylions @slowburnxyz Though I’m not a fan of abusing volunteer bitcoin full-node storage…
RT @ChristopherA: @kimdhamilton @vinayvasanji @crabbylions @slowburnxyz @vinayvasanji There is a lot more context on BTCR past & BTCR futur…
Replying to @kimdhamilton, @vinayvasanji, @crabbylions, @slowburnxyz and @Rubric_Podcast
On the topic of visiting limits on op_return, see the discussion thread on bitcoin-dev starting at https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-February/021387.html
Replying to @kimdhamilton, @vinayvasanji, @crabbylions, @slowburnxyz and @Rubric_Podcast
See also this bitcoin-core issue on changing the op_return limit: https://github.com/bitcoin/bitcoin/issues/27043. The issue was closed as “not-planned”, but then later reopened.
@peterktodd also offered to start work on a PR about this at https://github.com/bitcoin/bitcoin/issues/27043
RT @ChristopherA: @kimdhamilton @vinayvasanji @crabbylions @slowburnxyz @Rubric_Podcast On the topic of visiting limits on op_return, see t…
RT @ChristopherA: @kimdhamilton @vinayvasanji @crabbylions @slowburnxyz @Rubric_Podcast See also this bitcoin-core issue on changing the op…
Replying to @exiledsurfer, @kimdhamilton, @vinayvasanji, @crabbylions, @slowburnxyz and @mikeinspace
I’m worried that asking essentially Bitcoin full-node volunteers to store that much data risks following in Ethereum’s footsteps, where only professionals can offer nodes. Right now, to offer an Esplora-class full node with all -tx + extra index data costs me about $100 a month.
Replying to @exiledsurfer, @kimdhamilton, @vinayvasanji, @crabbylions, @slowburnxyz and @mikeinspace
Yes, you can do a Bitcoin full-node without tx data, or even do a pruned full-node, but we have to think long-term (decades). That being said, changing the limit of op_return from 80 to 128 or 256 bytes allows for a lot of functionality without as much risk.
Replying to @exiledsurfer, @kimdhamilton, @vinayvasanji, @crabbylions, @slowburnxyz and @mikeinspace
For instance, I can post a transaction with a fully elided #GordianEnvelope containing thousands of claims in <128 bytes, and then use proof-of-inclusion to demonstrate that those claims where signed and exist. https://www.youtube.com/watch?v=3G70mUYQB18
RT @ChristopherA: @exiledsurfer @kimdhamilton @vinayvasanji @crabbylions @slowburnxyz @mikeinspace I’m worried that asking essentially Bitc…
Replying to @Truthcoin
Replying to @mikeinspace
Replying to @DrMemebrain, @exiledsurfer, @kimdhamilton, @vinayvasanji, @crabbylions, @slowburnxyz and @mikeinspace
We have some ops people puzzling how to reduce the costs, but if you are hosting Esplora on a performance virtual instance, even when putting the full-node data on a less expensive remote node, the storage costs are the largest portion. Over $150/m. We may be able to get 1/2.
Interesting thread🧵on “the tank man of the digital age”. Our decentralized identity community needs to better understand of how to help people like this. LESS (Legally-Enabled Self-Sovereign Identity) isn’t going to solve this; we need better minimized-trust identity solutions! https://twitter.com/rachel_cheung1/status/1642877064360632322
RT @BobMcElrath: PoW remains the only reasonable method I’ve ever seen to transfer costs from receiver to sender. In the coming world of LL…
Replying to @adam3us and @tierotiero
We’d love to see this as part of https://spotbit.info, which offers a tor service that aggregates price feeds from multiple sources. The idea was that there would be many out there to check against, or you could host your own. Still a POC (today I note live graph is broken).
Replying to @fuji_money, @Blockstream, @bitfinex and @krakenfx
Gordian Envelope & dCBOR was presented at last week’s IETF Dispatch, but we need to highlight its simplicity & how it addresses general IETF requirements for greater privacy. Blockchain Commons aims to refine presentations to focus more on these. https://datatracker.ietf.org/doc/minutes-116-dispatch-202303270030/ [4/12]
There are many wallet developers supporting interoperability of PSBTs using animated QRs — this is a significant achievement for the Gordian Developer Community: https://github.com/blockchainCommons/Gordian-Developer-Community/#ur. We are seeking video clips wallets to demonstrate PSBT support for a joint video. [3/12]
If you don’t have time for the video, we have a summary of the meeting, the presentation PDF, along with an audio file and raw transcript at: https://github.com/BlockchainCommons/Gordian-Developer-Community/discussions/108 [2/12]
Today’s Gordian Developer Meeting showcased key updates from Blockchain Commons, focusing on self-sovereign control and wallet interoperability. Let’s dive into the main takeaways: https://www.youtube.com/watch?v=EyYiwYpui5Q [1/12]
There was a brief discussion on a variety of other topics including a proposal from @FullyNoded for #nostr service discovery as an update to the QuickConnect spec, and we discussed how we might generalize it for other forms of discovery … https://github.com/Fonta1n3/nostrnode-macOS [7/12]
The most recent Gordian Envelope I-D adds a compressed data case, and the dCBOR I-D allows for null map entries. All reference implementations have been updated in line with these changes. https://blockchaincommons.github.io/WIPs-IETF-draft-deterministic-cbor/draft-mcnally-deterministic-cbor.html [6/12]
For these IETF drafts, we are renumbering some CBOR tags for the IANA application. It should not affect current apps, but if you are using some of the more recent tags, check out this update. In particular, use of any distributed function call tags. https://blockchaincommons.github.io/WIPs-IETF-draft-envelope/draft-mcnally-envelope.html [5/12]
If you are a wallet developer (not just cryptocurrency wallets, but also identity wallets) and care about resilience and interoperability, you should join the Gordian Developer Community. A variety of channels for discussion and announcements at: https://www.blockchaincommons.com/subscribe.html [11/12]
Our next monthly call will coincide with Silicon Salon 4, with topics such key exfiltration prevention w/ @Blockstream’s Andrew Poelstra, bigint in silicon w/ @lkcl, and discussion on open hardware requirements. https://www.eventbrite.com/e/silicon-salon-4-tickets-558196208887 [10/12]
After the main presentation [⏳54m47s], the last 1/2 hour had a lively discussion of topics like legacy bitcoin signing with QRs, support of BIP 85, key rotation for #nostr, and other interoperability topics. https://youtu.be/EyYiwYpui5Q?t=3287 [9/12]
There is now an open-source library from @Proxy with JavaCard implementation of the Gordian SSKR shared secret spec, ideal for constrained devices. This should allow for some interesting new functionality in NFC cards. https://github.com/proxyco/jc-sskr [8/12]
RT @lkcl: thx christopher for the opportunity. i’d like to have also presented about the Vectorised chacha20 algorithm we did (all 20 round…
RT @lkcl: nutshell: we’re proposing 3-in 2-out mul/div/shift ops that use one extra 64-bit reg as “carry-in carry-out”. SVP64 “magically” c…
RT @lkcl: @jon_trossbach @geofflangdale the only other ISAs i know of that have this type of “large” carry (more than 1 bit carry-in/out) a…
Replying to @lkcl, @jon_trossbach and @geofflangdale
ChaCha20Poly1305 is of interest as that is the baseline encryption used by Gordian Envelope, but there has been some concern about performance on constrained processors (especially since AES is often accelerated).
Replying to @lkcl, @jon_trossbach and @geofflangdale
But I agree that bigint is a more useful place to start. There was some discussion a few years ago about if some of the huge registers in some vector chips for video could be reused for cryptography. They were as large as a scan line (I think 1920 bits). But I never heard back.
Replying to @LizLum and @jasonhenrichs
Our web of trust design workshops work quite powerfully (11 so far). Just likely likely don’t scale past 100+ people. I believe it’s a Dunbar Number Problem.
I’m fascinated by the art & craft of collaboration. It is a central part of my life. In 2018 I co-authored a book on collaborative board games @MeeplesTogether. I’m in the final week of a #Kickstarter focused on what I’ve learned about collaborative play: https://twitter.com/DyversHands/status/1641713296192712705
Airgaps: By using QR codes to communicate with disconnected devices like hardware wallets, sensitive data (e.g., seeds, keys) are protected from most theft and hacking attempts. Security is greatly improved and exploits become less feasible. [3/10]
See Animated QRs in action and discover the problem they solve in this brief video: [2/10] https://www.youtube.com/watch?v=HsFF5HPKQIk
Animated QRs are one of Blockchain Commons’ first notable successes in our mission to enhance wallet interoperability. They have become essential for Bitcoin’s PSBTs (Partially Signed Bitcoin Transactions). 🧵… [1/10] https://www.blockchaincommons.com/devs/animated-qrs.html
The problem with QRs: Standard QRs have limited data capacity and large ones can become unreadable on consumer devices. Animated QRs solve this by transmitting several QR frames, enabling the conveyance of larger data sets like PSBTs. [5/10]
Why Airgap PSBTs? Airgaps complement PSBTs as they allow transactions to be created on internet-connected devices but signed on airgapped ones. With multisigs gaining popularity, PSBTs enable individual key holders to sign with their own choice of signing devices. [4/10]
Wallet Developers: Join the Gordian Developer list and Signal channel to stay updated on Blockchain Commons’ continued meetings and offerings in support of interoperability. [9/10]
https://www.blockchaincommons.com/subscribe.html
Read our Animated QR article for the full details on how Blockchain Commons’ Animated QRs enable airgapped wallets, and their future beyond just PSBTs [8/10]
https://www.blockchaincommons.com/devs/animated-qrs.html
Some other Bitcoin wallets that are now supporting our Animated QRs are: @bluewalletio @CasaHODL @DIYbitcoin @Blockstream @SeedSigner. More are being added regularly to this list in the Gordian Developer Community: https://github.com/blockchaincommons/gordian-developer-community#urs [7/10]
Wide Use: Blockchain Commons’ Animated QRs have already seen broad adoption in the Bitcoin wallet developer community, enabling reliable PSBT transmission via QR codes. Here are some of the key early adopters @FOUNDATIONdvcs @KeystoneWallet @SparrowWallet @FullyNoded [6/10]
Users: Demand support for interoperability in your wallets. Become a patron of Blockchain Commons to support this work to protect your digital assets’ safety and reliability! [10/10] https://github.com/sponsors/BlockchainCommons
Replying to @SeedSigner
It currently is on our road map, but not before Gordian Companion for collaborative seed recovery (SSKR Shamir shares this quarter). But the tools are very similar so not far behind it. Of course, more financial sponsors of @BlockchainComns asking for it will help.
RT @FOUNDATIONdvcs: Thankful for the work of @BlockchainComns around interoperable standards like these!
Foundation have been long term sp…
There are some very important decisions being made over the next year by the EU about the future of human-rights focused decentralized identity. Will every transaction have KYC vs. GDPR. LESS Identity vs Trust-Minimized. Be influential about these choices at… https://twitter.com/RWOTEvents/status/1646325438481072129
I’m frustrated by centralized control of DNS for decades & it’s only getting worse! 🤬“Either by design, or unintentionally, they’ve proposed allowing any government in the world to cancel, redirect, or transfer to their control applicable domain names!” https://freespeech.com/2023/04/19/red-alert-icann-and-verisign-proposal-would-allow-any-government-in-the-world-to-seize-domain-names/
RT @matthew_d_green: The EARN IT act is back. That means the US has joined the U.K., Europe and China in making an aggressive push to scan…
RT @AlecMuffett: New ‘magical thinking’ law puts everyone’s privacy at risk, warns Signal president
Bloody genius commentary from @mer__…
This is foundational work, but any foundation is ultimately based on an architecture, so we began publishing a new series of articles talking about what our architectural concepts are! [4/11] https://www.blockchaincommons.com/musings.html
We also saw great success in the legislative field, with Wyoming passing laws to both protect private keys and allow registration of digital assets. We hope that others will follow their models. [3/11] https://www.blockchaincommons.com/news/PrivateKeyWRDABills/
One of our more important advances was the introduction of dCBOR as an IETF Internet-Draft. This is deterministic CBOR, which is a requirement for our Gordian Envelope work. [2/11] https://datatracker.ietf.org/doc/draft-mcnally-deterministic-cbor/
At @BlockchainComns we’ve published our 2023-Q1 quarterly update on new developments so far this year, including foundational work, reference updates, reports on community adoption, further work with the community, and of course, a peek at plans for the rest of 2023. [1/11] https://twitter.com/BlockchainComns/status/1649510048861945860
Finally, we continued our community work with a new series of Developer Meetings https://github.com/BlockchainCommons/Gordian-Developer-Community/tree/master/meetings and with Silicon Salon 3. [8/11] https://www.SiliconSalon.info
We also celebrated the community adoption of specifications such as URs and Animated QRs and talked about the beginning of our work for standardization of projects such as Gordian Envelope and dCBOR. [7/11] https://www.blockchaincommons.com/devs/animated-qrs.html
There’s lots more in the report, including discussions of recent maintenance of our existing reference apps such as Spotbit. [6/11]
As one other bit of foundational work, Blockchain Commons also revamped its website to make it more easy to maintain. [5/11] https://www.blockchaincommons.com/
Become a sponsor to ensure that Blockchain Commons’ work on self-sovereign control of assets, decentralized digital identity, wallet interoperability, and more can continue! [11/11] https://github.com/sponsors/BlockchainCommons
Keep up-to-date with our work via our new announcement-only mailing list and our Developers Signal Channel. [10/11] https://www.blockchaincommons.com/subscribe.html
Take a look at the Q1 quarterly report for the full details of Blockchain Commons’ work this Winter. [9/11] https://www.blockchaincommons.com/quarterlies/Q1-2023/
Why are we discussing this in the Silicon Salon? As we design semiconductors for cryptographic use, we also need to make them trustless. This is one of a number of cryptographic techniques to verify that a chip doesn’t cheat. We need to standardize it. [4/8]
How to solve the problem? Andrew will talk about “anti-exfil”, in which a hardware wallet and host computer engage in a 2-round interactive protocol to produce a signature. [3/8] https://blog.blockstream.com/anti-exfil-stopping-key-exfiltration/
The problem is that if a hardware wallet doesn’t generate a nonce randomly, key leakage will occur! It can happen in as few as two signatures! Even worse, a compromised device could covertly do this without others knowing. [2/8] https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki#alternative-signing
We are thrilled to have Andrew Poelstra, Director of Research at @Blockstream, talking about the threat of key exfiltration from trusted devices at our upcoming Silicon Salon 4 (May 3rd 9am PDT). 🧵[1/8] https://www.eventbrite.com/e/silicon-salon-4-tickets-558196208887
Support these Salons and our goal of bridging the cryptographic, secure chip design, and wallet communities by becoming a GitHub sponsor of @BlockchainComns. [8/8] https://github.com/sponsors/BlockchainCommons
Silicon Salon is about the intersections between cryptography, semiconductor design, and secure hardware wallets. All of our presentations are afterward uploaded to our Silicon Salon website. [7/8] https://www.siliconsalon.info/salons/
We will also have presentations on open-source hardware challenges and on scalar and vector draft biginteger instructions for the Power ISA, with discussions of each. [6/8]
Sign up for Silicon Salon 4, which will run next Wednesday, May 3rd, starting at 9am PDT, to attend the presentation, and join in the conversation on the future requirements for chip transparency and open hardware. [5/8] https://www.eventbrite.com/e/silicon-salon-4-tickets-558196208887
RT @kanzure: Open source chips are the way forward.
Trust in our tech infrastructure goes beyond software. Enter the world of open silicon for cryptographic semiconductors – fostering innovation and security. Join us at the Silicon Salon to dive deep into the foundations of trust!🧵 [1/9] https://www.eventbrite.com/e/silicon-salon-4-tickets-558196208887
Kerckhoffs’ principle: a cryptographic system’s security should rely solely on secret key secrecy, not on algorithm or implementation obscurity. Open silicon adheres to this, promoting trust & robust security. [3/9] https://en.wikipedia.org/wiki/Kerckhoffs’s_principle
Open silicon offers enhanced chip security, improved physical security, efficient hardware bug resolution, reduced software bugs, and faster innovation. I talk about this in my latest “Musing of a Trust Architect” [2/9] https://www.blockchaincommons.com/musings/musings-open-silicon/
We will also have presentations from Andrew Poelstra of @Blockstream on preventing key exfiltration and from Luke Leighton @lkct & David Calderwood on scalar and vector draft biginteger instructions for the Power ISA, with discussions of each. [6/9]
Don’t miss next week’s Silicon Salon 4 featuring Mark Davis of @cramiumlabs on “Pitfalls and Approaches to Open Source Security Semiconductor” exploring open silicon’s history, challenges, and potential solutions. Let’s shape best practices together! [5/9]
Silicon Salon, hosted by @BlockchainComns, encourages cooperation and knowledge sharing among diverse stakeholders to drive open, secure cryptographic semiconductor development. Be part of the solution! Watch videos from previous events [4/9] https://www.siliconsalon.info/salons/
Silicon Salon 4 is on May 3rd, 9am PT. Reserve your virtual seat at this groundbreaking event and contribute to the future of cryptographic security.[8/9] https://www.eventbrite.com/e/silicon-salon-4-tickets-558196208887
To tackle these challenges, collaboration is key. Together, we can advance cryptographic security, foster innovation, and build a more secure, trustworthy tech infrastructure with open silicon. Let’s make it happen! [7/9]
Support @BlockchainComns to continue this crucial work, enhancing cryptographic security through events like the Silicon Salon. Become a Github Sponsor today! [9/9] http://github.com/sponsors/BlockchainCommons
Replying to @qlzqtMmiMi8fZxJ, @bitcoin__help, @notgrubles and @Blockstream
We have on the @BlockchainComns roadmap to do a QR verifier app. It would validate UR PSBTs and other common Airgap requests. More an issue of funding priorities. http://GitHub.com/sponsors/BlockchainCommons