Implement CIP-66 TX type

[carterqw2]

See CIP-66.

Tasks

Preview Give feedback

1. Accept CIP-66 transactions in legacypool #189
   type:enhancement +1
2. Sort CIP-66 transactions in legacypool #190
   type:enhancement +1
3. Validation of CIP-66 transactions in legacypool #191
   type:enhancement +1
4. Handle CIP-66 transaction in State Tansition Function #196
   type:enhancement +1
5. Receipt handling for CIP-66 transaction #195
   type:enhancement +1
6. Add CIP-66 transaction e2e tests #192
   type:enhancement type:tests +2
7. Add CIP-66 transaction unit tests #193
   type:enhancement type:tests +2
8. Add CIP-66 transaction tracing tests (if necessary) #194
   type:enhancement type:tests +2
9. Plan CIP-64 to CIP-66 switch #112
   type:question +1

[mcortesi]

@karlb i think having an single issue with 120hs of estimate will make it very hard for you to provide updated estimates along the way.

Most probably your thinking process for the estimate was to provide an estimate to each of the "tasks" in the tasklist, and the sum was 120hs. So maybe it's worth splitting into smaller tasks.

Similary. Are the items on the task able to be done in a vaccumm? Can you work on one of the times, and check them, then on the next? If that's the case, more reason to split it, since you DO have checkpoints. Even that most probably you need some "skeleton task" where you create some basic types. This will also allow you to split the tasks into many people.

cc @lvpeschke