C4's CBP Exam Committee has just released version 2.0 of the Certified Bitcoin Professional examination.
The world of Bitcoin is constantly evolving, and it's important for the CBP exam to stay current. This new version of the CBP exam uses the most up-to-date content when testing applicants to ensure they demonstrate a working understanding of Bitcoin.
What has changed?
After a year and a half worth of question statistics, the CBP Exam Committee was able to identify questions that caused confusion amongst applicants. These questions were rewritten to maximize clarity while still testing knowledge.
Dozens of questions that were removed, replaced, or modified to reflect prevailing clarity of the topics. We have also shifted away from referencing specific BIP numbers to testing an applicant's knowledge of the core concept embodied by the various BIPs. For example, in the following cases the BIP numbers have been removed and replaced by their more descriptive phrases:
- BIP32 -> Deterministic Wallets
- BIP38 -> Passphrase-Encrypted Wallets
- BIP70 -> Secure Payment Protocol
The most significant change made to the CBP is the inclusion of a 33rd topic: UTXOs. This topic tests applicants' knowledge of how Bitcoin makes use of unspent transaction outputs and how they relate to balances in your wallet.
What hasn't changed?
The CBP exam is still a non-technical exam and is targeted at professionals who need to use bitcoin in their duties. The v2.0 CBP exam can still be compared to a "Driver's License" in that it ensures you know how to use Bitcoin safely, but does not cover the technical details of how Bitcoin works.
I'd like to help!
The CBP Exam Committee is chaired by Dr. Ethan Wilding of LedgerLabs. We're always looking for people to be part of the committee to help ensure that this exam accurately reflects the most up-to-date standard body of knowledge about bitcoin and how to use it safely. If you would like to be part of the committee, or if you have any suggestions, please contact Dr. Wilding at firstname.lastname@example.org.