---
# System prepended metadata

title: BC Internships Weekly Reports 2020-07-10

---

# BC Internships Weekly Reports 2020-07-10

###### tags: weekly-reports

## @chiselinc

### Work from Week 4

* determined path forward for Bitcoin Standup (adapting scripts to run on PowerShell and WSL, with documentation for both older computers and Windows 10) based on broad research (most useful pathways from solved /bitcoin repo Issues and bitcointalk forum)
* Updated README.md and CONTRIBUTING.md and created INTERNSHIPS.md root document in BlockchainCommonsCommunity
* Attended PDT Thursday evening office hours and learned about Wolf McNally's cool research and projects

### Next Steps

#### Bitcoin Standup for Windows

* Write up initial recommendations for Windows project in HackMD
* Get repo made from template for Bitcoin-Standup-Windows
* Find a more experienced Windows dev to consult with as I start attempting to adapt scripts for PowerShell


#### Blockchain Commons Community 

* Engage fellow interns to contribute their thoughts to INTERNSHIPS.md
* Consult with Christopher on updates to be made on README.md 
* Gain admin access to HackMD group and organize some templates for PM/comms

## @cprkrn

PENDING

## @fakhrulKhir 

PENDING

## @gg2001 

### Summary of work done

PENDING

## @gorazdko
Week 4:
* implemented screens for a single xpub key (segwit) and two encoding options (base58 and QrBase58). Approaching milestone 2 here.
* I consider Milestone 1 achieved, although technically it isn't due to lack of review in BC community
* I am reusing #49 for further development
* worked 32 hours this week, so I am 8 hours behind the schedule
* also i am posting my weekly reports exclusively here from now on. If PGP signed reports are still desirable let me know.

## @javiervargas

### Work from Week 4

* Updated tor chapter with more details. 
* Started c-lightning chapter.
* Started testing aperture, running issues on configuration between proxy and REST server.

### Next Steps

* Finish c-lightning chapter
* Resolve or ask help about aperture.

### Total Hours Worked

10 Hours.

PENDING

## @jodobear 

### Work Completed

1. Split the SS into logical scripts. [link](https://github.com/jodobear/Bitcoin-Standup-Scripts/tree/jodobear/Scripts/scripts)
2. Fixed a few bugs in the scripts.
3. Currently implementing c-lightning & lnd.
4. Created PR for a genericized certificate of completion. @Christopher I can merge it if you are good with it or should I just merge it since I already shared the previous draft with you?

### Total Hours Worked

34 hours.

### Assistance Requested

1. With the issues descibed below.
2. Anyone know of a good source for deep diving in setting up hidden services & systemd services?

### Issues

I faced quite a bit of issues while implementing c-lightning & lnd.

#### Original [StandUp.sh](https://github.com/BlockchainCommons/Bitcoin-Standup-Scripts/blob/master/Scripts/StandUp.sh)

After installing the script for `Pruned Testnet`, the command `bitcoin-cli getwalletinfo` results in `error: Could not connect to the server 127.0.0.1:8332`. I have to then run `bitcoind -chain=main` to successfully execute the command. This should not be the case as the rpc should connect to the correct port based on the network that bitcoind is currently running on. Also, when `bitcoind -chain=test`, on running `bitcoin-cli getwalletinfo` we get the same error even after explicitly running bitcoind with specified network. Am i missing something here?

#### c-lightning

**STAUS:** WIP

**RESOLVED:** Faced quite a bit of time trying to setup the required directories & config since lightningd sets up the node on first run. But, while installing on a server it needs to be setup before it's run. So, hopped on the #lightningd IRC and Rusty resolved it for me. The solution was quite obvious to make the dirs and config in the script and lightningd would recognize them on start.

**UNRESOLVED:** Currently lightningd service exits with following error:

```sh
Failed to enable unit: File lightningd.service: No such file or directory
Failed to start lightningd.service: Unit lightningd.service not found.
```

#### LND

**STATUS:** WIP

I have been struggling here quite a bit figuring out user permissions, directories and how lnd configures itself with bitcoind.

**UNRESOLVED:** Currently lnd exits with the following error `(code=exited, status=216/GROUP)`. I believe i'm not setting the directories or permissions properly.

```sh
● lnd.service - LND Lightning Network Daemon
   Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sat 2020-07-11 17:30:26 GMT; 22s ago
  Process: 14146 ExecStop=/usr/bin/lncli --lnddir /var/lib/lnd stop (code=exited, status=216/GROUP)
  Process: 14142 ExecStart=/usr/bin/lnd --configfile=/etc/lnd/lnd.conf (code=exited, status=216/GROUP)
 Main PID: 14142 (code=exited, status=216/GROUP)

Jul 11 17:30:26 deb systemd[1]: lnd.service: Control process exited, code=exited status=216
Jul 11 17:30:26 deb systemd[1]: lnd.service: Unit entered failed state.
Jul 11 17:30:26 deb systemd[1]: lnd.service: Failed with result 'exit-code'.
```

### Learnings

1. Learnt a lot about user permissions.
2. Refined my bash scripting.
3. In my conv with @fonta1n3Learnt about the `--chain` flag while running bitcoind to launch bitcoind in particular network which doens't require to change `bitcoin.conf` every time.


### Next Steps

1. Resolve rpc connection issue.
2. Finish implementing c-lightning & lnd.
3. Refactor the entire script to use functions instead of a series of commands for better debugging, management of code & to avoid side effects.
4. Add Ride the Lightning, BTCPayServer, Esplora & HWI


## @watersnake1
### Summary of Work Done

## Blockchain Commons Summer Internship 2020 Weekly Report - Week 3 - Christian Murray

### Summary of Work Done
Spotbit Development:  
	* Completed `/now` API route
	* Completed `/hist` API route
	* Completed all modules detailed in the spec from milestone 1 including all helper functions
	* Added neccesary helper functions not present in the spec
	* Completed workable initial product with some bugs
	* Merged first initial PR into master branch with basic documentation.
	* Began attempting to implement the Celery Task Queue in the celery branch
Other:  
	* Informal testing of internal functions
	* Added more error checking conditions
	* Researched Celery task queues and formulated plan to implement them
	* Organized Github repo into development branch, documentation branch, and Celery branch
	* Updated documentation

### Milestone Approval Requests
Currently in progress on milestone 2. I anticipate finishing this milestone on time.

### Hours Worked
15.

### Hours Remaining
10.
