---
# System prepended metadata

title: BC Internships Weekly Reports 2020-07-02

---

# BC Internships Weekly Reports 2020-07-02

###### tags: weekly-reports

## @chiselinc

### Work from Week 3

* 1-on-1 chat with Christopher Allen to clarify path to move forward
* Reviewed [Bitcoin Core's specific docs/support path](https://bitcoincore.org/en/download/) for Windows setup
* Revisited existing Blockchain Commons documentation to determine what needs editing
* Cleaned up tooling and development environment for both Windows and Linux
* Started to deep-dive on Windows scripting and possibilities for [WSL](https://docs.microsoft.com/en-us/windows/wsl/about) as potential answer for Windows 10 users

### Next Steps

#### Bitcoin Standup for Windows

Aiming to be back on track and **deliver Milestone 1 on time** - will output as HackMD file (mini-report with recommended path forward for project).

#### Blockchain Commons Community Docs

My ideas for low-hanging fruit to start with next week, please confirm @ChristopherA:
- General cleanup on the [root repo page](https://github.com/BlockchainCommons/BlockchainCommonsCommunity/blob/master/README.md)
- Change "Externships" in Readme.md from linking solely to [external twitter thread](https://twitter.com/christophera/status/988856246349508609?s=21), and create its own page where we describe this current global internship experiment?

## @cprkrn

PENDING

## @fakhrulKhir 

PENDING

## @gg2001 

### Summary of work done

* Made revisions requested by @shannona for LBTCftCL sections
* Merged Node.js and Go sections into LBTCftCL, hence fully completing milestone 1
* Currently reading through the FullyNoded-2 codebase and experimenting with it, in order to complete milestone 2

## @gorazdko

My work regarding week 3:

* wrote Rust section in LBTCftCL: Accesing bitcoind with Rust 
* UR library updated to the newest spec several times #48
* researched libwally integration into Arduino and submitted PR #49
  * tried various ways of integrating it:
    * with libwally as a whole (with secp256k1)
    * libwally and secp256k1 as separate entities
    * tried to optimize the aliases into less/more readable code
  * It turns out that any other way of integrating (than showed by Snigirev) is
    extremely difficult, because Arduino does not support recursive builds

## @javiervargas

* About the LBFCftCL course i've added some improvements to C section and i've started the tor section reaching 3 chapters.

* I have encountered an error in FullyNoded2 that occurs when an incoming transaction is consulted and created an issue in the repository. It happens if node has txindex=1. It has been corrected.
* I have sent another bug to Fontaine about creating BIP39 Wallets on FullyNoded, he's dealing with it right now.

* I have added documentation to draft about the key-send functionality that allows you to make payments in lightning without having an invoice. Key-send is possible in LND and c-lightning as a plugin.

* I've installed and testing minisign tool and reading code.

## @jodobear

### Work Completed

1. Merging Linode and Standup Scripts(SS).
2. Adding help to SS.
3. Documented all variables.
4. Added confirm step.
5. Tested the installation on debian/buster64 10.4.0 VM. Everything so far works except for Tor.

FILE: [ss.sh](https://github.com/jodobear/Bitcoin-Standup-Scripts/blob/jodobear/Scripts/ss.sh)


### Total Hours Worked

14 hours.

### Issues

1. My instance of Debian/buster64 10.4.0 didn't have gpg installed. Added that check.
2. Tor installation gets stuck at this line:
```sh
Warning: apt-key output should not be parsed (stdout is not a terminal)
Executing: /tmp/apt-key-gpghome.mZMd3XOUko/gpg.1.sh --recv-keys --keyserver keys.gnupg.net 74A941BA219EC810
...
The following signatures couldn\'t be verified because the public key is not available: NO_PUBKEY 74A941BA219EC810
Reading package lists...
```
Reproduced on Linux Mint. 1 out of 4 tries succeeded.
cmd: `apt-key adv --recv-keys --keyserver keys.gnupg.net  74A941BA219EC810`
Exact error: `gpg: packet(13) too large`
Known error, currently working on resolution.

3. UFW: Has a step that needs manual intervention. Need to automate. Log:
```sh
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Skipping adding existing rule
Skipping adding existing rule (v6)
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
Firewall is active and enabled on system startup
/usr/sbin/ufw
```
### Next Steps

1. Test on a VPS.
2. Get feedback on the existing script.
3. Add Lightning, HWI & BTCPay.

## @watersnake1
### Summary of Work Done
SpotBit (formerly referred to as fn-server)
* Progression through milestone 2: implementation according to the design spec already posted
* Completed modules:
        - install
        - prune
        - request
        - read_config
* With help from Christopher, the name SpotBit has been chosen. In the future, a different name may be used to refer to the historical data aspect of the project. Christopher has created a website, email and twitter account under this name.
* Of the completed modules, I have tested extensively only `install` and `read_config`.

btc-standup-lightning:
* I have delegated the lead of this project to @jodobear. He is already farther along in the implementation of this project than me. I will continue to coordinate with him and offer assistance whenever possible. On June 30 I completed milestone 1 for this project. Milestones 2 and 3 are not neccesary for the completion of btc-standup-lightning.


