Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Feature: Account Abstraction - Custom Validation Signature Scheme #191

Open
julio4 opened this issue May 24, 2024 · 8 comments · May be fixed by #229
Open

Feature: Account Abstraction - Custom Validation Signature Scheme #191

julio4 opened this issue May 24, 2024 · 8 comments · May be fixed by #229
Assignees
@OkoliEvans

Comments

@julio4
Copy link
Contributor

julio4 commented May 24, 2024

Description

Account Abstraction replace Externally Owned Accounts (EOA). Accounts are implemented as smart contract called smart wallet.

Account Abstraction allows for validation abstraction, which means that it is possible to implement the validation part of transaction inside a smart wallet in any way possibles.

In this example, we want to show how we can implement a custom validation method using a different signature scheme.

Criteria:

  • Clearly explain the separation between the signer and the account.
  • Focus on the implementation. There’s already lots of explanations about it in the Starknet Book, give a succinct overview of the most important points.
  • SNIP-6 will be explained in Feature: Account Abstraction - Smart Wallet Account Contract #188 (by @Jemiiah), so focus only on the custom validation part.

Resources:

ODHack

To be eligible for additional rewards, be sure to review and follow the ODHack Common Guidelines and Contributing Guidelines.
Be sure to join the telegram group and introduce yourself.
@julio4 julio4 added the ODHack label May 24, 2024
@KodeSage
Copy link

KodeSage commented May 24, 2024 •
edited
Loading

Hi @julio4
my name is James Harrison, A Software Engineer I will love to work on this tasks.
steps I would take to work on this tasks are as follows

  • I would thoroughly go through the starknet book and give detailed explanation on the separation between the signer and the account.
  • I will implement thoughly the custom validation scheme using cairo.
  • timeline to finish this tasks is 4days

@julio4
Copy link
Contributor Author

julio4 commented May 24, 2024

@KodeSage I'll assign you. Please open a draft PR as soon as possible for early feedback on the specific validation scheme chosen. Please do not use generative AI to write explanations as well.

@Jemiiah
Copy link
Contributor

Jemiiah commented May 30, 2024 •
edited
Loading

@julio4 i would love to work on this incase KodeSage is not interested. i know how to go about the work

@KodeSage
Copy link

I'm still working on it, will create a PR very soon

@julio4 julio4 removed the ODHack label Jun 9, 2024
@OkoliEvans
Copy link
Contributor

If this becomes available I'll like to get it done @julio4

@julio4
Copy link
Contributor Author

julio4 commented Jun 19, 2024

If this becomes available I'll like to get it done @julio4

Yes it is available, please take the time to read #200. It will be the first section in the AA chapter so this Signature Scheme example will follow it.

This was referenced Jul 1, 2024
Draft
Open
@Jemiiah
Copy link
Contributor

Jemiiah commented Jul 15, 2024

@julio4 I would love to work on this issue if you allow it 😌🚀

@julio4
Copy link
Contributor Author

julio4 commented Jul 19, 2024

@julio4 I would love to work on this issue if you allow it 😌🚀

@OkoliEvans is already actively working on it currently!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@OkoliEvans OkoliEvans

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Account Abstraction - Custom Validation Signature Scheme OkoliEvans/StarknetByExample
4 participants
@julio4 @KodeSage @OkoliEvans @Jemiiah