Exercise should be done using the Signet test network.
A remote Signet node has been created for this exercise, all you have to do is to send bitcoin-cli commands to it.
You need to replace your bitcoin.conf config with these lines below to connect to it:
signet=1
[signet]
rpcuser=btrustbuildersrpc
rpcpassword=btrustbuilderspass
rpcconnect=161.35.161.124
...and then execute bitcoin-cli -signet getblockchaininfo.
Using the command above with return an object containing various state info regarding the blockchain on Signet which you can confirm on https://mempool.space/signet.
HINT: Use bitcoin-cli help and bitcoin-cli help <command name> to learn what commands are available and what they do.
You can also check out Bitcoin Core RPC API Reference docs
NOTE: You don't need to start a local bitcoin daemon, just use the bitcoin-cli command to execute RPC commands to the remote Signet node.
- Fork this repository.
- Go to the
Actionstab and enable github workflow for your repository by clickingI understand my ...
-
Clone your fork to your local computer.
-
Add your bitcoin cli commands to the script files:
01.sh to 08.shin thesubmissionfolder. Example:$ bitcoin-cli -signet getblockcount
-
Commit and push your changes to the
mainbranch of your remote fork. -
Confirm your forked repository has a green check mark.
-
For the final exercise, follow instructions in
FINAL-TASK.MDfile and update all otherxxx.txtfiles. -
Submit your solution to this form: Google form.
PS: You can commit and push as often as you like and GitHub Actions will re-evaluate your code every time. You will need to look through the auto-grader logs (in the "Actions" tab) to see what exactly you got right or wrong.
- Learn me a Bitcoin: link
- Bitcoin RPC API Reference: link
- Bash Scripting Tutorial – Linux Shell Script and Command Line for Beginners: link
Submissions must be your own work. Do not copy from other students, solution repositories, or past cohorts. Sharing or copying answers is not allowed. Violations may result in your submission being invalidated or in follow-up under the program’s policies.
You may use AI tools to study and to clarify concepts, but the commands and code you submit must be written by you. Do not paste in AI-generated answers as your submission. The exercises are for your learning; relying on AI to produce answers will undermine that and may be treated like other academic misconduct.
These rules are in place so that you actually practice using Bitcoin CLI, build real skills, and can be fairly assessed. Doing the work yourself is how you learn; shortcuts defeat the purpose of the exercises and don’t prepare you for what comes next in the program.

