Syrius Wallet Mobile App

@DrBlaze_21 is the mobile wallet limited to $ZNN and $QSR in the wallet? I sent myself some test $DORSY and I received it but it’s not showing in the mobile wallet.

Also, is there a rate limit on how frequently the mobile app polls the rpc for TXs? There seems to be a large wait between when a TX hits the mobile wallet and when it shows up in the wallet.

1 Like

If the projects are voted favorably before September 1st, I have one more big surprise for you at the start of next month :flying_saucer:

https://x.com/edgepillar/status/1829919204612374845
https://x.com/edgepillar/status/1828406488219459952

:white_check_mark:

3 Likes

Hi, what was the big surprise or we still waiting?

Plausibly waiting for more opportune timing. It’s generally better to coordinate news in order create momentum. I support this strategy, if true. Speculating.

Introducing the most awaited feature for Syrius Mobile:

Bitcoin support:

:white_check_mark: Bitcoin mainnet integration
:white_check_mark: Native Taproot support P2RT addresses
:white_check_mark: Bitcoin signet integration
:white_check_mark: Native Segwit support P2WSH addresses
:white_check_mark: Mempool.space integration
:white_check_mark: UTXO management
:white_check_mark: Custom fee management with RBF support
:white_check_mark: Electrum node support

Syrius Mobile v0.4.0 for testing (you must uninstall the previous version):

SHA-256 hash:

e2a1f8ad84a44bec31436f16b28b630446ec17e7aa0f4422726f6e37a237c39e

@0x3639 thank you for the Prices API.

And many thanks to @john.maxwell that refactored a large part of the codebase and implemented the Taproot integration and many more. Stay tuned for more info!

Thank you for all the support so far!

15 Likes

Uploaded to DO Spaces in case we run out of bandwidth.

https://hypercore.nyc3.digitaloceanspaces.com/mobile-wallet/v0.4.0/app-release-v0.4.apk

Please check the hash before installing this to make sure it matches.

4 Likes

Great work!

Feedback:

  • Plasma/PoW generation seems to be UI/network blocking, meaning users can’t swap to other networks while it’s being performed i.e say I collect rewards on NoM then try to change network to Supernova ZVM to mint some kitties. Could PoW be done in the background?

I’ll send some sats and keep testing. I’ll also try to replicate the issues CF was having on previous versions.

7 Likes

@DrBlaze_21 would it be possible to deploy a github action so we can build the .apk right in Github and host it there?

PoW is already done in the background. I’ve isolated the Network switching on purpose to avoid unnecessary complexity. The user must be aware on the network where he performs actions.

Feedback is welcomed.

I’m testing on both emulators and real devices.

Check out @aliencoder’s branch.

I’m preparing to open-source the EVM and Bitcoin parts. I’ll ask for 2 more projects from AZ for the Bitcoin integration.

From that point forward, @john.maxwell will take the lead and start the unification between the desktop and mobile codebases.

1 Like

Hello,

I’ve been cleaning the mobile codebase before making it public. Will post the code until the end of the week.

Update Syrius Mobile v0.4.0 for testing (you must uninstall the previous version):

https://workupload.com/file/Jg3TrtwmbZJ

SHA-256 hash:

d932c1b56ed796a3624d84d2c3eb29c0c24783727e6dbc9a23add279a211c432

I’ll create the last 2 AZ projects for the Bitcoin integration.

I want to thank the community for the support throughout this bear market. And let’s continue supporting @john.maxwell from now on.

8 Likes

The Backup wallet and Confirm seed view cannot be used when using an increased font-size. See issue Cannot select words when confirming seed when using increased font size

I wanted to point out that this is v0.5.0

Here is v0.5.0 on DO Spaces if the link above expires. Please check the checksum before using.

https://hypercore.nyc3.digitaloceanspaces.com/mobile-wallet/v0.5.0/syrius-release-v0.5.0.apk

@DrBlaze_21 I’m testing the new mobile wallet and ran into an issue that requires the wallet to be restarted to receive a new transaction. See issue here: App requires restart to receive transation · Issue #10 · drblazer21/syrius_mobile · GitHub

Also, 100 ZNN give away for testing and posting on the mobile app.

1 Like

can you please respond to the other post with a screen shot of your device with feedback on the app?

Fixed.

Fixed.

Update Syrius Mobile v0.5.1 for testing (you must uninstall the previous version):

https://workupload.com/file/JeTmfwSmkpv

SHA-256 hash:

d5f1bf865ed3b72a424d767c6fe46b58b865cafb0107c94edd8e9c27de55e78e
1 Like

Syrius Mobile v0.5.2 is live! :alien:

All the codebase is now open-source.

I’ve fixed all the bugs and closed all pending issues @0x3639 @CryptoFish

Update Syrius Mobile v0.5.2 for testing (you must uninstall the previous version):

Thanks to @aliencoder we now have automatic builds for the Android version:

I’ve requested the funds unlock for the last 2 phases (EVM support):

I’ve posted the remaining 2 AZ projects:

Happy to contribute with 100 ZNN for the testing fund @0x3639 DM me the address.

Thank you all for the support so far, helping me out with testing the app and with @john.maxwell the wallet project is in good hands.

6 Likes

@DrBlaze_21 I removed the old app and installed the new universal app from the repo, but I get the following error:

App not installed as package conflicts with an existing package.

This is the first time I’m getting this error.

Same is true for v0.5.1

However, when I install v0.5.0 I do NOT get that error, so it must be an issue introduced in v0.5.1.

This error appears when you try to install the app while the old version is still present. Please uninstall the old version before install v0.5.2.

The x86_64/universal version is for testing on an emulator (on a PC). Less than 0.1% Android devices support the x86_64 CPU architecture.

Yes I have uninstalled the app and I’ve tried x86_64 also. I get the same message. However, when I uninstall and reinstall v0.5.0 I do not get the message.

I am running this on a sandbox in graphineOS but this is the first time I’ve experienced this error when upgrading. I’ve tested every version on this sandbox the same way.

Can anyone else replicate this issue? I can blow out the sandbox and create a new one and try that