Recent changes to this wiki:

DAO person
diff --git a/ikiwiki.setup b/ikiwiki.setup
index ed1b8a8..96638cf 100644
--- a/ikiwiki.setup
+++ b/ikiwiki.setup
@@ -3,7 +3,7 @@
 # Setup file for ikiwiki.
 # name of the wiki
-wikiname: wesl-ee 🐉
+wikiname: wesl-ee
 # contact email for wiki
 # where the source of the wiki is located
@@ -18,7 +18,7 @@ default_pageext: wiki
 only_committed_changes: 0
 # rcs backend to use
 rcs: 'git'
-add_plugins: [ 'teximg', 'syntax', 'inline', 'goodstuff', 'link', 'date', 'favicon', 'graphviz', 'parentlinks', 'sortnaturally', 'meta', 'linkmap', 'shortcut', 'recentchangesdiff', 'recentchanges', 'autoindex', 'headinganchors', 'img' ]
+add_plugins: [ 'mirrorlist', 'wikitext', 'teximg', 'syntax', 'inline', 'goodstuff', 'link', 'date', 'favicon', 'graphviz', 'parentlinks', 'sortnaturally', 'meta', 'linkmap', 'shortcut', 'recentchangesdiff', 'recentchanges', 'autoindex', 'headinganchors', 'img' ]
 # plugins to disable
 disable_plugins: ['htmlscrubber']
 # additional directory to search for template files
