[Epic]: ♻️ Revamped contract deployment

[spalladino]

Epic issue for tracking development of the new contract deployment scheme as specified in the yellow paper. The overall idea is to keep old deployments working while we gradually implement the new ones side-by-side, and only then remove them.

⚠️ Constructor abstraction requires reading nullifiers to check that a contract has been initialized. If it isn't yet possible to read a nullifier in the same tx that it was emitted, then some flows may not be implementable for the time being.

Introducing contract classes

Beta Give feedback

1. [contract-deploy] Store separate structs for contract classes and instances #4053
   +0
2. [contract-deploy] Compute addresses using class id #4054
   +0
3. [contract-deploy] Allow registering classes and instances separately in PXE #4055
   +0
4. [contract-deploy] Update kernel checks for called functions to rely on contract classes #4056
   +0

Supporting private deployments

Beta Give feedback

1. [contract-deploy] Execute a private function in an undeployed contract #4057
   +0
2. [contract-deploy] Construct a contract privately from another contract #4058
   +0
3. [contract-deploy] Construct a contract privately from aztecjs directly #4059
   +0
4. [contract-deploy] Add deployer field to contract address #4434
   +0
5. [contract-deploy] Verify executed bytecode in PXE #4435
   +0

Implementing constructor abstraction

Beta Give feedback

1. [contract-deploy] Macro for emitting an initialization nullifier in the constructor #4060
   +0
2. [contract-deploy] Macro for checking initialization nullifier in all private functions #4061
   +0
3. [contract-deploy] Macro option for removing initialization nullifier check in a function #4062
   +0
4. [contract-deploy] Support multiple constructors in the same contract #4063
   +0
5. [contract-deploy] Verify that initialization arguments match address preimage #5154
   +0

Supporting public deployments

Beta Give feedback

1. [contract-deploy] Implement class registry contract #4069
   +0
2. [contract-deploy] Listen to class registry events in nodes #4070
   +0
3. [contract-deploy] Implement instance deployer contract with private deploy function #4071
   +0
4. [contract-deploy] Listen to instance deployed events in nodes #4072
   +0
5. [contract-deploy] Validate that the deployment nullifier is emitted in the public kernel circuit #4076
   +0
6. [contract-deploy] Public deploy function in instance deployer #4073
   +0
7. [contract-deploy] Add public constructors #4074
   +0
8. [contract-deploy] Universal deploy methods for instance deployer #4075
   +0
9. [contract-deploy] Broadcast individual private and unconstrained functions from ClassRegisterer #4427
   +0
10. [contract-deploy] Capture individual functions broadcasted from ClassRegisterer in the node #4428
    +0
11. [contract-deploy] Broadcast all private and unconstrained functions from ClassRegisterer #4462
    S-needs-discussion +1
12. [contract-deploy] Load broadcasted instances from the node in the PXE #4463
    +0

Wrapping up

Beta Give feedback

1. [contract-deploy] Include class and instance contracts in genesis #4077
   +0
2. [contract-deploy] Remove deployment transactions #4078
   +0
3. [contract-deploy] Remove contract tree from global state #4079
   +0
4. [contract-deploy] Review aztec.js and aztec-nr APIs for private and public deployments #4080
   T-epic +1
5. [contract-deploy] Implement "internal" as an app-level check in a macro #4449
   +0
6. [contract-deploy] Update benchmarks #4644
   +0
7. [contract-deploy][docs] Add details on the contract deployment flow on the docs #5460
   +0

Related issues

Beta Give feedback

1. Inconsistent constructor calls #3210
   T-bug +1
   
2. [contract-deploy] CLI check-deploy should return failing exit code if contract is not deployed #3400
   C-cli +1
3. [contract-deploy] Store bytecode hash for a contract in addition to verification key hashes #3395
   A-protocol +1
4. [contract-deploy] Ensure there are no private functions with duplicate selectors #4433
   +0

[PhilWindle]

Closing this epic as it's very old. If anything still needs to be done, a new epic should be created and issues created against it.