(HIP-423) Long-term scheduled transactions

[tinker-michaelj]

Problem

State API

Beta Give feedback

1. Define Schema for block stream-friendly state organization #16059
   HIP-423 +1
   
2. Ensure remaining throttle capacity per second is in a dedicated leaf #16071
   HIP-423 +1
   
3. Add migrations from existing state #16068
   HIP-423 +1
   
4. Update readable/writable stores to use new states #16069
   HIP-423 +1
   
5. Remove old schema state #16343
   HIP-423 +1
   

Preliminaries and tech debt

Beta Give feedback

1. Refactor Schedule handlers for a simpler verification assistant #16044
   HIP-423 +1
   
2. Eliminate duplication in ContractService signature verifiers #16056
   HIP-423 +1
   
3. Add HandleContext#keysWithValidSignatures() #16023
   HIP-423 +1
   
4. Eliminate special case for ScheduleCreate payer key management
5. Simplify recreating per-function throttles from snapshots

Support waitForExpiry=true

Beta Give feedback

1. Add time-driven event processing for triggering scheduled transactions #16019
   HIP-423 +1
   
2. Dispatch each authorized transaction with a separate SavepointStack to avoid tech debt #16311
   HIP-423 +1
   
3. Extend Dispatch to take the throttles being used at consensus #16397
   HIP-423 +1
   
4. Extend Dispatch to take the preferred strategy to validate signatures and authorize the transaction #16312
   HIP-423 +1
   
5. Create an alternate factory for UserTxn #16192
   HIP-423 +1
   
6. Extend ScheduleService with a method that returns iterator over all ExecutableTxn. #16431
   HIP-423 +1
   
7. Calculate correctly the following and preceding chid transactions timestamps #16577
   HIP-423 +1
   

Throttling

Beta Give feedback

1. Do not perform expensive auto-associate/auto-create checks at ingest, throttle at consensus #16398
   HIP-423 +1
   
2. Evaluate simpler strategy of automatically allocating a fraction of network capacity for schedules
3. Prefer a simpler approach of auto-scaling these fractional buckets instead of HIP algorithm

Fees

Beta Give feedback

1. Consider using a simpler cost scaling strategy instead of adding SCHEDULED subtypes #16455
   +0
   
2. Update ScheduleCreateHandlers to charge more for longer-lived scheduled transactions #16479
   +0
   
3. Extend Dispatch to customize the fee charging strategy
4. Validate how costs should scale with schedule lifetime (linear, sublinear, etc?)

Testing

Beta Give feedback

1. Rehabilitate the mono withAndWithoutLongTermEnabled() HapiTest modifier #16010
   HIP-423 +1
   
2. Evaluate ways to generalize use of spec.autoScheduledTxns for rapid coverage #16011
   HIP-423 +1
   
3. Port any long-term specific tests from mono code base. #16012
   HIP-423 +1
   

Solution

Implement the above tasks.

Alternatives

No response