-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Account abstraction/unification #3
Comments
We discussed this on the R&D call yesterday. We have rough consensus that it makes sense to move forward and turn this into a spec. I'll work on a SMIP. The main concerns were from Iddo, who's rightfully worried about: 1. the cost of spinning up SVM just to verify transactions (and the DoS risk), 2. multisigs with daily spending limits being drained through tx fees, and 3. implications on future validator role design. There are also outstanding questions re: how this impacts tx receipts, whether the default() method is allowed to touch state at all, and how we want to "unwrap" or "decompress" transaction data flowing into this method - natively, in Wasm/SVM, or some hybrid. |
So generally I think that what we want is a design that is forward-compatible to enable this feature (custom default()) in the future w/o changing the transaction syntax and signature procedure and for 0.3 only pre-compiled verification should be supported. This is the only way I see how this big feature can be designed and implemented in matter of weeks and not months. |
Re: 1., we still need to work this part out. It depends partly on design, partly on implementation. Ideally the design would involve spinning up the VM - otherwise, the entire idea of AA and a This is intended to be a placeholder issue, @avive can we take further discussion to the research forum? |
design is complete and this has been implemented. will revisit as part of ongoing VM design work. |
https://community.spacemesh.io/t/account-abstraction/151
spacemeshos/SMIPS#49
See also #64
To do:
The text was updated successfully, but these errors were encountered: