Add demo projects for Web3 scenarios #150

DemesneGH · 2024-11-26T13:27:12Z

This PR introduces a new projects/ directory dedicated to demo projects that showcase real-world applications. These projects are more complex and feature-rich than the examples in the examples/ directory.
Additionally, we are releasing a basic ETH wallet project for the Web3 scenario.

As outlined in projects/README.md, our goal is to provide developers with practical reference implementations that demonstrate how to effectively use the SDK in real-world scenarios. Currently, we are focusing on Web3-related projects, with plans to expand to additional scenarios in the future.
We believe these demo projects will be valuable resources for developers looking to build TAs tailored to real-world requirements.

b49020 · 2024-11-26T14:37:39Z

Thanks @DemesneGH for this PR. It's really nice to see real world use-cases supported upstream. Care to write some tests for this project?

ivila · 2024-11-29T06:37:34Z

Actually during my development, I will use git path for teaclave dependencies, it's more convenient as can be use cross my team (and we use no_std).
For example, when I want to use optee-teec, I just type the following:

cargo add optee_teec --git https://github.com/apache/incubator-teaclave-trustzone-sdk.git --branch main

And in cargo it will:

[package]
name = "demo"
version = "0.1.0"
edition = "2021"

[dependencies]
optee-teec = { git = "https://github.com/apache/incubator-teaclave-trustzone-sdk.git", branch = "main", version = "0.2.0" }

b49020 · 2024-11-29T07:22:56Z

Acked-by: Sumit Garg <sumit.garg@linaro.org>

b49020 · 2024-11-29T07:28:37Z

Actually during my development, I will use git path for teaclave dependencies, it's more convenient as can be use cross my team (and we use no_std).

Agree that's better for development. In case of deployment it's better to use released version of OP-TEE crates here:

https://crates.io/crates/optee-teec
https://crates.io/crates/optee-utee

@DemesneGH is releasing new version of crates still on your ToDo list?

DemesneGH · 2024-11-29T07:46:28Z

@DemesneGH is releasing new version of crates still on your ToDo list?

Yes it is. Let me figure out the release process on crates.io.

DemesneGH · 2024-11-29T08:03:20Z

Yes it is. Let me figure out the release process on crates.io.

@mssun Could you help to add my account as the owner of these 5 crates?:

https://crates.io/search?q=optee-

Seems the operation is:
cargo owner --add DemesneGH (Reference: https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner)

DemesneGH · 2024-11-29T08:08:13Z

Actually during my development, I will use git path for teaclave dependencies, it's more convenient as can be use cross my team (and we use no_std).

@ivila BTW could you share some information about what your team is working on with this SDK, such as the specific scenario? We're gathering real world use cases and would greatly appreciate your input.

mssun · 2024-11-30T06:16:55Z

Yes it is. Let me figure out the release process on crates.io.

@mssun Could you help to add my account as the owner of these 5 crates?:

https://crates.io/search?q=optee-

Seems the operation is: cargo owner --add DemesneGH (Reference: https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner)

Done. Please check and let me know if it's okay.

DemesneGH · 2024-12-03T02:54:53Z

Done. Please check and let me know if it's okay.

It works, thanks! @mssun

ivila · 2024-12-03T03:02:57Z

Actually during my development, I will use git path for teaclave dependencies, it's more convenient as can be use cross my team (and we use no_std).

@ivila BTW could you share some information about what your team is working on with this SDK, such as the specific scenario? We're gathering real world use cases and would greatly appreciate your input.

@DemesneGH Sorry I miss your response, we are using it for trusty computation, for example, PIR(private information retrieval), deep learning. We used to develop by C, and it's painful as we always met problem like memory leak or memory fault(use after free), use teaclave really helps a lot.

DemesneGH · 2024-12-04T09:13:22Z

@DemesneGH Sorry I miss your response, we are using it for trusty computation, for example, PIR(private information retrieval), deep learning. We used to develop by C, and it's painful as we always met problem like memory leak or memory fault(use after free), use teaclave really helps a lot.

@ivila Thanks for your insights, issues, and PRs over the past few days. We really need polish the Rust SDK better for real-world use cases. Please feel free to discuss any problems you encounter with us.
Additionally, we would also appreciate contributions to the real-world examples, such as a minimal demo for deep learning, etc. If you're interested please feel free to open the PR, thanks!

