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…

Our cofounder @jarradhope_ opens @ETHRome today at 16:00 CET with a keynote presentation viewing crypto as a revolutionary power centre. We’re also helping with the event’s closing party on Sunday to solidify the alliances made during the hackathon and forge new ones. Details…

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…

Vac’s Applied Cryptography and Zero-Knowledge Service Unit has just shipped a new version of Zerokit (https://t.co/0nx4Tp9czM), which includes support for the spam-mitigation protocol RLN-v2. @PrivacyScaling 's trusted setup ceremony for the RLN circuits concluded in September…

🇮🇹 Waku’s @ETHRome schedule is filling up!! If you’re attending, you’ll find us at: 👉 The @web3privacy Now warmup event on 5 Oct for a technical talk on Waku delivered by @vpavlin (details and registration

t.co

👉 ETHRome itself — we’re sponsoring the…

#EthStatusProgress

Logos goes live again on @X Spaces tomorrow at 16:00 UTC. Talking with host @Fergulati about the relationship between network state philosophy and the tech we build is Logos programme lead @Corpetty and author and Logos content writer @SterlinLujan .

Status Weekly Roundup: Mobile team Version 1.25 (alpha) of Status Mobile is now available on GitHub! 🎉 We have been busy testing and fixing the bugs that our marvellous QA team was reporting – still some way to go, but getting better by the day! We've also been working on refining the UI, adding more animations, and broadening the scope of device syncing. #EthStatusProgress

With his thought-provoking talk, @jarradhope_ closes the first day of #HCPP23. Jarrad views crypto through the lens of Bertrand de Jouvenel’s political works and those of other elite theorists. By casting the space as a new centre of power, he hopes to shed light on who we are,…

Status Weekly Roundup: Keycard team 🥳 Great progress! Our Keycard Pro prototype can now scan a transaction provided as a QR from @MetaMask (or any other ERC-4527-compliant wallet), have it inspected by the user, have it signed by a @Keycard_ inserted in Keycard Pro, and then send the transaction back to the ERC-4527-compliant wallet. Here’s a video example with an ERC-20 transfer. #EthStatusProgress

📢 Hackers of @ETHRome , we have a treat for you. We’re co-hosting the Privacy Soirée with @CryptoCanal & @RAILGUN_Project ! Join us from 20:00 CET on 6 Oct. to discuss privacy tech over bespoke cocktails in a secret venue close to the main hackathon. 🤫 Apply to join us here:…

Status Weekly Roundup: Wallet team Here are some of our latest updates from all the hard work we've been doing lately: 👉 You can now update the JSON-RPC URL you prefer to use for each chain. We provide defaults, but you can use your own if you prefer (for example, to connect your Status Wallet to a self-hosted node). 👉 In the activity view, we are continuously adding more filters. You can now filter your activity view by collectibles (ERC-721) or by similar transactions. 👉 We've achieved a significant development milestone: syncing Status Wallet accounts across multiple devices is now feature-complete! This is quite an extensive feature, as a result of the demanding requirements we set ourselves: 1) private keys should never be passed over the internet, 2) users should have all their accounts available across all their devices, 3) the experience needs to be user friendly and intuitive for non-technical users. Completing all the design and development work needed to make this possible is a major success 🎉🎉 👉 One last thing: a couple of months ago, we began developing the mobile app’s new wallet. So far, we have implemented most of the UI components needed for the mobile wallet MVP 🎉, and we are now starting on the integration with the backend. More updates coming soon! #EthStatusProgress

Logos and @ethstatus cofounder @jarradhope_ returns to Hackers Congress by @Paralelni_polis this year. Jarrad will present on the development of political thought underpinning crypto’s rise and how the space can be seen as a new centre of power globally on 29 Sept. at 18:00 CET.…

. @ethstatus is hiring remote! ⚡ Distributed Systems Researcher (Blockchain) ⚡ Senior DevOps Engineer (Blockchain) ⚡ Software Engineer Distributed Systems Testing ⚡ Technical Business Development Lead Apply now👇

Our latest blog post delves deeper into our data availability sampling research. It focuses on our analysis of @ethereum Foundation and @miga_labs data to understand how larger blocks and geographical locations influence block propagation times from the perspective of different…

Our cofounder @jarradhope_ delivers @PowSummit ’s closing keynote today at 17:40 CET in Prague. His presentation is titled 'Crypto as a Revolutionary Power Centre.' If you’re at #POWSummit, join us to discover where Jarrad thinks our space is heading.

