Changing vote from no to abstain until I get more clarity on path to get syrius app on my phone.
Here is the roadmap to list the mobile wallet on iOS and Android stores:
- Setup website - syriuswallet.com I bought the domain
- Setup and style the support forum. We have a working version - support.syriuswallet.com. This will be part of a separate AZ. @Stark has been helping when he has time. Maybe @tortcher can help with forum styling to match the site.
- We need to finish the work John Maxwell is doing and @CryptoFish’s review work. This is part of separate AZs and the work is ongoing and very active. They are merging the code bases and refacting much of it. John proposed 3ish AZs and CF has 1 approved to review John’s work. You can track progress in matrix.
- We have an apple developer account (200 usd to setup). I also needed to setup an LLC. We can sign MacOS builds today in Github. We need to deploy that to
/syriusin the main repo. - Torcher needs to help me build an adhoc version of the iOS app (locally) so we can deploy the necessary secrets and manifest to github. This will enable github to build updated iOS versions and deploy to the app and android stores automatically.
- I should probably request some AZ to pay for the developer account, setting up the support forum, and doing many hours of work trying to get these binaries built and signed for the apple and android stores. I have not submitted because I have not been successful yet in building the iOS app. I’m sure it will build. it’s just no so easy for someone who has never done it before.
I think that is it. Did I miss anything?
3 Likes
I also wanted to mention, that without the syriuswallet.com website we should not list the app. Im not sure if it is a hard requirement, but it is if we want to be taken seriously.
It also think that @jovi should receive some AZ for all the logos and versions they created. That should be part of what I submit. The logos were very cool and we had many versions. We also got some headers for the store site.
@tortcher you should check them out.
It wasn’t really intending for this to be part of this proposal, but I was able to compile the app for IOS and deploy to my private TestFlight environment. There are a few configurations that I noted need to be updated for the submission process which I have documented. I will be working with @0x3639 to get it deployed and working within the actual organization account. Here are some videos (I apologize for the resolution - they were taken with an iPad).
I have posted a few videos as well here:
It wouldnt let me post them again, I think it flagged my domain.
1 Like
LOL is #6 an actual step or foreshadowing 
So 1 is this AZ?
2/4/6 is your az for “adjacent” work?
5 is part of 1 or 2/4/6?
WTF is 3? I wouldnt think refactoring is required to launch the app but I could be wrong. If this is a dependency @john.maxwell @CryptoFish how long will it take and can you remind us of the AZ ask for this? Also, can you confirm these steps?
Yes I will submit an AZ after the work is done. I’m honestly so busy right now I cant stop to figure it out. It will be fair given that I’ve probably spent > 1000 hours here doing stuff without charging a single AZ.
#1 is Torcher’s AZ
Correct
Torcher can help me in probably and hour or two. But I’ve already spent many many hours working on this already and previously getting github actions to work with signing macOS builds for syruis. @aliencoder and I have been working on that too. It’s been a group effort. I will include a fair amount of time which excludes learning in my AZ.
Torcher took the day off and built the iOS app here.
See @john.maxwell post. This is critical work discussed on the forum which merges the Syrius mobile wallet and desktop code base. He is working full time on this merge and refactoring the codebase. It will also bring bitcoin functionality to the desktop wallet. It a huge and critical update. CF is reviewing all the work and has an approved AZ to do so.
John is a stud and has been crushing the work. Active in matrix and I’ve posted all his PRs to telegram.
So 1 - the website is 2 months & 5k ZNN 40k QSR
2/4/5/6 can run in parallel(?) and are ? (can those even be lumped together?)
3 is a dependency or nice to have? If dependency do we know time and cost (I think the proposal was not specific on either + quite some time has passed since it was submitted
How long is apples approval process and is there a chance we get rejected? Can android be expedited or does that need to run on the same timeline?
What else is missing?
If we can align on a timeline and number of AZ required then I would be in favor of approving all AZ but not approving any payout until I have actually downloaded a working app on my phone. Know that is not “fair” to devs that are doing their part but that is my own personal definition of success at this point.
This requires coordination / collaboration across dev teams of course but that should be happening anyway.
with all due respect. this is an unrealistic hurdle. many of these things are interrelated - one depends on the other. John has not submitted an AZ. It will be based on hours spent. My will be based on success and delivery. Torcher submitted his.
Should we just all stop work and do nothing? We will not be able to coordinate this as you would like.
Im curious. I see the bitcoin AA was approved. @sultanofstaking do you know what this is used for and why we need it?
The roadmap and path I’ve laid out above is very clear. We have people working all over the world unrelated to each other working in tandum and in parallel. People are picking up parts of work and no one is in “charge” of this project.
The work on syruis is high quality and tangible. No rugz (yet). I cannot deliver what you are asking for. So are you asking us to stop all work?
- no code merge & refactor
- no app store listing
- no website
Until several unrelated people develop a max AZ ask? Everything is fluid and depends on evolving work scopes. John’s work is evolving as he uncovers issues. CF work is a function of John’s work. Everything is related to others we don’t control.
Please reconsider your criteria.
Guys I don’t want to come off as a bully. This is a complicated project and I’ve been working on this stuff for months in small increments. We have many moving parts and pieces all run by people who are loosely coordinated. I’m sort of the glue given my role with github.
- John and CF are advancing a LOT of work now on syrius.
- The mobile wallet is ready to list on the App & Android stores. I’ve never done that before. I know the big picture things that are involved, but will only really know when I get into it.
- I dont have time to “get into it now” because I have other things that are taking priority.
- For sure we need a website and support forum.
- We have someone offering to make a very professions support forum. I hope we can support that work.
- My role in all this is evolving and I cannot define it now. It’s a lot of random stuff. When I’m done with that work I’ll ask for an AZ. It will not exceed 1 full AZ. But I cannot know how much it will be until I’m done.
- I will not charge for my learning time. And trust me, I’ve spent a lot of that already on signing the macOS software.
- I think my actions here speak for themself and I hope no one questions my intensions. The goal is to list the mobile wallet on the app and android stores.
So back to @tortcher 's AZ to move this project forward. Does anyone have specific concerns about that work?
I also wanted to point out that Torcher did a full review of the app > on matrix. Thank you @tortcher for doing that.
1 Like
Thanks @tortcher for stepping up to get this done.
I dont know the ins and outs of the app signing and app store listing process but getting these final steps pushed thru is a clear deliverable goal that needs to be completed asap.
Getting this exposure for Syrius is a huge win, its a beast of a wallet and deserves a professional landing page to match, this is a good fit imo.
1 Like
First, I’d like to thank @tortcher for taking on this critical, blocking task to give Syrius the spotlight it deserves. I also appreciate the detailed AZ, as well as the clearly defined phases and success criteria.
I fully support this AZ. The scope and deliverables are clear, and the price seems reasonable. I’m also pleased to see an idle alien returning to the front lines—getting more contributors back in action is always a plus.
I’d also like to address the concerns raised by @sultanofstaking and acknowledge the value of the detailed responses about the current Syrius roadmap and overall project status. While I personally did not feel these explanations were necessary, they do offer valuable clarity on the larger scope of Syrius.
Though I agree with Sultan’s concerns in principle—each AZ should indeed undergo proper scrutiny—Syrius remains the project that has rightly received the largest allocation of funds to date. Because of this, it’s inherently more complex and ever-evolving.
It wouldn’t be logical to block someone’s work simply because future dependencies exist. That would be like blocking the multi-chain bridge until a governance module is in place. However, it is crucial to be aware of upcoming blockers and to maintain a clear roadmap for overall project delivery. For this reason, I appreciate the new AZ scrutiny, as it shows genuine care and accountability.
Finally, I hope contributors do not interpret this renewed scrutiny as a negative signal. On the contrary, see it as an indication that you’re part of a maturing ecosystem. By upholding higher standards for all contributions, we ensure that the collective sum of our efforts will be worth it.
3 Likes
I dont think any hurdle is unrealistic. I am only one voice here so if people submitting AZ dont value it and think they can get by w;out addressing me then just ignore me but i cant sit here any longer and pretend to care, approve things, and have no idea what I just approved or if it will ever add any value to the network.
If I were to bring a proposal for an investment to at my dayjob w/out addressing dependencies and when to expect to see ROI I wouldnt even make it to questions, they would just tell me no and come back with a complete proposal. I expect the same for anyone asking me for an investment and frankly a bit surprised so see some actual due diligence be positioned as pushback and unrealistic hurdles
3 Likes
I hope this work gets approved and I hope we get a wallet very very soon. I dont want to approve another mobile wallet AZ only to be sitting here in this same position 6 months from now while someone tells me there is another step nobody discussed and it will be another max AZ and 2 - 3 months (at minimum)
1 Like
Thank you for this feedback. I agree. In my job I would never approve a deal that is not completely thought out.
Here we are dealing with a different beast. We are working on an ever evolving project that is being developed by people all over the world. The software is advancing in multiple directions without one person responsible for everything.
Torcher is submitting an AZ for one piece of a large project that is moving forward. We need a website to list the wallet in the app store. But there is more work to list the app and it will happen separately. If we expect someone to assume responsibility for everything involving syrius nothing will move forward.
We gotta work with what we got and syrius has a proven track record of making good, incremental progress.
1 Like
The first mobile wallet proposal was in June 2022… and we still don’t have a clear roadmap
I hope this gets approved but I’ll only approve in the context of a clear concise roadmap to get the app on my phone with logically placed AZ payouts
Tortcher I hope u realize this is not pushback on you directly but this entire process as a whole. I appreciate the quick responses to everything but I am sure you can understand the quoted text is actually insane
I think Dr. Blaze specifically excluded the app store listing. He left that up to the community because it requires doxing. So not sure how this process could be any better.
I’m just here doing small parts to achieve the goal as time permits. We have a track record of delivering.
In my opinion, the taproot bridge is a far more interesting project to focus a high degree of scrutiny. They could be working on something that is expecting many AZs and from what I can tell they are looking to expand the functions of Sentinels and it’s not clear if they are willing to submit a ZIP.
1 Like
Sure taproot deserves scrutiny but that is a separate topic. Everything deserves scrutiny.
You ever present a technical topic to a non-technical board? It is not the boards job to understand the tech and it is not their job to do mental gymnastics to determine if there is a real plan in place. It is their job to review the information presented and make decisions that uphold their fiduciary responsibilities.
Like it or not, the more we start thinking like this the more efficient AZ will become. I also think this mindset will be required to boost pillar participation especially for things like supermajority votes. Better to start building the muscle now.
2 Likes