This Air-gapped, accounting system for IOTA and Cardano is a client/server database and application generator.
Everything including the generator was written in plain vanilla javascript, HTML, and CSS without anyone else's frameworks, databases or tools.
There are no packages or dependencies other than NodeJS and the javascript libraries for the currencies you use.
This makes for manageable security auditing and reduces the possibility of package supply chain attacks. Another benefit is simple installation.

A code generator reads metadata from a data dictionary and creates the client side user interface and the server side code which is much the same for all tables in the system. So once the generator and the data dictionary have been audited, then the system as a whole is largely proven to be secure. That's because the generator creates the same basic code throughout the entire system. Changes to the code are made in one place and ripple down to all parts of the system automatically when the system is regenerated.
The generated server side code will run on most any computer using most any operating system.
The generated user interface runs in the browser.

This software generates secure accounting/banking systems for cryptocurrency that individuals, corporations, and governments can use for managing their business and for cooperating with each other.

Built to run on a single airgapped PrivateKeyVault for individuals or on an airgapped network for large institutions or government. All this code will run on any device that can run NodeJS.
This is the last piece of the puzzle in The PrivateKeyVault family of repositories.

The code generator and all the generated code is extremely well commented and very easy to read so as to facilitate an audit. A video tutorial will be made soon explaining how it all works and what each line of code does. This will also facilitate an audit.

• Database Functionality.
  • JSON database is human readable and easy to reason about.
  • Locking is used to make the application multiuser.
  • An unlimited amount of users and very complex behavior can be supported through the interactions of these simple systems with smart contracts.
  • Transactions are rolled back if any part of a transaction fails.
  • All records in the database (no matter from what table) get their unique ids from a single incremented source so that every record has a system wide unique id that identifies when it was created with respect to all the other records in the database.
  • Any adds, changes, or deletes to a record are recorded in a log that captures the entire record in it's new state. This along with the system wide unique ids allows the entire database to be reconstructed to represent any point in history.
• A Code Generator - Meta-Programming:
  • Rather than writing code such as: server-side page handlers along with Post, Get, Put, and Delete Validation code, and then writing the client-side HTML forms and supporting javascript for queries, adds, updates, and deletes for every table in the database, we have a script called meta.js to do that for us. It's a program written entirely in vanilla javascript which contains instructions for building working sofware. This code generator reads metadata from the data dictionary which is a JSON file containing data definitions, and the business rules that make each table, each record, and each field unique. Also in the data dictionary are any customized code snippets for behaviors which must depart from the business rules in the generator. Running the generator assembles all this information into well commented, working software that is the accounting/banking system. The final code is very easy to read and reason about because all the looping was done when the code was generated to produce simple javascript and HTML that needs to do only one job. This method of programming (Meta-Programming) is compatible with Procedural Programming, Object Oriented Programming, and Functional Programming.

Generates a query screen for each table in the system.
Search for records and save your queries to use again.

This is a NoSQL database application generator.
Generate tables for:
* General Ledger, Inventory, Purchase Orders, Accounts Payable, Customers, Vendors...
* Generate the system for whatever you need to manage, just like any accounting system.
Each record is just a line of JSON in a table.
Each table is just a text file full of JSON lines.
A generated app is just a collection of JSON editors, each generated to handle a particular JSON table.
JSON editors support records (JSON lines) of unlimited length, unlimited nesting levels, and enforce your schema.

• Like any accounting system, this application maintains it's own ledger.

  • The system does not rely on the blockchain ledger to report balance information although both ledgers must reconcile correctly.
  • This is for increased reporting performance and to track required information which is not captured on the blockchain.
  • Think of it this way: The controller of a company does not ask the bank how much he has in his bank account - he already knows from looking in his own accounting system. In the same way, a modern accounting system for cryptocurrency must track balances without needing to query the blockchain. This system works as follows: The seller's accounting system generates a smart contract when the sale is made. The customer enters into the contract. At the appropriate time, the contract notifies the customer that it is time to make a payment. Following the typical path through the contract, the customer pays the contract and the contract notifies the accounting system. The accounting system is updated automatically and the smart contract is closed. This model does not account for the fact that anyone can put funds in any address but it does make billing and matching invoices to payments automatic. Anyway, sidechains and hydra heads might be used to gain control over what may be deposited into an address and maintaining a node is a good way to reconcile and index what is happening on the blockchain.

• Accounting sytems joined through blockchains make triple entry accounting possible:

  • This means that not only must the ledger balance within a company but ledgers must balance across companies, banks, and government agencies.
  • This is the ultimate in transparancy. Triple entry accounting will help the public make good decisions and fight corruption.

• First a simple database application was written and tested. Then code templates were modeled into the generator and data dictionary from the programs in the simple application. From that point on, changes to the application have been made in the generator and in the data dictionary. After any changes are made, the application is regenerated by running the generator. This way, major changes to functionality ripple down through the entire system without having to change the handlers for each table and their user interfaces. This eliminates most programming errors, enforces a uniform user experience, and allows us to make big changes to the system in a very short amount of time. Any fixes are made in one place and ripple down to all affected parts.

  • The big payoff here is in the audit. As a system grows in size it becomes exponentially harder to audit. So rather than trying to audit the generated code. All we need to do is audit the code generator and the metadata used to generate the application. This is a much smaller and more manageable job thats lead to much tighter security and faster fixes when security flaws are discovered.

• Generate truly random seeds (not pseudo-random) with special hardware built into every raspberry pi 2, or use another method if you want,

Large centralized systems are very hard to secure. That's why we keep hearing about hacks at large institutions. Large means lots of vulnerabilities and complex means that these weaknesses are very hard to see. This doesn't matter so much with a large accounting system when the actual funds they track are secured by banks. But an accounting system for cryptocurrency also protects the currency from theft. It must be both accounting system and bank.

Small simple systems are inherently more secure and easier to protect because small means fewer vulnerabilities and simple means those weaknesses are easier to spot.

Since the accounting/banking system we are building is for a decentralized ledger, it does not have to be big or complicated as in centralized systems. Think about how very simple creatures, like bees, when grouped together perform complex behaviours, like voting, in a very efficient manner without any centralized system to count the votes - without a centralized system to get hacked. There will be many of these simple accounting/banking systems (bees if you will) that when working together will provide the complex behaviors society needs for efficient collaboration.

• Smart Contracts - How Our Small Accounting/Banking Systems Interact With Each Other To Do Big Things
  Think: smart money, Think: smart information
  Now we can embed computer software into the money and data we send which defines how we want them to behave.
  These smart contracts are created and authorized by our accounting/banking systems and then executed on special distributed ledgers called blockchains.

• Keeping Control of the Process
  We don't want our busy little accounting/banking systems moving money, casting votes, or transceiving any kind of information without our explicit knowledge and consent. This is why we have developed this open source airgapped computer called the PrivateKeyVault to run our little accounting/banking systems. This computer ensures that no information moves in or out of the system without a human gatekeeper reviewing the content and explicitly granting permission to allow the transmission. Any computer can be used but is should be airgapped and physically secured to prevent tampering.

Let's get started.
To use this application simply follow the instructions below.

• Install NodeJS on your airgapped computer and your online computer if you are using two machines.
• If you are just experimenting with small amounts of IOTA then you may prefer to use an online machine only.
• You may be wondering, how am I supposed to install software on an airgapped machine that does not connect to the Internet?
• Your airgapped computer does not have any private information on it yet, so for right now it's ok to connect to the Internet.
• When all the software is installed and you are ready to sign transactions, then you simply pull the plug on the Internet and never connect to it again.
• Then you will create new seeds and new addresses from behind the airgap and use these instead of the experimental ones you are playing with now.
• If you are using a PrivateKeyVault or a raspberry pi 2 then NodeJS installation instructions are here.
• Otherwise download NodeJS for your system here.

