You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point, we can take the workflows into production. We won’t have new code for the handlers, and we won’t be using any of the states or other APIs, but we will have the workflows done and in production. At this point we are using the new gRPC handlers and not the ones in mono-repo.
At this point, all pre-handle work will be in the new code and not in the mono-repo. We can actually ship when ready for individual pre-handles, we don’t have to have them all done to ship any. We can ship them as they are available.
At this point, we will have all queries and all pre-handle running on the production network. In theory, these could be done in parallel with the pre-handle work, we don’t have to finish all pre-handle to get started on queries, but practically it might make sense to have everybody focus on one type of transaction at a time.
At this point all transaction handling code, pre-handle, query, gRPC is all being handled by new business logic, but still on the current merkle tree data structure.
At this point, we can use the Schema APIs for handling schema migrations. Up to this point, we have to use the mono-service migration APIs for handling migrations.
Updated Roadmap
hedera-app
#4689hedera-admin-service
modules #4220handle()
method in transaction handlers in each module to delegate tomono-service
#4719Triage
June 9th - Final Date before beginning E2E Testing
hedera-app
module #4198hedera-smart-contract-service
modules #4217hedera-util-service
modules #4221hedera-app-spi
module #4224Remaining Sprint Backlog Items Ready to Be Pulled
prehandle
andhandle
in TokenUpdateHandler #6340handle
for TokenAccountWipeHandler #6389E2E Testing
Iterate++
Final Testing
RecordStreamValidator
implementations #4529Future
minutesUntilScheduledTime
andsizeOfScheduledTransaction
#4154Old Items
At this point, we can take the workflows into production. We won’t have new code for the handlers, and we won’t be using any of the states or other APIs, but we will have the workflows done and in production. At this point we are using the new gRPC handlers and not the ones in mono-repo.
stores
for each module #4725At this point, all pre-handle work will be in the new code and not in the mono-repo. We can actually ship when ready for individual pre-handles, we don’t have to have them all done to ship any. We can ship them as they are available.
At this point, we will have all queries and all pre-handle running on the production network. In theory, these could be done in parallel with the pre-handle work, we don’t have to finish all pre-handle to get started on queries, but practically it might make sense to have everybody focus on one type of transaction at a time.
At this point all transaction handling code, pre-handle, query, gRPC is all being handled by new business logic, but still on the current merkle tree data structure.
For each service, design new merkle state layout and migrate and update stores #4740At this point, we can use the Schema APIs for handling schema migrations. Up to this point, we have to use the mono-service migration APIs for handling migrations.
0x00
) byte. #4753Future
Tests and CI
Merge Platform and Services code together
Metrics and Monitoring
Core Facilities:
Final state
![final state](https://user-images.githubusercontent.com/233103/214102660-a8dacbab-ac01-4edf-bc83-9d6d3ab1aadc.png)
The text was updated successfully, but these errors were encountered: