nuCypher Walkthrough (WIP)

  • Person A (Alice) takes data (in this example) and enters it into the computer. She creates a policy describing what people should have access to the data and when it expires.

  • The computer (Enrico) generates a symmetric key and encrypts the data; then it encrypts the symmetric key with Alice’s public key (capsule).

  • The header (capsule) is essentially  a randomly generated key from the computer (Enrico: think password generator) that can decode the data in the rest of the message.

  • The encrypted data + header is uploaded to IPFS.

  • Person B (Bob), who wants to read the data, downloads the encrypted data + header and sends only the header to a number of proxy re-encryption nodes (Ursula), which re-encrypt the header with Bob’s public key. They send back this header, which Bob can decrypt with his private key thanks to the magic of proxy re-encryption.

  • Person B uses the header, which contains the decrypted symmetric key, to read the rest of the data.

Will be adding more explanation and nuance later, but this is a basic walkthrough about how we tried to visualize and understand nuCypher. Please feel free to correct us or connect with us!

For a more in depth explanation, see

MakerDao's Dai and Delphus

Rationale for Tutorial

While Dai is a useful tool and allows for stability of a platform, there are not many instructions on how to implement this token into either a new Distributed Application or an existing one. Further, existing documentation does not appear to exist with few understandable comments, which, to be fair, is somewhat understandable with such a new implementation.

MakerDao’s official chat has been more than helpful, but we believe that it may allow for easier integration if there was a documented journey from start to finish, including the most common errors found, it may be useful for others.

We will be showing snippets of our code as we implement them, and our full source code will be released at the public release (we aim to be open source).

Thank you for joining us on this journey, and we hope that it ends up working for both you and us.

MakerDao's Dai and Delphus

Why does Delphus use Dai?

If you don’t know what Delphus is and would like to know more, please check out our earlier post here as well as our website here.

As you may already know, the one issue most have with cryptocurrencies is the overall volatility of most networks.

For example, Bitcoin, mostly due to surrounding hype and a positive relationship between investors and miners, spiked in prices, reaching $20,000 back in December, but then “normalizing” down to its current price of around $8,000.

These increasingly different prices, often with no correlation to any conventional market trends to the average user, provide for a marketplace not useful for many cases in which a static amount of value may need to be stored. This is the case with Delphus as the researcher -> participant payments cannot change in value throughout the duration of the study.

There are many viable options for addressing this issue, with new stablecoins appearing every so often. The stablecoin most prominent, trusted and well supported by developers as of now is MakerDao’s Dai. It is tied 1:1 with the US dollar with very few deviations of non-discernible value (>.01 cents). It is collateralize using valuable assets in the open-source Maker contract.

For this reason, it is far easier for researchers to set static payments that can be distributed through smart contracts, rather than relying on the rise and fall of a cryptocurrency. Since we rely on the Ethereum Blockchain, we can use the ERC20 token, Dai, in order to keep stable prices and allow both researchers and patients an easy way to receive non-volatile payments.

This allows us to garner better communication between the researcher and the patient, while reducing the risk of patients not receiving their specified payment or complaining about how what could be $1,000 the first day, is $5 the next day (they probably won’t be complaining if the price increases). Further, as Dai is being continuously developed and scaled with them introducing more collaterals to their system, it is ideal for the ever-expanding field of medicine and clinical trials.

Thus, we arrived at the logical conclusion of incorporating Dai into our project and we’d like to share with any interested parties, the entire process of its integration.

edited product name from reblock to Delphus

Scintillating News

Our Plans for the Future

Welcome to the official blog of Scintillating and Delphus.

In this blog, we would like to talk about the development of our product.

In an age of increasing lack of privacy, evidenced by corporations like Facebook and Amazon, data is easily sold off and not valued by corporations. The medical field specifically faces a large problem when dealing with the results of studies; data transparency is nonexistent in comparison to the quantity of available data from said studies. An estimated 90% of study results are never released, preventing others from building upon their work and creating an open scientific community. Even if obtained, sensitive data is difficult to secure from alteration or tampering which creates issues with study transparency and consent in the long term. Finally, discovering participants is costly and time-consuming, while the budget of many researchers is comparatively not enough to deal with these issues alone.

Researchers need software that can cut costs and save time. They require tools capable of managing payments and securing data. Patients need a greater access to their own data and a larger degree of privacy.

While other companies have developed their own clinical trial management platforms in an effort to solve these issues, these conventional systems often create new problems. They do little to preserve the results of completed studies for future researchers and breed distrust due to a lack of transparency. Thankfully, these issues can be solved via the blockchain which allows for immutable and transparent studies through smart contracts. Using Delphus, the blockchain-based decentralized study management system, all of these problems are solved.

Delphus is our flagship product that aims to improve clinical studies by modernizing the workflow of researchers’ data submission and collection.

By using the blockchain, we can dramatically cut down the costs of data management and are able to improve communication between participants and researchers through trustless smart contracts.

We aim to finish the minimum viable product of Delphus by the end of July, which includes these features:

  • COM token (with dividends)
  • Uploading consent forms, consent recording
  • The ability to create a study with custom fields
  • Integrated participant database
  • Encrypted upload of data points to IPFS
  • Distribution of funds to patients through ETH
  • DAI as intermediary currency for stability
  • Importing/exporting data points
  • Comprehensive system for adding data fields to allow for customizable studies
  • Seamless tutorial and smoothly flowing UI

By implementing all of these features, we can solve the key issues that worsen the experience for both researchers and participants. After this, we will do extensive testing before expanding to local colleges.

If you would like to learn more, you can visit our website here.

edited product name to Delphus