-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
7 changed files
with
160 additions
and
63 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,23 +1,47 @@ | ||
# 🏗️ Core Technologies | ||
|
||
## 🔐 Zenroom | ||
Zenroom is responsible for all underlying cryptographic operations within the DiDRoom ecosystem. It provides a secure execution environment for cryptographic operations and smart contracts, ensuring privacy, security, and integrity in digital interactions. Notably, Zenroom runs isomorphically on the web, mobile, and servers across various platforms in a deterministic way. | ||
- [Documentation](https://dev.zenroom.org/) | ||
- [GitHub](https://github.com/dyne/zenroom) | ||
- [Site](https://zenroom.org/) | ||
Zenroom is responsible for all underlying cryptographic operations within the Didroom ecosystem. It provides a secure execution environment for cryptographic operations and smart contracts, ensuring privacy, security, and integrity in digital interactions. Notably, Zenroom runs isomorphically on the web, mobile, and servers across various platforms in a deterministic way. | ||
|
||
::: tip RESOURCES | ||
|
||
[Documentation](https://dev.zenroom.org/) | ||
|
||
[GitHub](https://github.com/dyne/zenroom) | ||
|
||
[Site](https://zenroom.org/) | ||
|
||
::: | ||
|
||
## 📜 Slangroom | ||
Slangroom enhances the Zencode language of Zenroom by allowing the addition of plugins. These plugins extend the functionality of Zencode by enabling actions that do not necessarily need to be performed within virtual machines. Slangroom's approach is super standard, making it easy to add custom functionalities within the Zencode natural language. Additionally, Slangroom is capable of running over web pages using WebAssembly. | ||
- [Documentation](https://dyne.org/slangroom) | ||
- [GitHub](https://github.com/syne/slangroom) | ||
|
||
::: tip RESOURCES | ||
|
||
[Documentation](https://dyne.org/slangroom) | ||
|
||
[GitHub](https://github.com/syne/slangroom) | ||
|
||
::: | ||
|
||
## 🛠️ No-code-room (NCR) | ||
No-code-room is a Single Executable Application (SEA) for Linux. It takes a filesystem with .zen (Zencode/Slangroom) contracts and creates API microservices using live-directory routing. NCR seamlessly generates REST services that are auto-documented with OpenAPI. Additionally, it creates small graphic interfaces on the fly, referred to as applets. | ||
- [GitHub](https://github.com/forkbombeu/ncr) | ||
::: tip RESOURCES | ||
|
||
[GitHub](https://github.com/forkbombeu/ncr) | ||
|
||
::: | ||
|
||
## 🔗 Dyne.org Decentralized Identifiers (DID) Service | ||
In 2022, Dyne.org implemented a W3C-DID method approved by the W3C governing board and included in the official DID method list. The DID service supports federation and provides tools for the creation, resolution, and management of decentralized identifiers (DIDs). It includes support for ECDSA, EDDSA, Schnorr, Ethereum address, as well as a Dilithium quantum-proof public key. | ||
- [GitHub](https://github.com/dyne/w3c-did) | ||
- [Online DIDs Explorer](https://explorer.did.dyne.org/) | ||
- [Specification](https://dyne.org/W3C-DID/) | ||
- [Site](https://forkbomb.solutions/component/w3c-did-federate-service/) | ||
::: tip RESOURCES | ||
|
||
[GitHub](https://github.com/dyne/w3c-did) | ||
|
||
[Online DIDs Explorer](https://explorer.did.dyne.org/) | ||
|
||
[Specification](https://dyne.org/W3C-DID/) | ||
|
||
[Site](https://forkbomb.solutions/component/w3c-did-federate-service/) | ||
|
||
::: |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,70 @@ | ||
# 🎮 Quickstart | ||
|
||
Get started quickly with Didroom by choosing one of the following deployment options: | ||
|
||
## Software as a Service (SaaS) | ||
|
||
If you prefer a hassle-free experience and want to start using Didroom without setting up infrastructure, our Software as a Service (SaaS) option is the way to go. Follow these steps to get started: | ||
|
||
1. Sign up for a Didroom account on our website. | ||
|
||
<video controls="controls" src="https://raw.githubusercontent.com/ForkbombEu/signroom/36065ffc2f8ae76598e653eaf85296ef1f41ba2a/screenshots/videos/registration.webm" /> | ||
|
||
2. Access the Didroom Control Room/Dashboard to setup you credential services | ||
|
||
For more detailed instructions, visit [Software as a Service (SaaS) Quickstart Guide](/quickstart#software-as-a-service-saas). | ||
|
||
## On-Premise Deployment | ||
|
||
For users who prefer full control over their infrastructure and data, Didroom supports on-premise deployment. Follow these steps to deploy Didroom on your own infrastructure: | ||
|
||
### 1. clone the repo | ||
|
||
```bash | ||
git clone --recursive https://github.com/forkbombeu/signroom | ||
``` | ||
|
||
::: warning | ||
|
||
Pay attention at the `--recursive` that will clone also the sub repositories! | ||
|
||
::: | ||
|
||
### 2. run the dashboard | ||
|
||
```bash | ||
cd signroom | ||
docker compose up --build | ||
``` | ||
|
||
this will run the backend of the dirdroom control room available on the network at | ||
|
||
```http | ||
http://localhost:8090/_ | ||
``` | ||
|
||
::: tip | ||
Pay attention at the final underscore, of the address | ||
::: | ||
|
||
### 3. login to the admin panel | ||
|
||
A default administrator user is created with the following defaults: | ||
|
||
**user**: `[email protected]` | ||
|
||
**pass**: `adminadmin` | ||
|
||
### 4. Setup the DID service | ||
|
||
The only reaquired step to be configure is the DID federated service. | ||
You can ask for your admin domain/context as specified on [`dyne/W3C-DID`](https://github.com/dyne/W3C-DID?tab=readme-ov-file#claim-your-own-domain-context-as-an-admin) | ||
|
||
Follow the video: | ||
|
||
1. login into the dashboard | ||
2. go on the `features` collection | ||
3. select the `DID` feature | ||
4. insert you admin data | ||
|
||
<video controls src="https://raw.githubusercontent.com/ForkbombEu/signroom/main/screenshots/videos/setup-did.webm" /> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters