Our third #SiliconSalon continued to reveal the future of cryptography leveraging semiconductors, and all are now available for your viewing! 🧵 [1/9] https://twitter.com/BlockchainComns/status/1620879378245902336
Replying to @ChristopherA
Dr. Sung Hyun Jo of @cramiumlabs, a manufacturer producing the next generation of security chips, focused their talk on their silicon expertise & talked about the requirements for a future with #MPC (Multi-Party Computation). [2/9] https://www.youtube.com/watch?v=r4PxckECvpo
Replying to @ChristopherA
Along with the videos, all of the slidedecks can also be found on the Silicon Salon III site. [6/9] https://www.siliconsalon.info/salon3/
Replying to @ChristopherA
We also had a lively discussion about hardware challenges, standards, collaboration, distributed key generation, and more. [5/9] https://www.siliconsalon.info/salon3/#additional-discussions
Replying to @ChristopherA
Finally, cryptographer Kavya Sreedhar from @Stanford’s VLSI Research Group (led by Mark Horowitz) presented “A Fast Large-Integer Extended GCD Algorithm” and offered related open-source semiconductor chip designs. [4/9] https://www.youtube.com/watch?v=liMA-8zmu1E
Replying to @ChristopherA
Andrew “bunnie” Huang of @bunniestudios offers a harrowing tale of how you can never quite know that all of your hardware is safe… but offers that there is a cost-benefit analysis. [3/9] https://www.youtube.com/watch?v=JMOWU6pFflw
Replying to @ChristopherA
You can also show your support of the efforts by @BlockchainComns to bring together an interdisciplinary community to define the future of security & privacy through leveraging cryptography on silicon by becoming a monthly sponsor via @github. [9/9] https://github.com/sponsors/BlockchainCommons
Replying to @ChristopherA
We are also seeking sponsors for these events! Demonstrate your company’s support for a future that includes better security through cryptography on chips! Mail us at team@blockchaincommons.com! [8/9]
Replying to @ChristopherA
We are seeking presenters for our next #SiliconSalon on May 3rd! Share your expertise on wallet hardware requirements & designs, open-source hardware & supply-chain security, and new semiconductor designs for secure cryptography or acceleration! [7/9] https://www.siliconsalon.info/contribute/
Replying to @pedrouid
Our CSR (Collaborative Seed Recovery) project is now adding Gordian Envelope to enable storage of critical metadata. Multiple wallet companies involved: See https://github.com/BlockchainCommons/Gordian/blob/master/CSR/README.md
Replying to @pedrouid
Here is a video playlist from our last couple of meetings.
https://www.youtube.com/playlist?list=PLCkrqxOY1Fbp-P1Yv-7gmu75i2QS2Z6vk
RT @mullvadnet: The proposed EU law Chat control will not only create a centralized mass surveillance system and violate people’s privacy.…
Replying to @cronokirby and @mayazi
In the Gordian wallet developers community we care a lot about interoperability at multiple levels in our architecture. For instance in Envelope, the base AEAD tag is for all AEAD variants, with the same ordering of elements. In MPC, we’d like…
Replying to @cronokirby and @mayazi
…to see data standards for storage of quorum shares no matter what cryptosystem the use. We’d to see well defined pre-final signature request with lessons from PSBT evolution, recovery & safe quorum partner contact metadata, etc. @jesseposner @chiselinc
RT @kanzure: @BrucePerens Wyoming started to do this for developers of digital asset software. I thought that was an interesting start. Mor…
RT @kanzure: @BrucePerens @ChristopherA It is mind-boggling to think about the comparative advantage a nation could have by adopting the en…
I am quite proud that the Wyoming Legislature has passed a bill prohibiting compelled disclosure of private keys—next step the Governor! I have been fighting for this since 2018. For context, see my article on this at: https://www.blockchaincommons.com/articles/Private-Key-Disclosure/ Thank you @rothfuss & @JaredSOlsen!
Replying to @cryptotothemoo1
For context about this bill see: https://www.blockchaincommons.com/articles/Private-Key-Disclosure/
Replying to @c3_trading
For context on this bill see: https://www.blockchaincommons.com/articles/Private-Key-Disclosure/
Replying to @Michael63140627
For context on this bill see: https://www.blockchaincommons.com/articles/Private-Key-Disclosure/
Replying to @CaitlinLong_, @rothfuss, @JaredSOlsen, @itsmikeyin and @GovernorGordon
For more context on this bill see: https://www.blockchaincommons.com/articles/Private-Key-Disclosure/
Replying to @PinkCowTokyo, @CaitlinLong_, @rothfuss, @JaredSOlsen, @itsmikeyin and @GovernorGordon
For more context on this bill (and answer to your question) see: https://www.blockchaincommons.com/articles/Private-Key-Disclosure/
Replying to @QuintenFrancois
For more context on this bill see: https://www.blockchaincommons.com/articles/Private-Key-Disclosure/
Replying to @Cointelegraph
For more context on this bill, see my article from last summer about it:
https://twitter.com/ChristopherA/status/1626243594364526592
Replying to @CoinDesk and @iamsandali
For more context on this bill prohibiting forced disclosure of private keys by Wyoming courts, see the article I wrote last summer advocating for it. The link is in:
https://twitter.com/ChristopherA/status/1626243594364526592
Replying to @BitcoinMagazine
For more context on this #Wyoming bill prohibiting forced disclosure of private keys by Wyoming courts, see the article I wrote last summer advocating for it in @BitcoinMagazine at https://bitcoinmagazine.com/legal/saving-bitcoin-private-keys-from-courts
Replying to @Coinzonestats
For more context on this bill prohibiting forced disclosure of private keys by #Wyoming courts, see the article I wrote last summer advocating for it. The link is in https://twitter.com/ChristopherA/status/1626243594364526592
Replying to @CryptoSavingExp
For more context on this bill prohibiting forced disclosure of private keys by #Wyoming courts, see the article I wrote last summer advocating for it. The link is in https://twitter.com/ChristopherA/status/1626243594364526592
Replying to @coincodecap
For more context on this bill prohibiting forced disclosure of private keys by #Wyoming courts, see the article I wrote last summer advocating for it. The link is in https://twitter.com/ChristopherA/status/1626243594364526592
Replying to @ChristopherA
You can see the details of the final bill “HB0086 - Disclosure of private cryptographic keys” at https://wyoleg.gov/Legislation/2023/HB0086
Replying to @dgwbirch, @rothfuss and @JaredSOlsen
Very broad! “a private key that relates to a digital asset, digital identity or other interest or right”.
Full text at https://wyoleg.gov/Legislation/2023/HB0086
Replying to @dgwbirch, @rothfuss and @JaredSOlsen
Also, last year Wyoming passed a digital identity bill that is also fairly broad, which goes beyond property rights but also supports principal authority under agency law. https://wyoleg.gov/Legislation/2022/HB0070 — I’ve an article on context about it at https://www.blockchaincommons.com/articles/Principal-Authority/
Replying to @21KandNoMore, @CaitlinLong_, @rothfuss, @JaredSOlsen, @itsmikeyin and @GovernorGordon
If you can provide a public key to the court, I don’t believe there are any exceptions. The key problem the bill is trying to solve is that there is no safe way to share a private key.
Replying to @dgwbirch, @rothfuss and @JaredSOlsen
This bill is focused on private keys, i.e. “relates to a digital asset, digital identity or other interest or right”. There is another law that defines digital asset private keys at https://www.wyoleg.gov/Legislation/2019/sf0125
Replying to @dgwbirch, @rothfuss and @JaredSOlsen
As far as private keys for digital identity, it is defined under another Wyoming law at: https://wyoleg.gov/Legislation/2022/HB0070
Replying to @dgwbirch, @rothfuss and @JaredSOlsen
IANAL, but neither really applies to your encrypted data. A court can still request access as they can today. You still have recourse today to try to deny that legal access, but I don’t believe through this law.
Replying to @randomnonameguy, @CorgiWontons and @Cointelegraph
More context on courts ability to demand private keys: https://www.blockchaincommons.com/articles/Private-Key-Disclosure/
@CryptoShraddha Regarding your Wyoming Private Key article, there is more context in my 🧵at https://twitter.com/ChristopherA/status/1626243594364526592 and article at https://www.blockchaincommons.com/articles/Private-Key-Disclosure/
RT @rothfuss: Thank you @ChristopherA for all of your work with the Select Committee on this topic! It took a few years…
Now let’s get b…
Replying to @ChristopherA
Developers unfamiliar with CBOR may want to read our “Why CBOR?” article, which talks about its advantages such as conciseness, full extensibility, self description, and ease of use in constrained and streaming environment. [3/8] https://www.blockchaincommons.com/introduction/Why-CBOR/
Replying to @ChristopherA
Developers already utilizing CBOR should take a look, as this is a supported library with a focus on cryptographic use cases, as it is one of the few (or only) to concentrate on the deterministic flavor of CBOR. [2/8]
dCBOR (deterministic CBOR) is now available for Rust & Swift in a new codec library from @Blockchaincomns. Here’s our announcement with all the links. [1/8] https://github.com/orgs/BlockchainCommons/discussions/184
Replying to @ChristopherA
We’ve been developing CBOR in part as a foundation for other projects such as Gordian Envelope, but we hope our work on CBOR itself is of use to everyone! [7/8] https://www.blockchaincommons.com/introduction/Envelope-Intro/
Replying to @ChristopherA
We’d also love to get your CBOR samples for use in demonstrations and examples, particularly identity and cryptography-related samples such as mDL/mDOC and COSE data. [6/8]
Replying to @ChristopherA
We’d love to get comments on our libraries. Do they work for you? Are they intuitive? Did you run into any problems? What do you think of the API? How about the Rust idioms (if using Rust)? Are there code security tools that you’d like to see added? [5/8] https://github.com/orgs/BlockchainCommons/discussions/184
Replying to @ChristopherA
We focused not just on CBOR, but the deterministic variant because it was crucial for our needs to produce repeatable hashes for complex objects. We suspect other developers will have other use cases where determinism is important. [4/8]
Replying to @ChristopherA
Please become a monthly sponsor of Blockchain Commons via @GitHub to ensure that we can continue these efforts that offer open source code for important security specifications & wallet interoperability! [8/8] https://github.com/sponsors/BlockchainCommons
Replying to @sashahodler
Replying to @wsfoxley
Replying to @adriancs23 and @wsfoxley
We also are working towards a Wyoming Registered Digital Asset. https://wyoleg.gov/Legislation/2023/SF0076
Replying to @adriancs23 and @wsfoxley
My testimony on this: https://wyoleg.gov/InterimCommittee/2022/S19-2022061408-02DigitalAssetsandWRDA.pdf
Replying to @adriancs23 and @wsfoxley
And slides: https://wyoleg.gov/InterimCommittee/2022/S19-2022061408-03WyomingWRDASlides.pdf
Replying to @mybenxtime and @btc
Some context: https://twitter.com/ChristopherA/status/1626243594364526592
Replying to @markfidelman
Some context: https://twitter.com/ChristopherA/status/1626243594364526592
Replying to @dgwbirch, @rothfuss and @JaredSOlsen
We also are working towards a Wyoming Registered Digital Asset. Proposed Bill https://wyoleg.gov/Legislation/2023/SF0076
Replying to @dgwbirch, @rothfuss and @JaredSOlsen
My testimony and slides: https://wyoleg.gov/InterimCommittee/2022/S19-2022061408-02DigitalAssetsandWRDA.pdf https://wyoleg.gov/InterimCommittee/2022/S19-2022061408-03WyomingWRDASlides.pdf
Replying to @markfidelman
Related: https://twitter.com/ChristopherA/status/1626739597576409089
Replying to @RepKeithAmmon and @BtcCasey
Some context: https://twitter.com/ChristopherA/status/1626243594364526592
Replying to @RepKeithAmmon and @BtcCasey
Is your state interested this? Or last year’s Digital Identity law, or the Wyoming Registered Digital Bill in progress? See my thread.
I’m frustrated that politicians & regulators are “conflated our non-leveraged, 100-percent liquid and solvent bank with FTX”. I worked hard to help #Wyoming avoid the kind of fraud that ultimately happened, but instead we are getting no federal support for best practices. https://twitter.com/CaitlinLong_/status/1626661344316473346
Replying to @wsfoxley
Also related is last year’s Digital Identity law, and a Wyoming Registered Digital Asset. See 🧵: https://twitter.com/ChristopherA/status/1626252393431334912
Replying to @dgwbirch, @rothfuss and @JaredSOlsen
If you like this type of smart foundational advocacy, support Blockchain Commons by becoming a monthly sponsor at https://github.com/sponsors/BlockchainCommons
Replying to @OR13b and @danbri
I believe it can be done, but my +0.75 vote was because I’m not sure.
Replying to @OR13b
We’d love to show you #Gordian Envelope sometime.
Replying to @raw_avocado
The most important patent needed to expire for Bitcoin to exist was the Haber Time Stamp https://patents.google.com/patent/US5136647A/en held by Surety. Required for anyone using a hash tree pre-2008. I tried to get a license for it at Certicom for a micro-currency in 99 but they wanted a 5% royalty.
🤔First sovereign with self-sovereign identity.
#bhutan #prince #ssi h/t @manusporny & ganesh
Latest #RebootingWebOfTrust collaboration, led by Phillip Long w/ @codenamedmitri & Golda Velez: “We propose a minimal format for connecting (and optionally cryptographically binding) credentials that will allow each use of third-party assertions to be represented as a set of… https://twitter.com/RWOTEvents/status/1630281887112638464
Replying to @ChristopherA
Our Collaborative Seed Recovery (CSR) video playlist contains our first several meetings from last Fall. [3/5] https://www.youtube.com/playlist?list=PLCkrqxOY1Fbp-P1Yv-7gmu75i2QS2Z6vk
Replying to @ChristopherA
Past meetings have brought together principals such as @Proxy @AutonomyWallet @crossbarinc @FOUNDATIONdvcs @SparrowWallet and many others! Details to join in tomorrow are in our post in the Gordian Developer Discussions area: https://github.com/BlockchainCommons/Gordian-Developer-Community/discussions/104 [2/5]
Tomorrow 3/1 4pm PT, @BlockchainComns is holding our first #GordianDevelopers meeting of the year. These meetings bring together the blockchain, digital asset, and digital identity communities to talk about open, interoperable, secure, and compassionate infrastructure. [1/5]
Replying to @ChristopherA
If the creation of open, interoperable, secure, and compassionate infrastructure is important to you, please also become a Blockchain Commons financial sponsor via GitHub: [5/5] https://github.com/sponsors/BlockchainCommons
Replying to @ChristopherA
If you’d like to receive more info on Gordian Developer meetings and their interoperable specification for wallets and infrastructure, you can join us in our Signal group or via a low-noise announcements list. [4/5] https://www.blockchaincommons.com/subscribe.html#gordian-developers