Jonathan Rainville 132ea05fc8
feat(accounts)_: cherry-pick Persist acceptance of Terms of Use & Privacy policy (#5766) (#5977)
* feat(accounts)_: Persist acceptance of Terms of Use & Privacy policy (#5766)

The original GH issue https://github.com/status-im/status-mobile/issues/21113
came from a request from the Legal team. We must show to Status v1 users the new
terms (Terms of Use & Privacy Policy) right after they upgrade to Status v2
from the stores.

The solution we use is to create a flag in the accounts table, named
hasAcceptedTerms. The flag will be set to true on the first account ever
created in v2 and we provide a native call in mobile/status.go#AcceptTerms,
which allows the client to persist the user's choice in case they are upgrading
(from v1 -> v2, or from a v2 older than this PR).

This solution is not the best because we should store the setting in a separate
table, not in the accounts table.

Related Mobile PR https://github.com/status-im/status-mobile/pull/21124

* fix(test)_: Compare addresses using uppercased strings

---------

Co-authored-by: Icaro Motta <icaro.ldm@gmail.com>
2024-10-23 09:53:25 -04:00
2024-09-26 09:10:59 +01:00
2023-01-13 17:52:03 +00:00
2024-09-27 06:37:32 +08:00
2022-03-28 13:14:12 +01:00
2022-03-28 13:14:12 +01:00
2024-09-27 06:37:32 +08:00
2024-09-27 06:37:32 +08:00
2021-07-20 10:57:38 +02:00
2024-09-27 06:37:32 +08:00
2024-09-27 06:37:32 +08:00
2024-09-27 06:37:32 +08:00
2024-09-27 06:37:32 +08:00
2024-09-27 06:37:32 +08:00
2024-09-27 06:37:32 +08:00
2024-09-27 06:37:32 +08:00
2024-10-07 13:07:33 +01:00
2024-04-18 18:48:02 +02:00
2016-09-21 10:00:29 +08:00
2024-10-23 12:35:07 +01:00
2024-04-10 11:43:13 +01:00
Description
The Status module that consumes go-ethereum
https://status.im
Readme
Languages
Go 98.6%
Python 0.7%
Shell 0.4%
Makefile 0.1%
Groovy 0.1%