---
# System prepended metadata

title: BC Internships Weekly Reports 2020-06-26

---

# BC Internships Weekly Reports 2020-06-26

###### tags: weekly-reports

## @chiselinc

### Work from Week 1 and 2

* Completed and signed work order form
* Refreshed on principles of PGP and got familiar with using it on Windows and Linux
* Completed W9
* Signed CLA for Bitcoin Standup Scripts repo
* Began broader research on running a Bitcoin node on Windows
* Refresher on git branching for collaborative workflow
* [Provided minor readability edits to @jodobear's Python chapter](https://github.com/jodobear/Learning-Bitcoin-from-the-Command-Line/pull/1/files)

### Next Steps

Defining a clearer path for moving forward with Milestones, and output for Milestone 1.

## @cprkrn

PENDING

## @fakhrulKhir 

PENDING

## @gg2001 

Work from week 1 and 2:

* Completed and signed work order form
* Completed W8-BEN
* Wrote Go and Node.js versions of LBTCftCL (Milestone 1)
* Submitted PRs:
    * [Wrote Node.js and Go sections #136](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/pull/136)
* Currently incorporating [feedback from @shannona](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/pull/136#issuecomment-649895233), before merging the PR (will probably finish by June 28th)


## @gorazdko

My work regarding week 1 and week 2:

* soldering and assembly of bc-lethekit
* familiarizing with the project bc-lethkeit
* submitted PRs:
  * fix compiler warning #41
  * Allow mixing entropy when dicing #46
* research of required libraries #40
  * made a PoC of cbor/ur library for Arduino
* bug inspection regarding blank display #45, #36
  but still working on a solution

Next week I plan to have fully integrated libraries (libwally and cbor/ur) to achieve milestone 1.

## @javiervargas

About topics:

* About the LBFCftCL course I have managed to complete two sections such as Java and C and I have created the respective PR.
* On FullyNoded2 I have tried different use cases and founded some corrections, all of them are already resolved and deployed in the latest version.
* As for BitcoinStandup I have proposed a way to modularize all its components to facilitate the execution and maintenance of the same script. This I also think would facilitate the user experience.
* I've seen your last tweet about LSAT and IFPS and I'm reading and creating a draft about LSAT.

## @jodobear

### BC Internship Weekly Report 20-06-26

This is the first weekly report.

#### Work Completed

1. Introduction with the team.
2. Setting Milestones and work direction.
3. Signing of the Work Order & W-8BEN.
4. LBftCLI Ch A0 Compiling Bitcoin-core from source [PR#124](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/pull/124) merged.
5. LBftCLI Ch 18.4 Accessing Bitcoind with Python [PR#131](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/pull/131) merged.
6. Basic structure and components of Standup Scripts.
7. Research on best practices for the Standup Scripts.

### Next Steps

1. Starting work on the Standup Scripts. Layout the structure and document variables and start writing `help`.
2. Continue with the next chapters of LBftCLI.

## @watersnake1

### Summary of Work Done
Logistics:
  * completed work order
  * completed W9
  * provided btc address for payment

fn-server (price history project)
  * Research:
    - Flask best practices, including the use of factories in order to implement features such as task queues
    - Celery task queues to improve performance
    - Connecting sqlite3 databases with the API
    - sqlite3 best practices
    - libraries / APIs to source price data from. I have so far decided that ccxt is the best option, because it connects directly to exchange APIs while removing the need for manually implementing a client for each one (since it is done for us already by them). Alternatively, I also have a similar library that I wrote in Python for a different job that could be used, but this library is poorly tested and would need to be tweaked. ccxt is superior.
    - how websocket could be implemented
    - how to lay out the sqlite3 tables
  * Specs:
    - wrote a final draft spec for the project, reflecting the results of the test implementation described below. It better details the exact function of the program andwill serve as my guide for implementing in milestone 2.
  * Testing:
    - implemented a simple test server that conformed to the original draft spec to test the feasibility of the spec. I found no major issues with my thinking in the spec.

btc-standup-lightning
  * Research:
    - Studied the existing standup code
    - Differences between C-lightning and LND implementations
    - Using QuickConnect / LNDConnect to generate QR codes
    - Best way to present the user with choice of LND or C-lightning
  * Specs:
    - wrote draft spec for this feature of standup 

### Milestone Approval Requests
I have completed milestone 1 for fn-server (price history), and will complete milestone one for btc-standup-lightning by June 30, in line with the dates I specified in my work order.

