Current Position
Jon Atack is an independent Bitcoin protocol developer and Bitcoin Improvement Proposal (BIP) editor. In a March 2026 interview, he described his BIP maintenance work and discussed working in El Salvador. This profile uses El Salvador as his documented professional-market association, not a claim about nationality or a verified residential address.
Background & Biography
Atack’s personal website dates his Bitcoin Core contributions to 2019 and his BIP-maintainer work to 2024. He describes a focus on reviewing proposed changes, identifying bugs and helping maintain open-source projects. In his March 2026 interview, he discussed his earlier freelance software-engineering work and subsequent move into Bitcoin development. Bitcoin Core contribution is a description of technical work, not employment by a company called Bitcoin.
Notable Contributions
His public professional description emphasizes code review and the examination of proposed changes rather than a single commercial product. The work he describes includes reading proposals, supplying technical context and suggesting fixes. These are maintenance activities that can help other contributors evaluate changes before software reaches users.
In 2026 he also publicly discussed BIP editing and differing approaches to Bitcoin implementations. This profile does not present his views about other developers as established facts, or confuse an editorial role with authority to change network consensus.
Why Katharos.ai Is Following Them
Katharos.ai follows Atack to examine the maintenance and review work behind Bitcoin software. Public debate can attract more attention than the technical changes under discussion. Reporting should connect attributable proposals and review comments with the actual status of the relevant software, while distinguishing a participant’s interpretation from independently established outcomes.
Areas to Follow
Follow published proposal reviews, documented maintenance responsibilities and technical explanations. Track whether discussed changes remain proposals, enter a released implementation or gain meaningful adoption. Separate debate about project governance from evidence about software behavior. Any future organizational affiliation or research-center announcement should be independently verified rather than inferred from earlier plans.
Reporting Scope
Coverage is limited to public professional work and attributable technical commentary. No current grant funding, company employment or completed research center is asserted. Inclusion is not endorsement by Katharos.ai or the subject, and the profile is not investment advice. Private residential details, personal holdings and unrelated personal controversies are outside scope.
Sources for Further Reading
Jon Atack professional website — https://jonatack.github.io/
Bitcoin Infinity interview, 23 March 2026 — https://www.bitcoininfinityshow.com/bitcoin-core-from-the-inside-jon-atack-bis-195/
Bitcoin Optech portrait — https://bitcoinops.org/en/about/
MIT licence — https://github.com/bitcoinops/bitcoinops.github.io/blob/master/LICENSE.txt
Photograph Licence Notice
Portrait reproduced with native padding; source: Bitcoin Optech.
The MIT License (MIT)
Copyright (c) 2018 Bitcoin Optech contributors
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.