tokenomics package implementation

Key Points

1. tokenomics packaged defines interaction with blockchain for the crypto-micropayments layer of the platform;
2. for this milestone, the implementation of tokenomics package amounts only to the implementation of the basic designed interfaces, so that the work can be picked up in Public Alpha Mainnet milestone scheduled later;
3. We want to implement minimal interfaces so that to minimize re-architecturing and re-factoring this aspect of the DMS when implementing Public Alpha Mainnet milestone;

Work Package Deliverables

For the v0.5.0, the tokenomics package implementation should include the following deliverables:

No	Deliverable	Proof
1	Minimal necessary interfaces as designed and specified in the design work package	As determined by design wp / We can consider this done as the package is closed and we have moved to the interface implementation phase
2	Implement contract closure sequence in deployment plan execution as a part of the job orchestration sequence	This has to be prioritized with respect to v0.5.0 release process and different release candidates
3	Each job invocation call should include reference to the contract, so that it could be checked / accounted for later; Implement tokenomics interface (and contract structure) so that they fit into the invocation step implemented by issue Job invocation and allocation sequence implementation
4	Implement Contract settlement after the job is done within the job orchestration sequence, considering how the contract was used and accounted during the invocation as well as Execution monitoring sequence	This has to be prioritized with respect to v0.5.0 release process and different release candidates
5	Consider Job completion sequence and logic and participate in the issue when implementing the above
6	Implement contract database and interface with it so that contracts could be signed off-platform (but using DID / signatures) but used in NuActor system in a way that makes it easily extendable to micro-payment layer integration after v0.5.0 release
7	Align the interface implementation with network tokenomics design epic and work done within its scope	in coordination with @0xPravar

Timeline

Minimal time as needed for minimal implementation. What is 'minimal' is determined by package design;

Additional notes and context

1. re-factored dms should first serve the needs of Public Alpha Solutions milestone and then Public Alpha Mainnet needs;
2. this work should balance the needs of above milestones, their timelines and minimize potential technical debt;
3. Given that minimal implementation is needed for this milestone, consider the preliminary design considerations and the work done until now, considering that this work will be further used in Public Alpha Mainnet milestone:
   1. Deploy our own cardano-node on a centralized server;
   2. Create an api that queries the blockchain using the cardano node
   3. only expose endpoints needed for DMS (for now at least)