Skip to content

Commit 255f6c7

Browse files
author
HackMD
committed
last changed at Apr 24, 2024 11:11 AM, pushed by Ryan Betts
1 parent 237baf3 commit 255f6c7

File tree

1 file changed

+41
-0
lines changed

1 file changed

+41
-0
lines changed

meetings.md

+41
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,47 @@
44

55
[Community Calendar](https://lu.ma/securedesign)[Github Discussions](https://github.com/ChainAgnostic/secure-design/discussions)
66

7+
## #12 April 24, 10am PST
8+
9+
### In attendance
10+
11+
- Ryan Betts, free agent (@depatchedmode)
12+
- Dan Finlay, MetaMask (@danfinlay)
13+
- Barbara Schorchit, MetaMask
14+
- Aaliyah Pierre
15+
16+
### Agenda & Notes
17+
18+
- 12th meeting milestone! Quick review of purpose:
19+
- focus on safe and secure web3 UX
20+
- safety and security must be commoditized; not a USP / product differentiator
21+
- "no defaults" — needs are very individual, and so individuals should be supported by best practices most relevant to them
22+
- EIP-3074: https://github.com/ChainAgnostic/secure-design/discussions/16
23+
- Dan: what is at the core of 3074? "Can you let somebody do anything?"
24+
- "We should default to we aren't sure it's safe to let anyone do anything today"
25+
- There should be multiple approaches, based on persona
26+
- Is this a dAPP tool, a wallet tool or ...?
27+
- It's a tool for enhancing EOAs to explore SCA interfaces. This leads to "what are better interfaces?"
28+
- Invokers are an opportunity to experiment with radical authorization patterns
29+
- Safety could be provided by the wallet itself (eg. Metamask)
30+
- [Permissions Standard?](https://www.notion.so/metamask-consensys/Onchain-Permissions-Standard-1ca8cf7534f245cc9c06e13abbd716c7)
31+
- Zero-dev - contract account wallet w permissions system
32+
- Ryan: Permissions (like AUTH) should be broken up into smaller bits!
33+
- Dan: What are those bits?
34+
- Dan: presenting onchain permission standard snap
35+
- Things that could be sketched via tightly-scoped permissions
36+
- token allowance / permit
37+
- Voting & vote delegation
38+
- what would a non-standard permission look like?
39+
- eg. warpcast permission delegation
40+
- Next steps:
41+
- Write a blog post about:
42+
- current UX understanding of 3074
43+
- the need for dApps to support both types of accounts
44+
- the benefits of a world where dApps can declare what they need before wallets reveal it
45+
- benefits of a world where dApps can just-in-time ask for permission — when it's needed
46+
- Organize next call: Berlin Blockchain Week in-person?
47+
748
## Wallet UnSalon: EthDenver 2024
849

950
### In Attendance

0 commit comments

Comments
 (0)