Kujira FIN marketplace: new order books

Good morning, fam. I love you.

A lot has changed in the past week in the @TeamKujira ecosystem. 

Let's take about forms: let's talk about the restructuring of the FIN marketplace and the impact that it has on how I'll be trading, going forward.

The first question you may have, however, is: "Hey, el geophf, love you work [always a good start #protip], ... how did you generate this graph?"

Logically, of course. 😎

1. ./graphista reads the marketplace and generates a CSV-file.
2. ./queries.cyp is a list of queries you run manually to import the data into a @neo4j graph database. Their Aura cloud platform has a lovely little free version I use to render these graphs.

Okay, now that we have the graph, we can query it.

'Query it'-...how?

I see a triumvirate of tokens on FIN:

1. $ATOM

2. $ETH

3. $DOT

I see secundus tokens:

a. $KUJI

b. $OSMO

I see two stables:

א. $USK

ב. $axlUSDC

I see One Ring to Rule them All

$ETH, ...or $ATOM? no: ... $USK?

So maybe those are the Three Rings for Elvin Kings under the Sun?

The point here [narrator: you have a point?] is that it doesn't matter: the graph is going to tell us how to arbitrate on any token of interest.

How?

Elementary, my dear Watson: graph theory.

./queries.cyp includes queries to arb token A, by following the paths:

A -depth-> A 

where depth ∈ [0..3]

Why do I say this?

We're going to generate new arb-paths for $ETH and $DOT, which are both now viable tokens on @TeamKujira blockchain, and we're going to regenerate the $ATOM arb-paths.

Then we're going arb those bags from what I have (basically nothing), to well: something.

Let's talk arbitration.

Arbitration lets you get more A from A, but 'more' is not MegaMind-sized, 'more' is more like: ε-sized.

So, if you're looking for 'geophf is gonna make me rich today!' well: keep looking, fren. Growing bags takes time, at least in my experience.

Meanwhile, it's 8 am, and it's time to generate my morning reports, shave, shower, and go to work.

I'll be updating the triumvirate arb-paths iteratively throughout the day.

Then, ./vern, my main man, ./vern will give me the most efficacious arb-paths.

ETH

Let's start with $ETH. The (sub)graph you see here represents wETH -> a -> b -> wETH, 

and, explicitly, the paths are:

n.name,a.name,b.name,z.name

wETH,USK,axlUSDC,wETH

wETH,axlUSDC,USK,wETH

Going forward, I'm moving the paths to a CSV-file where you can view the explicit paths here.

The $ETH-arb, with paths 2-deep:

Finally for $ETH-arb: paths 3-deep. 

DOT

$DOT arb paths of depths 1, 2, and 3.

Explicated here.

Do you notice something about these paths? Tokens that have both $USK AND $axlUSDC order books become prevalent, so: both $SCRT and $STARS show up more than $OSMO now.

So I have to do those, too.

ATOM

$ATOM arb-paths, explicated here.

We do need to call out, explicitly, the ATOM -> OSMO and the OSMO -> ATOM paths. Why? to avoid the ATOM/OSMO order book when trading is light there. 

The two path-files are 

• ATOM-OSMO.csv
• OSMO-ATOM.csv

And, finally: all arb-paths, everywhere, explicated here.

Fun fact: if you have all arb-paths, you have all paths by extracting sub-graphs that match your endpoints, A -> B, from the set of all arb-paths.