From 271ea3cfb6323ce12808c9c16df75d25ac89112f Mon Sep 17 00:00:00 2001 From: Tomek Marciniak Date: Mon, 15 Jul 2024 12:24:07 +0200 Subject: [PATCH] fix: fix readme tasks --- README.md | 35 ++++++++++++++++++++--------------- 1 file changed, 20 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index a508f00..905e8f4 100644 --- a/README.md +++ b/README.md @@ -56,23 +56,28 @@ classDiagram ## To do and considerations -PoC Scope: -[ ] Update the implementation of `ecdsaProgram` to allow both `secp256k1` and `secp256r1` (accounts being controllable by both Passkeys, and Ethereum wallets). -[ ] Do we need an actual `EntryPoint` smart contract? Can it be replaced with a simple web server running o1js contracts? +The following scopes and milestones are proposed. -MVP Scope: -[ ] `Paymaster` specification (Since Mina is gasless, the implementation of `Paymaster` will probably be a lot different). Would the paymaster's responsibility be paying the 1 Mina account creation fee, and a fixed (potentially 0.1 Mina) fee per transaction? -[ ] Account deployment to Zeko. -[ ] Batch execution of user operations. -[ ] `Account Factory` contract with an off-line stored addresses deployed to Mina/Zeko. -[ ] Integrate MinAA with Pallad (Add new key agent for Passkeys in Pallad, and signing operations with Passkeys). +### PoC Scope -Further scope: -[ ] AA+MPC, TypeScript SDK to programmatically deploy and initialize accounts for zkApps. -[ ] Claimable wallets based on OAuth and email. -[ ] Session keys to enable batch execution of user operations. -[ ] Serverless signing and computation like in Lit Protocol. -[ ] Decentralized solution without any Web server. Will it be feasible? +- [ ] Update the implementation of `ecdsaProgram` to allow both `secp256k1` and `secp256r1` (accounts being controllable by both Passkeys, and Ethereum wallets). +- [ ] Do we need an actual `EntryPoint` smart contract? Can it be replaced - with a simple web server running o1js contracts? + +### MVP Scope + +- [ ] `Paymaster` specification (Since Mina is gasless, the implementation of `Paymaster` will probably be a lot different). Would the paymaster's responsibility be paying the 1 Mina account creation fee, and a fixed (potentially 0.1 Mina) fee per transaction? +- [ ] Account deployment to Zeko. +- [ ] Batch execution of user operations. +- [ ] `Account Factory` contract with an off-line stored addresses deployed to Mina/Zeko. +- [ ] Integrate MinAA with Pallad (Add new key agent for Passkeys in Pallad, and signing operations with Passkeys). + +### Further scope + +- [ ] AA+MPC, TypeScript SDK to programmatically deploy and initialize accounts for zkApps. +- [ ] Claimable wallets based on OAuth and email. +- [ ] Session keys to enable batch execution of user operations. +- [ ] Serverless signing and computation like in Lit Protocol. +- [ ] Decentralized solution without any Web server. Will it be feasible? ## ERC-4337 vs MinAA