60545a6608
* fix: remove placeholder icons * fix: swipe action button style * lint fix * fix: swipe action button space * fix: lint * Fix for two separate sections with different colors shown on the chat screen (dark mode) (#16265) * Fix for two separate sections with different colors shown on the chat screen (dark mode) * lint-fix * temporary hide mutual update's messages (#16290) * chore: fix unit test for slide button (#16302) * nix: upgrade interpreter from 2.11.1 to 2.14.1 This is a mild upgrade that should not cause any controversy. You can read about changes here: - https://nixos.org/manual/nix/stable/release-notes/rl-2.12.html - https://nixos.org/manual/nix/stable/release-notes/rl-2.13.html - https://nixos.org/manual/nix/stable/release-notes/rl-2.14.html Relevant `infra-ci` change: - https://github.com/status-im/infra-ci/commit/e4e9796f The simplest way to upgrade to `2.14` your version locally is using: ```sh nix-channel --update nix-env -iA nixpkgs.nixVersions.nix_2_14 nixpkgs.cacert sudo systemctl daemon-reload sudo systemctl restart nix-daemon ``` For MacOS the instructions are a bit different: https://nixos.org/manual/nix/stable/installation/upgrading.html Keep in mind you should use `nixpkgs.nixVersions.nix_2_14` instead of just `nixpkgs.nix` to avoid getting newer than `2.14`. Signed-off-by: Jakub Sokołowski <jakub@status.im> * nix: add upgrade script for Nix interpreter Now developers can upgrade to current Nix version using just: ```sh make nix-upgrade ``` For manual instructions see: https://nixos.org/manual/nix/stable/installation/upgrading.html Signed-off-by: Jakub Sokołowski <jakub@status.im> * fix switcher cards position in ios (#16301) * Fix community tags and button spacing (#16292) Linked to https://github.com/status-im/status-mobile/issues/16119, fixes these issues: - Clipped community tags. They should extend to the edge of the screen. - Outdated information box message. Updated according suggestion in Figma https://www.figma.com/file/h9wo4GipgZURbqqr1vShFN/Communities-for-Mobile?type=design&node-id=7035-462899&t=wED97E4Mtv9v6OXf-0 - Add correct padding between community tags and the Request to join Community button. * Add decision about team structure & wallet team * [#16118] bottom nav tab notification color (#16236) * [#16066] bottom sheet height (#16285) * Update prettier config for the project. (#16303) * Update prettier config for the project. * Add prettier to make lint-fix. * fix: placeholder icons for join community, identity verification request * fix: lint * Make profile photos visible by default (#16095) * Fix incorrect channel option (#16314) * e2e: tests fixes * tests: fix type of shell used for linting Otherwise Node modules are not installed. Signed-off-by: Jakub Sokołowski <jakub@status.im> * nix: upgrade nixpkgs to latest nixos-22.11 Notable upgrades: * Bash `5.1` to `5.2` * Git `2.37.3` to `2.40.1` * Curl `7.85.0` to `8.0.1` * OpenSSL `3.0.5` to `3.0.8` * Go `1.18.6` to `1.18.9` * NodeJS `18.9.1` to `18.16.0` * Java `1.8.0_322` to `11.0.11` * Ruby `3.1.2` to `3.1.4` * Python `2.7.18` to `3.10.11` * Clojure `1.11.1.1165` to `1.11.1.1273` * Clj-kondo `v2022.10.05` to `v2023.04.14` * Zprint `1.2.5` to `1.2.6` * Bundler `2.3.22` to `2.4.13` * Gradle `6.9.2` to `6.9.4` * Android Platform Tools `33.0.2` to `33.0.3` * Android SDK Tools to Android SDK Command-Line Tools Removals: * Zprint since the version in `nixpkgs` was newer than in overlay. * Xcode wrapper definition was removed since my fixes were merged: - https://github.com/NixOS/nixpkgs/pull/204278 - https://github.com/NixOS/nixpkgs/pull/228696 Signed-off-by: Jakub Sokołowski <jakub@status.im> * ci: build generic status-go and all shells When discussing caching of `status-go` with Sid I noticed that the build we cache daily created from our nightly build is different from the build we create locally due to a single input. In a release CI host we can see the IPFS URL is that of Infura: ``` > find /nix/store -maxdepth 1 -name '*-status-go-*android' | tail -n1 /nix/store/2cc8ilhx5g3k2awbn4sla61n4cml2405-status-go-0.130.1-d2cce5e-android > RESULT=$(find /nix/store -maxdepth 1 -name '*-status-go-*android' | tail -n1) > nix show-derivation $RESULT | tr ' ' '\n' | grep IpfsGateway github.com/status-im/status-go/params.IpfsGatewayURL=https://status-im.infura-ipfs.io/ipfs/ ``` But for a local build the URL is the default, which is our own gateway: ``` > nix-build --no-out-link -A targets.status-go.mobile.android /nix/store/1p53m7a6y1kg3vcyd8d06scf3bsyn5rk-status-go-0.157.2-47711c4-android > RESULT=$(nix-build --no-out-link -A targets.status-go.mobile.android) > nix show-derivation $RESULT | tr ' ' '\n' | grep IpfsGateway github.com/status-im/status-go/params.IpfsGatewayURL=https://ipfs.status.im/ ``` This difference causes builds of `status-go` that get uploaded to our Nix cache to not match what developers locally would build, which results in a cache miss. This changes the Nix cache CI jobs to instead of building only dependencies (`buildInuts`) to simply build the generic versions of `status-go` without nightly specific inputs. Signed-off-by: Jakub Sokołowski <jakub@status.im> * nix: fix applying nix.conf by using correct env var According to this line from the docs: >The system-wide configuration file sysconfdir/nix/nix.conf (i.e. /etc/nix/nix.conf), >or $NIX_CONF_DIR/nix.conf if NIX_CONF_DIR is set. Values loaded in this file are not >forwarded to the Nix daemon. The client assumes that the daemon has already loaded them. https://nixos.org/manual/nix/stable/command-ref/conf-file.html#description Our usage of `NIX_CONF_DIR` has been wrong for a while now. The correct way of applying this config is using `NIX_USER_CONF_FILES`. In addition the `extra-substituters` no longer exists in the docs. Use of `trusted-substituters` is necessary according to: >At least one of the following conditions must be met for Nix to use a substituter: > >- the substituter is in the trusted-substituters list >- the user calling Nix is in the trusted-users list https://nixos.org/manual/nix/stable/command-ref/conf-file.html#conf-substituters Signed-off-by: Jakub Sokołowski <jakub@status.im> * Upgrade `react-native-camera-kit` library to resolve camera issues in Sign In screen (#16248) Signed-off-by: Mohamed Javid <19339952+smohamedjavid@users.noreply.github.com> * Update prettier script. (#16324) * Update prettier script. * Add target and component-spec to prettierignore. --------- Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: Mohamed Javid <19339952+smohamedjavid@users.noreply.github.com> Co-authored-by: Alexander <alwxndr@gmail.com> Co-authored-by: flexsurfer <flexsurfer@users.noreply.github.com> Co-authored-by: Jamie Caprani <jamiecaprani@gmail.com> Co-authored-by: Jakub Sokołowski <jakub@status.im> Co-authored-by: Parvesh Monu <parvesh.dhullmonu@gmail.com> Co-authored-by: Icaro Motta <icaro.ldm@gmail.com> Co-authored-by: Andrea Maria Piana <andrea.maria.piana@gmail.com> Co-authored-by: Ulises Manuel Cárdenas <90291778+ulisesmac@users.noreply.github.com> Co-authored-by: Rahul Pratap <rahulpsingh@users.noreply.github.com> Co-authored-by: Yevheniia Berdnyk <ie.berdnyk@gmail.com> Co-authored-by: Mohamed Javid <19339952+smohamedjavid@users.noreply.github.com>
Status - a Mobile Ethereum Operating System
Join us in creating a browser, messenger, and gateway to a decentralized world. Status is a free (libre) open source mobile client targeting Android & iOS built entirely on Ethereum technologies. That's right, no middle men and go-ethereum running directly on your device.
Why?
We believe in a medium of pure free trade, economies with fair, permission-less access and a world without intermediaries. We want to create policies that can exist between friends or scale globally, we want to communicate securely and be uninhibited by legacy systems.
We want to take responsibility for our data, the way we conduct ourselves privately and promote this way of life to a mass audience.
We want deep insights into our own economies so we can make informed, data-driven decisions on how to make our lives better. The Ethereum blockchain, Smart Contracts, Swarm and Whisper provides us a path forward.
If this interests you, help us make Status a reality - anyone can contribute and we need everyone at any skill level to participate.
How to Contribute?
Go straight to the docs or join our chat and choose what interests you:
-
Developer Developers are the heart of software and to keep Status beating we need all the help we can get! If you're looking to code in ClojureScript or Golang then Status is the project for you! We use React Native and there is even some Java/Objective-C too! Want to learn more about it? Start by reading our Developer Introduction which guides you through the technology stack and start browsing beginner issues. Then you can read how to Build Status, which talks about managing project dependencies, coding guidelines and testing procedures. The doc/ directory also has valuable information for contributors.
-
Community Management Metcalfe's law states that the value of a network is proportional to the square of the number of connected users of the system - without community Status is meaningless. We're looking to create a positive, fun environment to explore new ideas, experiment and grow the Status community. Building a community takes a lot of work but the people you'll meet and long lasting relationships you form will be well worth it, check out our Mission and Community Principles
-
Specification / Documentation John Dewey once said "Education is not preparation for life; education is life itself ". Developers & Designers need guidance and it all starts from documentation and specifications. Our software is only as good as its documentation, head over to our docs and see how you can improve what we have.
-
Blog Writing Content is King, keeping our blog up to date and informing the community of news helps keep everyone on the same page. Jump into our chat and discuss with the team how you can contribute!
-
Testers It's bug hunting season! Status is currently under active development and there is sure to be a bunch of learning, build status from scratch or if an android user check out our nightly builds. You can shake your phone to submit bug reports, or start browsing our Github Issues. Every bug you find brings Status closer to stable, usable software for everyone to enjoy!
-
Security Status is a visual interface to make permanent changes on the Blockchain, it handles crypto-tokens that have real value and allows 3rd party code execution. Security is paramount to its success. You are given permission to break Status as hard as you can, as long as you share your findings with the community!
-
Evangelism Help us spread the word! Tell a friend right now, in fact tell everyone - yell from a mountain if you have to, every person counts! If you've got a great story to tell or have some interesting way you've spread the word about Status let us know about it in our chat
Status API
View our API Docs and learn how to integrate your DApp into Status. You can read more about how to add your DApp to Status here.
Give me Binaries!
You can get our Beta builds for both Android and iOS on our website, through our nightly builds or by building it yourself.
Core Contributors
Special thanks to @adrian-tiberius. Without the dedication of these outstanding individuals, Status would not exist.
Contact us
Feel free to email us at support@status.im or better yet, join our chat.
License
Licensed under the Mozilla Public License v2.0
Testing Supported by
