# Internship Project Milestones

At least two: a middle one, and what you want to end with in August!

## Collin:
* Mid-July: Substantial amount of terms gathered and sorted. All terms will have proper legal source attached.
* End: Document is clearly organized, aesthetic, and mind-map is inserted into the document for each term.
___
## Chaitika [Support : Shoryak]:
* July Third week: Research and First Draft complete in an sequential format as suggested in the To-Do list.
* End: Final document that has categorically subdivided text; in a format that is acceptable for version 3.
#### Update:
* Created the draft document.
* Covered introduction to schnorr, adaptor signatures and others.
* it's link https://hackmd.io/@ji_LY7wfSaq0dviMlEd-Jg/r1sK3JDTc
## Shoryak:
* July Third week: Set up the github repository for integrating tf bip322 signing to btcdeb
* End: Add two commands to tf functionality in btcdeb one for signing which allows to sign using an address and privatekey and one verify message command.
* **tf signmessage [address] [message] [privKey]**
* **tf verifymessage [address] [message] [signature]**
## Davis

* July Third week: Improve Spotbit Documentation.
* End: Improve integration of the web frontend
Pull request reviewed and merged with the following [updates](https://github.com/BlockchainCommons/spotbit/pull/79) to Spotbit
* Serving static content in JavaScript disabled environment
* Restructure and update the frontend code the FastAPI way
* Write the API routes to serve the front-end
* Add about page and update the new Blockchain Commons logo
* Update README with instructions to setup development environment.
* Support: **Ehnamuram Enoch**

##### Technical Debt
Wasn't able to write request to parse the data to the frontend because the API still being cleaned up.

##### Future Plans
I intent to contribute more to Spotbit. Also interested in working on Mori-cli once my rust is good enough.

## Enoch
* July Third Week: Read on the brand and message of Blockchain commons and how this brand is properly communicated in other project website. Seeing that the main use case is to provide consistency on Bitcoin Esplora that correlates with other web projects.
* End: Update the website frontend by making modifications as well as improve accessibility with torgap, These modifications will be made in such a way that consistency is attained.
* Support: **Davis Bwake**

#### Update
Created a pull request with the esplora redesign
* Created a fork of Blockstream esplora for Blockchain Commons esplora
* Made changes to the webpage frontend
* Added proof of concept as well as tor link
* Added About Bitcoin Esplora on the page.
* Made changes to the config file. deploy_esplora.sh on the linode server
* Linked esplora directory on the server to the new Bitcoin esplora fork.
* Added more environment variables to be used by the new Blockchain Common esplora fork
* Sent to deymow to open pull request for the esplora instance.

#### Technical Debt
* Wasn't able to make the changes go live on the bitcoin esplora server
* Docker file was not properly updated and hence changes do not reflect on the server

#### Future Plans
I intend to keep working on bitcoin esplora instance for blockchain commons, and keep adding updates to it. Also planning on venturing into other blockchain commons related projects in the future.

## Shikhar Vashistha

* **Primary**: *Integrate/Update a New C Library into LBTCftCL*
* **July Third Week**: Research and start with initial implementation/improvement of new C library in LBTCftCL* i.e. *`libbitcoinrpc`*
* **End**: Update the the library & documentation to include the new features accordingly.
* (Comments: Contact Shannon about reproducing the C build bug, when you a repo, let Shannon know) - Fixed the error as desired and commented in the issue.

* **Seconday/Supporting**: *Update DIDs for secp256k1 as per BIP39* **&** *Stand-Alone BIP-322 (Generic Signed Message Format Leveraging Bitcoin Script) CLI App*

### Update :
* Fixed the issue in `libbitcoinrpc` and the [pull request](https://github.com/BlockchainCommons/libbitcoinrpc/pull/1) has been merged to the fork included [changelog.md](https://github.com/shikharvashistha/libbitcoinrpc/blob/fix/implementation/CHANGELOG.md) with the code.
* Created a [pull request](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/pull/589) to update the course as well and that's merged as well.

# Deymow:

* **Project:** BIP0322 Implementation using Jupyter Notebooks
A well written documentation on BIP 322 Implementation using Jupyter Notebooks has been created
https://hackmd.io/Z1d9ge45Rwaq5xovc_AqSw?both
* **Update:**
i) I created PR for all the project achieved by Blockchain Common's interns
ii) A Method of Procedure has been developed on how to submit a PR
https://hackmd.io/8r5SFywPSuq6UzyU5GJQCQ
iii) I have spinned up a small vm on AWS cloud. On this server, I have been able to clone the BIP322 repo by wip-abramson, install all necessary dependencies which include buidl whose script engine supports taproot
iv) I have also been able to launch jupyter server and currently, I am running the notebooks (signing notebook and verification notebook)
v) In time past, I researched on how to categorise discussions in Blockchain Commons GitHub Community.
https://github.com/BlockchainCommons/Community/issues/157
* **Feedback:**
My documentation has been shared with Will Abramson and he advised me to try and apply bip322 to some usecase and document it in notebooks if interested

# Deepika:

**Project:** Update DIDs for secp256k1 as per BIP 39

* * *July Third Week:* Explore what Schnorr signature for secp256k1 can offer leveraging k1 multisig to DIDs and Verifiable Credentials.
* * Generate test vector schnorr signature for secp256k1.
* * End: "application/did+cbor" contains hexadecimal data, generate a 12-word mnemonic sentence from that.
* (comment: you might want to look at bc-bytewords)
* two problems: did:key (type:ENCONDEDBYTES)
* bitcoin does 32 byte x-only pubkey
* others do 33 byte pubkey (x & y)
* 32 -> 33 byte Conversion: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-July/020663.html
* signature: 64 bytes, we CBOR. Existing tags?
* Update: Ran txid2txref and experimenting with createBtcrDid on testnet

# Devesh:

* **Project:** Improve Lightning Node Documentation and add new chapters
* **Updates:** Lightining node is setup and contents of 2 chapters are planned, just need to finalise ideas and prepare drafts

* **Milestones:**
* **July 3rd Week:** Complete the entire planned chapters and start planning for a further developed guide
* **End:** To add as much content as possible to the repository, a lot of aliasing work had to be done which can be explained in the notes.

# Eunoia:

**Project**: Mori-CLI
**Milestones**:
* July third week: Explore alternative ways to achieve the aim of Mori-CLI and understand the progress done so far in this project.
* End: Generate descriptor for B i.e the user who will be able to spend after N blocks
* Improve error handling and add tests