- 
-
-
-
- {% if author.image %}
- 
- {% endif %}
-
- {{ author.name | upcase}}
- - {% if author.handle %} -{{ author.handle }}
- {% endif %} -
- {{ content }}
-
- {{ author.handle }}
- {% endif %} -
-
-Session A (January 29th — February 9th) is appropriate for developers
-who already work on Bitcoin or Bitcoin applications and who want an opportunity
-to dive deep into protocol design, adversarial thinking, threat models and
-security considerations with long-standing Bitcoin Core developers. We will
-also discuss Bitcoin’s most pressing challenges: scaling, fungibility and
-privacy.
-
-### Topics covered:
-
-- Categorization of threat models: centralization pressures, consensus issues,
- user protection, privacy and fungibility
-- Mining: history, pools, mining centralization pressures, mining games
-- Soft forks: approaches and history, Flag day upgrades, IsSuperMajority
- signaling, BIP9 signaling, BIP148 UASF, BIP91, etc
-- Hard forks: history, current research, consensus and network considerations
-- Consensus approaches: proof-of-work, proof-of-stake, other models
-- Fungibility and scalability: trade-offs for different approaches, chain
- analysis, fungibility technologies, signature aggregation, key aggregation
-- Smart contracts and trustless systems: lightning, tumblebit, sidechains,
- discreet log contracts and scriptless scripts
-
-Session B (February 12th — February 23rd 2018) is appropriate for
-software developers with an interest in Bitcoin technologies and who want to
-contribute to Bitcoin Core or other open source Bitcoin projects, but who have
-not yet done so.
-
-### We will cover aspects such as:
-
-- History and philosophy of Bitcoin and the Bitcoin Core project, the BIP
- process, important
-- Contributing to Bitcoin Core: examples of PRs and code rev
-- The architecture of Bitcoin
-- Bitcoin consensus and transact
-- The P2P net
-- A history of chain forks and fail
-- SegWit: rationale, history, design, activa
-- Payment channels and light
-
-Candidates who are able to dedicate four weeks to working on Bitcoin may apply
-to both sessions. Expect both sessions to be very hands-on. We’ll spend about
-half the time on talks covering the topics above, not to mention great
-conversation over lunch. Primarily, though, you’ll learn by doing — either by
-carrying out independent research and investigating systems you find
-interesting in the space, or by contributing to Bitcoin Core or related
-projects while collaborating with established Bitcoin Core developers. Talks
-will primarily be led by Matt and John, with input from Alex, Suhas and Russ.
-There may also be guest speakers over the four weeks.
-
-### Wednesday Night Meetups
-
-To extend participation to those who live in the New York area but are not able
-to dedicate two or four weeks to attending the Residency program, we are also
-opening our doors to a small number of participants on Wednesday evenings in
-the weeks leading up to the Residency. We’ll go over some of the material from
-the Residency program and be on hand to help with your Bitcoin Core PR or
-related project.
-
-If you’ve wanted to contribute to Bitcoin Core or are working on an open-source
-Bitcoin project and want some guidance from established Bitcoin Core
-contributors in an informal setting, this is a great opportunity.
diff --git a/_posts/2018-08-20-lightning-apps-residency.md b/_posts/2018-08-20-lightning-apps-residency.md
deleted file mode 100644
index 136e012..0000000
--- a/_posts/2018-08-20-lightning-apps-residency.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-layout: post
-title: "Chaincode Lightning Applications Residency"
-author: chaincode_labs
-name: "Chaincode Labs"
-image: /assets/images/residency2018.png
-alt: Image of a yellow rectangle
-category: "News"
----
-Chaincode is proud to announce a Lightning applications residency program, taking place in
-New York, Oct 22–26 2018! We’ve already hosted two residency programs, in 2016 and 2018. Those were focused on the Bitcoin
-protocol and contributing to Bitcoin Core. This time we’re going to try
-something a bit different.
-
-The Lightning network is maturing every day and we’re beginning to see great
-applications like satoshis.place and yalls.org being built on top of it. There’s
-a huge amount of excitement growing around Lightning applications, but
-knowledge of how to build those applications is currently scarce and
-diffuse.
-
-We want to help bootstrap the emerging Lightning applications developer
-ecosystem, so we’re hosting a week-long residency specifically for Lightning
-application developers (as opposed to Lightning protocol developers), organised
-by us, with mentoring and speaking by experts in the Lightning applications
-space.
-
-
-
-### We’ve got a stellar line-up of guest speakers:
-
-- Chris Stewart is the founder of SuredBits, a
- real-time micropayment-powered data service, built on top of the Lightning
- network. He is also the maintainer of bitcoin-s and a former Chaincode
- resident.
-
-- Christian
- Decker is an engineer at Blockstream and is a maintainer of the c-lightning Lightning implementation. He is also co-author
- of the 2015 Duplex Micropayment Channels paper and the
- 2018 eltoo paper.
-
-- Elaine
- Ou is an engineer at Global Financial Access. She has implemented
- the LightningBuddy and Jellybean applications on top of Lightning.
-
-- Jack
- Mallers is the lead developer of zap, a desktop and iOS wallet for Lightning
- payments
-
-- Justin Camarena is an engineer at bitrefill,
- the first payment processor to accept mainnet Lightning payments. He was the
- lead engineer for integrating Lightning into bitrefill’s payment system.
-
-- lightningk0ala is the creator of the wildly popular satoshis.place Lightning app. He’s an expert on
- Lightning-powered games.
-
-We’re looking for experienced applications developers, perhaps with a
-background in web apps or Ethereum apps, who want to learn about integrating
-Lightning payments into applications. No experience of the Bitcoin or Lightning
-protocols are required.
-
-The residency will be project-based, and applicants will build a prototype
-application over the course of the week. Residents will have a chance to
-present their work on Friday afternoon.
-
-All guest speaker talks and presentations will be video recorded and made
-freely available. We want to scale the benefits of this residency to engineers
-who aren’t able to join us in person.
-
-We’re really excited about this new residency and are looking forward to some
-excellent talks and amazing new Lightning applications
diff --git a/_posts/2019-01-31-2019-residency.md b/_posts/2019-01-31-2019-residency.md
deleted file mode 100644
index 7f90783..0000000
--- a/_posts/2019-01-31-2019-residency.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-layout: post
-title: "Chaincode 2019 Summer Residency"
-author: chaincode_labs
-name: Chaincode Labs
-image: /assets/images/residency2019.png
-alt: Image of a yellow rectangle
-category: "News"
----
-We’re proud to announce the fourth Chaincode residency, to be hosted in our new
-office in Midtown Manhattan this summer.
-
-Supporting the developer community and helping new contributors get their start
-in Bitcoin protocol development is a key part of our mission. Over the past
-three years, our residency programs have helped many developers start
-contributing to Bitcoin projects. Alex Bosworth and Johan
-Halseth (Lightning Labs), Neha Narula (MIT DCI), James
-O’Beirne and John Newbery (Chaincode Labs), Chris
-Stewart (SuredBits), Pierre Rochard (Lightning Node Launcher), Rene
-Pickhardt (LN developer and educator) and Will
-O’Beirne (Lightning Joule and WebLN) are all Chaincode
-Residency alumni.
-
-
-
-This summer’s edition is our most ambitious yet, building on the experience
-we’ve gained from our previous residencies. Our new office has allowed us to
-radically expand the scope and duration:
-
-- The first three weeks will consist of a seminar and discussion series, giving
- all residents a thorough grounding in Bitcoin and Lightning protocol
- development. Seminars will be led by Chaincode employees and guest speakers,
- including some of the most prolific contributors in Bitcoin and Lightning
- protocol development. Previous guest speakers include Pieter
- Wuille, Peter Todd, Tadge Dryja, Alex Bosworth, Christian
- Decker, and Cory Fields.
-
-- Armed with this knowledge, the residents will spend the next two months
- writing code and making impactful contributions to open source Bitcoin and
- Lightning projects. Each resident will be paired with a mentor to help guide
- them through the process and will have access to the Chaincode team and their
- peers for day-to-day help. We’ve recruited some exceptional protocol engineers
- to act as mentors, including Christian Decker, Gregory
- Sanders, Matt Corallo, Fabrice Drouin, and many more.
-
-Bitcoin is blessed with an extraordinarily generous developer community. Our
-volunteer mentors are some of the leading contributors to the Bitcoin and
-Lightning protocols, and they’re devoting their time to help train and educate
-the next generation of protocol developers.
-
-We’re looking for developers from all backgrounds to apply. The only
-requirements are that you want to learn about Bitcoin and Lightning and that
-you’re excited about the prospect of spending summer writing code and
-contributing to open source Bitcoin projects. We’ll set each resident up with
-accommodation and a stipend to support living expenses in New York for the
-summer. International applicants are welcome.
-
-If you want to experience a life-changing educational experience in one of the
-most vibrant cities in the world, we invite you to apply. Come join us and make
-this your summer of Bitcoin!
diff --git a/_posts/2020-02-19-2020-residency.md b/_posts/2020-02-19-2020-residency.md
deleted file mode 100644
index 1fe4f9b..0000000
--- a/_posts/2020-02-19-2020-residency.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-layout: post
-title: "Chaincode 2020 Summer Residency"
-author: chaincode_labs
-name: "Chaincode Labs"
-image: /assets/images/residency.png
-alt: Image of a yellow rectangle
-category: "News"
----
-### We’re thrilled today to be announcing our fifth residency program, hosted in our office in New York in June 2020
-
-Over the last 4 years, we’ve hosted a series of residencies to help train and develop the next generation of
-Bitcoin and Lightning protocol and application engineers.
-
-Chaincode’s mission is to support Bitcoin, and we believe a critical part of
-that work is creating a welcoming, inclusive environment for less experienced
-contributors to find their start in Bitcoin.
-
-
-
-### We’ll host two seminar sessions, one for Lightning and one for Bitcoin protocol development (applicants can apply to both):
-
-- The Lightning session (June 1st — 5th) will cover the history of payment
- channels and the Lightning Network; the BOLTs; routing and liquidity; attack
- vectors and privacy considerations; and the future of Lightning. Previous guest
- speakers include Tadge Dryja, Alex Bosworth, Christian
- Decker and Fabrice Drouin.
-
-- The Bitcoin session (Jun 11th — 19th) will cover the history and philosophy
- of Bitcoin and Bitcoin Core; how to be an effective contributor; the
- categorization of threat models; consensus issues and soft forks; and
- fungibility, privacy and scalability concerns. Previous guest speakers include
- Pieter
- Wuille, Matt Corallo, Giulia Fanti and Ethan
- Heilman.
-
-We’re extremely proud of our ressies, and of the work we’ve done to help
-onboard deserving new contributors into the Bitcoin developer world. Our alumni
-have done extraordinary things across the Bitcoin ecosystem, whether that’s
-joining companies to contribute to open source projects (Carla
-Kirk-Cohen, Alex Bosworth and Johan Halseth at Lightning
-Labs; Amiti Uttarwar at Xapo; James O’Beirne at DG Labs; John Newbery and Antoine
-Riard at Chaincode Labs), running organizations (Neha Narula
-at MIT DCI),
-starting their own companies (Chris Stewart at SuredBits; Andre
-Neves at Zebedee) or becoming influential individual contributors (Rene
-Pickhardt as an educator; Will
-O’Beirne by launching Lightning Joule; Pierre
-Rochard as a developer and advocate; Fabian Jahr as an OKCoin-sponsored full-time Bitcoin contributor). Our
-residents have diverse backgrounds and come from all over the world, but they
-have some things in common: they’re talented and passionate about Bitcoin and
-Lightning.
-
-So if you love Bitcoin or Lightning, you’re eager to learn, and you’re ready to
-make impactful contributions to the open source ecosystem, then we’d love for
-you to apply. We truly believe the Chaincode Residency offers a unique
-opportunity to catapult your Bitcoin career.
-
-We’ll provide lunch and a beautiful workspace located in Midtown Manhattan.
-Travel and accommodation are provided on a case-by-case basis. Come join us for
-a life-changing educational experience in one of the most vibrant cities in the
-world this summer.
diff --git a/_posts/2020-07-21-residency-postponed.md b/_posts/2020-07-21-residency-postponed.md
deleted file mode 100644
index 3eab536..0000000
--- a/_posts/2020-07-21-residency-postponed.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-layout: post
-title: "Chaincode 2020 Residency Postponed"
-author: chaincode_labs
-name: "Chaincode Labs"
-image: /assets/images/residencyupdate.png
-card_image: /assets/images/residency-update-twitter.png
-alt: Image of a yellow rectangle
-category: "News"
----
-
-This year continues to be one of immense challenges and change. While we were optimistic for a residency to take place in 2020, we have officially decided to postpone until it is safe to do so. We are targeting a 2021 date, but will solidify as we know more.
-
-We had accepted a small group of participants at the time we were forced to pause our selection process. Those participants will receive an automatic invitation to the rescheduled program and we will resume the selection process once new dates have been decided. We will hold off announcing any participants until the full group has been selected.
-
-We believe the program benefits most from an in-person format, which guides the decision to not move online. We look forward to resuming the process and will post updates as we have them.
diff --git a/_posts/2020-09-17-2020-internship.md b/_posts/2020-09-17-2020-internship.md
deleted file mode 100644
index e0bd768..0000000
--- a/_posts/2020-09-17-2020-internship.md
+++ /dev/null
@@ -1,179 +0,0 @@
----
-layout: post
-title: "Chaincode's 2020 Summer Internship"
-author: chaincode_labs
-name: "Chaincode Labs"
-image: /assets/images/internship.jpg
-alt: Image of internship
-category: "News"
----
-
-This summer, we hosted our first internship program at Chaincode Labs. After
-an extensive interview and technical code challenge process, we selected [Troy
-Giorshev](https://twitter.com/troygiorshev), studying at [Queens
-University](https://www.queensu.ca/), and [Hope
-Yen](https://www.linkedin.com/in/hope-yen-hk/), studying at [Carnegie
-Mellon](https://www.cmu.edu/), to work alongside Chaincode mentors while
-becoming immersed in the Bitcoin Core and Lightning communities. Their time
-with us came to an end in August, and we're excited to see what they do next.
-
-Before he left us for his final year at university, we spoke to Troy about his
-experience at Chaincode, and what future interns and Bitcoin open source
-contributors can expect.
-
-#### Q: What were your overall impressions of working at Chaincode on open source software?
-
-The summer was rewarding beyond my wildest dreams. I was embraced by
-a worldwide community, whose skilled members advised me as I proposed projects
-and supported me as I built them, I dove deep into a storied codebase,
-learning and pushing my limits every step of the way, and despite having only
-worked for a few months, I was able to review the work of others and influence
-the future of Bitcoin.
-
-#### Q: What software project were you contributing to?
-
-I worked on Bitcoin Core, which is the predominant software Bitcoin users run
-to interact with the blockchain, wallet, and network. It's an open source
-project, and the process for contributing is a little different from working on
-a proprietary project.
-
-#### Q: What was your summer project? How did you propose that to the community?
-
-In my previous experiences as a developer, I was assigned tasks and had very
-little say over the direction of development efforts. So proposing a project in
-this capacity is not something I’d ever done before. Even the few times I
-had proposed projects, the stakeholders were clear. When working on Bitcoin
-Core, I had to propose my project to other developers with far more knowledge
-of the codebase! Consistently, though, the community was willing to give me a
-shot and motivated me to see the project through.
-
-One thing that's obviously different is that there are no Project Managers
-here! The maintainers (people who have the ability to merge changes into the
-repository) do not give direction. The best contributors to Bitcoin are
-self-driven and flexible.
-
-After some guidance from my mentor, I had a project picked out. I'd add message
-dumping and usage statistics to our P2P connections, allowing developers and users
-to debug P2P issues and gain visibility into what's happening on those connections.
-
-I started by writing up and posting a [design
-document](https://gist.github.com/troygiorshev/f2fedca9b2ab8a2c6449c92d92e17678),
-outlining the goals of the project and its capabilities, which gave everyone in
-the community a chance to review my proposal. It showed I was open to critique
-and willing to work towards a solution with others. After getting feedback, the
-next step was to make a proof of concept so that other developers could try the
-functionality for themselves. I built my proof of concept, wrote a clear
-description, and opened [the
-Pull Request (PR)](https://github.com/bitcoin/bitcoin/pull/19509).
-
-#### Q: And what happens after you've opened a PR?
-
-With my PR open, contributors started leaving review comments. Oh so many
-review comments! I grew tremendously as a developer by defending my design
-decisions. When I was [asked](https://bitcoincore.reviews/19509#l-54) why I
-was focused on a minimal file descriptor usage, I was able to point at both the
-history of the project and to a [currently open
-issue](https://bitcoincore.reviews/19509#l-81) to justify my choice. With
-Bitcoin Core being a security-critical application, I was given the chance to
-[critically
-examine](https://github.com/bitcoin/bitcoin/pull/19509#issuecomment-661838550)
-whether my work could open up a DoS vector, and I had to justify why what I had
-written was safe. The questions were tough but fair. Consistently reviewers
-were respectful, and it was clear they had the best interests of Bitcoin in
-mind. As long as I was clear and responded with the same amount of respect,
-the conversations came to something useful.
-
-At the time of writing, my PR is still open. I am still making changes, and
-others are still reviewing it. Bitcoin is a long-running project, and the cost
-of a bug is immense, so it does not move quickly. Only when a PR has an
-abundance of review and when maintainers are confident that all aspects of the
-addition have been explored will a PR be merged.
-
-#### Q: What was your day-to-day work like?
-
-Bitcoin Core is a security-critical and highly performant application. Because
-of this, the opportunity repeatedly arose to have technical discussions and
-make considerations that, in other projects, may be passed over. One example of
-this was a small change in one of my PRs, changing the return value of a
-function to be an Optional. An Optional type allows you to return either a
-value or a null, and is an alternative to, say, returning a Boolean and passing
-out a value by reference. When implementing this change, I had to verify it
-was being done in a sufficiently performant way (i.e. that the method was not
-needlessly making copies of the object it was returning). I verified this not
-by simply trusting documentation but by digging [deep into the implementation
-of the Optional
-type](https://www.boost.org/doc/libs/1_61_0/libs/optional/doc/html/index.html).
-As someone who had not worked significantly in C++ before, this gave me lots to
-explore. In the end, I was able to justify to others that my code was the best
-it could be.
-
-#### Q: How else did you contribute to the Bitcoin Core project this summer?
-
-The best way to participate in the community and to help out Bitcoin is to
-review PRs. Bitcoin’s community is filled with world-class developers and
-applied cryptographers. They come from a variety of backgrounds, but all come
-together under the common purpose of pushing Bitcoin forward. The success of
-open source development projects like Bitcoin rests on good review, and there
-is no shortage of interesting PRs waiting to be explored.
-
-When reviewing a PR, it's not enough just to review the changes themselves.
-The changes need to be understood in context with the rest of the project, and
-the changes need to be approved both in concept and in implementation. As a
-reviewer, this gave me a great opportunity to explore new parts of the
-codebase. It was occasionally necessary to perform “code archaeology” by
-[digging
-through](https://github.com/bitcoin/bitcoin/pull/19107#issuecomment-674243013)
-the git history of the project, exploring when a feature was introduced and how
-it evolved. I was consistently surprised by what I learned! Overall, it has
-taken many years for this process to become what it is today. Bitcoin has had
-an [eventful
-past](https://b10c.me/blog/004-the-incomplete-history-of-bitcoin-development/)
-and given the hard work of contributors, I know it will continue to have an
-exciting future!
-
-#### Q: What are some concrete steps aspiring contributors can take to get more involved in the Bitcoin development process?
-
-First, get yourself set up with an IRC client. A good command line option is
-[irssi](https://irssi.org/), but if you are someone who would rather use a
-mouse, there are various GUI options available. Join us on
-[Freenode](https://webchat.freenode.net/) over at `#bitcoin-core-dev`. Another great
-place to get started is the [Bitcoin Core PR Review
-Club](https://bitcoincore.reviews/), which is an open meeting that happens every
-Wednesday at 1700 UTC on `#bitcoin-core-pr-reviews`. Each week the host will go
-over an interesting or unique PR, accompanied by notes and questions, with the
-goal of helping you get used to Bitcoin’s PR review process. The review club is
-designed for newcomers and everyone is welcome to come and ask questions. Check
-out [the intro guide](https://bitcoincore.reviews/your-first-meeting) for more
-on how to get started.
-
-Eventually, you will want to join other communication channels. The best
-option is the [Bitcoin Optech
-Newsletter](https://bitcoinops.org/en/newsletters/). It posts every week,
-giving a curated summary of everything going on in the Bitcoin space including
-discussions occurring on the [bitcoin-core-dev mailing
-list](https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev). On
-the mailing list itself, you can find the unfiltered technical discussions on
-the cutting-edge of Bitcoin development.
-
-Once you have a node set up, a great resource is [Learning Bitcoin from the
-Command
-Line](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line).
-If you are ever confused, check out Jameson Lopp’s [Bitcoin Information and
-Resources page](https://www.lopp.net/bitcoin-information.html), which is a gold
-mine of Bitcoin knowledge. And when you're ready to start working on the code,
-go read
-[CONTRIBUTING.md](https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md).
-It will be your best friend going forward.
-
-There are mentors out there, but sometimes they are hard to find. I can not
-stress the value of mentorship enough, especially for someone new to
-development. I had the privilege of working under [John
-Newbery](https://twitter.com/@jfnewbery), who guided me through navigating both
-the codebase and the unique world of open source development.
-
-If you need a hand, reach out to me. You can find me on twitter at
-[@troygiorshev](https://twitter.com/troygiorshev) and on IRC at `troygiorshev`.
-
-And last but certainly not least:
-
-Go review a PR!
diff --git a/_sass/main.scss b/_sass/main.scss
index 2c8c6c1..6a02d97 100644
--- a/_sass/main.scss
+++ b/_sass/main.scss
@@ -203,11 +203,44 @@ header {
font-size: 0.75rem;
}
+.page-intro {
+ max-width: 42rem;
+ line-height: 1.7rem;
+ font-size: 1.1rem;
+ p {
+ margin-bottom: 1.2rem;
+ }
+}
+.section-lead {
+ font-size: 1.1rem;
+ margin-bottom: 0;
+}
+.section-lead-past {
+ margin-top: 3.5rem;
+}
+
.jobs-container {
margin-left: 5rem;
margin-right: 5rem;
}
+.jobs-copy {
+ margin-top: 3rem;
+ max-width: 48rem;
+ line-height: 1.7rem;
+ font-size: 1.1rem;
+ p {
+ margin-bottom: 1.2rem;
+ }
+}
+.jobs-container .jobs-copy a {
+ color: $yellow;
+ text-decoration: none;
+}
+.jobs-container .jobs-copy a:hover {
+ color: white;
+}
+
.department {
border-top: 1px solid white;
padding-top: 1rem;
diff --git a/about.html b/about.html
index 1829c7a..ed91233 100644
--- a/about.html
+++ b/about.html
@@ -28,15 +28,6 @@
- 
+ 
+ + Engineers at Chaincode are tasked with identifying and pursuing the work + they believe is most important to Bitcoin's long-term success. We rarely + list traditionally defined roles because our work is so self-directed. The + best way to apply to work at Chaincode is to do the kind of work you would + do at Chaincode: make meaningful contributions to Bitcoin open-source + research and development. +
++ We're always interested in ideas and work related to Bitcoin that are not + on our radar. If you're working on problems in distributed systems, + cryptography, computer security, networking, privacy, or related fields + and believe your work has relevance to Bitcoin, we'd love to hear from + you. Reach out to us at + info@chaincode.com. +
+ Chaincode supports Bitcoin through open-source engineering, research, and + education. +
++ Engineers and researchers at Chaincode are free to pursue the Bitcoin + open-source projects they believe are most important. Members of our team + have contributed to Bitcoin Core, the Lightning Network protocol, and + novel cryptography that is relevant to Bitcoin. +
++ We also design and run educational programs that help current and future + contributors build the knowledge and skills needed to participate in + Bitcoin's development. Our goal is to support both the work being done + today and the people who will shape Bitcoin's future. +
+The following projects represent some of our team's work:
+
+ 
+ 
+ 
+ Some of our past projects include:
+ +
+ 
+
+ Chaincode's research initiatives aim to support rigorous investigation of + the open questions and challenges facing Bitcoin. We seek to foster + greater engagement between Bitcoin and the academic community, helping + ensure that the strongest ideas and insights contribute to Bitcoin's + long-term development. +
+
+
+