Status Weekly Roundup: Desktop UI team We use various tools in our daily work with Qt. In addition to the standard well-known tools, there are also some tools that we have made ourselves. Some are quite complex, e.g. Storybook. Other tools we have created are very simple but nevertheless very practical. An example of such a tool is the Tracer component. Wherever it is added, it automatically adds a frame around the parent component. This is often enough to verify the size and position of the component. The most basic implementation of Tracer might look like this: Rectangle { z: 1000 border.color: 'red' color: 'transparent' anchors.fill: parent } This basic implementation works fine with most standard components. Problems only arise when we try to use it inside a layout (e.g. Flow, Row, RowLayout) because the layout will try to manage the size and position of our Tracer. To avoid this, we use a little trick when Tracer is defined inside the layout. It involves transferring Tracer to the Overlay component. Inside Overlay, we periodically update the size and position so that it is above the layout component. The full implementation can be found on our GitHub:

t.co

Thanks to this, Tracer fulfils its role regardless of what component it is defined in! #EthStatusProgress

Waku is a layer below XMTP. Consequently, its approach to spam prevention is different. Currently, we are working to implement RLN as an application-agnostic DoS-prevention mechanism and have recently made great progress integrating it into our clients. XMTP, like @ethstatus ,…

Status Weekly Roundup: Design team As we build such a complex and extensive app, we need to create a consistent, efficient, and always-evolving source of truth for its design. With thousands of individual components with dozens of permutations each, our design system is the backbone of the Status apps. We’re very proud of the work done, and we hope this will show when you try the new Status Mobile 2.0 app! #EthStatusProgress

Our cofounder @jarradhope_ will close out the first annual @PowSummit presented by @LTCFoundation & @ETCCooperative with a keynote presentation titled ‘Crypto as a Revolutionary Power Centre’ on 27 Sept. at 17:40 CET. The PoW Summit runs from 25–27 Sept. in Prague ahead of the…

Status Weekly Roundup: Mobile team Over the past few weeks, we've been hard at work perfecting our fresh UI, enhancing the user experience for paired devices, and embarking on a new wallet UI project. 🛠️ We're currently in the final testing phase for alpha release 1.25, and we're hoping to roll it out in the coming days! 🤞 Stay tuned for the latest updates! #EthStatusProgress

Status Weekly Roundup: Keycard team After spending months evaluating and trying various ARM chipsets from NXP, STM, and Renesas, we have decided to develop our @Keycard_ hardware with STM32H573, a cortex-M33-based chipset. It has everything we need: it’s powerful enough for all our features, has a line of security and cryptographic features, and is power efficient. Moreover, it’s a recent addition to the ST line, is manufactured in ST brand new factories in Europe, and will be available for many years to come!

t.co

#EthStatusProgress

Status Weekly Roundup: Wallet team Our Wallet team is back with updates! Now, in addition to the ability to send ERC20 and ETH tokens, the Status Wallet supports sending NFT tokens. We are also in the process of building the functionality needed to ensure that all ERC20 tokens minted by Status Communities (using Status’ token minting tool) are correctly displayed in your Status Wallet. Because: 👉 Status is permissionless 👉 There can be an indefinite number of Status Communities 👉 Any Status Community can mint any number of different tokens (remember, Status is permissionless!) 👉 ‘Status community-minted’ tokens most likely won’t be featured in the Uniswap token list 👉 Following our principles, we reject the idea of any centralised solution to this problem Solving this has been quite a challenge! However, we’ve found a fully decentralised and permissionless solution, and we are busy implementing it 🙂 #EthStatusProgress

📢 We just updated Status’ Terms of Use and Privacy Statement. You can check the new versions on our website here

t.co

and here

Status Weekly Roundup: Desktop Messenger team We are hard at work on our next milestone: the 0.15 release. This release will include a very interesting but complex feature – full tokenisation of community ownership. Each Status Community will have a single Owner Token, and the account that holds a Community’s Owner Token will be the owner of that Status Community. Transferring community ownership then becomes a matter of simply sending the Owner Token to a different address. Previously the only way to transfer ownership of a Status Community was by manually sharing the Community’s private key (a temp stop-gap solution). This is a terrible way to manage community ownership for all the obvious reasons! Tokenising community ownership is the correct solution, but it is a large work item that introduces quite a bit of additional complexity. Because we want to make it as easy as possible for somebody to create a new Status Community, new community owners won’t be required to mint their Owner Token when they create a new Community (as this would require the person creating the Community to have ETH to pay the gas fee). Instead, a community owner can defer minting the Owner (and TokenMaster) Tokens until a later date, but of course, the Community’s Owner Token will need to be minted before an Owner can transfer ownership of their community. Check out our update next week to learn more about how this all works! #EthStatusProgress

