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 #203

Closed
hwwhww opened this Issue Dec 6, 2017 · 5 comments

Comments

Projects
4 participants
@hwwhww
Contributor

hwwhww commented Dec 6, 2017

Subtasks

  • Implement CREATE2 opcode #224
  • Implement PAYGAS opcode #234
  • Standard Account Contract #225

@pipermerriam pipermerriam referenced this issue Dec 6, 2017

Closed

STUB: New transaction format #194

1 of 1 task complete

@hwwhww hwwhww added the eth2.0 label Dec 6, 2017

@pipermerriam pipermerriam referenced this issue Dec 6, 2017

Closed

Sharding Roadmap #190

1 of 15 tasks complete

@pipermerriam pipermerriam changed the title from STUB: Account Abstraction to Account Abstraction Dec 6, 2017

@NIC619

This comment has been minimized.

Show comment
Hide comment
@NIC619

NIC619 Dec 13, 2017

Contributor

I will start to work on the implementation of Account Abstraction #203
and starts with CREATE2 opcode.

Contributor

NIC619 commented Dec 13, 2017

I will start to work on the implementation of Account Abstraction #203
and starts with CREATE2 opcode.

@NIC619

This comment has been minimized.

Show comment
Hide comment
@NIC619

NIC619 Dec 20, 2017

Contributor

I'm half way on adding CREATE2(#224) and PAYGAS opcode(#234) but since CREATE2 involves ENTRY_POINT address( b'ffff…ffff') and other account abstraction implementations like removing nonce(this is still under debate), checking tx.sender address (must be ENTRY_POINT) and different transaction validation function, it seems better to start from fundamental changes first and add those opcodes on top.

Contributor

NIC619 commented Dec 20, 2017

I'm half way on adding CREATE2(#224) and PAYGAS opcode(#234) but since CREATE2 involves ENTRY_POINT address( b'ffff…ffff') and other account abstraction implementations like removing nonce(this is still under debate), checking tx.sender address (must be ENTRY_POINT) and different transaction validation function, it seems better to start from fundamental changes first and add those opcodes on top.

@hwwhww hwwhww added this to In progress in Sharding Phase 1 - Stage 1 Jan 8, 2018

@hwwhww

This comment has been minimized.

Show comment
Hide comment
@hwwhww

hwwhww Jan 31, 2018

Contributor

Notes for nonce abstraction:

  • no nonce in account
  • no nonce in tx
Contributor

hwwhww commented Jan 31, 2018

Notes for nonce abstraction:

  • no nonce in account
  • no nonce in tx
@NIC619

This comment has been minimized.

Show comment
Hide comment
@NIC619

NIC619 Feb 24, 2018

Contributor

Implement PAYGAS opcode: checked.

Contributor

NIC619 commented Feb 24, 2018

Implement PAYGAS opcode: checked.

@hwwhww

This comment has been minimized.

Show comment
Hide comment
@hwwhww

hwwhww Sep 26, 2018

Contributor

deactivate

Contributor

hwwhww commented Sep 26, 2018

deactivate

@hwwhww hwwhww closed this Sep 26, 2018

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