Target mobile devices

[richard-ramos]

Zerokit can be succesfully compilled to mobile architectures with rustup or https://github.com/cross-rs/cross, but using this library would still require some dev work, as described in these links:

• https://mozilla.github.io/firefox-browser-architecture/experiments/2017-09-21-rust-on-android.html
• https://mozilla.github.io/firefox-browser-architecture/experiments/2017-09-06-rust-on-ios.html

In golang, we have gomobile which simplifies this work. We should look for a similar tool for rust projects or consider writing a script that would generate a .aar file for Android with the common architectures (x86_64, x86, armeabi-v7a and arm64-v8a) and a .xcframework for ios (ios-arm64 and ios-arm64_x86_64-simulator)

[oskarth]

@AtHeartEngineer @fryorcraken are there specific use cases that you think having e.g. RLN on mobile would be useful for?

[fryorcraken]

Any use case that applies to the browser applies to mobile.

In regards to shipping this issue, I believe it is easier to build PoCs for the browser, so as long as we are prototyping, browser + nwaku should be enough.

Once we have a platform considering using RLN then we will need to deliver for mobile too. So I would time that/review this around mainnet readiness for RLN. Apart if a platform reaches out and would like to prototype on mobile.

[oskarth]

We already have browser PoC but not mobile PoC.

This issue is also about Zerokit/RLN in general, and to make it easier for people who want to do ZK dev on mobile. Right now there's no good story for this, and we aren't far from making Zerokit useful on mobile.

[AtHeartEngineer]

I can't think of any that would be useful on mobile that wouldn't also run in the browser/wasm. I think wasm is probably the most important target.

[s1fr0]

Maybe this could be relevant if we are unable to add multi-threading in RLN-WASM for proof generation.

[oskarth]

A lot of the value with mobile support comes from making it easier for mobile developers to use RLN, Zerokit and ZK in general.

E.g. see what @richard-ramos has done with go-waku here https://waku.org/platform#mobile-application

[s1fr0]

A lot of the value with mobile support comes from making it easier for mobile developers to use RLN, Zerokit and ZK in general.

E.g. see what @richard-ramos has done with go-waku here https://waku.org/platform#mobile-application

Sure! What I meant is that relying on WASM/browsers to make RLN available to mobile could result in a bad user experience if, e.g. we're unable to generate proofs fast (especially in messaging applications) or tree persistence is inefficient.

Indeed rln-wasm, at the moment, has a subset of features we have in rln, and this mainly comes from WASM and some structural differences we have in browsers. However, I also believe that many of these limitations can be solved with some technical effort, although I don't have enough knowledge of WASM to say what is feasible or what is not.