systemaccounting / mxfactorial

a payment application intended for deployment by the united states treasury that eliminates monetary inflation, systemic default risk, and the uncompetitive access to capital

systemaccounting optimizes the flow of capital by expediting the discovery of economic opportunity through physics and data science. dashboarding real-time business performance within an equally-accessible space spanned by a metric not only maximizes capital's throughput between investors and entrepreneurs, it also transparently benchmarks lending rates between borrowers and lenders. in addition to eliminating interest rate manipulation by central commitees, systemaccounting solves monetary inflation and systemic default risk through its practice of cross-user, double-entry accounting. by recording transactions as conserved quantites, user equity remains separate and protected from the liability produced by government-chartered lending firms

content

economic policy as code video series

faqs

q. is this a "cryptocurrency"?
a. no, and please use the word encryption

q. is this a "blockchain"?
a. no, and please use the word replication

q. i dont find any words in here used by the media. what is this?
a. encryption solves access risk. replication solves single point of failure and inconsistency risk. neither of these solutions are relevant to modeling a currency as an electric current. this payment application solves current economic issues by replacing "monetary" policy with a natural physical law. encryption and replication are secondary

q. what is the equation?
a. u = transactions per second, w_i = value conserved per transaction, Mx! = value visible in a combinatorial game

q. do you have any demos?
a. watch the economic policy as code video series

q. how to explain this project to non engineers?
a. share the economic policy as code video series

q. why is the code public if the license is private?
a. publicly used code is a public structure

use cases

public demonstration of the following use cases through a systemaccounting function:

• expressing a conservation law through a data structure disambiguates delivered value from expected value, and replaces committees with an automated financial stability criterion
• producing a scientific measure of the equilibrium price of capital signals the demand for capital with an empirical rate of return instead of a government defined word, and removes the ability of a central authority to manipulate the price of credit
• SELECT SUM(price) FROM transactions WHERE time = NOW(); maximizes & protects for individuals a scientific standard the publicly-measured quarterly or annual 'GDP' violates
• where an industry is chartered, protected, and primarily depended upon by a government requiring election assistance, conserving value & liability (information) separates the balance sheets of governments from individuals, and eliminates socializing the default risk of any individual or firm
• establishing the conditions studied by combinatorial game theory through physics & data science ends public dependency on such resources as credit ratings, quarterly filings, the Consumer Price Index (CPI), and the federal reserve economic data (FRED) platform
• accounts as projective coordinates: structuring transactions between debiting and crediting users across time as a binary logarithmic event creates a 2^n dimensional space in a data model
• data as multivectors: financial value is a bivector-valued function of buyers and sellers adding ownership-coordinates to a 3d space parameterized by "time". the dual positive and negative string values expressed by the anticommutativity of the "creditor" ∧ "debitor" = - ("debitor" ∧ "creditor") exterior product defines the continuity point a time-dependent projection depends on to propagate zero-sum changes to account balances

                                                 ★
                                                 ∧
                                               /   \
                            dual +/− value @ t       dual +/− value @ t+n
                                            /         \
                {                                          {
                  "debitor": "John",                         "debitor": "Mary",
                  "creditor": "Mary",                        "creditor": "Isaac",
                  "item": "bread",                           "item": "milk",
                  "price": "3.25",                           "price": "3.25",
                  "time": "2019-07-12T12:11:31",             "time": "2019-07-14T07:36:15",
                }                                          }

// "Mary" account balance Δ = 0 after selling and buying in
// autonomous market pricing bread = milk

• contracts as code: enabling transaction automation through publicly-contributed scripts, e.g. automating tax, debt & equity sales, dividend, interest, wage and bill payments (input)
• maintaining publicly-accessible static and streaming endpoints servicing third-party visualization and optimization (output)

this project intends to exploit the software engineering community's familiarity with data science to rapidly develop their capacity to describe an economy using mathemtical physics. software engineers may be expediently converted to phd-level experts because they come equipped with the technology to test, adopt, and communicate the subject to others. adding to the project's list of features is designed to foster enough interaction between engineers and the data model that a movement to eliminate nothing but public ignorance becomes generally accepted as possible only when it's precipitated by activism pursued—not in the streets where slogans, bottles, and rocks are blindly hurled at others who are equally frustrated with their economy, but on knowledge's frontier where science and technology are used as tools to empower mankinds revolution in the cloud

environment

• client: mxfactorial.io
• api: api.mxfactorial.io

license

private, receiving added value is sustained & acknowledged by sending value

contribute

• to contribute code, negotiate rates in new or existing issues, fork, build your environment, then send pull requests
• supporters preferring to contribute funds may do so from the financial support page

byoe development

1. git clone https://github.com/systemaccounting/mxfactorial, or fork and git clone
2. make new-iam in project root to create a temporary admin iam credential for your gitpod workspace
3. git checkout -b feature-branch
4. create a gitpod by navigating to a context url in the browser, e.g. https://gitpod.io/#https://github.com/systemaccounting/mxfactorial/tree/feature-branch
5. build your own environment: follow prompts to build infrastructure and deploy app code to aws (10 mins)
6. make test ENV=dev in project root to test creating a transaction request and approval
7. make get-secrets ENV=dev in project root to create an .env file with the CLIENT_URI and GRAPHQL_URI variables
8. navigate to CLIENT_URI and GRAPHQL_URI in a browser to view the web client and graphiql explorer
9. import services/graphql/postman/graphql.postman_collection.json into postman and set the GRAPHQL_URI environment variable to test the api, e.g. graphql/balance
10. make delete-dev to tear down cloud environment (leave workspace running until finished)
11. delete gitpod workspace in browser ui
12. make delete-iam to delete gitpod iam credential

notebook

access ./mxfactorial.ipynb jupyter notebook locally:

docker run \
  --rm \
  -p 8888:8888 \
  -v $PWD/mxfactorial.ipynb:/home/jovyan/mxfactorial.ipynb \
  jupyter/datascience-notebook

requirements

• wireframes
• public drive
• data model

roadmap

• set up managed application & persistence layer
• produce requirements & code for:
  • data model
  • endpoints
  • mobile web client for transactions (write)
  • mobile-enabled web client for visualizing economic activity (read) through the data layer feature of the google maps javascript api

note: both transaction and visualization clients will be strictly served by publicly-accessible endpoints to demonstrate for the u.s. treasury that with enough security, anyone may build an app that submits transaction data to the public ledger, thereby eliminating "banks" from the value transmission equation