We hate hearing tales of web3 settlers losing it all. 😡 We build Keycard hardware and software to democratise access to hardware wallet security. 🛡️ If you’re a builder, you can integrate Keycard into your wallet app via our open-source SDK. If you’re a user, Keycard is…

Status Weekly Roundup: Desktop UI team QML components consuming models (like ListView or Repeater) are very flexible about what that model is. It can be the most powerful C++ custom model inheriting from QAbstractItemModel, QML's handy ListModel, ObjectModel, or a plain JavaScript list. However, this is not the end of the possibilities. For example, a list of QtObjects (or components that inherit from QtObject, like Item) can also be used as a model. This creates an interesting possibility of treating properties defined in objects as model roles. Let's take a look at the example presented in

t.co

Using this approach, we can conveniently embed labels into objects in the StackLayout as read-only properties and use Repeater inside TabBar, as a model providing children of the StackLayout: /ethstatus/status/1704139436068356152/photo/1 Thanks to that we don't have to maintain the correct order in two places (first for labels and later for corresponding objects in the layout). #EthStatusProgress

Logos is live on @X Spaces today at 16:00 UTC. @mattyTokenomics , @FredSantos_FS , & @mart1n_xyz from our Tokenomics team chat to host @Fergulati , diving deep into network state economics. Join us.

✈️ Look out @ETHSafari . Waku will be seeing you soon! 🦁 We’ll be giving a short talk on our decentralised communications protocols at 10:15 EAT on Sat 23 Sept on the Valley Stage. Come along, learn, & chat with us about Waku, & ask about the swag @ac1d_info designed for us 😎

Vac’s Deep Research team has just released a first proof of concept for @ethnimbus Tor Push. While there is still a lot of work remaining to bring greater privacy to Ethereum validators, this is a significant first step. See the RFC here https://t.co/xzQc751fg2, and our…

Members of Status’ design team will be at @Offscript9 in Corfu between 18 and 22 Oct! We can’t wait to participate in this immersive creative experience and share what we’ve learned over the many years we’ve been building in the space. If you’d like to join us, you can find more details here:

t.co

Keycard update: The software for Keycard Pro (code name for @Keycard_ 's upcoming hardware wallet) is fully open source and we also designed it to be abstracted as much as possible from the hardware actually used: hardware-specific interactions are kept separated from the application part. We have successfully run our code on NXP i. mx RT 1060 series and STM STM32 series. Stay tuned for more information on which chipset we will use in production!

👋 Hey! It's time for your #WakuWednesday update. It’s a little lighter than usual but we’ve a lot of eco dev, go-waku, and js-waku updates to reveal very soon! 👉 Research: We’re working on the definition of capped bandwidth for Waku and how RLN should be configured:…

Logos goes live on @X Spaces with @4aelius , Research Lead for @Waku_org , and @SterlinLujan , author and Logos’ content writer, today at 16:00 UTC. Join us to learn about the vital role communications play in realising the network state vision.

Here we go

t.co

The culmination of months of hard work by the @ethereum foundation, @Codex_storage and many many others. Super happy to see this coming together!

We just published a research blog on Nescience — a zkVM designed to provide a user experience similar to contemporary public blockchains but with robust privacy features.

t.co

The post outlines the challenges arising when creating a zero-knowledge virtual…

Keycard Update @Keycard_ 's upcoming hardware wallet can now scan QR codes formatted with ERC-4527! Check our prototype in the video:

Our next @X Space goes live on 5 Sept. at 16:00 (UTC). Joining host @Fergulati is @4aelius , Research Lead for @Waku_org , and @SterlinLujan , author and Logos’ content writer. The 3 will discuss realising network state philosophy with a focus on communications. Set a reminder…

. @ethstatus is building the tools and infrastructure for the advancement of a secure, private & open web3 Now hiring remote! ⚡ Distributed Systems Applied Research ⚡ Lead Software Engineer (Chat SDK)

👋 Hey there. It’s time once again for your #WakuWednesday round-up of everything Waku: 👉 Eco Dev: We're preparing to participate in several upcoming events. Our next ones are @DeComputeConf in Singapore and @ETHSafari in Kenya – both in September 👉 Research: We progressed on…

Keycard update A new release for @Keycard_ is out!

t.co

brings a couple of new features, which are documented here

t.co

They include: 👉 Improved supply chain security: A client wallet can now challenge the card and check its certificate to make sure the card was manufactured by the certificate issuer (IDENT apdu) 👉 Plausible deniability: We introduced a duress pin that can be set up when the card is initialised by a client wallet (INIT apdu) 👉 Chain code export is now possible, further aligning Keycard's behaviour to that of hardware wallets like Ledger or Trezor (EXPORT KEY apdu)

🤔 Did you know that Waku is already providing decentralised communications infrastructure across web3? Don’t believe us? Ask @RAILGUN_project : ‘RAILGUN contributors selected Waku to run its relayer network as an early-stage but promising product of the privacy-centric…

Status Weekly Roundup: Desktop Messenger team In the 0.13 release of Status Desktop, you can choose the mode your @Waku_org node is going to be in. Waku is the peer-to-peer messaging protocol we use, but it can use a lot of bandwidth in the default mode Status Desktop uses, which is called Relay. If you're using a computer with bad specs or you have a lower bandwidth Internet connection, you now have the option to switch Waku to a light mode, aka Waku's 'Filter and Light push' protocols. With 'Filter and Light push', you only receive the Waku messages you're interested in. You are not participating in the network as much as you would be by using Relay mode, hence making your node 'lighter'. #EthStatusProgress

Congrats to @EthereumPhone as it prepares to ship preorders! EthOS 2.0 includes Nimbus light web proxy enabling on-phone apps to independently verify data received from hosted nodes/external endpoints. It’s a great step in reducing Ethereum users' reliance on centralised infra.

Status Weekly Roundup: Docs team 📚🔍 Greetings from the Status Docs team! This week, we've been working hard on documenting Status Wallet accounts. You can create as many accounts as you need in your Status Wallet. For example, you can have dedicated accounts for long-term and short-term investments, as well as a stablecoin emergency fund. Having multiple accounts makes it much easier to keep track of your funds and save money towards specific goals. 💰 You can even add other crypto accounts that you don’t use in Status as watch-only accounts. For example, you don't need to import your hardware wallet account into your Status app to keep track of your balance. Simply add it as a watch-only account and you're good to go. Status Wallet aims to help you seamlessly manage your funds across as many Ethereum-based chains as you need. We'll keep discussing lots of exciting features, so stay tuned for tips and tricks ✨ #EthStatusProgress

We had the pleasure of sitting down with @ShaneMac , co-founder of @XMTP_ Episode Topics: 1️⃣ Shane's journey into web3 2️⃣ Practical use in @CoinbaseWallet & @converseapp_ 3️⃣ Dev tools & network effects with web3 messaging Available on YouTube and all streaming platforms 👇

👋 Hey there! It's time again for your #WakuWednesday update! Let’s go: 👉 Eco Dev: js-waku debug guide is up

t.co

👉 Research: Task breakdown for the next 6 months is done and now being reviewed 👉 nwaku: New release 🥳. See v0.19.0 changelog here…

Logos @X Spaces starts today at 16:00 UTC. Joining host @Fergulati will be @ishikawa_dr , Logos’ activist campaigns director, & @dryajov , project lead at @Codex_storage . The 3 will discuss how Logos’ tech enables the network state. Join us:

Status Weekly Roundup: Desktop UI team With this tweet, we start the 'QML tips & tricks' series, in which we'll share interesting details related to working with the Qt/QML framework :-) QML property aliases are a convenient and frequently used element of QML syntax. Aliases allow us to skip type specification and expose the properties of nested objects as part of the interface. However, there are cases where aliases can cause bugs that are quite difficult to find. Like for example in this simple code in the attached image. At first glance, the first `MenuSeparator` should be visible because it is bound to `summary.showMax`, which has been set to `true`. However, we must remember that `showMax` is an alias for the `visible` property, which is propagated in the component hierarchy from the parent to all children. So setting `summary.visible: false` also sets the `visible` property of the `maxText` component to false. As a result, `showMax` explicitly set to true is overwritten and set to false… Our menu separator is not visible! For this reason, it's better to avoid creating aliases for special properties that are propagated in the component hierarchy, such as visible or enabled. Of course, changing `showMax` from an alias to a regular property solves the problem! #EthStatusProgress

Status Weekly Roundup: Keycard team Our upcoming hardware wallet will support ERC-4527

t.co

so that it will work with every software wallet (like MetaMask) that supports this standard without requiring the wallet to make any Status Keycard-specific modifications. We are currently busy implementing support for this standard. We are writing everything from scratch in C because we want this to run on a memory-constrained microcontroller and we don’t want to have dynamic memory allocation (as this will be better for performance). The memory constraints are very tight, but we think we can do it! 🙂 One last note: @Keycard_ update tweets will be paused for the next couple of weeks as a few folks will be on summer vacation, but don’t worry, updates will resume as soon as we are back! #EthStatusProgress