RT @timpastoor: If you create positions of power, you attract those with money able to corrupt said power. If you want to solve for governm…
RT @ChristopherA: Once again, to raise funds in support of our future open & trust-minimized Self-Sovereign Identity #SSI projects at @Bloc…
Replying to @DropYourNFT
RT @zallarak: I met @ChristopherA years ago at a Bitcoin dinner in SF. He spoke about board games and how to teach children. Only at the en…
Replying to @zallarak
Security of BGP routes is still one of my bigger infrastructure concerns. It is an interesting problem to me as it is essentially a P2P web-of-trust problem. However, I’ve made no progress on it. Bill Woodcock @woodyatpch & @TheBlueMatt likely both know more on current status.
Replying to @zallarak, @woodyatpch and @TheBlueMatt
For an overview on BGP https://www.cloudflare.com/learning/security/glossary/what-is-bgp/
Replying to @zallarak, @woodyatpch and @TheBlueMatt
For an overview of the security problem: https://www.packetlabs.net/bgp-security/
Replying to @zallarak, @woodyatpch and @TheBlueMatt
IMHO, a key challenge to solving the BGP problem is that the stakeholders are uncomfortable with moving forward on suggested solutions that are CA (certificate authority) based and thus centralized, but are too conservative to invest in more decentralized solutions. Stalemate.
Replying to @zallarak, @woodyatpch and @TheBlueMatt
RT @ChristopherA: @zallarak @woodyatpch @TheBlueMatt IMHO, a key challenge to solving the BGP problem is that the stakeholders are uncomfor…
RT @woodyatpch: @ChristopherA @zallarak @TheBlueMatt Yeah, that’s exactly right. RPKI, the notional fix, is a hammer looking for a centrall…
Replying to @ricburton
We have a number of swift native libraries at https://GitHub.com/BlockchainCommons, but our core cryptographic libraries are still largely wrappers of the venerable & well vetted secp256k1 code base in C
Excellent high-level view by @woodyatpch about the real source of yesterday’s Facebook BGP problems: monoculture, inertia, lack of innovation. I’d probably add that many of these are also caused by lack of funding for infrastructure and its commons. https://twitter.com/woodyatpch/status/1445359437380669447
RT @woodyatpch: @markrprior I very much agree that simple building-blocks, that fit together flexibly and modularly, are best. I am eternal…
But our sale of this NFT is more than that! At Blockchain Commons @BlockchainComns we are focused on identifying and solving underlying fundamental problems of blockchain infrastructure & security. [3/12]
I hope that you’ll bid on the piece to uphold our creation of an open self-sovereign identity (#SSI) infrastructure that is decentralized, trust-minimized, platform-neutral, blockchain-neutral, and vendor-independent. [2/12]
Blockchain Commons is currently auctioning its second NFT, Identimancer #1, created by 88B88:X8IB @voodoovoid17, to support our continued work on self-sovereign identity. [1/12] https://opensea.io/assets/0x495f947276749ce646f68ac8c248420045cb7b5e/23329406590917769582697114686361498707644446075778430145570703786260194918401/
Beyond that, most Ethereum transactions are conducted through a browser plugin that uses javascript. That can make your single key even more vulnerable. You could be compromised through your wallet or because you’re transacting from an internet-connected computer. [6/12]
Right now Ethereum assets are very vulnerable. To start with, Ethereum is focused on a model of one seed generating one hot private key. That key does everything, holding your NFTs, sending funds, and authorizing contract use. It’s a Single Point of Failure AND Compromise. [5/12]
Identimancer #1 and future sales from the #SSI NFT collection represent Blockchain Commons’ entry into the world of #Ethereum, where I hope to demonstrate some of our same principles of self-sovereign #SmartCustody & responsible key management that I pioneered for Bitcoin. [4/12]
We’d like to similarly encourage responsible key management on #Ethereum, though there are real challenges such as the very high cost of smart-contract based multisigs, which creates a requirement for alternative solutions. [9/12]
To date, Blockchain Commons has worked with the #Bitcoin wallet community to address similar problems on the elder side of blockchain cryptocurrency, with airgapped wallets, partitioned services, and our Gordian principles of independence, privacy, resilience & openness. [8/12]
Meanwhile, approval UXes are non-standard and non-intuitive. It’s way too easy to use something like a token drop as a cover to trick someone into providing enough authorization to steal their funds. https://www.bsc.news/post/airdrop-scams-continue-to-surface-on-layer-1-defi-networks [7/12]
Also consider becoming a monthly sponsor of Blockchain Commons, to support our continued work on specifications that help everyone. Or try out the new #TwitterTips! [12/12] ៚ https://github.com/sponsors/BlockchainCommons
If you’re an artist interested in contributing a self-sovereign themed NFT for a future auction, please also drop me a line! Thank you for your support of Blockchain Commons and our newest work on responsible key management for Ethereum! [11/12]
Bidding on the Identimancer #1 NFT will signal that you’d like to see Blockchain Commons supporting ways to improve the safety of Ethereum assets. Help us to bring our lessons learned to a second cryptocurrency! [10/12] https://opensea.io/assets/0x495f947276749ce646f68ac8c248420045cb7b5e/23329406590917769582697114686361498707644446075778430145570703786260194918401/
A nice breakdown of how the randomness required for good private keys is accomplished in Bitcoin Core. I consider this to be the minimum best practice for software generated keys, but presumes no side-channel or compromise of your hardware or software. Addressing those is harder. https://twitter.com/raw_avocado/status/1445024873382809604
RT @trentmc0: NFT art with a self-sovereign identity twists, by one of the pioneers of SSI. 🧙♂️
RT @ChristopherA: Blockchain Commons is currently auctioning its second NFT, Identimancer #1, created by 88B88:X8IB @voodoovoid17, to suppo…
RT @ChristopherA: Identimancer #1 and future sales from the #SSI NFT collection represent Blockchain Commons’ entry into the world of #Ethe…
RT @ChristopherA: Latest update to Gordian SeedTool for iOS & Mac from @BlockchainCmns offers our first support for Ethereum, expanding our…
Replying to @opensea
Replying to @levikornelsen
Solstice & equinox days are easy to plan for. However, the cross quarter days are off as much as a week from the traditional calendar. Thus the real Samhain is November 6-7, not October 31. https://www.archaeoastronomy.com/2021.html
If you are an NFT creator on http://Foundation.app you can support our #SSI & #SmartCustody efforts by voting for us in the Community Upvote 🌐 @withFND at https://foundation.app/@ChristopherA
The curated collection on @OpenSea of our last two NFTs that were auctioned off to support Self-Sovereign Identity #SSI is at: https://opensea.io/collection/ssi
RT @ChristopherA: Noah’s Law “Any conversation about decentralization eventually evolves into a conversation about reputation.” @noahthorp…
👍🏼“The browser has become the single biggest point of centralization on today’s Web.” https://www.evernym.com/blog/w3c-vision-of-decentralization/
I’m seeking more pithy & evocative short “poster” phrases associated with self-sovereignty & #SSI beyond the classic “not your keys, not your coins”. Examples: “my keys, my authority”, “don’t shackle yourself”, “our internet, not facebook’s”, “embrace digital resilience”. Ideas?
Replying to @La__Cuen
I’ve been trying hard to find a good one for over a year. Particularly a difficult issue if you earn & spend or otherwise actively use cryptocurrency without using exchanges. The zenledger etc. all use exchange API. Seriously considering funding to create a small service company.
RT @AlecMuffett: 1/ THE MOST IMPORTANT information security discussion of the day will be about the publication of #BugsInOurPockets, a pap…
Replying to @dustyweb
So when can I do native Schnorr typed variables so I can do cryptographic ocap?
Replying to @JWWeatherman_
I am uncomfortable with all of the current drive chain proposals, but I do believe a drive chain could be plausible, but is harder than their proponents believe. @BlockchainComns did a review of one proposal but they didn’t really want to hear our suggestions. Nothing since.
Replying to @dustyweb
The best libraries are the secp256k1 used by bitcoin, or the slightly more advanced fork secp256k1-zkp which has some more advanced features like range proofs. One thing I like about latest bitcoin schnorr is it is always 32 bytes, as are private & public keys.
RT @accessnow: This Thursday at 9am ET ✨ SAVE THE DATE!
Join @NorwayUN, @svaradarajan, @AgnesCallamard, @MaryLawlorhrds, @solomonbrett and…
RT @torproject: Privacy isn’t about hiding bad things. It’s about protecting what makes us humans: our day-to-day behavior, our personality…
Privacy is not just about security or avoiding monetary loss. We act differently when we’re being watched, so privacy is also about the “right to be yourself”. Related is a contextual “right to be understood”, as a private moment taken out of context can easily be misinterpreted. https://twitter.com/torproject/status/1450488158416687107
This is an interesting legal approach — I do believe that communities should be able to have have legal standing without having to be registered corporate “citizens”. I suspect in the end that communities not having legal “personhood” like natural persons & corps will kill it. https://twitter.com/doctorow/status/1450852890638118912
This is why @BlockchainComns asks for signed CLAs from all of our code contributors. I wish we didn’t have to, but to have ability to enforce our open source & patent licenses requires us to have legal standing. We have lost some volunteers because of our strict CLA requirement. https://twitter.com/doctorow/status/1450852885638500353
Truth. The best cryptographers & cryptographic engineers I’ve worked with start with serious doubts about their own work, and then have others assist with thorough review before changing that belief. Even then, doubts remain. Nothing is perfect. https://twitter.com/robot__dreams/status/1451578632128716803
RT @InvestWithDiego: UK Court Will Let Craig Wright Serve Claims Against 16 Bitcoin Developers https://www.coindesk.com/markets/2021/05/12/uk-court-will-let-craig-wright-serve-claims-against-16-bitcoin-developers/ https://t.co/mflVoUm…
“New contributors should join anonymously (it’s tricky).” It is tricky! At @BlockchainComns we have been working toward a guide for pseudonymous developers. An early work in progress but useful. Contributors welcome: https://github.com/BlockchainCommons/Pseudonymity-Guide https://twitter.com/jonasschnelli/status/1451268523616051201
Replying to @cmdoerfler and @gulovsen
For next version I’d like to add more examples on risk modeling / adversary analysis, in particular as regards to developers of crypto code vs human-rights activists. You can see our general approach to risk/adversary in free our #SmartCustody book. /cc @namcios https://twitter.com/ChristopherA/status/1451607614974935041
RT @songpinganq: This is Chinese qr code vaccine passport system. It includes your name photo age family members address employer, whether…
Replying to @cmdoerfler, @gulovsen and @namcios
When I personally advise those considering pseudonym, the first part is diving into their threat/adversary model. It is more expensive in time, care & resources to defend against a state actor for human-rights work vs defend against civil lawsuits, trolls & SWATers for crypto.
RT @ChristopherA: @cmdoerfler @gulovsen @namcios When I personally advise those considering pseudonym, the first part is diving into their…
Replying to @cmdoerfler, @namcios and @gulovsen
Hard to do well solely in Twitter. Here is a large tweetstorm on #SmartCustody Adversaries. A similar analysis of risk modeling & adversaries is what we are striving for: https://twitter.com/ChristopherA/status/1267560491657728000
Replying to @cmdoerfler, @namcios and @gulovsen
We definitely need to curate best practices a lot more. One of the biggest threats to pseudonymity is Process Fatigue. Here, perfection is clearly the enemy of the good. https://twitter.com/ChristopherA/status/1280954188063596544
RT @ChristopherA: @cmdoerfler @namcios @gulovsen We definitely need to curate best practices a lot more. One of the biggest threats to pseu…
RT @namcios: @cmdoerfler @ChristopherA @gulovsen Next version of Pseudonymity-Guide in the works - will include better walkthrough of topic…
RT @namcios: @cmdoerfler @ChristopherA @gulovsen Focus currently on human rights activists seeking to guard from medium not high profile ac…
Replying to @cmdoerfler, @namcios and @gulovsen
Our work was funded by volunteers, and some financial support from our GitHub Sponsors and Patrons like @hrf. Thus current early draft of our guide has an emphasis on activists, but wd plan to later be more specific for devs. This also includes things like how to do the work.
Replying to @cmdoerfler, @namcios, @gulovsen and @HRF
We are also working toward some long term projects to support developers at risk, including understanding requirements. For instance, here is the Amira User Engagement Model, for a hypothetical future activist dev: https://w3c-ccg.github.io/amira/
I have real reservations about wallets being built into browsers. At minimum there should be isolation between the functions of request vs signing transactions, which Wallet Connect supports. I also suggest segregation of keys for auth, which is not the current practice in ETH. https://twitter.com/ricburton/status/1451357816535486501
Though biometric tech will have a role in the future of digital identity, it also has huge risks. 👎🏻 #aadhar #worldcoin, 👍 Apple’s TouchID. I was disappointed that #RWOT draft on best practices led by @johnrcallahan never shipped—it was a good start: https://github.com/WebOfTrustInfo/rwot6-santabarbara/blob/master/draft-documents/Biometrics.md https://twitter.com/jamie247/status/1452260428659167232
If someone from the original paper, or has participated in #RWOT wants to take over lead on this draft paper to update & finish it, let us know.
Replying to @ineiti and @SarahJamieLewis
Agreed, but with qualifications. First some terms: I don’t consider what you are calling global PoP, instead it is PoP in a context (which in addition to anti-sybil needs a safe proof of inclusion zkp). …
Replying to @ineiti and @SarahJamieLewis
But even if you have that, there are still other risks, particularly around the proof of inclusion. For instance there is the “Clark Kent” risk: you loose your job unless prove you are not a member of a group (in Clark’s case, a group that includes Superman). There are more.
Replying to @ineiti and @SarahJamieLewis
I’m not saying that working toward some type of “proof of unique personhood in a group context” isn’t incredibly valuable, but I’m suggesting be humble and realize it will not be easy and you are unlikely to mitigate or even spot all the risks. Most PoP teams don’t seem to yet.
Replying to @ineiti and @SarahJamieLewis
I am, in particular, very concerned about some current global proof of personhood projects, in particular those that require or allow correlation (linkage) to real world identities. When largely 1st-world cis white males are are willing to risk privacy to show status, be scared.
Replying to @ineiti and @SarahJamieLewis
I commend you to read @SarahJamieLewis’s collection on Queer Privacy. It is pay-what-you want, but I hope you offer something. Her editorial role in this community to be safer is important. https://leanpub.com/queerprivacy
See also: https://twitter.com/ChristopherA/status/1452345201360400384
The Lightning Wallet @MuunWallet has failed my #SmartCustody test, and I am unable to recover test funds. Many fragile points: confusing & non-standard recovery process, no mnemonics, logs you out of old device before new device success, too many fragile parts, and more.👎 …
There is also some security theatre here for a kind of wallet that usually has smaller amounts of funds, which combined with their attempts to make some parts easier, the combo fails. …
So easy to mess up. The critical part of the recovery is a password and backup hex, also requiring backup. However, they do not support keychain or other secure places to store, nor do they do a health check on either to do so. Then when you try multiple times, log you out. …
Recover requires a working email. I saved the recovery keys but didn’t properly save the password or hex also required. If your old wallet is working, when you try to authorize a new wallet, they log you out of your first wallet before confirming new wallet is recovered. …
They clearly were trying to fix some pain points in the Lightning recovery, but ended adding more. You have to remember a recovery password, or you have write down non-standard hex not mnemonics. They will mail you or save PDF with keys but they are encrypted & thus fragile. …
I suggest a good place for further discussion is in the Airgap Wallet Community https://github.com/BlockchainCommons/Airgapped-Wallet-Community/discussions/
I urge all the Lightning Wallet companies to work harder on standardization of recovery processes. Each will have have unique tradeoffs due to different architectures, but much is the same. I also suggest leveraging appropriate platform tech (for instance iCloud) or use QRs. …
To be clear, recovery of a Lightning wallet is much harder than Bitcoin, but every step in the @Muun recovery process is new & non-standard. I had no problems restoring @bluewalletio or @Breez_Tech which aren’t perfect but not nearly as fragile. …
Just tested migration of @PhoenixWallet & @get_zion Lightning Wallets. Both were easy & functional, though I have questions for long-term vendor independence. So far only @MuunWallet has failed.
When I was Principal Architect at @Blockstream, I was a big advocate for Chaumian-style federated solutions over the Liquid federation. Given that I did some work with David Chaum in early ‘90s, I am biased. I’m glad to see the concept move forward to implementing by @EricSerion! https://twitter.com/Blockstream/status/1453099343301517316
Replying to @getsqt and @Blockstream
Yes, it is kind of L2. A Chaumian bank’s weakness is that the bank was centralized. Instead with bitcoin it is possible to create a federation that is the “centralized” part of the bank. Not totally trustless as Liquid is not totally trustleess, but has some good properties.
Note that in the past Adobe’s tech largely relied on centralized certificates. If they fully support you to choose a root of trust such that anyone can issue claims and verify, which is possible with (but not required by) Verifiable Credentials & DIDs, I’ll be less skeptical. https://twitter.com/beaniemaxi/status/1453174086578970627
Replying to @beaniemaxi
Replying to @NathanHeadPhoto
Replying to @JWWeatherman_, @getsqt and @Blockstream
Certainly the bank federation as a whole can do a proof-of-reserves, and they, in turn, know how many Chaumian tokens they have issued and are redeemable. But I don’t know of a way for an individual with Chaumian tokens to be offer a proof-of-reserves other than by spending them.
This new 1.0.0 release is fully integrated with Bitcoin Core 22.0, the newest bitcoin release, and works with this week’s release of macOS Monterey 12.0.1 and is tested all the way back to macOS Catalina 10.15.7. [3/11]
The goal of Gordian Server is to make Bitcoin easy and accessible. It does that by automatically installing a full Bitcoin Core server on your Mac, and providing you with an accessible UI for using it. [2/11] https://github.com/BlockchainCommons/GordianServer-macOS
Many people are assembling Rasberry Pi class devices as full nodes. Yet there exists a huge number of old Macs out there that can still serve. We’ve recently released the Gordian Server for Mac in its first feature-complete free version as v1.0.0. [1/11] https://github.com/BlockchainCommons/GordianServer-macOS/releases/tag/v1.0.0
You can always compile our reference code on your own using xCode, but if you prefer, you can also grab a DMG that should work on any up-to-date macOS Catalina compatible or newer Mac hardware. [7/11] https://github.com/BlockchainCommons/GordianServer-macOS/releases/tag/v1.0.0
Finally, we’ve worked hard on improving the stability and monitoring the status of your bitcoin full node, through reboots, restarts, and other changes. [6/11]
Want to choose your own location for your blocks or data directory on another disk? Want to set up or harden your environment for secure development? Use other Mac Apps locally or take our Learning Bitcoin course? These unique optional setups are now possible as well. [5/11]
In addition, Gordian Server integrates the latest Tor v3 support, allowing for correlation-resistant privacy. No one in your cafe needs to know you have bitcoin. Moreover, we’ve improved Gordian Server’s cross-compatibility options, standard RPC ports, and much more. [4/11]
In particular, I like my old 13” mid-2012 Macbook Air—it has USB-3 & firewire, 4-8 GB RAM & up to 1TB SSD if you want a tx-indexed full node. Not only can it run Catalina, I can run Debian and TailsOS for even more secure environments. It is my great travel burner laptop. [9/11]
Got a computer that doesn’t officially support Catalina? We’ve had good luck with the Catalina Patcher on old cheap (<$100) Mac Minis & iMacs going back to 2008! But use at your own risk. [8/11] http://dosdude1.com/catalina/
If you find this sort of utility useful and would like to see more, please become a supporter of Blockchain Commons. We’re creating reference applications for use by anyone, and working with other blockchain companies to encourage compatibility.៚ [11/11] https://github.com/sponsors/BlockchainCommons
For me, it is nice to have a full node available on my personal laptop with Bitcoin Core keeping an eye on my watch-only accounts, and I can use keys from Gordian Wallet or @FullyNoded iOS apps wherever I am in the world, as long as my laptop is on the internet. [10/11]
Bitcoin Standup was one of Blockchain Commons’ earliest projects — it was a set of Bitcoin scripts that could be used to easily set up a secure Debian server VPS running Bitcoin. [2/10]
Yesterday we released Gordian Server, our Bitcoin & Tor installer for the Macintosh. In addition to this release, we continue to support Debian Linux systems and virtual machines with an update to our Bitcoin Standup Scripts. [1/10] https://github.com/BlockchainCommons/Bitcoin-Standup-Scripts https://twitter.com/ChristopherA/status/1453653837978365958
The second is integration with Cypherpunkpay, which allows you to optionally install an engine for accepting Bitcoin payments through your Tor service and/or website. [6/10] https://cypherpunkpay.org/
The first is integration with Bitcoin Core 22.0, which required updating to their new methodology for release signing. Now you’ll know you’re using the most up-to-date Bitcoin Core, with access to i2p, taproot, and more. [5/10] https://bitcoincore.org/en/releases/22.0/
We’ve just released a new 0.8.0 version of the our Bitcoin Standup scripts with two great new features. [4/10] https://github.com/BlockchainCommons/Bitcoin-Standup-Scripts/releases/tag/v0.8.0
Bitcoin Standup is popular with students and interns taking our “Learning Bitcoin From the Command Line Course” as they could set up an inexpensive VPS server and do their coursework anywhere in the world [3/10] https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line
As always, you can run these install programs as a VPS Stackscript from Linode or directly from the command-line for a Linux system. We’re also working on a major new release for Gordian Server, our integrated Mac installation software, also with more plugins. [9/10]
We expect there to be more optional integrations like this in the future, giving you the ability to install a variety of Bitcoin and Lightning applications. We are currently testing c-lightning, esplora, and electrum server. [8/10]
The Cypherpunkpay work was supported by a grant from the @HRF, who was looking for ways to better support activists. This is a small first step. [7/10] https://hrf.org/
If you’d like to support this type of work, intended to make Bitcoin more accessible to everyone, please consider becoming a patron of Blockchain Commons. ៚ [10/10] https://github.com/sponsors/BlockchainCommons
Replying to @La__Cuen
It has been frustrating to try get support from Coinbase for activities like #SmartCustody, #RebootingWebOfTrust & @BlockchainComns. No success yet.
Moving more of our critical infrastructure over to Rust and supporting real security reviews and where possible formal verification is important. Tor is one of those pieces. Architecture is important too—for instance Tor hot keys worries me, I would prefer OS or hardware support. https://twitter.com/nickm_tor/status/1454131220208627726
RT @dannyryan: @josephdelong Make it a social norm for all DAOs (and other network tokens) building on Ethereum to allocate 1.5% of their t…
RT @windley: It’s telling that Facebook didn’t decide to build the metaverse as a true metasystem with standards, protocols, and open acces…
Another season has gone by, so Blockchain Commons has released another quarterly report. Happily it was another busy quarter, with lots of new contributions to the blockchain community. [1/11] https://www.blockchaincommons.com/quarterlies/Q3-2021-Report/
That wasn’t our only release. Not only did our Bitcoin Standup scripts get updated to Bitcoin Core 22.0, but we also published our Feature-Complete version of Gordian Server. [5/11] https://github.com/BlockchainCommons/GordianServer-macOS/releases/tag/v1.0.0
Another big task was our iteration through a few new versions of Gordian SeedTool, our reference app for resilient and interoperable cryptographic seed storage. [4/11] https://github.com/BlockchainCommons/GordianSeedTool-iOS/blob/master/Docs/MANUAL.md
We haven’t stopped working on new libraries, including a port of a more efficient QR generator for Swift. [3/11] https://github.com/blockchaincommons/QRCodeGenerator
The big news is that we got our first external security review completed, and thus we now consider our Shamir and SSKR libraries production ready, thanks to help from Radically Open Security @ROSecurity. [2/11] https://github.com/BlockchainCommons/bc-sskr/blob/master/SECURITY-REVIEW.md
…and Spanish! [7/11] https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/tree/spanish-translation/es
We also saw major updates for our Learning Bitcoin from the Command Line course, in the form of translations to both Portuguese …[6/11] https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/tree/portuguese-translation/pt
If you like what we’re doing, and especially if you’re interoperating with our specifications, please become a supporter of Blockchain Commons by tipping us here on Twitter, or monthly through GitHub! [11/11] https://github.com/sponsors/BlockchainCommons
There was lots more this season, including DID support, testimony on Wyoming eResidency, expansion into the Ethereum space, and the successful conclusion of our second intern program. It’s all in our report! [10/11] https://www.blockchaincommons.com/quarterlies/Q3-2021-Report/
Some of our documentary work is more future looking, such as our new paper on Principal Authority (new under #Wyoming law), and how it links up with self-sovereign identity. [9/11] https://www.blockchaincommons.com/articles/Principal-Authority/
We’ve new articles too, including some SSKR docs for power users, discussing when to use various Shamir sharding scenarios, and why sharding seeds can be dangerous! [8/11] https://github.com/BlockchainCommons/crypto-commons/blob/master/Docs/sskr-overview.md#for-power-users
Replying to @RealSexyCyborg
At @BlockchainComns we have a virtual internship program with over a dozen. Most are we’re not 1st world but many now have good jobs in the community. We also have Spanish & Portuguese version now of our Learning Bitcoin. We are working on guides for pseudonymous development. …
Replying to @RealSexyCyborg and @BlockchainComns
…we are a small, benefit corp, supporting secure open infrastructure, but trying hard to think globally. What else should we be doing?
RT @TimSweeneyEpic: If the government forces founders to sell out to pay taxes on theoretical gains as companies grow, they’re handing cont…
Replying to @ai
We’ve been working hard on an open infrastructure for wallets to be able to do this. We have a really excellent multisig design for Bitcoin with no single points of attack, failure, collusion and even has some time-failure modes. However, it has much more difficult in Ethereum.
Replying to @ai
Replying to @ai
Replying to @ai
In particular see “Designing Multisig for Independence & Resilience” Advanced Multisig section: https://github.com/BlockchainCommons/SmartCustody/blob/master/Docs/Multisig.md#examples-advanced-multisig
RT @darrello: “A DIF & ToIP joint Statement of Support for Decentralized Identifiers (DIDs) v1.0 as a W3C Standard” by Decentralized Identi…
The first startup I founded went bankrupt. A fellow founder encouraged me to move on by saying “Now you are a real entrepreneur. Get started.” It is true — I became a better entrepreneur because of it. Other fields (in this case law exams) have similar tough failures that teach. https://twitter.com/EHA_appeals/status/1454305365198180352
RT @trbouma: I always wondered if the date chosen to publish the #Bitcoin White Paper (Oct 31) was actually a coincidence with #Reformation…
Replying to @MartyBent, @ODELL, @MTanguma and @parkeralewis
Hope your team becomes sponsors of @BlockchainComns — we are focused on building open infrastructure, including tools, reference code, architecture & docs.