Particl Copay Release

As some of the Particl community may have noticed on Github, the team has been working on developing a project named Copay for a few weeks and are wondering what it is. Finally the time has come to publicly announce the details of the project. It is Particl’s very own version of Copay! Particl Copay is designed to be a mobile multi-sig wallet downloadable on Google Play Store. This is Particl’s answer to the ongoing question “Why did you choose to start off with Bitcoin’s latest codebase?”.

Particl is not just releasing a PART multi-sig mobile wallet, it’s also releasing a statement that Particl would be able to capitalize on any of the open sourced Bitcoin Core 0.14.2.1 (soon to be 0.15.0) codebase. This was one of the bold and strategic decision by the team to start a new chain as they believe it maximizes the long term availability of open sourced features and applications such as native segwit, pruning and now, Copay. As of the moment, this move is slowly starting to pay off as it would normally take months for a dedicated team in order to come up with a multi-sig wallet. On Particl’s case, they just forked the codebase and switched to Particl (and yes, license was reviewed and we are welcome to use it).

Particl Copay has been under internal testing for 2 months, hence the reason why the team is comfortable releasing this on mainnet, bypassing the testnet phase. This release also partly checks off one of the team’s roadmap schedules “Third Party Integration”, which is well within Q3–2017. This would give the team more open resources to handle the remaining task for the quarter, which is the highly anticipated “Particl Electron Wallet App”.

Of course, Particl team does not plan to stop here. There are currently talks about Lightning development, quick upgrade to Bitcoin Core 0.15.0 codebase and others. Starting another exciting initiative would be completely possible too such as hardware wallets perhaps? Of course, coming up with the minimum viable product (MVP) is still the top priority of the team, but no matter what open sourced feature the team would be interested to include, it will not take a significant amount of time for them to adopt these features.