In my opinion I want to wait for the final conclusions regarding dynamic Plasma. AppStores usually are against proof-of-work in mobile devices and it would be harder to list an app that uses CPU/GPU to compute PoW.
Moreover, people with lower end devices would need to wait more time to send/receive transactions, making the UX progressively worse.
That’s why I’m advocating for a hybrid approach where we have a tri-lane system for creating Plasma:
PoW with multiple algos (RandomX, SHA-3 and Equix)
Fuse (lock) QSR with dynamic thresholds
Burn ZNN
I’m trying my best to find ways to complement the feeless narrative with a more robust system, while promoting game-theoretic compatible models that will ensure the long term sustainability of the network.
Burning ZNN/fusing QSR would be the preferred way to go for mobile users that are constrained by low computing resources.
Alternatively, PoW can be an option for APKs or IPAs distributed outside official AppStores if they reject the apps containing the libpow binaries.
Just wanted to provide feedback from the dev meeting today. It’s likely @DrBlaze_21 is waiting on resolution of Dynamic Plasma to finish his work for many of the reasons stated above.
Here is the latest tl;dr update on Dynamic Plasma.
Different wallet. I highly recommend using syrius to connect to the bridge. We are moving away from the browser plugin in favor of something new called a Metamask Snap.
This happens because I’m using the Coingecko API that has rate limiting. I’m caching now the results, but we will need to pay for the API usage when we release the production builds.
Noted.
You can switch between addresses, but you need to tap in the top right corner. We can improve the UX here. The edit button isn’t enabled yet.
Check now.
I’m open to suggestions on how to display Plasma amounts for the user.
This error appears when libargon2 library is missing from the APK. Please download the newest version.
Plasma or dynamic Plasma are abstracted away from the users.
Yes, check the new WalletConnect feature.
I’m planning to request funds for the work delivered so far. I’ll wait for the community to test this new build. If there are any bugs, I’ll fix them and upload a stable version.
After that I’ll proceed with creating 3 projects with 1 phase each to unlock the funds that will cover all the expenses so far. I’ll also open-source the codebase such that others will be able to contribute and audit the code.
Going from now on, I want to share with you the following release schedule: 1 or 2 months for development (depending on the complexity of the features) and 1 month for testing.
The community will be able to request and vote for new features:
Security pack: biometrics, secure storage, root detection, 2FA, etc.
Tried to connect the bridge and that works beautifully. But then when connecting to metamask it wants to connect to the desktop version of metamask not my android one.
Tried the browser in metamask wallet itself but that one won’t connect because syrius extension is only for chromium browsers.
I’ve been providing the data on the health check to @digitalSloth but we need to improve it some. I’ll work with @sumamu to improve what I have so far.
Regarding the ZNN/QSR data, I think I can provide that. I guess I can just query Coingecko at the approved rate limit, and then recast that data with a higher rate limit. Is that what you are looking for?
As @0x3639 said he provides me with the orchestrator status and I currently have this endpoint https://zenonhub.io/api/nom/bridge/get-bridge-info that can be used to check if the bridge is halted but it doesnt take into account the time challenges. If you wanted I could make a new route that combines the two status checks?
For the ZNN/QSR price I already pull that from Coingecko hourly and cache it so could create an endpoint to access this. For volume data I dont have anything setup for the ETH side but can provide any NoM specific data you need.
For this we need Ethereum (EVM) WalletConnect support in the bridge interface. For the moment the bridge interface only supports Zenon via WalletConnect and Ethereum via the Metamask extension.
Or we can integrate the bridge into the mobile app, but we first need Ethereum wallet support.
