Draft: Subledgers implementation #285
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This draft implements subledgers as specified in the specification by @samcamwilliams and @twilson63.
Added Handlers for Spawning Processes:
Spawn-Subledger: Handles the spawning of subledger processes with appropriate tags.NotifySpawn: Collects and prepares subledger initialization data.Init-Subledgers: Initializes subledgers and notifies the deployer.Note: These handlers could potentially be merged into a single handler when fix on spawn and #840 are in production.
Added Handlers for Subledger-Specific Operations:
Credit-Notice: Handles crediting tokens to subledgers.Withdraw: Manages the withdrawal of tokens from subledgers.Improvements Needed:
Code Duplication in
subledger_code.lua: Currently, the code insubledger_code.luais duplicated to assign it to the spawned process. Does anyone know a better way to handle this to avoid redundancy?Stack Issues with Init-Subledgers: Due to code duplication, adding the Init-Subledgers code in subledger_code.lua results in a recursive loading problem. This prevents the creation of sub-subledgers and needs to be addressed.