• Check out the documentation - found here
• The iota.js library and install instructions are found here.
• To install:
  • Make a new directory on each machine. Call it iotajs.
  • At the bash console, cd into the directory.
  • Execute the following command at the bash console to create a package.json file.
  • The package.json file is used to manage your project.
  • npm init Accept all the defaults.
  • Next install the iota.js library by executing the following command at the bash console.
  • npm install @iota/core

• Then execute the following command at the BASH console.
• git clone https://github.com/johnshearing/IOTA-Secure-Airgapped-Accounting-System.git
• Now the Client/Server wallet is installed in a new directory called IOTA-Secure-Airgapped-Accounting-System
• Change the name of the directory to something shorter. Call it ias for IOTA Accounting System.
• At the BASH console, CD into the ias directory

Run the following command to start the NodeJS server:
node ./index.js
Finally, open your browser and enter the following address:
http://localhost:3000/
You should see the application running in your browser.

The app runs well but it doesn't do anything IOTA or Cardano related yet.
Functionality to manage cryptocurrency will be built in very shortly.
The focus now is on getting the framework right.
Then building on top of this framework will go quickly.

This project depends upon IOTA and Cardano libraries. So we are trusting that the IOTA foundation and IOG have taken all the necessary steps to secure their libraries and all dependencies. In the future we can write and audit our own libraries to interact with the IOTA Tangle and the Cardano Blockchain but this is not an appropriate place to start our work.

This code has evolved into a system which is capable of describing and changing its own data dictionary - its own DNA if you will. The generator reads JSON from the data dictionary which contain instructions to build all the forms and code required to make and manage JSON documents. These generated forms and code are descriptive enough to make valid entries in the data dictionary which created the forms and code in the first place. So this application generator can now be used to build, maintain, and change itself as well as to build other types of database applications and data transformation utilities. Oddly, while the JSON produced from the generated forms can contain all the same data as the JSON in the data dictionary from which it was produced, the data structure of the new JSON is different from the original and so will require a different generator to produce a form which is capable of replicating the original JSON from the data dictionary. It seems it may be difficult or impossible to build a machine that can reproduce it's own exact form. I wonder if we are bumping into Godel's Incompleteness Theorems. In any case, this experiment shows that it is possible for a machine to produce a different (complementary) machine which is capable of producing it's parent in exact detail. This is how DNA replicates.

This video animation shows how DNA is used to manufacture proteins.
The JSON in the data dictionary holds this same relationship with the generator and the HTML forms produced.
The JSON tells the generator how to make forms in the same way that DNA tells RNA how to make proteins.

This video animation shows how proteins are used in the replication of DNA.
It shows the complementary nature of the two strands which make the double helix.
This is the same complementary relationship between the two lines of JSON in the data dictionary.
So it appears that I bumped into the same problem that nature encountered when building a replicating machine.
It also appears that my solution was the same.
This is not surprising - as you will see in the next section - my methods are the very same as those used by nature.

Trust the Lord with all thine heart; and lean not unto thine own understanding.
In all thy ways acknowledge him, and he shall direct thy paths.
Proverbs 3:3-6

When I started this project I had only a vague idea of what I was trying to accomplish.
I wanted to make an accounting system for cryptocurrency that would be easy to audit.
All I do is write, test, meditate on the results, study, delete the bad stuff, and write again.
I'm doing the work but I'm not trying to control were it's going.
Perhaps some will understand when I say that the experience is spiritual and that the entire project is a demonstration of faith.

Most people need to know what they are going to make before they start their work.
But I have discovered that it is possible to accomplish tasks that are way beyond the limits of my own intellect by letting go of the big plan and just doing the work set down in front of me. This is exactly what nature does.
I feel blessed and I love God. The work you see here is the result.

Thanks, John