- Review document [Status Blog - Status vs Telegram](https://docs.google.com/document/d/1bSPxTITJW43b371uqSO3rdOkn96V8c4z63P13HCmSeY/edit#heading=h.d4m03guwjlrf) #reviewed
- [Data collection and terms&conditions are the first major impresisons of opening the client#21293](https://github.com/status-im/status-mobile/issues/21293)
- [# Feat/log and panic#5849](https://github.com/status-im/status-go/pull/5849#pullrequestreview-2321567843) - #approved
- Added a couple of points about `defer` stack order and checked when should the `common.LogOnPanic()` function be called in the `defer` stack (first?).
- Had some [additional conversation](https://github.com/status-im/status-go/pull/5849#discussion_r1771068007) about the order in which panics and defers interact
- See https://go.dev/play/p/A2ik-YSGsWW
- This is potentially a problem
## Ad Hoc
- Send Arwen the Cross IFT Suggestions [[#Cross IFT Suggestions]]
- Asked Eric if he would be able to add as necessary any other legal team members to the group you created? https://github.com/orgs/status-im/teams/legal
- Added a branch rule on `master` that requires all PRs to be reviewed by the code owners.
- Opened the first PR, requires approval from Legal team:
- Where can I learn more about the Rhythm of Business? Learn more about the ROB here: https://www.notion.so/IFT-Rhythm-of-Business-e61b16873554470d892b20d70fbf014f#cbb05629eeea47e69d555db7badd6d38
- Where can I find the IFT Annual strategy? Read the 2024-2025 IFT strategy here: https://www.notion.so/33838150ef0b42b3993aa2a963e15503?pvs=24#17f148a5a00c44869ed566c0d3fe04d8
- Project Steering Committee Workspace: The document is open for feedback today and tomorrow (16, 17 September). The goal of the September meeting is to establish a baseline and kick-off the work of the committee. Notion, here: https://www.notion.so/Workspace-Project-Steering-Committee-fd0af02def0c459cb9cf4de7f68dc5bf. Document, here: https://docs.google.com/document/d/1TYWvktmtgCtZykGmGiFxQzKTAyr6V55N81ZIUM3bvOU/edit
- IFT Steering Committee Workspace: The document will be open for feedback next week (23, 24 September). Narratives will be finalised that same week by the committee. All IFT Studio Teams set commitments and tasks between 30 September and 4 October. Notion, here: https://www.notion.so/Workspace-IFT-Steering-Committee-967af9f4f4754a1fa98b18971d7c4715
- __“I still have questions!”__
- If you still have questions on decision-making that are relevant to the whole org, add them to this document: https://docs.google.com/document/d/1zieqnRMtplw5XLxMypmhFZdNoPjrmAcLkIKZzjQsNz8/edit. I’ll personally go through every relevant question before the October Townhall (14 October).
- In this meeting, the team discussed the status of wallet security testing. They acknowledged that the wallet was released without a formal audit, unlike previous releases, and decided to conduct internal pentesting before seeking external certification. They considered using a familiar security firm, Least Authority, for an external audit of a specific wallet version. The team addressed concerns about which code version to test and agreed to finalize a timeline. Next steps include reaching out to the firm for quotes and scheduling further meetings to discuss progress
- [Least Authority audit of Keycard integration of Status Desktop](https://github.com/status-im/least-authority-audit/blob/master/initial-report/Least%20Authority-%20Status%20Desktop%20Client%20and%20Keycard-go%20Initial%20Audit%20Report.pdf)
