Status Weekly Roundup: Design team While we love all the benefits of being a fully remote organisation, we still make sure we get together in person a couple times every year. This past week, the Status Design team met in Corfu, Greece, for an offsite as we work on the last few details before the launch of our new website in the next couple of weeks! We can't wait to show the world what we've been working on! 😊

 While in Corfu, we also attended @Offscript9, an experiential offsite that connects some of web3's best designers. It was great to meet with designers from @MetaMask, @safe, and @bitrefill and identify and discuss possible solutions to shared problems like aligning on terminology and human-readable transaction metadata. The future is bright for web3 ✨ #EthStatusProgress

Status Weekly Roundup: Keycard team We have implemented BIP-39 mnemonic generation on Keycard Pro. We’re using the TRNG (True Random Number Generator) from STM32H573 for generation. This allows fully air-gapped private key generation to any @Keycard_ inserted in Keycard Pro. #EthStatusProgress

Status Weekly Roundup: Wallet team It's time for this week's Wallet dev updates! Support for Sepolia is complete, so everything in Status Wallet is now lined up and ready to replace Goerli and Goerli Arbitrum. Goerli remains the default for the time being. We will finalise the switchover to Sepolia when the rest of the ecosystem is ready. Our transaction activity UI can detect and surface Token Minting actions, which is especially useful for Status Community users. In the background, fetching balance history and activity history have now been merged into a single process to prevent too many network calls. We've also made some optimisations for newly generated accounts that don't yet have any transaction history. The mobile wallet team has been hard at work, too. The QR code scanning functionality is now working, and background graduates have been added to the UI. We've also set up the Wallet Edit Account screen and improved the text input component, addressing a few iOS quirks. And the new mobile wallet Activity Tab and Buy Tokens drawers are in the works! #EthStatusProgress

Status Weekly Roundup: Desktop Messenger team One thing we haven’t talked about much, but that has made its way into our 0.14 release, is the improvements to the Status Community Management home screen. These improvements include a shiny new graph that displays the number of messages posted in your Status Community over time. It lets you see when your community is most active and see trends in your community’s messaging activity. Obviously, this is all fully decentralised, running in your Status clients, and of course, no personal data is tracked; this functionality just reuses the data already present in your local Status Desktop database. This is only the first of several Status Community Management analytics graphs we have planned. More graphs that can be useful for Status Community Owners, TokenMasters and Admins will be added in the future. #EthStatusProgress

Status Weekly Roundup: Desktop UI team In the Qt/QML world, models are an important and frequently used concept. They allow us to conveniently provide data to our UI components. The simplest generic ListView model is available directly in QML as part of QtQuick. However, we often create dedicated models in C by inheriting from classes implementing QAbstractItemModel (e.g., QAbstractListModel). In addition, we also often use the very convenient QML library SortFilterProxyModel (github.com/oKcerG/SortFilter…), which allows us to create in a flexible, declarative way intermediate models for sorting, filtering, and some other transformations of the source model. SortFilterProxyModel is great, but sometimes a proxy that accepts only one source model is not enough. There is often a need to combine data from two models into one common model, in a similar way to databases where we perform JOIN operations on tables. Of course, this can always be done using a dedicated model that internally combines all the data we need. However, the need to combine different data from different models is so common that we came up with the idea of ​​creating a reusable proxy model implementing this type of transformation. The working name is LeftJoinModel. Currently, it is just an idea, but the first prototype implementation will be created soon. We will definitely share details in our future posts. Stay tuned! #EthStatusProgress

Status Weekly Roundup: Mobile team This week we have been busy with addressing a bunch of UI feedback that was collected from the previous 1.25 release. On top of that we have been helping create the backend for the new tokenized community ownership feature, which will allow the ownership of a community to change without having to share a private key. We’ve also been busy fixing message reliability issues related to the new Waku ‘lightpush and filter’ protocol and community encryption. #EthStatusProgress

Status Weekly Roundup: Keycard team Soon Keycards will be available in a new colour!! 🌞 #EthStatusProgress

Status Weekly Roundup: Wallet team This week in the world of wallets, the mobile wallet team has been integrating the new UI with recent backend improvements. 🔨 Users can now create new accounts with a personal touch by giving each account its own emoji, colour, and name — which is then reflected throughout the UI in every location where an account is surfaced to the user. Editing and managing multiple accounts in Status Mobile is now a seamless experience, too. For seasoned crypto enthusiasts, the new Status Mobile Wallet now lets users keep a close eye on wallets of interest with watch-only accounts. 👁️ Next on the Mobile Wallet horizon: diving into all things related to transactions! Now onto the Desktop Wallet. Whether or not the balance of a watch-only address is aggregated into the user’s total balance and the ‘all accounts aggregate view’ can now be configured individually on a per address basis. Previously it was a global setting that meant a user could only choose between having all or none of their watch-only accounts aggregated into their total balance and all accounts view. We also made some improvements related to emojis so that the way we handle emojis is now aligned between mobile and desktop. #EthStatusProgress

Status Weekly Roundup: Desktop Messenger team Another feature we’ve been working on in the Messenger Team is the Profile Showcase! We are implementing this feature together with our colleagues in the Desktop UI team. It lets you share which Communities you're part of on a per-Community basis with either: the whole world, just your mutual contacts, only your mutual contacts whose identity you have verified, or nobody at all. With this feature, you will be able to discover Status Communities by seeing the Status Communities your friends are part of. Of course, we keep your privacy at heart, so this feature is optional. You decide which community memberships you want to reveal (or not) and to whom. Show the whole world which Status Communities you are part of, just the contacts that you trust, or show nobody at all — your data, your privacy, your choice. #EthStatusProgress

Status Weekly Roundup: Desktop UI team This week’s QML development time saver! When working with large codebases, there often arises a need to better organise or split a large QML file into smaller pieces, or reusable components. One logical (and tedious) way to do it would be to copy the portion of text to the clipboard, create a new QML file at the desired destination, and paste it there. But there’s a much quicker way to do it: put your cursor over the component, bring up the context menu, and select “Refactoring -> Move Component into Separate File”. Alternatively, you can also press “Alt Enter” to invoke the same menu. In the config dialog, you can then choose the path where you want to save the new file, and assign properties. Happy hacking! #EthStatusProgress

Status Weekly Roundup: Design team With the release of our new website around the corner, we wanted to share some of the magic that goes on behind the scenes to bring our new illustration style to life. Enjoy ✨ #EthStatusProgress

Status Weekly Roundup: Mobile team This week we have finally finalised the scope for the 1.26 alpha release, and we have been busy integrating community tokenisation functionality (now that the community tokenisation functionality is up and running in Status Desktop). We have also been working on implementing the new format of links that will enable Status users to share links to users, Communities, and channels within Communities with their friends — including those friends who don’t yet have Status installed. Last but not least, we’ve made some performance improvements to fetching and retrieving data, which will help make the user experience smoother. #EthStatusProgress

Status Weekly Roundup: Keycard team The first KeycardPro prototype board is in our hands! 🚀 We are currently testing this prototype to validate our hardware, and the next step will be to start designing the next revision of the PCB that will integrate with our industrial design. 🙂 #EthStatusProgress

Status Weekly Roundup: Wallet team This week we started work on integrating the Sepolia chain as one of our testnet chains to replace Goerli by the end of this year. The Arbitrum testnet will also be transitioning to Sepolia. In our activity UI you can now filter your activity to only see transactions relating to specific NFTs that you currently own or that you have previously owned. Work on integrating WalletConnect 2.0 has also commenced! Meanwhile, our mobile wallet team has been hard at work perfecting UI components like saved addresses and account lists and has introduced a 'network dropdown' component. Finally, the standardised in-app authentication flows have now been built — you can use a password, biometrics, or the Status @Keycard_ 🙂 #EthStatusProgress

Status Weekly Roundup: Desktop Messenger team Remember us previously talking about the Discord Import Tool that lets you bring your Discord Community (including all of its message history) into Status? Well, we’re now improving this functionality by letting you import a single Discord channel into a new channel in an **existing** Status community at any time! This gives you the freedom to progressively transition from Discord to Status, one or two channels at a time. It also means you can import sensitive channels individually to make sure that all the message history for that channel always stays private! 🤫 #EthStatusProgress

Status Weekly Roundup: Desktop UI team When it comes to drag and drop, generally anything is possible in QML — at least if the entire process takes place inside the application we control. However, sometimes there is a need to perform a drag-and-drop operation from our application to an external one. Then the possibilities are limited, especially if we have no control over the external application code. Fortunately, many applications support drag and drop based on the well-known MIME type format, which is also nicely supported in QML. This allows us to define how the dragged information should be treated. For example, in the video below we drag content from our application to QtCreator. Depending on the MIME type selected, the submitted data will be treated differently. As we can see, choosing the appropriate MIME type allows us to achieve appropriate behaviour on the side of the external application. #EthStatusProgress

Status Weekly Roundup: Keycard team With @Keycard_ Pro, you will have full control over your keys. You will be able to either generate (with a true random number generator) a new mnemonic for your card or import a key by typing a recovery phrase in. Here’s a video of the UI (still a prototype) for the recovery phrase import. #EthStatusProgress

Status Weekly Roundup: Wallet team Another improvement we’ve made to our wallet transaction activity UI: To repeat a transaction, you can now simply click a button and our send modal will open pre-populated with the exact same parameters. In the collectible (NFT) UI, last week we implemented more graceful handling of the failure scenario cases with error states and retry options. Now that all @Keycard_ functionality is integrated and working, we’ve moved on to improving Keycard testability and last week, we implemented a mock to test all possible Keycard interaction states. This will be leveraged by our QA team who are currently creating automated tests for Keycard’s use with Status Desktop. On the mobile wallet side of things, we’ve been busy getting the foundations needed to implement the new UI designs. Now that most of this foundational work is complete, we have started creating the first phase of the new wallet screens and connecting them to the backend. #EthStatusProgress

Status Weekly Roundup: Desktop Messenger team This week, we bring you part two of how the full tokenisation of community ownership works. Last week, we talked about the Deployer contract that lets members of a community know the bona fide Community Owner. However, there is a crucial step left to make sure a Community continues to run correctly after ownership has been transferred. Previously, the Community’s metadata was signed using the Community’s private key, but now the new Owner doesn’t have that key. The solution: we sign the Community with the Owner’s private key! Since members know who the Owner of a community is (the hodler of the Owner Token), we can enable this new method and guarantee that it will be legitimate! It’s not that simple to implement, but we’re working hard, and the implementation is close to being ready! Check in next week for more info on our awesome features 😉 #EthStatusProgress