DemesneGH · 2024-12-04T09:22:56Z

Actually during my development, I will use git path for teaclave dependencies, it's more convenient as can be use cross my team (and we use no_std). For example, when I want to use optee-teec, I just type the following:
cargo add optee_teec --git https://github.com/apache/incubator-teaclave-trustzone-sdk.git --branch main
And in cargo it will:
[package]
name = "demo"
version = "0.1.0"
edition = "2021"

[dependencies]
optee-teec = { git = "https://github.com/apache/incubator-teaclave-trustzone-sdk.git", branch = "main", version = "0.2.0" }

Actually during my development, I will use git path for teaclave dependencies, it's more convenient as can be use cross my team (and we use no_std).

Agree that's better for development. In case of deployment it's better to use released version of OP-TEE crates here:

https://crates.io/crates/optee-teec https://crates.io/crates/optee-utee

@DemesneGH is releasing new version of crates still on your ToDo list?

Release 0.2.0 for 6 optee- crates have been published in crates.io: https://crates.io/search?q=optee
Now we can import the crates by optee-teec = "0.2.0". For reference the code version for these 0.2.0 release is 20e6988 .

The crates will be updated accordingly with each future release (the next planned release is 0.3.0).

m4sterchain · 2024-12-05T16:29:11Z

projects/web3/eth_wallet/README.md

+- Transaction Signing: Signing Ethereum transactions without exposing private
+  keys to the normal world.
+- Key Erase: Erasing keys when they are no longer needed.
+


Could you please add

Security assumptions for this example if possible.

Disclaimers.

Doc updated, please check, thanks!

m4sterchain · 2024-12-05T16:37:34Z

projects/web3/eth_wallet/ta/src/main.rs

+
+    Ok(proto::CreateWalletOutput {
+        wallet_id,
+        mnemonic,


Please highlight the security assumption and potential risks for returning mnemonic in this sample TA.

doc updated

projects/web3/eth_wallet/ta/src/main.rs

- eliminate unwrap(); - sync ta_static.rs from a6b5cfb

projects: add basic eth wallet demo

c9b4187

DemesneGH requested a review from m4sterchain November 26, 2024 13:28

DemesneGH added 4 commits November 27, 2024 03:57

Add test script for projects/eth_wallet

e236453

ci: build projects (std only)

f9cb97d

project: add license for eth_wallet/tests.rs

4c86df3

projects/doc: add new for eth_wallet and format

3bca04b

m4sterchain reviewed Dec 5, 2024

View reviewed changes

DemesneGH added 2 commits December 6, 2024 03:56

eth_wallet/ta: eliminate unwrap()

ba94f98

- eliminate unwrap(); - sync ta_static.rs from a6b5cfb

eth_wallet/doc: add security assumptions

0e1dab7

m4sterchain approved these changes Dec 10, 2024

View reviewed changes

DemesneGH merged commit edcb7a2 into apache:main Dec 12, 2024
7 checks passed

DemesneGH mentioned this pull request Jan 23, 2025

[DISCUSSION] Release Version Number and Schedule #165

Open

Add demo projects for Web3 scenarios #150

Add demo projects for Web3 scenarios #150

Uh oh!

Conversation

DemesneGH commented Nov 26, 2024

Uh oh!

b49020 commented Nov 26, 2024

Uh oh!

ivila commented Nov 29, 2024

Uh oh!

b49020 commented Nov 29, 2024

Uh oh!

b49020 commented Nov 29, 2024

Uh oh!

DemesneGH commented Nov 29, 2024

Uh oh!

DemesneGH commented Nov 29, 2024

Uh oh!

DemesneGH commented Nov 29, 2024

Uh oh!

mssun commented Nov 30, 2024

Uh oh!

DemesneGH commented Dec 3, 2024

Uh oh!

ivila commented Dec 3, 2024

Uh oh!

DemesneGH commented Dec 4, 2024

Uh oh!

DemesneGH commented Dec 4, 2024

Uh oh!

m4sterchain Dec 5, 2024

Choose a reason for hiding this comment

Uh oh!

DemesneGH Dec 6, 2024

Choose a reason for hiding this comment

Uh oh!

m4sterchain Dec 5, 2024

Choose a reason for hiding this comment

Uh oh!

DemesneGH Dec 6, 2024

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.