Epic: Modularize Token Service Implementation #5767
Labels
Epic
A body of work that can be broken down into specific tasks.
Hedera Token Service
Issues related to the Hedera Token Service.
Modularization
Issues or PRs related to modularization
Milestone
In phase one, we will see a full CI run pass, with Token Service operations largely performed by workflows and modularized business logic and the Merkle tree root being
MerkleHederaState
.📨 The issue is still in draft and will be completed with sub-issues
Staking Service And CryptoTransfer Implementation
handle
#6395.pureChecks
andvalidateSemantics
implementations for CryptoTransferHandler #6412TransferList
andTokenTransferList
for records in finalize method looking at state changes #7217PBJ
Account
PBJ Object instead of Account and AccountBuilder implementations #6104AccountID
andTokenID
in all the places in PBJ objects under state instead oflong
#7092PRE-HANDLE
Pre-handle will now be "workflow-aware", so within
HederaMerkleState#preHandle
, we will first extract the function, and then either call into themono-service
signature expansion; or into the pre-handle workflow.Tasks
pureChecks
andvalidateSemantics
implementations for Crypto operations (Other than CryptoTransfer) #5805pureChecks
andvalidateSemantics
implementations for Token operations #5806HANDLE
Once again handle will become workflow-aware, so that within
HederaMerkleState
we can immediately adapt a platformTransaction
with metadata derived from the pre-handle workflow into aSignedTxnAccessor
.However, instead of delegating the final business logic to a
TransitionLogic
, this must be done via aHandler
that (as in INGEST),Tasks
QUERY
As above, ideally the adapters are implementing API's that approximate what we expect to be the final versions. (Or at least are highly suggestive of what will have changed/improved in the final API's.)
Testing
The text was updated successfully, but these errors were encountered: