Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Glossary #2

Open
stappersg opened this issue Oct 29, 2023 · 1 comment
Open

Glossary #2

stappersg opened this issue Oct 29, 2023 · 1 comment

Comments

@stappersg
Copy link

At https://dephy.io/introduction.html are many things in crowd.

It would be good thing to add a glossary that explains what

  • DID
  • oracle
  • ZK
  • several logos
    are.

(The idea behind this issue is to prevent more reports on What oracle? and What is Direct Inward Dailing, DID, in this project? (and maybe having a place for expressing What is DePIN?, What are Solana programs? and such.))

@jasl
Copy link
Member

jasl commented Oct 29, 2023

Most of these are blockchain-related. Let me give a brief explanation.

DePHY has two parts:

An open-sourced IoT networking solution, including firmware SDK and MQTT gateway (allowing to self-host or be a cloud service), abilities will be similar to existing solutions, such as AWS IoT.
We choose MQTT (the industry standard) here.

We hope the service can be a public good and decentralized so that people and organizations can deploy the gateway at the edge, near the end-users.
So, we're trying to build a decentralized IoT message relay network. We plan to transform MQTT to NoStr on the Internet because, in my opinion, I believe the NoStr protocol isn't as good for SNS as they claimed, but it should be suitable for IoT messages, and it has defined many features like authentication, payment, encrypted, etc.
The relay network is also open-source, so you could try your private relay network, but you have to ensure connectivity by yourself.
And you can subscribe to the relay network to build your analytics services.

You can consider DID similar to MAC address, but with cryptography, TEE (TrustZone), and eFuse, we want the DID to be tamper-proof and unique. So, the whole network can use DID and message signatures to identify the device.

Finally, we use blockchain as a payment layer. We probably do not require end-users to charge to use the networks, but we hope to get a charge from companies and share the income with volunteers who help to enhance the network.

Oracle and Zero-Knowledge are concepts of blockchain, to short, Oracle is for submitting IoT data to blockchains, and ZK provides a proof that the data is validated.
One of our motivations is that the blockchain industry seeks to connect with IoT. They call it DePIN, and we're trying to contribute in this field, so we set blockchain support as first class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants