Skip to content

systemaccounting/mxfactorial

develop
Switch branches/tags
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

systemaccounting

contribute Discord

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, wi = 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:

                                                 ★
                                                 ∧
                                               /   \
                            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 user-generated, 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

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 own 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. install project dependencies listed under root install makefile target
  3. set s3 bucket names in root project.json to unused values
  4. add logging permissions to us-east-1 api gateway with cd infrastructure/terraform/aws/environments/us-east-1 && terraform init && terraform apply
  5. create artifact and origin buckets by duplicating and customizing resources in infrastructure/terraform/aws/environments/init-dev as new ./init-stg directory, i.e. duplicate main.tf and storage.tf from ./init-dev in new ./init-stg directory, customize, then cd infrastructure/terraform/aws/environments/init-stg && terraform init && terraform apply
  6. from project root, build and push all artifacts to s3 with make all CMD=initial-deploy ENV=stg
  7. create infrastructure by duplicating and customizing resources in infrastructure/terraform/aws/environments/dev as new ./stg directory, then cd infrastructure/terraform/aws/environments/stg && terraform init && terraform apply
  8. deploy migrations to new environment rds with cd migrations && make resetrds ENV=stg
  9. deploy client with cd client && make deploy ENV=stg
  10. from project root, make get-secrets ENV=stg to store newly created CLIENT_URI and GRAPHQL_URI values in root .env file for manual testing in browser
  11. OPTIONAL: make all CMD=deploy ENV=stg from project root to redeploy all services

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

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