---
# System prepended metadata

title: BC Internships Weekly Reports 2020-08-14

---

# BC Internships Weekly Reports 2020-08-14

###### tags: weekly-reports

## @chiselinc

### Work from Week 6


### Next Steps

#### Bitcoin Standup for Windows


#### Blockchain Commons Community 


### Learnings


## @cprkrn

PENDING

## @fakhrulKhir 

PENDING

## @gg2001 

* Created a basic beancount db generator in swift
* mainly reading about the beancount format
* TODO: implement a simple function to generate beancount file based on BTC sends/receives


## @gorazdko

* implemented slip39 ur export option
* some ui modifications
* testing
* 32h


## @javiervargas

* Finish lighting chapters.
* Found some bugs FullyNoded.
* Finish lsat prototype and asked feedback about first draft.


### Next Steps



## @jodobear 

### Work Completed

1. Add setting for a separate bitcoin data directory
2. Install Esplora
3. Add c-lightning-http-plugin
4. Bug fixes

### Total Hours Worked

25 hours

### Assistance Requested

### Issues

1. Can't verify key fingerprint for docker since `apt-key` error for output shouldn't be to terminal.
2. Having difficulty to setup Hidden Service for docker container.

### Learnings

Symlinks are awesome!

### Next Steps

1. Launch Standup VPS on Linode
2. Stack Script rewrite
3. lBTCftc review


## @watersnake1
### Summary of Work Done
Spotbit is now in version 0.1.1. I have tried to work on improving spotbit's functionality and stability for this release, so that it might be deployed on other servers soon.
This week, I have:
* bugfixed the prune() method that was causing database issues
* added more error checks throughout spotbit
* cleaned up print statements and made if-else logic more compact
* finished implementing historical data collection; spotbit can now access the history of any supported exchange
* I checked all 109 ccxt exchanges and found 23 that had either gone down or have non-functional apis. These have been removed from the complete list of available exchanges.
* added config settings relating to getting exchange history
* made the example_config file reflect the latest changes
* added logging
* Paid for milestone 2

Challenges:
* The main issue I see with spotbit now is lagging data. When many exchanges are being supported simultaneously some exchanges do not seem to be able to "keep up" with current data. I have a guess that this has to do with running many threads on a very weak computer (raspberry pi 3). I am guessing that some threads are simply not able to always be executing, and since there are around 4 threads each with lots do, one or more of them may just get sidelined forever. To test this, I am going to do two things: one, check every table and see if there is a pattern of which exchanges are behind that correlates to what thread they are in or their position in that thread. And two, I am going to turn off performance mode and push everything to one thread and see if there is a difference. Since this is an issue that is specific to my situation I am still going to relase 0.1.1 today. The result of the first experiment was that only exchanges in the first thread kept up to date, while exchanges in other threads fell behind quickly. The second experiment is still in progress.