DM me if you’ve encountered any issues with the app.
It’s an important improvement for the overall security of the keyStore.
The mobile wallet is almost production-ready, including the Security Pack features. I’m also conducting a code review to prepare the source code for release. This includes the znn_sdk_dart (that will work with mobile filesystems as well) and other libraries that I’ve modified in order to support our specific security features.
If everyone is OK, I’ll start with submitting a phase for the first AZ project this week. Thank you!
8 Likes
DrBlaze_21:
our specific
Will the mobile version also support Ledger devices?
Question has already been answered, literally scroll up 3 posts.
1 Like
romeo
March 18, 2024, 12:28pm
189
Can anyone transfer me some testnet funds please?
z1qzt7sh7cs23fc0pf04jawmqnyfsecar35zmxg
dthgti
April 14, 2024, 10:59am
192
can i have some testnet funds? thank you.
z1qqedc0ffrpc3vlsxddg9rdw32rw64ea048uah8
1 Like
0x3639
April 14, 2024, 11:04am
193
Done
If you need more funds visit TG - @znn_faucet_bot
/faucet ZTS and welcome to NoM.
1 Like
0x3639
April 18, 2024, 12:43am
194
@DrBlaze_21 I wonder if your work can “easily” be ported to run as a zApp as contemplated in the unikernel proposal .
2 Likes
0x3639
April 20, 2024, 9:51pm
195
DrBlaze_21:
Yes, there a lots of cases that need to be taken in consideration, that why the mobile syrius will likely need to connect to a remote node.
PoW will be computed on the user’s terminal. There are 2 options we can use:
@DrBlaze_21 where did you end up with performing PoW on the mobile device. How are we accomplishing this?
Any update when the Mobile wallet is ready for mainnet?
The Syrius Mobile Wallet: Pixel perfect. Hardware wallet security. Seamless operation.
The Masterpiece is now live:
iOS emulator screenshots:
Splash - Hardware security - Loadings - Plasma fusing - Send
Receive ZTS - Rewards section - Delegate - Stake - Hide balances
Manage addresses - Settings - Backup - Delete wallet - Seed warning
Screenshot protection - Root/emulator detection - 2FA OTP - WalletConnect integration
18 Likes
DrD3
May 14, 2024, 9:49pm
198
Goddam that looks fire!!! Nobody said it was Christmas - thanks Nick!
1 Like
0x3639
May 14, 2024, 10:28pm
199
Sir, thank you for all your hard work on this!!
1 Like
0x3639
May 14, 2024, 11:25pm
202
DrBlaze_21:
Plasma fusing
is QSR required? Or will the phone perform PoW?
0x3639
May 14, 2024, 11:58pm
203
has anyone tried to build the app? I’m getting an error reported here
opened 11:57PM - 14 May 24 UTC
I tried to build with
`flutter pub get`
then
`flutter build apk --relea… se`
And got the following errors.
```
flutter build apk --release ok 18s 06:53:49 PM
FAILURE: Build failed with an exception.
* What went wrong:
Could not resolve all files for configuration 'classpath'.
> Could not resolve com.android.tools.build:gradle:7.4.2.
Required by:
unspecified:unspecified:unspecified > com.android.application:com.android.application.gradle.plugin:7.4.2
> No matching variant of com.android.tools.build:gradle:7.4.2 was found. The consumer was configured to find a runtime of a library compatible with Java 8, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '7.5' but:
- Variant 'apiElements' capability com.android.tools.build:gradle:7.4.2 declares a library, packaged as a jar, and its dependencies declared externally:
- Incompatible because this component declares an API of a component compatible with Java 11 and the consumer needed a runtime of a component compatible with Java 8
- Other compatible attribute:
- Doesn't say anything about org.gradle.plugin.api-version (required '7.5')
- Variant 'javadocElements' capability com.android.tools.build:gradle:7.4.2 declares a runtime of a component, and its dependencies declared externally:
- Incompatible because this component declares documentation and the consumer needed a library
- Other compatible attributes:
- Doesn't say anything about its target Java version (required compatibility with Java 8)
- Doesn't say anything about its elements (required them packaged as a jar)
- Doesn't say anything about org.gradle.plugin.api-version (required '7.5')
- Variant 'runtimeElements' capability com.android.tools.build:gradle:7.4.2 declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
- Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
- Other compatible attribute:
- Doesn't say anything about org.gradle.plugin.api-version (required '7.5')
- Variant 'sourcesElements' capability com.android.tools.build:gradle:7.4.2 declares a runtime of a component, and its dependencies declared externally:
- Incompatible because this component declares documentation and the consumer needed a library
- Other compatible attributes:
- Doesn't say anything about its target Java version (required compatibility with Java 8)
- Doesn't say anything about its elements (required them packaged as a jar)
- Doesn't say anything about org.gradle.plugin.api-version (required '7.5')
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 1m 17s
Running Gradle task 'assembleRelease'... 79.6s
Gradle task assembleRelease failed with exit code 1
```
Thanks Blaze!! Can you also provide an .apk file under releases?
2 Likes
Thanks for the fab work Zir 
