-
Notifications
You must be signed in to change notification settings - Fork 1
Recurring orders #136
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
Description
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.
One thing that keeps popping into my head over and over is the idea of recurring orders.
This might be able to model things like bloc taxation (#64): when a member joins, they accept some form of contract, which the protocol automates to enable periodic purchasing of some service owned by a bloc. If some concept of loans are somehow worked out, it could be used for repayment of loans as well. This is really preliminary and might be a crap idea, I'm just kind of adding it so I don't forget.