Process: Exploration starting 2016-05-27 ending 2016-05-27

If you were logged in and working on this process, you would log your work on this page.

Outputs

Scheduled:

Document - Documentation 1.00 Idea due May 27, 2016
Completed: produces 1.00 Idea May 27, 2016
  Resource: Document - Documentation: Education & Literature review 1.00 Idea

Work

Planned Work: (Requirements are ordered by due date)

Work - Analysis and Strategy: 1.00 Time - Hours due May 27, 2016

Analyse the information gathered by different affiliates and extract the essential, produce synthesis, reformat in a more coherent way, extract next steps of the project from it.

Unassigned
Work events:
May 31, 2016 1.30 Time - Hours Done by mikecohen

We spent the later half of the hangout on may 30th identifying upcoming challenges ("blockers") and specifying the content of the upcoming project update (blochain explained in laymens terms)

See Abran's meeting notes for details

May 31, 2016 1.50 Time - Hours Done by Jim

Continued hangout with Mike and Abran. discussed blockers.

May 31, 2016 1.50 Time - Hours Done by Valentin

Discussion with Mike, Jim

Work - Training others: 1.00 Time - Hours due May 27, 2016

Help affiliates get up to speed with the work done here.

Unassigned
Work events:
June 3, 2016 4.00 Time - Hours Done by Valentin

Discussion with affiliates about BC, protocols, proof and stuff

Work - Information mining: 1.00 Time - Hours due May 27, 2016

Search information sources for pertinent information, filter and curate.
If you read and document log that under documentation.
You can use Diigo
https://www.diigo.com/user/tiberiusb/blockchainaccess_project?type=all&snapshot=no&sort=updated
with Tags "blockchainaccess_project" and "paper" or "book"
You can also use other tools to build a list of references.

NOTE that this work requires reading. Log all time spent, but just make sure you justify.

Unassigned
Work events:
June 15, 2016 4.00 Time - Hours Done by FrancoisE

Research and resume wroting on Externality

June 3, 2016 3.00 Time - Hours Done by Valentin

cf Synthesis on the doc called exploration phase

June 3, 2016 6.00 Time - Hours Done by Tibi

Searched the web and read documents.

Curated using Diigo
https://www.diigo.com/user/tiberiusb/blockchainaccess_project?type=all&snapshot=no&sort=updated

and in the Exploration doc.
https://docs.google.com/document/d/1qlFmaD14IJ-BslXCVIccF8Yrzg5EAbSs-u17DyAZ8-M/edit#

I also restructured the Exploration doc, branded it, added summary section, etc.

June 2, 2016 3.00 Time - Hours Done by Jim

Went deeper into immutability of the blockchain data structure and the different safeguards based on the block-adding mechanisms and rules of different blockchains
Produced a presentation: .https://docs.google.com/presentation/d/10BI2gld3ZNXdzHT0crkVopPH0w2mdt3xz-HGFv9ra38/edit?usp=sharing
Reference links:
https://d28rh4a8wq0iu5.cloudfront.net/bitcointech/readings/princeton_bitcoin_book.pdf
https://bitsonblocks.net/2016/02/29/a-gentle-introduction-to-immutability-of-blockchains/

May 30, 2016 0.60 Time - Hours Done by Tibi

reading sources of info relevant for the info structure I created in the Exploration phase doc. I log the rest as Documenting, which is writing from my own experience and whatever I found while mining.
one example of mining is my reading of the Partner state.
https://diigo.com/08mb20

May 25, 2016 5.00 Time - Hours Done by Jim

Deep research on the state of consensus protocols that lead to building a presentation. White papers were added to the project drive:
https://drive.google.com/open?id=0B-s1IR1iOMsNOFdBS3RZcDMtZm8
Other links:
Ethereum research gitter: https://gitter.im/ethereum/research
Casper protocol research: https://www.youtube.com/watch?v=syn0ZWMC4xs&list=PLsMIFzUId4x-rGmX-Jrg8wtvTR1BYwvKb

Work - Documenting: 20.00 Time - Hours due May 27, 2016

Create summaries of your reading, in a way that you can save time to other affiliates, if they want to integrate the same information.
While documenting, also think that your summaries can be picked up in reports.
Other will use your summaries to analyse and strategize.

Work stigmergically!

Unassigned
Work events:
June 13, 2016 2.00 Time - Hours Done by Jim

Formulated a response to some of Manon's questions:
https://docs.google.com/document/d/155hnYVgOIvv-LdfftNckuGbviJmWgH4V3VJy8gvGDT8/edit?usp=sharing
Uploaded to eVision's CRM

June 4, 2016 6.00 Time - Hours Done by Jim

Prepared a presentation on immutability and the blockchain, what it means, how the mechanics work and the difference with PoW and PoS also public and private chains. There is also a comparison to how current systems work. We can work this into the main study as the performance indicator for the data structure and how it preserves data integrity.
https://docs.google.com/presentation/d/10BI2gld3ZNXdzHT0crkVopPH0w2mdt3xz-HGFv9ra38/edit?usp=sharing

June 3, 2016 0.50 Time - Hours Done by Tibi

Wrapped up the project progress report and sent to eVision.
https://ezone.evision.ca/display/InterSpace/Progress+Reports

June 1, 2016 1.00 Time - Hours Done by Jim

Produced a general description of blockchain technology and assessment of the confusion around it in an effort to frame it for the study.
https://docs.google.com/document/d/1G_GAD-NcZTIYXH1nRC6g_590e5JLphKGK0JOGMXjDT8/edit?usp=sharing.

May 31, 2016 2.50 Time - Hours Done by mikecohen

Started working on outline for project update as per agreed in meeting (may 30)

Providing clear and jargon free explanation of a blockchain as a data structure
https://docs.google.com/presentation/d/1Ot0fNFg_I1yvGK9JZwbO7UCT3WTviS9uyAs0IJltDKE/edit?usp=sharing

May 31, 2016 3.00 Time - Hours Done by Jim

Worked done on the following presentation: Why private blockchains?
https://docs.google.com/presentation/d/11sUT6MYD5BE9Bn0qlakM0utSmCvyjyTxA9R_oeLkiqA/edit?usp=sharing

May 30, 2016 2.50 Time - Hours Done by Tibi

updated the intro in the Exploration doc, and developed my section. see doc history for proof. I had to reconfigure my structure and to add content. I transferred text I wrote to my blog here, and left a link.
http://multitudeproject.blogspot.ca/2016/05/the-sharing-collaborative-and.html

May 27, 2016 3.00 Time - Hours Done by Jim

Work done on the following presentation: Consensus protocols, to showcase the strengths, weaknesses and applications of each.
https://drive.google.com/open?id=13fAP_xOeniTw0WiQD7UZW-XreW3rK7vPtNILTk_cork

Work - Meeting: 50.00 Time - Hours due May 27, 2016

Log time spent on meetings here. Mention the people you were in a meeting with and link to a meeting notes doc.

Unassigned
Work events:
July 6, 2016 4.00 Time - Hours Done by FrancoisE

Meetings and panel at communautique.

June 3, 2016 3.00 Time - Hours Done by Jim

Tibi, Mike, Abran, Yannick, Valentin, Francois and myself met to discuss:

- Share latest info gathered from exploration phase

- What to show for the upcoming progress report

- Upcoming challenges (openness of KABA to helping with API and dev, determing topology, spec and requirements for existing gov. infrastucture)

- Project governance and VAS equation details (how to remunerate info mining - distinguishing irrelevant research from relevant research unused in final document from relevant research used in final document)

- Jim shared the hangout link on an ethereum discussion board and a few curious onlookers joined

See link for details: https://www.youtube.com/watch?v=hXlfhSKqqoM

June 3, 2016 1.00 Time - Hours Done by Tibi

Hangout, meeting - no need to list participants, because a video was recorded.
https://www.youtube.com/watch?v=hXlfhSKqqoM

June 2, 2016 2.50 Time - Hours Done by Jim

Went with Mike and Tibi to eVision - see Mike's log for details

May 30, 2016 3.00 Time - Hours Done by Valentin

Meeting Mike, Tibi, Jim, ..

Unplanned Work:

Work event: Work - Training others 1.00 Time - Hours June 8, 2016 Done by Jim

Help Tibi understand what a smart contract is, in the context of blockchain technology.

Work event: Work - Meeting 3.00 Time - Hours May 30, 2016 Done by mikecohen

Tibi, Jim, Abran, Yannick, Valentin, Francois and myself met to discuss:

- Share latest info gathered from exploration phase

- What to show for the upcoming progress report

- Upcoming challenges (openness of KABA to helping with API and dev, determing topology, spec and requirements for existing gov. infrastucture)

- Project governance and VAS equation details (how to remunerate info mining - distinguishing irrelevant research from relevant research unused in final document from relevant research used in final document)

- Jim shared the hangout link on an ethereum discussion board and a few curious onlookers joined

See link for details: https://www.youtube.com/watch?v=hXlfhSKqqoM

Work event: Work - Facilitation and coordination 0.75 Time - Hours May 30, 2016 Done by Abran

Started discussion on Sensorica CRM about some aspects of governance, the role of project responsible, budget allocation for business building work.

Poll for business building rewards
http://crm.sensorica.co/t/poll-budget-allocation-for-marketing/180?u=abran

Project Governance
http://crm.sensorica.co/t/defining-the-scope-of-this-project/181?u=abran

Summarizing meeting and actions to be taken
http://crm.sensorica.co/t/things-to-do-notes-from-meeting-on-30th-may/172?u=abran

Role of Project Responsible

Work event: Work - Meeting 3.00 Time - Hours May 30, 2016 Done by Abran

Meeting with Jim, Tibi, Mike, Mr.King and others.

Details provided by Mike in his log.

Citations

Unplanned Citations:

Cited: The Partner State p2pFoundation post 1.00 Idea May 30, 2016

Process context:

Pattern: Documentation
Context: Access
Order: Work order 218 , Exploration due: 2016-05-27

Previous processes:

Next processes:


Process notes:

This is the process to log exploration time, which is essentially literature review and mapping.

At the same time use this opportunities to sharpen your knowledge about block chain and its applications. You are getting paid to learn and teach others!

Open document
https://docs.google.com/document/d/1qlFmaD14IJ-BslXCVIccF8Yrzg5EAbSs-u17DyAZ8-M/edit

NOTE: a log is a claim for revenue. Anyone can raise a RED FLAG and question a log.
Logs must be documented and traceable.
Misleading the group can induce lose of reputation, which affects the ability to extract value from this project.