This talk was held at the Azure Meetup Berlin on March, 28th. It's the second version of this talk. In a joint development iBERA AG and Microsoft have developed a solution for the industry of food trade to exchange lab reports for pesticides and other relevant documents confirming the quality of food. Those documents go a long way from the original farmer over transport companies until finally to the food retailing. iBERA has the knowledge and hardware to check food fast for pesticides and Microsoft supported creating a solution to save documents in the cloud and to exchange them tamperproof. This talk gives insights into this joint project, the motivations and decisions, the architecture, and how we built it. Peter Kirchner is Software Engineer in Commercial Software Engineering (CSE) at Microsoft. CSE's purpose is to build together with customers and partners on new products and solutions. 

1. Blockchain in the
Food Supply Chain
Peter.Kirchner@Microsoft.com
Social everything: about.me/peterkirchner
28.05.2018 @ Azure Meetup Berlin

2. Topics
Covered
What? Why?
Architecture
Prototype
Smart Contract
Implementation
Deployment

3. Food Supply Chain
• joint project of SCS (aka iBera) and Microsoft
• prototype in 2017 H2; 2nd phase of project in planning stage
• ease current processes
• attestation of related data and documents
• focus on as little as possible use cases
• Make it happen!
Supplier Farmer
Dealer /
Wholesaler
Retailer
Retail
Stores

4. Proofs and Data Container
• „proof“ is a data container
• private and public data
• terminology will be changed in
version 2
• easy misconception in context of
blockchain (blocks, chain etc.)
• redundant terms like proof, data
entry, data container
data container
private
data
encrypted
data
public
data
plaintext
meta data
owner of
data
container
link to
previous
container

5. Architecture

6. Companies stay self-governed

7. Exchange of private data
(continuation of companies stay self-governed)

8. Deployment
Targets
Ethereum
local via geth or
testrpc/ganache
for individual
development
remote
Ethereum
network
private
(consortium)

9. Workflows
in Prototype
Workflow 2:
Receive the
proof
Receive the proof via mail
Validate the proof
Workflow 1:
Storing a Lab
Report
Receive it via mail
Store it via the Outlook Add-In
Forward the proof

10. Smart Contract
• Events
• StoreProofCompleted
• TransferCompleted
• Functions
• storeProof()
• transfer()
• … (some helper functions)
contract ProofOfProduceQuality {
struct ProofEntry {
address owner;
string encryptedProof;
string publicProof;
string previousTrackingId;
}
…
}

11. Implementation
• 3 projects
• Umbrella:
https://github.com/Azure/blockchain-supply-
chain-solution
• https://github.com/Azure/supply-chain-
office-integration
• https://github.com/Azure/supply-chain-
services
• https://github.com/Azure/supply-chain-
smart-contracts

12. Deployment Items
in Azure
• Web App
• or App Service
Environment
• Storage
• Blobs
• Tables
• Ethereum Template
• VM Scalesets
• Load Balancer
• Public Ips
• etc.

13. Deployment Modes – Pros & Cons
• Manually
• [+-] needs documentation
• [+] you know what happens after
reading documentation
• [-] repeating work while developing and
testing
• [+] if external dependencies change,
easier to adapt
• [-] risk of slips
• Templates & Scripts
• [+-] needs documentation and
• [+-] useful script comments
• [-] you (really) know what happens after
studying all scripts and templates
• [+] saves time while developing and
testing
• [-] needs time to create
• [-] if external dependencies change, you
have to troubleshoot foreign code
• [+] no risk of slips

14. Template
Structure
deploy.conf
deployScript.ps1
EthereumConsortium/
• template-webapp.json
• template-ase.json
• parameters.json
• scripts/
• configure-geth.sh
• configure-geth-azureuser.sh
• …
• …
…

15. References
GitHub https://github.com/Azure/blockchain-supply-chain-solution
Code Story https://www.microsoft.com/developerblog/2018/02/26/using-
private-ethereum-consortium-network-store-validate-
documents/
This
Presentation
Share link in Meetup event page next week.