mainnet_pat 2026

Hey everyone, I would like to announce a FundMe.cash campaign to fund a whole year of my full-time work for the BCH community. I've decided to make this fundraiser time-based instead of project-based because there are a lot of projects which will benefit from my contributions, and running several smaller funding campaigns is not really viable; see the project breakdown below.Project breakdownMajor projectsHD Wallet implementation in mainnet-js, integration into CashonizeHD Wallet support in WC2 specification, implementation in the @bch-wc2 NPM package, integration into Cashonize, upgrade of WC2 interfaces for better error handling - The current BCH WC2 spec is very specific about the transaction – the transaction signing request must define the exact transaction shape; the wallet may not alter it to add any new inputs or outputs, just perform the signing. This approach turned out to be a great start for BCH dApps, but it narrows the freedom of UTXO spending choice of the wallet, making the requesting dApp only know the UTXOs of the connected address. This approach fails miserably in the case of an HD Wallet – a client shall not know all HD addresses of wallets but only the specified connected addresses. I propose to revisit the spec and add support for partial transaction signing requests, where additional P2PKH inputs will be provided by the wallet, both non-HD and HD with subaddresses, opaque to the dApp. - Furthermore, the current spec returns to the client a `undefined` result for any underlying wallet errors associated with signing or any other internal handling. The updated spec aims to define a new result object which indicates the error code and message, corresponding to the most common signing failure cases, to enhance the Wallet-dApp interaction.Exploratory work on CashScript enhancements to support: - MAST contracts and QuantumRoot contracts * I have authored MAST support in NexScript (link 1, link 2), a clone of CashScript on Nexa, and it is possible to port this work back to BCH, with new modern features as functions, bitwise ops and higher VM limits. * I also want to explore the implementation of QuantumRoot contracts described by Jason. - Contracts with global state kept in sidecar token UTXOs * Having a lot of experience in CashScripts compiler modification from my work on Nexa's NexScript and adding the debugging functionality to CashScript, I am confident I will be able to extend the CashScript compiler to support Solidity-like syntax to define contract state variables. The values of these variables will be stored in token NFT commitments and provided in sidecar inputs to be spent together with this contract. Such a syntax will bring BCH's CashScript closer to the EVM world's Solidity, with the potential to attract more developer attention and to port existing EVM projects and innovate on our blockchain. - Further development of the testing suite to become a standalone package similar to Hardhat * This CashScript add-on I have authored grew mature and independent enough to be extracted from the repository. It is already used in two of my recent projects – the SushiBar staking contract and the Olando community project – and has received many updates. It is now time to create a templating project from it, similar to Hardhat for EVM.I expect major projects to take up to 60% of the budget.Minor projectsOngoing maintenance and improvements of mainnet-js: restructure packages to make including the lib as a dependency more lightweight, native BIP39 support using libauth, encrypted storage of wallet secrets, support DS-proofs for incoming payments, support SIGHASH_UTXOS signing, BIP21 URI scheme payment protocol, updating documentation, and other issues from the backlog.Better token support in Sickpig's explorer: add full token metadata support, and improve the address page to list all tokens as a summary.Implement the x402 spec for micropayments in BCH and CashTokens. Develop a gating proxy service which enforces the payment scheme, an example application which makes use of this service and implements the user-facing UI for conducting such payments using a built-in wallet and a WC2-connected wallet.Implementation of CashFusion for CashTokens. We have discussed the details with Jonald, and he is excited to work on this task together with me.4byte.directory-like web index of BCH contracts. It will both help the wallets to identify the P2SH contract spends and the P2S contract locks. The latter is also very handy because P2S locks will not have an address in our usual sense.Contributions to Cashonize and its community forks: CC-Wallet (built-in cauldron support) and Olando-Wallet.Support for watch-wallets, support for importing WIF and hex-encoded private keysSupport internationalizationImplement the improvements from new mainnet-js developmentsI expect minor projects to take up to 30% of the budget, including the compensation for delegated tasks and collaboration with other developers.Ongoing supportThere are many projects of mine which require maintenance, support and enhancements. I do want to have time to respond to community requests and keep them cool and nice and provide the means to interact with them on API or development level. Or better to be embeddable in other projects. Specifically, among those are the TapSwap.cashNFT marketplace and the BCHPUMP.cash CashTokens launchpad, which could become wallet-embeddable software.I am running many community-enhancing servers – bchn.pat.mn, fulcrum.pat.mn, explorer.pat.mn, blockbook.pat.mn, chaingraph.pat.mn, ipfs-bch.pat.mn, bcmr.pat.mn and others. This campaign will help these being further maintained and server costs covered for the entire 2026.I expect the support work and maintenance costs to take about 10% of the budget.Would love to doThere is always some cool work around waiting to be done, and I will be happy to pick it up if budget allows.Contributions to BCHN - `/someone` is needed in supporting CEX handling of CashTokens, and I have a good contribution history to that repo. - Improvements of RPC calls and their hardening, including whitelisting the call methods, akin to those used in my proxy service bch.pat.mn - Improvements to web-specific CORS handlingContinue work on Subsquid integration; more detailsCampaign objectiveWith this fundraiser, I seek to raise 500 BCH to fund the long-term work on the features and new projects described above. With my vast experience in BCH development and knowledge of the projects I will be working with, I am confident that my contributions will be very valuable for the community.Who am I?I am pat, a hobby Bitcoiner since 2011 and a Bitcoin Cash developer since 2020.My most recent and notable contributions were in the field of CashTokens and BCH infrastructure: I added CashTokens support to the BlockBook indexer, implemented atomic swaps between Monero and Bitcoin Cash, created BCHPUMP.cash and xPUMP staking, and added debugging functionality to CashScript. I've pioneered the WalletConnectV2 support in BCH for the Cashonize wallet, prepared mainnet-js for the May '23 upgrade, created Paytaca Connect, developed the dApps for Emerald DAO and BitCats Heroes Club, consulted BCH Guru developers, and launched TapSwap.I have contributed to many BCH projects: BCHN, Fulcrum, Electron-Cash, LibAuth, CashScript, gs++, SLPDB and others.In October 2021, I teamed up with Kasumi and became the Lead Dev for MistSwap, bringing analytics, governance, sideshift integration, LNS, SmartSafe, Sonar.Cash and much more to the MistSwap and smartBCH network.I've started my way working for read.cash and later switched to help with mainnet.cash – the main library used by noise.cash. I've brought numerous features to mainnet.cash, the most notable being SLP, smartBCH and cashtokens support.I am most active on GitHub and Telegram.