Skip to content

Commit

Permalink
Merge pull request #700 from dfinity/fix-images
Browse files Browse the repository at this point in the history
Additional image/link fixes
  • Loading branch information
jessiemongeon1 authored Feb 1, 2024
2 parents 6ef3e6a + 6137cff commit 67c46e6
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 17 deletions.
10 changes: 1 addition & 9 deletions motoko/encrypted-notes-dapp/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ We wanted to build an example of a simple (but not too simple) dapp running pure
1. Client-side **end-to-end encryption**.
2. **Multi-user** and **multi-device** support.

To demonstrate the potential of the IC as a platform for developing such dapps, we implemented this example using two distinct canister development kits (CDKs). The Motoko CDK allows developers to implement actor-based dapps using the [Motoko](/motoko/main/motoko.md) language. The Rust CDK allows implementing dapps in [Rust](/developer-docs/backend/rust/index.md). In both cases, canisters are compiled into WebAssembly files that are then deployed onto the IC.
To demonstrate the potential of the IC as a platform for developing such dapps, we implemented this example using two distinct canister development kits (CDKs). The Motoko CDK allows developers to implement actor-based dapps using the [Motoko](https://internetcomputer.org/docs/current/motoko/main/motoko) language. The Rust CDK allows implementing dapps in [Rust](https://internetcomputer.org/docs/current/developer-docs/backend/rust/index). In both cases, canisters are compiled into WebAssembly files that are then deployed onto the IC.

## Architecture

Expand All @@ -51,8 +51,6 @@ To support multiple devices per user, IC Vault employs a device manager; a canis

For further details and user stories, please refer to the [README file](https://github.com/dfinity/examples/blob/master/motoko/encrypted-notes-dapp/README.md).

![High-level architecture overview diagram of the Encrypted Notes dapp](_attachments/encrypted-notes-arch.png)

## Note management

- Users are linked to II in the frontend, getting the user a principal that can be used for calling API queries and updates.
Expand Down Expand Up @@ -100,12 +98,6 @@ Once authenticated with II:

- If a user wants to register a subsequent device, the frontend calls `register_device`, passing in the `alias` and `publickey` of that device. The frontend then calls `submit_ciphertexts([publickey, ciphertext])` for all the devices it needs to register. This allows the registered devices to pull and decrypt the AES key to encrypt and decrypt the user notes.

## Sequence diagrams

### Adding a new device

![UML sequence diagram showing device registration and synchronization](_attachments/encrypted-notes-seq.png)

## Encrypted note taking dapp tutorial

Follow the steps below to deploy this sample project.
Expand Down
8 changes: 4 additions & 4 deletions motoko/invoice-canister/docs/bounty-task-checklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -260,10 +260,10 @@ In addition to this, there's also a [Testing Glossary](TestingGlossay.md) showin
- [x] https://github.com/dfinity/invoice-canister/issues/19
- [x] Extensive Motokodoc and in-method-body comments literally everywhere / generated `dev docs`.
- [x] All testing is also extensively commented.
- [x] Standalone (non-generated) developer doc [DesignDoc.md](./docs/DesignDoc.md) covering specifications, API, security and critical aspects.
- [x] Commented [invoice.did](./invoice.did) at project's root.
- [x] Coverage in [README](./README.md) including integration of invoice canister.
- [x] [Diagram flow chart](./docs/invoice-payment-flow.png) of typical "ok" invoice lifecycle.
- [x] Standalone (non-generated) developer doc [DesignDoc.md](DesignDoc.md) covering specifications, API, security and critical aspects.
- [x] Commented [invoice.did](../invoice.did) at project's root.
- [x] Coverage in [README](../README.md) including integration of invoice canister.
- [x] [Diagram flow chart](invoice-payment-flow.png) of typical "ok" invoice lifecycle.

### [SEC-F22] Potentially sensitive invoice details are stored in plain text on the canister #26 ###
- [x] https://github.com/dfinity/invoice-canister/issues/26
Expand Down
4 changes: 0 additions & 4 deletions svelte/svelte-motoko-starter/README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
<p align="left" >
<img width="240" src="assets/logo.png">
</p>

# Svelte Dapp with Motoko & Internet Identity

This repository is meant to give [Svelte](https://svelte.dev/) developers an easy on-ramp to get started with developing decentralized applications (Dapps in short) for the Internet Computer blockchain. Dapps, also known as smart contracts are specialized software that run on a blockchain.
Expand Down

0 comments on commit 67c46e6

Please sign in to comment.