"There is a critical DoD need to develop a secure messaging and transaction platform accessible via web browser or standalone native application. The platform separates the message creation, from the transfer of the message within a secure courier to the reception and decryption of the message."
"By doing this, significant portions of the DoD back office infrastructure can be decentralized, 'smart documents and contracts' can be instantly and securely sent and received thereby reducing exposure to hackers and reducing needless delays in DoD back office correspondence. As an example, Military Interdepartmental Purchase Requests (MIPR) could be implemented using the secure ledger.”
Our team responds to DARPA's request.
What it does
Trusted spy is given enrollSecret that corresponds with enrollID. Spy destroys enrollSecret once registered. HQ destroys enrollSecret once it verifies Spy has registered. Spy adds block with a payload(secret) to blockchain. The block’s payload is hidden in the block. The block’s CCID is publicly available. Each block’s payload can be decrypted with CCID and enrollID. This slideshow illustrates the process. https://docs.google.com/presentation/d/1Xe0-jpLZ570bg-SgNV3b5ESOGDO3dL8TqeI8L9BNgRw/edit?usp=sharing
How we built it
Used IBM bluemix to host the blockchain. Used its API to communicate with our PHP and HTML files.
Challenges we ran into
Figuring out the IBM Blockchain API Creating a strong system where only trusted users are allowed to post and access information on the blockchain.
Accomplishments that we're proud of
Communicating and interacting with the blockchain was a first for the whole team. Winning 2nd prize for the IBM challenge https://www.linkedin.com/pulse/black-ops-messaging-won-ibm-second-prize-nyc-alberto-fontana?trk=prof-post
What we learned
How the IBM blockchain functions.
What's next for Black Ops Messaging