A Financial Programming Language
There seem to be various Financial Programming Languages out there. ( to list )
User:Dante wants "Everyone to become their own economist" , enabling "Everyone to code their wished transactions, their personal needs, and their choices of interdependencies".
Dante is interested in creating an annotation system ( programming language ) which can enable all kinds of transactions, with the potential to add any type of architecture as an engine within distributed tools using such language, and enabling all active users to add code into the system.
It is a suggestion for a tool to suggest and enable transactions and financial architectures.
last updates related to threads about this process of understanding how to "programming a self-programmable financial language" ( computing done by users )
or "p2p system for being your own economist" on
The objective being that such potential language could be used by any user of the system, so that they can create and add their own requests ( for beginners ), projects ( more advanced users ), or even add their own financial architectures using the language ( even more advanced ).
Hence make it granular , as to enable simplicity, but potentially interconnected, as to enable complexity,
and enable visualization of inter-dependencies, as to enable transparency, and choice.
From there on, individual users can choose to be connected, or not, to non-transparent architectures that would want to interact wit the networked systems, in which every peer user can create its code, and each peer user can choose to participate or not in transactions defined by other peoples code.
Hence to sum up, the objective is that all existing financial architectures and services can be represented using such language, enabling the data of all types of transactions in all languages to be potentially interdependent, while also enabling emergent forms of direct governance by using each user to choose the type of transactions they are willing to be involved in, and which types of transactions they would like to suggest for other users to participate in.
It can represent interest based credit units, mutual credit , c3, gifts, donations, threshold transactions, f2f, etc
using any type of measurement unit ( objective , but also individually subjective ) while adding any further type of context ( such as geo-location )
while enabling access to information of input and total output to be open, unless they have been closed ( which also enables people to make choices as for the us of closed systems )
Letter sent on July 5 2010 , by Dante-Gabryell Monson :
I realize I picture intuitively such type of relations ( in space, in my mind ), but I do not have an understanding of mathematical representations.
In terms of my current systems thinking, I realize it could be interesting to have some kind of programming language to annotate various components/code that are mostly used.
For example, at the base ( ? ) - request relations : "requests (need)" , "request to support (offer to satisfy need)" - request of request relations : such as "conditions before activating the transactions of the request, or of the request to support" ( such as the architecture of http://www.kickstarter.com/ ) , or "loss of value of certain units over time when in a certain context" ( hoarding ? ) such as with demurrage )
Side example : Some of these conditions being for example, in the current monetary system, repayment of a certain type of unit over a certain amount of time, at a certain interval, plus interest over time. With time, type of unit, and interest being "objects" in the system related to "conditions", and units potentially seen also as the product of this architecture.
and based on these, various potential approaches to make these two meet - approaches which can be "engines/processes" as objects in such language, such as : - direct matching - distributed multi hop matching ( distributed clearing ? ) etc...
- other "functionalities" as objects can be added, such as meta-information systems related to the objects ( geolocation, accumulated content such as energy use or labor time, labor conditions, cumulated individual subjective evaluations, etc )
- p2p "accreditations" of completed transactions ( between giver and receiver ), which can for example be used as a type of data which can be used related to future choice making of individuals, when they evaluate the best "policy" corresponding to their needs, such as for example a policy aimed at maximizing their "personal empowerment ( based on set individual goals or intentions ) by empowering others"
- "active" objects , which can code into the system , such as "individual profiles" which can act, or "project profiles" which can act ( such as by "issuing an architecture related to the transactions they want to project", including requests, or requests to support, with this or that conditionality, etc )
With all of this, I would like to visualize and express all types of architectures !
Through trying to define such kind of broader annotation system, how would a f2f approach, such as the one you propose, be annotated?
It seems to use a distributed multi hop matching. side note: does does it actually create a matching, or does it rather diffuse information of a request ( request as need to receive, or request as support ) as to enable users in the f2f to respond to it by "creating" a request ( to support, or to receive ) that can match it ?
Such as on the freecycle email lists, except that it would be distributed through channels that posses trust ( through private key ) ?
What I would like to see, is through such annotation ( or even using such annotation as a programming language ), enable a broader operating system of inter-dependent networked architectures.
I would also like to use some kind of Bittracker
And a question to all programmers in cc... What language to use ?
I am not a programmer yet, and am not sure what programming tool to use as to best enable such kind of definitions, in this context. Perhaps "Processing" ( http://wiki.processing.org/w/Main_Page ) for ease of use, as a sketch? But not as a software which enables distributed communication with its peers through a network ?
Or would a multi paradigm language be of "best" use ? Such as