But I do not see BOW LPs as a viable part of my Kujira-portfolio: they are far too buggy, 'disappearing' liquidity too often, requiring I SUBMIT TICKETS TO RECOVER FUNDS!??!?
Monday, March 27, 2023
Kujira BOW LP-efficacy: an analysis
But I do not see BOW LPs as a viable part of my Kujira-portfolio: they are far too buggy, 'disappearing' liquidity too often, requiring I SUBMIT TICKETS TO RECOVER FUNDS!??!?
Thursday, December 29, 2022
Graph-theory pop-quiz: remove risky FIN order books
CAVEAT:I won't mind of you remove the $SCRT and $STARS tokens altogether.I will be quite put out of you remove either the $ATOM or $OSMO tokens. Remove NEITHER $ATOM NOR $OSMO.Those have viable arb-paths (just not viable ones that are ATOM/OSMO or OSMO/ATOM-adjacent).
DEFINITION of DONE:
Queries against the graph generate arb-paths for all-isomorphic-paths.csv that do not include ATOM/OSMO, OSMO/ATOM, nor SCRT nor STARS.
ATOM-OSMO.csv, OSMO-ATOM.csv, and all other CSV files in ch08/efficacy/data/ become obsolete (why?)
Friday, December 16, 2022
Rust pop-quiz: all-paths vern
Rust pop-quiz:
improve ./vern:
So that ./vern takes a file of ALL arb paths (besides the markets), and two arguments: start-coin, A, and end-coin, B, and finds most efficacious paths, A -> B.
- (answer)
Tuesday, December 6, 2022
Trading policy
- Cancel the trade.
- Run ./vern from the last executed trade in the path, creating a new path.
- generate that new path in ./gantt
- execute the new trade.
Monday, December 5, 2022
Rust pop-answer: vern-prime
Rust pop-answer to generalizing ./vern to any paths, A -> B:
./vern, my main man, ./vern got a face-lift.
n.b.:
./vern n A data/market.lsv data/A.csv
For some token, A
is idempotent to
./efficacy n data/market.lsv data/A.csv
Sunday, December 4, 2022
Rust pop-quiz: ./vern-prime
Hint
- (answer)
Friday, December 2, 2022
2022-12-02 Trade: 140 OSMO -> ATOM
I'm going to do a little experiment. @TeamKujira has silently minimized the $OSMO-play. None of their LP pairs has $OSMO.
So I'm going to trade away my $OSMO for $ATOM. One approach is:
- OSMO,ATOM
But I think ./vern has a better approach:
- OSMO,axlUSDC,KUJI,USK,axlUSDC,ATOM
- Which way will be faster?
- Which way gets more more $ATOM?
- Which play will I go for?
2022-12-03 placed: 70.27 $axlUSDC -> _ $KUJI, BUY at 0.573retracted- OSMO,axlUSDC,USK,KUJI,ATOM
- 2022-12-06 placed: 70.27 axlUSDC -> _ USK, SELL at 0.9569 fulfilled
And we have a winner!
The circuitous route-branch
- I canceled the stuck 70.27 axlUSDC -> KUJI order
- ./vern, my main man, ./vern tells me to place this order:
- retract order
- place new limit order, BUY at 0.618 (instead of 0.61).
- 2022-12-06 placed: 67.24 USK -> _ KUJI, BUY at 0.618 fulfilled
- 2022-12-07 placed: 63.1055 USK -> _ ATOM, BUY at 9.005 fulfilled
Closing a long-play trade
2022-12-02 Trade: 100 $axlUSDC
Let's 'create' $axlUSDC.
./vern says:
- axlUSDC,USK,ATOM,OSMO,axlUSDC
but, of course, we wish to avoid ATOM / OSMO order book (?) so the path around that is:
- ATOM,KUJI,USK,ATOM,axlUSDC,OSMO
Our gantt-chart is:
Friendly reminder (to myself, mostly) that gantt-charts are only good up to the point where they are made. Changing market conditions may require (significant) course corrections. Caveat trader.
The first trade in this series is:
- axlUSDC,
OSMO,ATOM,USK,KUJI,axlUSDC
Thursday, December 1, 2022
2022-12-01 Trade: 100 USK
Next, ./vern suggests a $USK-trade.
- USK,axlUSDC,KUJI,ATOM,axlUSDC,USK
It's a straightforward path.
... that never got off the ground. 🙄
USK,ATOM,OSMO,axlUSDC,USK
- 2022-12-06 placed: 100 USK -> _ ATOM, BUY at 9.488 fulfilled
- USK,ATOM,(KUJI,USK,ATOM,axlUSDC),OSMO,axlUSDC,KUJI,USK
- USK,ATOM,(KUJI,axlUSDC,OSMO),ATOM,USK
- OSMO,axlUSDC,KUJI,USK,ATOM























