diff --git a/src/index.mdwn b/src/index.mdwn
index 9782078..ac45d6d 100644
--- a/src/index.mdwn
+++ b/src/index.mdwn
@@ -1,7 +1,7 @@
 This site belongs to [Wesley Coakley](, also known on
 the Internet as [wesl-ee]( and locally known
-simply as [[Me]] (⌒▽⌒) I am a DeFi dev working in the Cosmos
-ecosystem and co-founder of a DAO building on the Juno blockchain.
+simply as [[Me]] (⌒▽⌒) I am building DeFi applications on Cosmos through a
+DAO organizing on the Juno blockchain.
 <figure class=profile>
 <img src="/img/avi.jpeg">

merkle tree img
diff --git a/src/Digital_Money/Bitcoin/Merkle_Roots.mdwn b/src/Digital_Money/Bitcoin/Merkle_Roots.mdwn
index 4bfca66..78b0784 100644
--- a/src/Digital_Money/Bitcoin/Merkle_Roots.mdwn
+++ b/src/Digital_Money/Bitcoin/Merkle_Roots.mdwn
@@ -43,7 +43,7 @@ next *depth* of the Merkle tree until there is only one pair to hash. Their
 parent is the Merkle root and is the ancestor of all nodes in the tree.
-<img src="">
+<img src="/img/merkle-tree.svg">
 <figcaption>Color-mixing example of a binary Merkle tree<br/>
 Notice the content of each parent node is a function of its children</figcaption>
diff --git a/src/img/merkle-tree.svg b/src/img/merkle-tree.svg
new file mode 100644
index 0000000..89e1c67
--- /dev/null
+++ b/src/img/merkle-tree.svg
@@ -0,0 +1,3 @@
+oid sha256:67df89153e1c7ef8108f6eceb2207a454e75b64439f178aa6d31e2ca1006a1b0
+size 12765

diff --git a/src/Digital_Money/Terra.mdwn b/src/Digital_Money/Terra.mdwn
index 303f6bc..e8272b1 100644
--- a/src/Digital_Money/Terra.mdwn
+++ b/src/Digital_Money/Terra.mdwn
@@ -48,6 +48,3 @@ few days.
 I was rekt personally but I came out alive somehow, and am lucky to have
 invested myself in a company that didn't keep its entire treasury in UST.
-Still, I believe in the things I am doing through my work at [[Levana]] and
-look forward to deploying our derivatives on a new chain.
diff --git a/src/Digital_Money/The_Problem_With_vAMM_Perpetuals.mdwn b/src/Digital_Money/The_Problem_With_vAMM_Perpetuals.mdwn
index a7ef865..8cc9220 100644
--- a/src/Digital_Money/The_Problem_With_vAMM_Perpetuals.mdwn
+++ b/src/Digital_Money/The_Problem_With_vAMM_Perpetuals.mdwn
@@ -1,10 +1,3 @@
-<div class=info>
-Although I am building a perpetual swap at <a
-nothing I say here is intended to be an official stance of Levana protocol on any
-matter past or present (´ ∀ ` *)
 Automated Market Makers (AMMs) are a staple of nearly every
 [[DeFi|Digital_Money/Decentralized_Finance]] blockchain
 worth mentioning. Show me a DeFi chain without an AMM and I will show you a
@@ -223,18 +216,5 @@ one party to match orders behind closed doors.
 Designing a new, safe, stable protocol that lets traders enter and exit the
 market freely, exchanging futures around the current spot price, and without fear
 of being forcibly liquidated or "stopped out" by a whale or a market-maker is
-one of the most interesting problems I have the pleasure of working on with the
-Levana team. I am excited that we are rolling out Levana's perpetual swap on the
-Osmosis chain. As we are well-familiar with the dev tools and workflows on
-Cosmos SDK chains, finding a home for our perpetual futures on Osmosis (also a
-Cosmos SDK chain) is a welcome relief.
-[[!img img/levana-osmosis.jpeg size=500x]] <figcaption>Sourced from <a
-Twitter</a></figcaption> </figure>
-This was just an overview of some of the troubles that vAMM perpetual swaps
-face. Though I've already hinted at ways we're addressing these issues more
-information, overviews and explainers about Levana's solution to these perpetual
-woes are coming soon™
+one of the interesting problems I had the pleasure of working on with the
+Levana team.
diff --git a/src/Me.mdwn b/src/Me.mdwn
index a1abe72..8f0ab97 100644
--- a/src/Me.mdwn
+++ b/src/Me.mdwn
@@ -2,15 +2,18 @@ Hi, my name is Wesley Coakley (🇯🇵  コークリー・ウェズリー) ☆
 On the Internet and in the crypto-space I use the handle **wesl-ee** because it
 sounds cooler.
-I am a core developer on [Levana Protocol]( and a
-graduate of [[School/North_Carolina_State_University]] with a B.S. in Computer
-Engineering and another B.S. in Electrical Engineering. I also accidentally
-took enough courses during my college tenure to collect my minor in mathematics
-on the way out the door.
+In November 2022 I co-founded a DAO building on the [Juno](
+blockchain; previously I worked as a core dev at
+[Levana]( on the [[Terra]] blockchain developing a
+perpetual futures market before the collapse of Terra's native UST.
-I began my career as a Software Engineer in NVIDIA's [Networking Business
-Unit]( (NBU) but quickly found a home
-developing financial tools for public, permissionless blockchains.
+Before I took the leap into developing public, permissionless financial tools on
+Cosmos blockchains I worked as a Software Engineer in NVIDIA's
+[Networking Business Unit]( (NBU).
+I graduated from [[School/North_Carolina_State_University]] with a B.S. in
+Computer Engineering and another B.S. in Electrical Engineering. I also
+accidentally took enough courses during my college tenure to collect my minor in
+mathematics on the way out the door.
diff --git a/src/img/levana-osmosis.jpeg b/src/img/levana-osmosis.jpeg
deleted file mode 100644
index bf1c839..0000000
--- a/src/img/levana-osmosis.jpeg
+++ /dev/null
@@ -1,3 +0,0 @@
-oid sha256:bff2e640871ef0a929fcf6f748323481d3d24278c67e57f4ef68f70f8cdf49ce
-size 72225
diff --git a/src/index.mdwn b/src/index.mdwn
index 750ee26..9782078 100644
--- a/src/index.mdwn
+++ b/src/index.mdwn
@@ -1,7 +1,7 @@
-This site belongs to [Wesley Coakley](, also known on
+This site belongs to [Wesley Coakley](, also known on
 the Internet as [wesl-ee]( and locally known
-simply as [[Me]] (⌒▽⌒) I'm developing a derivatives exchange at [Levana
+simply as [[Me]] (⌒▽⌒) I am a DeFi dev working in the Cosmos
+ecosystem and co-founder of a DAO building on the Juno blockchain.
 <figure class=profile>
 <img src="/img/avi.jpeg">

smaller gendo
diff --git a/src/img/avi.jpeg b/src/img/avi.jpeg
index ff9fad7..8ca9da3 100755
--- a/src/img/avi.jpeg
+++ b/src/img/avi.jpeg
@@ -1,3 +1,3 @@
-oid sha256:64d4a4443ef32913daa702e7305603c491dd500ea192378f45a28b932567b067
-size 118643
+oid sha256:19a06e29ee2444def91d2692f01692d54a12bfd19dd6da2a4bfeb0a235681bb9
+size 116722

it's me but it's also gendo
diff --git a/base/avi.jpg b/base/avi.jpg
deleted file mode 100644
index f80a821..0000000
Binary files a/base/avi.jpg and /dev/null differ
diff --git a/src/img/avi.jpeg b/src/img/avi.jpeg
new file mode 100755
index 0000000..ff9fad7
--- /dev/null
+++ b/src/img/avi.jpeg
@@ -0,0 +1,3 @@
+oid sha256:64d4a4443ef32913daa702e7305603c491dd500ea192378f45a28b932567b067
+size 118643
diff --git a/src/index.mdwn b/src/index.mdwn
index 3779f61..750ee26 100644
--- a/src/index.mdwn
+++ b/src/index.mdwn
@@ -4,7 +4,7 @@ simply as [[Me]] (⌒▽⌒) I'm developing a derivatives exchange at [Levan
 <figure class=profile>
-<img src="avi.jpg">
+<img src="/img/avi.jpeg">
 <figcaption><ul class=net-presence>
 <li class=twitter><a href="">Twitter</a></li>
 <li class=github><a href="">GitHub</a></li>

BMW_318ti: clarify grounding consequence
diff --git a/src/BMW_318ti/Short_it_to_Zero.mdwn b/src/BMW_318ti/Short_it_to_Zero.mdwn
index d553156..a605b69 100644
--- a/src/BMW_318ti/Short_it_to_Zero.mdwn
+++ b/src/BMW_318ti/Short_it_to_Zero.mdwn
@@ -152,8 +152,16 @@ fuel pump began to prime and I saw 40 psi in the fuel rail!
 [[!img img/318ti-fuel-pressure.jpeg size=400x]]
-This is not a permanent solution, or one that will really get me farther than
-the inspection station (my vehicle registration lapsed in July), but it's a
+Shorting to ground (ie shorting it to zero) essentially removed the DME from
+having say as to when the fuel pump should be on: in this configuration the pump
+will run all the time that the key is in position 2 or the engine is spinning,
+which for my purposes is almost all of the time as I don't often idle in my car
+if the engine is off.
+This is not a permanent solution however or one that will really get me farther
+than the inspection station (my vehicle registration lapsed in July), but it's a
 problem I enjoyed solving because it taught me a lot and reminded me my EE
 degree is not entirely pointless. I will probably replace the fuel pump in due
-time anyhow as the original one from '96 is still in there.
+time anyhow as the original one from '96 is still in there. Likely I will also
+pull the DME and inspect it for damage, potentially replacing the transistor
+that switches on the ground for the fuel pump relay.

318ti: Short it to zero
diff --git a/src/BMW_318ti/Fuel_Delivery.mdwn b/src/BMW_318ti/Fuel_Delivery.mdwn
new file mode 100644
index 0000000..3930ebd
--- /dev/null
+++ b/src/BMW_318ti/Fuel_Delivery.mdwn
@@ -0,0 +1,19 @@
+The 318ti is a gasoline powered car. With the exception of the
+which is powered by natural gas all brands on the E36 chassis run on gasoline. I
+have heard my 318ti's [[M44_Engine]] runs best on 93 octane.
+Gasoline is stored in a tank underneath the car and is pumped to the fuel
+rail by a fuel pump that physically sits in the gas tank. The fuel rail is
+pressurized to 40 PSI when the car key is turned to position 2, ie the position
+before attempting to crank the car. To achieve pressurization the fuel pump is
+run for 30 seconds. It takes far less than 30 seconds to pressurize the fuel
+delivery system, and any excess gas which is pumped to the rail during this time
+(or anytime the pump is running for that matter) is returned to the tank to
+maintain 40 PSI.
+4 fuel injectors sit atop the fuel rail and inject fuel into the engine. The
+M44 is a "port injection" engine meaning fuel is sprayed into the intake
+manifold a brief distance away from the cylinder but not into the cylinder
+itself ("direct injection"). Fuel injectors are a core part of
+the [[Fuel_Injection]] system.
diff --git a/src/BMW_318ti/Fuel_Injection.mdwn b/src/BMW_318ti/Fuel_Injection.mdwn
new file mode 100644
index 0000000..cc6cbe0
--- /dev/null
+++ b/src/BMW_318ti/Fuel_Injection.mdwn
@@ -0,0 +1,26 @@
+The engine of any gasoline-powered car only needs 3 things to run:
++ Fuel
++ Air
++ Spark
+Air is pulled in through an intake manifold by the negative pressure created
+when post-combustion gases evacuate the engine cylinder. In contrast fuel is
+pushed into the fuel rail by a positive pressure created in the fuel lines that
+constitute the [[Fuel_Delivery]] system by the fuel pump.
+Fuel is atomized at the injectors before being injected into the engine cylinder
+for efficient combustion. In the case of computer-controlled combustion engines
+the onboard computer decides when to fire each fuel injector. On a four-cylinder
+engine like my 318ti's [[M44_Engine]] cylinders are fired in the 1-3-4-2 order.
+The computer uses a mass airflow sensor to measure the amount of air that is
+entering the intake manifold to determine how much fuel to spray into the
+cylinder. In the case of the M44 this is a hot wire sensor MAF that is situated
+just downstream from the airbox.
+Here is the pleasant video that taught me about fuel injection initially:
+<iframe width="560" height="315" src="" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
diff --git a/src/BMW_318ti/Knowledge.mdwn b/src/BMW_318ti/Knowledge.mdwn
new file mode 100644
index 0000000..e62372f
--- /dev/null
+++ b/src/BMW_318ti/Knowledge.mdwn
@@ -0,0 +1,6 @@
+[[!map  pages="BMW_318ti/*
+    and !BMW_318ti/Knowledge
+    and !BMW_318ti/Work
+    and !BMW_318ti/Short_it_to_Zero"
diff --git a/src/BMW_318ti/M44_Engine.mdwn b/src/BMW_318ti/M44_Engine.mdwn
new file mode 100644
index 0000000..d67d601
--- /dev/null
+++ b/src/BMW_318ti/M44_Engine.mdwn
@@ -0,0 +1,10 @@
+The 318ti was equipped from the factory with two different types of engines:
+on the early 318ti (1994 〜 1996) this was the M42 engine; on the later
+318ti (1996 〜 2000) the M44 engine succeeded the M42. Both engines are
+inline-4; all M44 engines leverage a dual-length intake manifold (DISA, short
+for DIfferenzierte SaugAnlage) while only some late M42 engines do. DISA
+increases the length of the intake at higher RPM. More systems which do this are
+called "variable intakes."
+I have heard the [[M44_Engine]] runs best on 93 octane but truthfully this is
+the only gas I have ever pumped into the car so take that as untested fact.
diff --git a/src/BMW_318ti/Short_it_to_Zero.mdwn b/src/BMW_318ti/Short_it_to_Zero.mdwn
new file mode 100644
index 0000000..d553156
--- /dev/null
+++ b/src/BMW_318ti/Short_it_to_Zero.mdwn
@@ -0,0 +1,159 @@
+In early April this year (2022) my beloved shitbox left me on the side of the
+highway. Despite cruising at a mere 60 mph (take "cruising" to be a figure of
+speech as cruise control was a premium, non-default option you'd buy from the
+BMW factory) the check-engine lamp began flashing and the car began to lose
+power. It always ran a little rough but never rough enough to trigger a critical
+failure like this. I knew this was a serious issue and I immediately took the
+car out of gear then coasted to a stop and turned the thing off. For once reading
+[old, near-dead car forums]( paid off as I had learned from the
+experience of others that a flashing check-engine light (CEL) on an OBD-II car
+(on OBD-I this is only a minor fault) was bad bad not good and indicitive of
+something that had become seriously fucked.
+Not willing to leave it overnight on the side of the road where my beautiful
+windows could be shattered I called a friend and we loaded it onto his trailer.
+We parked the car at his garage and I went to work on it the next weekend. When
+we rolled it off the trailer with the key in [position
+2]( a
+strong smell of gasoline appeared; further it seemed some gasoline had dripped onto
+the concrete below. This was the second indication that something was fucked.
+[[!img img/318ti-trailer.jpeg size=400x]]
+Clearly this was the immediate problem I needed to fix and may have been the
+cause of that loss of power. Because fuel leaked from the car I decided to start
+by diagnosing the car's [[Fuel_Delivery]] system. The fuel lines running from
+the rear of the car to the front were dry. I lifted the car up, crawled
+underneath and traced the wet fuel to the upper intake manifold; I probably
+could have found this without lifting it up but ¯\\\_(ツ)\_/¯
+It appeared fuel was leaking from the top of the first cylinder injector and
+dripping down onto the lower intake manifold and finally spilling onto the
+floor. To get to the injectors on the 318ti you need to first remove the upper
+intake manifold.
+After pulling the injectors I found that the rubber o-ring that seals the
+injector to the rail was torn so I ordered a rebuild kit and replaced it.
+Perhaps the injector was not seated well, causing fuel to push past the o-ring.
+In any case it was a shame as I already replaced the o-rings two years before
+when I bought the thing. I had recently removed the rail to try swapping in a
+new set of injectors I bought from eBay to cure my rough idle (spoiler: they
+weren't all four from the same car so the thing terrible) so the theory I hadn't
+reseated them correctly makes sense. Plus the injectors are held in place by
+metal clips that I probably installed wrong.
+After I fixed this problem I tried to run the fuel pump manually to check for
+leaks by shorting pins 30 and 87 of the [[Fuel_Pump_Relay]]; unfortunately I
+shorted the wrong two pins and then the pump would not prime after turning the
+key. Without pressure in the fuel rail the car would not start.
+It was around this time that I was to travel to Israel to meet a handful of
+people at Levana in-person, and with that only flight only a few days away I
+decided to have the car towed to the house I just bought, quite a good drive
+away from the garage where it presently sat. The car stayed in the garage at my
+house even before we'd stayed a full day there.
+[[!img img/israel-haifa.jpeg size=400x]]
+As an aside, having the car towed twice in a month convinced me to buy a truck,
+but unfortunately I've not at this time acted on that conviction; there are
+very few small US trucks made in the last 15 years and I don't care for a very
+large vehicle, just one that's equipped to tow a trailer with a car weighing a
+US ton or two on top.
+The E36 sat for a while until life settled down. We visited Israel,
+[[Digital_Money/Terra]] collapsed, we moved in to the new house, welcomed a 3
+month old puppy into our home over the Summer and finally work became a regular
+cadence some time around September. I finally began to work on the car seriously
+again around this time. When you have at least one "reliable" car you can afford
+to do this instead of rushing to fix it and potentially making things worse. 
+I began to diagnose what I had fucked up by shorting pins 30 and 87. Logically I
+started at the fuel pump in the back and worked my way forward. I tore out the
+back seat cushio (surprisingly removable on my car) which gave me access to the
+fuel pump. There are two devices stuck in the fuel tank: on the driver side
+there is a fuel-level sender unit, and on the passenger side is the fuel pump,
+which also has a sender unit attached. For some reason the fuel tank is
+physically separated into two sides with a pump between them; each sender
+measures the fuel level on its corresponding side.
+Pulling fuel lines was a reminder that the OEM parts were manufactured and
+installed before I was alive, and the car was rolled onto a lot in November '96,
+probably a few days after my birthday.
+<blockquote class="twitter-tweet tw-align-center" data-dnt="true"><p lang="en" dir="ltr">continually reminded the lines in this car are as old as me <a href=""></a></p>&mdash; wesl-ee 🐉 (@wesl_ee) <a href="">September 25, 2022</a></blockquote> <script async src="" charset="utf-8"></script>
+Anyhow, I did not realize the _sender_ unit is behind the driver and the _fuel
+pump_ is behind the passenger. Pictured above is the top of the sender unit
+behind the driver. I had started working on the wrong side, treating the sender
+unit as if it was the fuel pump. I probed voltage at the sender unit and saw
+voltage; I therefore figured I must have blown out the fuel pump somehow,
+because the unit was getting adequate voltage and should be running but it was
+not. I ordered a new fuel pump, dusted off my hands and called it a day.
+When the pump arrived I tore out the old sender unit and went to replace it with
+the fuel pump only to find there was no pump on that side.
+[[!img img/318ti-fuel-in-the-tank.jpeg size=400x]]
+It was at this moment I realized I fucked up for what felt like the 10th time in
+this arc. I muscled the sender back into the tank (with the o-ring it is a very
+snug fit) and probed the unit in the _other_ side of the tank. As it turns out
+the fuel pump was not getting voltage at all so it's hardly surprising it wasn't
+I tracked the problem back to the fuel pump relay. Here is its electrical
+[[!img img/318ti-fuel-pump-relay-wiring-schematic.jpeg size=400x]]

(Diff truncated)
diff --git a/src/pubkey.txt b/src/pubkey.txt
index 1b23d8c..ec8f296 100644
--- a/src/pubkey.txt
+++ b/src/pubkey.txt
@@ -5,87 +5,95 @@ oOFe43PoqtuHLtSTEf98s6PuKqpugvR6mRtdfmlGgHFUCYI7xdMrW8hmNXxlO0em

BMW_318ti: make room
diff --git a/src/BMW_318ti.mdwn b/src/BMW_318ti/index.mdwn
similarity index 100%
rename from src/BMW_318ti.mdwn
rename to src/BMW_318ti/index.mdwn

[[IPFS]] link
diff --git a/src/Hooya.mdwn b/src/HooYa/index.mdwn
similarity index 95%
rename from src/Hooya.mdwn
rename to src/HooYa/index.mdwn
index f8b5494..d54157e 100644
--- a/src/Hooya.mdwn
+++ b/src/HooYa/index.mdwn
@@ -211,7 +211,7 @@ been leased; this data is released once its lease expires.
 ### 2 — Leased Ephemeral Storage
 In addition to running the HooYa! daemon which maintains consensus (1) all
-validators are expected to run an <a href="">IPFS</a> daemon. This daemon
+validators are expected to run an [[IPFS]] daemon. This daemon
 connects validators to each other in a private cluster separate from the
 "global" IPFS instance that we often refer to when talking of IPFS. The private
 IPFS cluster provides ephemeral storage of the images that HooYa! has reached
@@ -224,13 +224,14 @@ required to store copies of all data ever indexed by HooYa!, only data whose
 lease is current because that space is reclaimed once the lease for that space
-To my knowledge no other Cosmos SDK chain (not even <a href="">Stargaze</a>
-which arguably should use this) leverages IPFS like this. I believe this is a
-wonderful decentralized alternative to things like <a
-href="">Pinata</a> for IPFS pinning that is especially
-attractive for NFT projects on Cosmos. *Even if other projects do not use
-HooYa!'s consensus (1) or neural-net prediction + generation (3) they can lease
-ephemeral storage (2) to store NFT metadata and images.*
+To my knowledge no other Cosmos SDK chain (not even <a
+href="">Stargaze</a> which arguably should use this)
+leverages IPFS like this. I believe this is a wonderful decentralized
+alternative to things like <a href="">Pinata</a> for
+IPFS pinning that is especially attractive for NFT projects on Cosmos. *Even if
+other projects do not use HooYa!'s consensus (1) or neural-net prediction +
+generation (3) they can lease ephemeral storage (2) to store NFT metadata and
 [... more to come here]

HooYa! rough
diff --git a/src/Hooya.mdwn b/src/Hooya.mdwn
new file mode 100644
index 0000000..f8b5494
--- /dev/null
+++ b/src/Hooya.mdwn
@@ -0,0 +1,256 @@
+[[!meta title="HooYa! Network"]]
+<table class=left-float>
+<th colspan=2>HooYa! Network</th>
+<th>Project Status</th>
+<th>Article Status</th>
+HooYa! is a Web3 community for commissioning and supporting manga & dōjin
+artists; it offers leasable storage space for illustrations submitted by artists
+and network users and provides a
+[folksonomy]( of descriptive,
+searchable tags and metadata for each illustration it hosts. HooYa! maintains
+also a folksonomy for images that are not stored on-chain but that may be
+accessible through other services such as Pixiv and Danbooru.
+[[!img img/hooya-slide.jpeg size="x500"]]
+It aspires to be rapidly become completely autonomous and self-governing by
+issuing its own governance tokens for use in image proposal / acceptance and
+metadata tagging. It also seeks to incentivize the on-chain commission + minting
+of new artworks by [manga]( &
+[dōjin]( artists (hereafter
+"illustrators") via these native utility tokens.
+### Background
+The service HooYa! provides is not novel; it finds inspiration from a handful of
+Web2 companies (mainly Japanese ones) and from the communities that form around these
+companies and the illustrators they support. I see HooYa! as a combination of
+these two communities in particular:
+- [Pixiv](, a Japanese-language community of illustrators who
+  connect with fans by posting original and derivative artworks
+- [Danbooru](, a
+  community dedicated to the archive of illustrations like those posted on
+  pixiv, known mostly for its extensive vocabulary of tags used for organizing
+  and labelling these images
+The wealth of information provided by Danbooru has helped many [unique
+projects]( to create
+machine-learning models that can both (a) predict appropriate tags for a given
+illustration ([example](,
+[src]( and (b) generate new
+illustrations that resemble the Japanese style
+HooYa! will leverage these pioneering predictive models to suggest tags on
+images submitted for inclusion on the network.
+### What is Pixiv?
+[Pixiv]( is a community of primarily Japanese illustrators who
+upload their illustrations, comics and short stories and share them with other
+pixiv members. This is one of the primary ways that illustrators can connect
+with their communities and make their artwork accessible to their fans. It is
+the [10th]( most visited
+site in Japan and is most popular among young Japanese illustrators and their
+Pixiv offers a Patreon-like subscription program called
+[pixivFANBOX]( which connect fans with illustrators
+publishing derivative and original illustrations on a regular basis by providing
+fans in each subscriber tier with special goods, articles and hi-res renders of
+illustrations released by the artist.
+Because drawing is a popular hobby in Japan (and one which is gaining popularity
+abroad) the idea of earning a living as an illustrator has attracted many creators,
+both Japanese and internationals, to the Pixiv platform.
+[[!img img/pixiv-shiratama-tier-1.jpeg size="x500"]]
+<figcaption>Example of a monthly subscription from <a
+href="">Shiratama's</a> pixivFANBOX
+In addition to subscription services pixiv also provides a space for
+illustrators to sell their illustrations, manga (both short- and long-form) and
+artbooks on its [BOOTH]( site. These can be
+digital-only releases but there are also physicals for sale which are produced
+through its pixivFACTORY service.
+Fans can commission personal works from illustrators by a feature on
+pixiv known as
+Requests can be funded entirely by an individual or can be crowd-funded by many
+fans pooling cash together to commission the piece.
+Finally, Pixiv lets fans and illustrators to add a limited set of tags to an image
+(up to 10) to an image. These Pixiv tags are more akin to hashtags on Twitter
+than semantic metadata as seen on sites like Danbooru.
+### Danbooru
+[Danbooru]( is a
+community that tags and archives images from Pixiv, Twitter, DeviantArt and many
+other platforms. Each image submitted for inclusion on Danbooru goes through a
+3-day review period after which it is either accepted or denied inclusion into
+the Danbooru canon. Danbooru maintains a large
+[vocabulary of tags]( which
+are key-value pairs used to describe an image. This makes the set of images
+easily searchable by specifying (eg) the illustrator, character, franchise or
+any objects in an image.
+[[!img img/danbooru-product-placement.jpeg size="x500"]]
+As shown above Danbooru lets me search things such as: illustrations of the Love
+Live! franchise which include product placement of some kind, by issuing the
+query <code>love&lowbar;live! product&lowbar;placement</code>. From left to
+right, top to bottom these are the [Subaru
+and the [Yamaha
+Danbooru limits searches to 2 tags unless the user has purchased a
+[Gold]( account, in which case the limit is
+raised to 6. Gold accounts cost a one-time purchase of $20 USD.
+<figure class=left-float><video width=300 height=300 loop autoplay controls>
+<source src="/vid/gwern-stylegan-portraits-interpolation-4x4.webm">
+Danbooru hosts over **4.9 million images** tagged with **162 million tags**, of
+498k unique tags as of the end of 2021. A single copy of this data consumes 4.5
+terrabytes of disk space.
+As alluded to earlier, this massive data set has allowed researchers to create
+predictive models leveraging neural networks to label the objects in a brand
+new illustration, thus reducing the workload on a single user tagging an image.
+In addition to predictive models, generative adversarial networks (in particular
+NVIDIA's StyleGAN) have been trained with the Danbooru set to draw brand new
+illustrations when prompted with a series of tags.
+To the left is <a
+href="">Gwern's</a> Danbooru2018
+portrait model trained to generate portraits in the Danbooru style (credit <a
+href="">Gwern</a> for the model and
+video). Each image in the interpolation is unique in that it is an original
+of the GAN, and though the model was seeded from the images collected on
+Danbooru the portraits are original creations.
+HooYa! uses the predictive model and the generative model in a few different
+ways (see below *3: Prediction* and *4: Generation*).
+HooYa! — A Decentralized Platform for [Dōjin]( & Manga Artists
+Now with some understanding of the context in which HooYa! is being developed I
+can explain the mechanics the HooYa! network.
+HooYa! at its core can be broken into three components:
+1. Consensus (of metadata, tags, governance, and the image canon)
+2. Leased ephemeral storage (of commissioned images and those minted on-chain)
+3. Prediction (of tags) + generation (of reference images)
+The first two of these four components may be familiar to some; the last one is
+a novel component to compute on a blockchain and is one thing (among many) which
+I hope will set HooYa! apart from many other chains, both on Cosmos and beyond.
+### 1 — Consensus
+HooYa! is a blockchain built on the **Cosmos SDK**. It uses Tendermint (like
+nearly every other Cosmos SDK chain) to maintain network connectivity and
+consensus across a group of validators. Many chains I have seen begin with a
+set of 100 validator slots and so this is what HooYa! adopts initially.
+Each node has a perfect copy of *the canon* which refers to the set of:
+- Images (uniquely identified by a SHA2-256 <a
+   href="">multihash</a>)
+- Ownership of those images
+- Tags describing those images
+- Metadata describing those images
+... that HooYa! indexes. HooYa!'s canon is a subset of network state and
+therefore any archival node can retrieve a full copy of the canon at any given

(Diff truncated)
devices: palmtop-tiger
diff --git a/base/local.css b/base/local.css
index 0da682a..e0025a6 100644
--- a/base/local.css
+++ b/base/local.css
@@ -29,6 +29,19 @@ section#content td {
 section#content table {
 	border: 1px solid;
 	margin: auto;
+    empty-cells: hide;
+section#content {
+    border: 0;
+section#content td.spread-img {
+    padding: 0;
+    margin: 0;
+    border: 0;
+    /* Pesky whitespace text nodes */
+    font-size: 0rem;
 section#content :is(h1, h2, h3, h4, h5, h6) {
@@ -52,6 +65,10 @@ section#content .longlink {
 	section#content { text-align: initial }
+@media only screen and (max-width: 600px) {
+    #content .left-float { float: none !important; }
 a { text-decoration: none }
 a { color: blue; transition: color .2s }
 a:hover { color: red }
@@ -125,6 +142,11 @@ figure {
 	display: block;
 	text-align: center;
 	margin: auto }
+#content .left-float {
+    float: left;
+    margin: 0 2ch 2ch 0 !important;
 p img {
 	max-width: calc(100% - 2px);
diff --git a/src/Devices/Pixel_4a.mdwn b/src/Devices/Pixel_4a.mdwn
new file mode 100644
index 0000000..0696027
--- /dev/null
+++ b/src/Devices/Pixel_4a.mdwn
@@ -0,0 +1,230 @@
+This Pixel 4a is hands-down my favorite phone I've ever used, and by-far it has
+offered me the most performance with the least amount of hassle. Plus it was
+hilariously cheap: in total I paid
+$216 for this cute thing, not including the service, which was basically pennies
+compared to other phone plans when I paid a base $20 per month + $10 per
+<table class=no-border>
+  <td colspan=2 class=spread-img>
+[[!img img/pixel-4a-sep-2022.jpeg size="x500"]]
+  </td>
+  <th>Device</th>
+  <td>Pixel 4a (<em>sunfish</em>)</td>
+  <th>Hostname</th>
+  <td><a href="">
+  Palmtop-Tiger</a></td>
+  <th>Dimensions</th>
+  <td>144mm x 69.4mm x 8.2mm</td>
+  <th/>
+  <td>2340 x 1080 (19.5:9)</td>
+  <th/>
+  <td>5.8in screen, 443ppi</td>
+  <th>Weight</th>
+  <td>143g</td>
+  <th>ROM</th>
+  <td>Lineage OS 19.1 (Android 12)</td>
+  <th>Owned</th>
+  <td>February 2021 〜 Now</td>
+  <th>Notable Hardware</th>
+  <td>3.5mm headphone jack</td>
+  <th/>
+  <td>Rear fingerprint scanner</td>
+  <th>Notes</th>
+  <td>Rooted w/ Magisk (v25.2)</td>
+  <th/>
+  <td>Ad-blocking w/ hosts file (AdAway)</td>
+  <th/>
+  <td></td>
+Despite being marketed mostly as a "budget" phone there are very few features
+missing from this phone that I feel I'd want; it boasts some features over the
+Pixel 4 that I really like: the 3.5mm headphone jack, rear-mounted fingerprint
+scanner and a thinner bezel than both the Pixel 4 and Pixel 4 XL all are
+features only the 4a boasts of the 3 phones in the Pixel 4 family.
+Before this I used a Samsung S10e for about a year before technically
+downgrading to this phone; the difficulty of rooting that particular Verizon
+model of the S10e frustrated me as I desperately wanted to install
+[AdAway]( as my system-wide adblocker
+as well as to uninstall the annoying Samsung bloatware apps. Though the hardware
+was nice for the time, I wanted a purer Android experience and the Samsung ROM
+was clearly not that. Plus, rooting a phone (and maybe flashing a custom ROM)
+makes me feel like I truly "own" my own device.
+The All-in-One
+Some lament that we no longer carry single-purpose devices like notebooks,
+stopwatches, flashlights or pagers as often (or at all) anymore. I was in this
+camp too for some time. To me, for a while, I considered phones as all-purpose
+tools and I used my Pixel 4a accordingly: I submitted to the easy modern
+lifestyle and loaded the phone to the brim with apps and used it idly, wasting
+time reading things I thought were important or relevant or communicating with
+people I've never meaningfully talked with anyhow, IRL or otherwise.
+For reasons like this many people consider phones to be all-in-one devices. I
+argue that this categorization depends on the person using the phone; I've
+only recently become aware of (and have recently begun practicing) the ability
+to use my phone as many single-purpose devices. At times it is a way to
+communicate with the people I work with, other times it is a convenient way to
+jot a note down so I do not forget, and yet other times it is a tool to dump
+thoughts onto my Twitter feed in basically a write-only fashion. The important
+thing is that I use it for the purpose I intend at the time I pick it up and
+put it down exactly when I am done with the task I ventured to use it for.
+When I flashed the 09.2022 build of Lineage OS onto my phone I took the
+opportunity to wipe my Pixel clean and install this set of apps and tools that
+would allow me to use my phone as I outlined above, ie as many single-purpose
+tools rolled into one:
+<table class=no-border>
+  <th>Launcher</th>
+  <td>Blue Line Console</td>
+  <th></th>
+  <td>Nova Launcher</td>
+  <th>Wallpaper</th>
+  <td>Kustom Live Wallpaper (KLWP)</td>
+  <th>System</th>
+  <td>AdAway</td>
+  <th></th>
+  <td>Magisk</td>
+  <th>File Sharing</th>
+  <td>Primitive ftpd</td>
+  <th></th>
+  <td>Share via HTTP</td>
+  <th>VPN</th>
+  <td>IVPN</td>
+  <th>Browser</th>
+  <td>Firefox Focus</td>
+  <th>E-mail</th>
+  <td>K-9 Mail</td>
+  <th>Chat</th>
+  <td>Telegram</td>
+  <th/>
+  <td>Discord</td>

(Diff truncated)
Recover broken images + videos from CDN
diff --git a/.gitattributes b/.gitattributes
index 264185c..ffd08d8 100644
--- a/.gitattributes
+++ b/.gitattributes
@@ -1 +1,2 @@
 /src/img/** filter=lfs diff=lfs merge=lfs -text
+/src/vid/** filter=lfs diff=lfs merge=lfs -text
diff --git a/src/Routing/FRR_OSPFv2_Plus_GSN3.mdwn b/src/Routing/FRR_OSPFv2_Plus_GSN3.mdwn
index 8e20453..cbce807 100644
--- a/src/Routing/FRR_OSPFv2_Plus_GSN3.mdwn
+++ b/src/Routing/FRR_OSPFv2_Plus_GSN3.mdwn
@@ -23,7 +23,7 @@ east-west traffic between two Alpine tenants. Area 0 is organized in a ring to
 demonstrate how link failures can affect routing around this topology.
-<img src="">
+[[!img img/frr-gns3-complete.png size=500x]]
 <figcaption>GNS3 topology which this article ultimately constructs</figcaption>
@@ -128,7 +128,7 @@ open go to "Edit" → "Preferences" → "Docker containers". Then create a new
 container template for the FRR image that was just built or pulled.
-<img src="">
+[[!img img/frr-gns3-docker-containers.png size=500x]]
 <figcaption>Docker container configuration in GNS3</figcaption>
@@ -144,7 +144,7 @@ stores its configuration files. The two important files here are `frr.conf` and
-<img src="">
+[[!img img/frr-gns3-docker-advanced.png size=500x]]
 <figcaption>Configuration of the persistent storage</figcaption>
@@ -195,7 +195,7 @@ Before networking containers together let's get comfortable working with just a
 single node.
-<img src="">
+[[!img img/frr-single-node.png size=500x]]
 <figcaption>Single-node setup</figcaption>
@@ -243,7 +243,7 @@ together using the "Link" option in the left-hand panel; just select which
 interfaces terminate either side of the link when connecting two nodes.
-<img src="">
+[[!img img/frr-two-node.png size=500x]]
 <figcaption>A two-node setup in GNS3</figcaption>
@@ -310,7 +310,7 @@ Flapping the `eth0` interface on `r2` will show an exchange of routing
 information in the Wireshark trace.
-<img src="">
+[[!img img/frr-wireshark-ospfv2-hello.png size=500x]]
 <figcaption>Example exchange of routing information in OSPFv2</figcaption>
@@ -329,7 +329,7 @@ Because two routers is never enough let's add two more! I will connect these
 four in a ring topology instead of a full-mesh.
-<img src="">
+[[!img img/frr-gns3-ring-topology.png size=500x]]
 <figcaption>A 4-node Ring Topology</figcaption>
@@ -439,7 +439,7 @@ that the subnet may be configured arbitrarily without affecting east-west
-<img src="">
+[[!img img/frr-gns3-access-layer.png size=500x]]
 <figcaption>End-devices in the access layer are connected together by the distribution layer</figcaption>
@@ -603,10 +603,11 @@ tab of the "Configure" window though I haven't found much use for them yet.
 I also suggest picking a cool icon for your VX!
-<img src="">
+<img src="/img/frr-gns3-cumulus-vx-install.gif">
 <figcaption>Installing and Configuring a Cumulus VX in the Ring Topology</figcaption>
 Since Cumulus Linux uses FRR as its routing suite it's straightforward to
 replace the old FRR container `r1` in the example topology with a CL VX since
 the config is the exact same. Since this is a VM and not an FRR Docker container
@@ -634,7 +635,7 @@ off-load the normal data-plane operations to.
 Anyhow this is the final topology!
-<img src="">
+[[!img img/frr-gns3-complete.png size=500x]]
 <figcaption>Final two-tier topology in GNS3</figcaption>
diff --git a/src/Routing/UDP_Holepunch.mdwn b/src/Routing/UDP_Holepunch.mdwn
index 540416c..b659fc8 100644
--- a/src/Routing/UDP_Holepunch.mdwn
+++ b/src/Routing/UDP_Holepunch.mdwn
@@ -83,7 +83,7 @@ router. I have no ports forwarded to my laptop so inbound connections are
 normally dropped at the WAN-side of the router.
-<img src="">
+[[!img img/go-nat-traversal-demo.jpg size=500x]]
 <figcaption>Demonstration of a NAT traversal across my home router</figcaption>
diff --git a/src/School/Embedded_Systems_ECE306.mdwn b/src/School/Embedded_Systems_ECE306.mdwn
index 23abe1f..e591620 100644
--- a/src/School/Embedded_Systems_ECE306.mdwn
+++ b/src/School/Embedded_Systems_ECE306.mdwn
@@ -50,10 +50,7 @@ debugging tools to port software from a lab (Windows) machine to the MSP430
-<a href="">
-<img alt="P1 Board"
+[[!img img/ece306-p1-board.png size=500x]]
 <figcaption>Example of the outcome of Project 1</figcaption>
@@ -99,10 +96,7 @@ reverse-engineering and SPI programming that everyone else missed out on; an
 example of my notes (annotated with my post-analysis) is posted below:
-<a href="">
-<img alt="LCD Dump"
+[[!img img/ece306-lcd-dump.jpg size=500x]]
 <figcaption>An annotated view of the waveform traced from a lab
 oscilloscope; using this (and 10 other sketches) I was able to
 reverse-engineer the entire initialization routine</figcaption>
@@ -642,10 +636,7 @@ requisite part of the course but which I found useful to have), a page of
 which is provided below:
-<a href="">
-<img alt="P10 Dev"
+[[!img img/ece306-clk-design.jpg size=500x]]
 <figcaption>A page from my lab notebook detailing clock propagation to
 various subsystems in the RC-Car</figcaption>
@@ -693,10 +684,7 @@ allowing students who actually *drive* their cars to speed ahead in the
-<a href="">
-<img alt="P10 Dev"
+[[!img img/ece306-p10-dev.jpg size=500x]]
 <figcaption>My typical development environment (note the coffee)</figcaption>
@@ -757,10 +745,7 @@ reverse-engineering the LCD driver and (re)writing the interface I was
 finally able to develop 24/7 on my Linux computer.
-<a href="">
-<img alt="P10 Run"
+[[!img img/ece306-p10-run.jpg size=500x]]
 <figcaption>The final obstacle course; no wonder the access points were
 overloaded!... each waypoint of the course is an orange mat barely bigger
 than the car itself (and notice the line-interception portion of the course)</figcaption>
diff --git a/src/School/Senior_Design_ECE484_ECE485.mdwn b/src/School/Senior_Design_ECE484_ECE485.mdwn
index 008009b..c4df60c 100644
--- a/src/School/Senior_Design_ECE484_ECE485.mdwn
+++ b/src/School/Senior_Design_ECE484_ECE485.mdwn
@@ -109,19 +109,13 @@ Laying out these detailed project requirements, we were able to generate over
 choosing a final design. The sketches we generated look similar to the ones below:
-<a href="">
-<img alt="Scope-like" src="">
+[[!img img/snr-design-scope.jpg size=500x]]
 <figcaption>An oscilloscope-like design</figcaption>
-<a href="">
-<img alt="Box" src="">
+[[!img img/snr-design-box.jpg size=500x]]

(Diff truncated)
wiki → src
diff --git a/.gitattributes b/.gitattributes
index 003e513..264185c 100644
--- a/.gitattributes
+++ b/.gitattributes
@@ -1 +1 @@
-/wiki/img/** filter=lfs diff=lfs merge=lfs -text
+/src/img/** filter=lfs diff=lfs merge=lfs -text
diff --git a/.gitignore b/.gitignore
index c0b82f7..9fa30c2 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,5 +1,4 @@
diff --git a/default.nix b/default.nix
index c7246e2..0da621f 100644
--- a/default.nix
+++ b/default.nix
@@ -19,6 +19,14 @@ in pkgs.mkShell rec {
+    # teximg
+    imagemagick
+    texlive.combined.scheme-basic
+    ghostscript
+    git-lfs
diff --git a/ikiwiki.setup b/ikiwiki.setup
index 525396d..b19c419 100644
--- a/ikiwiki.setup
+++ b/ikiwiki.setup
@@ -12,6 +12,8 @@ srcdir: src
 destdir: www
 # base url to the wiki
+# extension to use for new pages
+default_pageext: wiki
 # enable optimization of only refreshing committed changes?
 only_committed_changes: 0
 # rcs backend to use
@@ -44,7 +46,7 @@ hardlink: 0
 # extra library and plugin directories
 libdirs: [ 'lib' ]
 # time zone name
-timezone: timezone
+timezone: :timezone
 # cookie control
 # set custom user agent string for outbound HTTP requests e.g. when fetching aggregated RSS feeds
 useragent: ikiwiki/3.20190228-1
diff --git a/wiki/ b/src/BMW_318ti.mdwn
similarity index 100%
rename from wiki/
rename to src/BMW_318ti.mdwn
diff --git a/wiki/ b/src/Coffee.mdwn
similarity index 100%
rename from wiki/
rename to src/Coffee.mdwn
diff --git a/wiki/Digital_Money/Bitcoin/ b/src/Digital_Money/Bitcoin/Merkle_Roots.mdwn
similarity index 100%
rename from wiki/Digital_Money/Bitcoin/
rename to src/Digital_Money/Bitcoin/Merkle_Roots.mdwn
diff --git a/wiki/Digital_Money/ b/src/Digital_Money/Decentralized_Finance.mdwn
similarity index 100%
rename from wiki/Digital_Money/
rename to src/Digital_Money/Decentralized_Finance.mdwn
diff --git a/wiki/Digital_Money/ b/src/Digital_Money/Terra.mdwn
similarity index 100%
rename from wiki/Digital_Money/
rename to src/Digital_Money/Terra.mdwn
diff --git a/wiki/Digital_Money/ b/src/Digital_Money/The_Problem_With_vAMM_Perpetuals.mdwn
similarity index 100%
rename from wiki/Digital_Money/
rename to src/Digital_Money/The_Problem_With_vAMM_Perpetuals.mdwn
diff --git a/wiki/ b/src/Distributed_Hash_Table.mdwn
similarity index 100%
rename from wiki/
rename to src/Distributed_Hash_Table.mdwn
diff --git a/wiki/Firefox/ b/src/Firefox/Smart_Searching.mdwn
similarity index 100%
rename from wiki/Firefox/
rename to src/Firefox/Smart_Searching.mdwn
diff --git a/wiki/HTML/ b/src/HTML/Semantic_HTML.mdwn
similarity index 100%
rename from wiki/HTML/
rename to src/HTML/Semantic_HTML.mdwn
diff --git a/wiki/ b/src/IPFS.mdwn
similarity index 100%
rename from wiki/
rename to src/IPFS.mdwn
diff --git a/wiki/ b/src/Japanese.mdwn
similarity index 100%
rename from wiki/
rename to src/Japanese.mdwn
diff --git a/wiki/ b/src/Me.mdwn
similarity index 100%
rename from wiki/
rename to src/Me.mdwn
diff --git a/wiki/ b/src/Meta.mdwn
similarity index 100%
rename from wiki/
rename to src/Meta.mdwn
diff --git a/wiki/Meta/ b/src/Meta/All_Pages.mdwn
similarity index 100%
rename from wiki/Meta/
rename to src/Meta/All_Pages.mdwn
diff --git a/wiki/Routing/ b/src/Routing/FRR_OSPFv2_Plus_GSN3.mdwn
similarity index 100%
rename from wiki/Routing/
rename to src/Routing/FRR_OSPFv2_Plus_GSN3.mdwn
diff --git a/wiki/Routing/ b/src/Routing/UDP_Holepunch.mdwn
similarity index 100%
rename from wiki/Routing/
rename to src/Routing/UDP_Holepunch.mdwn
diff --git a/wiki/School/ b/src/School/Embedded_Systems_ECE306.mdwn
similarity index 100%
rename from wiki/School/
rename to src/School/Embedded_Systems_ECE306.mdwn
diff --git a/wiki/School/ b/src/School/North_Carolina_State_University.mdwn
similarity index 100%
rename from wiki/School/
rename to src/School/North_Carolina_State_University.mdwn
diff --git a/wiki/School/ b/src/School/Senior_Design_ECE484_ECE485.mdwn
similarity index 100%
rename from wiki/School/
rename to src/School/Senior_Design_ECE484_ECE485.mdwn
diff --git a/wiki/School/ b/src/School/Sophia_University.mdwn
similarity index 100%
rename from wiki/School/
rename to src/School/Sophia_University.mdwn
diff --git a/wiki/ b/src/Tokyo.mdwn
similarity index 100%
rename from wiki/
rename to src/Tokyo.mdwn
diff --git a/wiki/ b/src/Virtual_Reality.mdwn
similarity index 100%
rename from wiki/
rename to src/Virtual_Reality.mdwn
diff --git a/wiki/favicon.ico b/src/favicon.ico
similarity index 100%
rename from wiki/favicon.ico
rename to src/favicon.ico
diff --git a/wiki/img/318ti-coliseum.jpeg b/src/img/318ti-coliseum.jpeg
similarity index 100%
rename from wiki/img/318ti-coliseum.jpeg
rename to src/img/318ti-coliseum.jpeg
diff --git a/wiki/img/318ti-diagnostics.jpeg b/src/img/318ti-diagnostics.jpeg
similarity index 100%
rename from wiki/img/318ti-diagnostics.jpeg
rename to src/img/318ti-diagnostics.jpeg
diff --git a/wiki/img/318ti-nightcore.jpeg b/src/img/318ti-nightcore.jpeg
similarity index 100%
rename from wiki/img/318ti-nightcore.jpeg
rename to src/img/318ti-nightcore.jpeg
diff --git a/wiki/img/drainage.jpeg b/src/img/drainage.jpeg
similarity index 100%
rename from wiki/img/drainage.jpeg
rename to src/img/drainage.jpeg
diff --git a/wiki/img/ftx-historic-funding.jpeg b/src/img/ftx-historic-funding.jpeg
similarity index 100%
rename from wiki/img/ftx-historic-funding.jpeg
rename to src/img/ftx-historic-funding.jpeg
diff --git a/wiki/img/hayes-stops.jpeg b/src/img/hayes-stops.jpeg
similarity index 100%
rename from wiki/img/hayes-stops.jpeg
rename to src/img/hayes-stops.jpeg
diff --git a/wiki/img/hayes.jpeg b/src/img/hayes.jpeg
similarity index 100%
rename from wiki/img/hayes.jpeg
rename to src/img/hayes.jpeg
diff --git a/wiki/img/levana-osmosis.jpeg b/src/img/levana-osmosis.jpeg
similarity index 100%
rename from wiki/img/levana-osmosis.jpeg
rename to src/img/levana-osmosis.jpeg
diff --git a/wiki/img/luna-brothers.jpeg b/src/img/luna-brothers.jpeg
similarity index 100%
rename from wiki/img/luna-brothers.jpeg
rename to src/img/luna-brothers.jpeg
diff --git a/wiki/img/mahoro.jpeg b/src/img/mahoro.jpeg
similarity index 100%
rename from wiki/img/mahoro.jpeg
rename to src/img/mahoro.jpeg
diff --git a/wiki/img/rubberband-perps.jpeg b/src/img/rubberband-perps.jpeg
similarity index 100%
rename from wiki/img/rubberband-perps.jpeg
rename to src/img/rubberband-perps.jpeg
diff --git a/wiki/img/terra-anchor-ltv.jpeg b/src/img/terra-anchor-ltv.jpeg
similarity index 100%
rename from wiki/img/terra-anchor-ltv.jpeg
rename to src/img/terra-anchor-ltv.jpeg
diff --git a/wiki/img/terra-ibc-to-osmosis.jpeg b/src/img/terra-ibc-to-osmosis.jpeg

(Diff truncated)