Skip to content

Protocol: Contract Deployment #3104

@iAmMichaelConnor

Description

@iAmMichaelConnor

Note: much of this will already have been written in the existing docs. It'll just need some tweaking (see here for the kinds of tweaks: https://github.com/AztecProtocol/aztec-packages/blob/master/yellow-paper/docs/intro.md).

Outstanding protocol questions that need to be resolved:

  • Remove the contract tree?
  • Do we enable contract bytecode upgrades?
    • How? (See discourse)
  • Do we enable contracts to be deployed from other contracts?
    • (Note: earlier in the year it was decided "No" - has our understanding of the problem changed?)
    • How?
  • The VM bytecode commitment circuit needs to be designed.

A list of things to consider:

  • Contract Deployment
    • Computing a contract address
    • Nullifying a contract address
    • Function Tree
    • Portal contract address
    • Broadcasting Bytecode (under various scenarios) and other contract info
    • Committing to VM bytecode

Metadata

Metadata

Labels

A-documentationArea: relates to documentationA-protocolArea: relates to designing / explaining the protocol

Type

No type
No fields configured for issues without a type.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions