-
Notifications
You must be signed in to change notification settings - Fork 1
Cost staging #139
Copy link
Copy link
Open
Labels
layer:coreRegarding the core protocol (cost tracking, transactional fabric, etc)Regarding the core protocol (cost tracking, transactional fabric, etc)project:papertag:economicsRegarding economics: dynamics, costs, incentives, etcRegarding economics: dynamics, costs, incentives, etctype:discussionDiscussion or ideas for future direction, input welcome (don't be shy)Discussion or ideas for future direction, input welcome (don't be shy)
Milestone
Metadata
Metadata
Assignees
Labels
layer:coreRegarding the core protocol (cost tracking, transactional fabric, etc)Regarding the core protocol (cost tracking, transactional fabric, etc)project:papertag:economicsRegarding economics: dynamics, costs, incentives, etcRegarding economics: dynamics, costs, incentives, etctype:discussionDiscussion or ideas for future direction, input welcome (don't be shy)Discussion or ideas for future direction, input welcome (don't be shy)
Type
Fields
Give feedbackNo fields configured for issues without a type.
When a worker performs labor, they don't get paid immediately. Rather, this cost must be staged as a sort of owed value. Similarly, when a mining company mines ore, they don't immediately get to pay themselves the resource-cost of that ore. Instead it's realized once the ore is ordered.
It seems to make sense to have some kind of staging area for costs that are yet to be paid to workers. In the case of labor, it would be paid via a bloc-defined trigger but in the case of resources it would be a protocol-defined trigger.
I'm not sure entirely how this looks yet but I need to get it out of my head and into the paper.