/biz/ - Business & Finance

>>18296451
I don't know anything about nano, but an acyclic graph is a data structure where elements point to each other in a particular direction, with none pointing backwards (which would form a cycle, not allowed in a DAG).
Git is structured on top of a DAG. If you don't know what Git is, it's the version control system used by nearly all programmers. Github is a web interface for a Git node. The way it works is everyone can do their own work and "commit" their work as a snapshot, then push that work to their peers. Conflicts are handled during a merge operations which may require manual intervention. In the end you have an authoritative history of all changes made and who made them.
I can see this working in a financial system. You'd have one straight line of checkpoints done with POW, and at any point a person could branch from the main checkpoint into their own world. In this world they can modify the ledger with a sequence of their own free checkpoints, and later submit this sequence back to the main sequence for merging. An automated process will ensure there are no collisions (double spends), and reject the branch if there is one. The person would have to correct their error before resubmission.
Such a system could take a huge amount of work off the main ledger by allowing outside transactions to be merged in all at once. The outside system will need it's own system of trust to ensure they don't end up with a failing merge with no recourse (someone paid you with a double spend and now they're gone). It's also possible to have a "fast-slow" system as well, where an official branch is always operated between any two main checkpoints, and this branch runs much faster than the main branch but with less security. For most transactions this is probably fine. Larger ones will want to wait for the next main checkpoint. I've seen this behavior in some coins. I wonder if this is the implementation.