{"id":60860,"date":"2026-06-21T22:47:31","date_gmt":"2026-06-21T14:47:31","guid":{"rendered":"https:\/\/nightfame.com\/style\/?p=60860"},"modified":"2026-06-21T23:05:21","modified_gmt":"2026-06-21T15:05:21","slug":"chapter-4-the-sandwich-attack-the-front-running-fencer","status":"publish","type":"post","link":"https:\/\/nightfame.com\/style\/chapter-4-the-sandwich-attack-the-front-running-fencer\/","title":{"rendered":"Chapter 4: The Sandwich Attack – The Front-Running Fencer"},"content":{"rendered":"
\n
\"\"<\/figure><\/div>\n\n\n

<\/p>\n\n\n\n

Nia drew three rectangles on the whiteboard, stacked vertically like a sandwich.<\/p>\n\n\n\n

\u201cFront slice,\u201d she said, tapping the top rectangle. \u201cThe Seeker buys the artifact at the original price.\u201d<\/p>\n\n\n\n

She tapped the middle rectangle. \u201cThe meat. You buy the artifact\u2014except you\u2019re not buying from the creator anymore. You\u2019re buying from The Seeker, at a higher price.\u201d<\/p>\n\n\n\n

She tapped the bottom rectangle. \u201cBack slice. The Seeker sells the artifact to you. The transaction completes. The block finalizes.\u201d<\/p>\n\n\n\n

Jesse stared at the diagram. \u201cWait. You\u2019re saying The Seeker buys the sword before<\/em> me, then sells it to<\/em> me in the same block? How is that possible?\u201d<\/p>\n\n\n\n

\u201cBecause the validator includes all three transactions in the same block, in that specific order.\u201d Nia drew arrows connecting the rectangles. \u201cThe Seeker\u2019s first transaction goes at the top of the block. Your transaction goes in the middle. The Seeker\u2019s second transaction goes at the bottom. By the time the block is finished, you\u2019ve bought the sword from The Seeker, not from the original creator.\u201d<\/p>\n\n\n\n

\u201cBut I thought I was buying from the creator.\u201d<\/p>\n\n\n\n

\u201cYou thought you were. But the Seeker inserted itself between you and the creator. It\u2019s like a middleman you never asked for\u2014one that charges you extra and gives you nothing in return except the thing you were trying to buy anyway.\u201d<\/p>\n\n\n\n

Jesse\u2019s stomach turned. He thought about the Emberheart sale. The way his transaction had failed. The way fifteen swords had been bought by the same address.<\/p>\n\n\n\n

\u201cDid this happen to me?\u201d he asked quietly.<\/p>\n\n\n\n

Nia hesitated. She looked at the whiteboard, then at her computer screen, then back at Jesse.<\/p>\n\n\n\n

\u201cI didn\u2019t want to tell you until you understood how it works,\u201d she said. \u201cBut yes. Let me show you.\u201d<\/p>\n\n\n\n

\n\n\n\n

She pulled up the Emberheart block again\u2014Block #4,821,033\u2014but this time she filtered the transactions differently. Instead of showing every transaction, she showed only the ones involving the Emberheart sale contract.<\/p>\n\n\n\n

\u201cHere\u2019s The Seeker\u2019s first purchase,\u201d she said, pointing to transaction #4. \u201cBought one sword for 50 credits.\u201d<\/p>\n\n\n\n

She scrolled down. \u201cHere\u2019s another user\u2014not you\u2014at transaction #52. They bought a sword for 60 credits.\u201d<\/p>\n\n\n\n

Jesse frowned. \u201cWhy would someone pay 60 credits when the price is 50?\u201d<\/p>\n\n\n\n

\u201cThey didn\u2019t mean to. Look at the seller address.\u201d<\/p>\n\n\n\n

Jesse leaned closer. The seller address for transaction #52 wasn\u2019t the creator\u2019s contract. It was 0x3f2a…9d11<\/strong>.<\/p>\n\n\n\n

The Seeker\u2019s address.<\/p>\n\n\n\n

\u201cThe Seeker bought the sword for 50 credits,\u201d Nia said slowly, \u201cthen immediately sold it to this user for 60 credits. The user thought they were buying from the creator. But the block shows they bought from The Seeker.\u201d<\/p>\n\n\n\n

\u201cBut the user\u2019s transaction was submitted to the creator\u2019s contract, right? How did it get redirected?\u201d<\/p>\n\n\n\n

\u201cIt didn\u2019t get redirected. The Seeker\u2019s second transaction\u2014the back slice\u2014was submitted after<\/em> the user\u2019s transaction, but it was ordered before<\/em> in the block.\u201d Nia drew a timeline on the whiteboard. \u201cIn reality, the user\u2019s transaction arrived in the mempool before The Seeker\u2019s back slice. But the validator ordered them differently. The Seeker\u2019s back slice went first, followed by the user\u2019s purchase. So by the time the user\u2019s transaction executed, The Seeker already owned the sword and had listed it for resale at a higher price.\u201d<\/p>\n\n\n\n

Jesse\u2019s head was spinning. \u201cSo the validator helped The Seeker steal from the user?\u201d<\/p>\n\n\n\n

\u201cThe validator didn\u2019t help. The validator just ordered transactions by gas fee. The Seeker paid higher fees for both its front slice and back slice, so both transactions jumped ahead of the user\u2019s.\u201d Nia sighed. \u201cThe validator gets paid either way. They don\u2019t care who wins.\u201d<\/p>\n\n\n\n

Jesse pointed to his own failed transaction at the bottom of the block. \u201cWhat about me? Did I get sandwiched too?\u201d<\/p>\n\n\n\n

Nia clicked on his transaction. \u201cYours failed because the sword was already gone. The Seeker had bought all fifteen copies it wanted. There was nothing left for you to buy, even at a markup.\u201d<\/p>\n\n\n\n

\u201cSo I didn\u2019t even get the chance to overpay.\u201d<\/p>\n\n\n\n

\u201cNo. You just lost.\u201d<\/p>\n\n\n\n

\n\n\n\n

Jesse stood up. Walked to the window. Outside, the university neighborhood was quiet\u2014students in classes, delivery bikes zipping past, a dog barking somewhere in the distance.<\/p>\n\n\n\n

Normal life. While inside this small apartment, he was learning that the digital world he loved was built on a foundation of invisible theft.<\/p>\n\n\n\n

\u201cHow many people has this happened to?\u201d he asked.<\/p>\n\n\n\n

Nia pulled up a different dashboard\u2014one that tracked something called MEV<\/em>, or Miner Extractable Value. The screen showed a graph that climbed like a mountain range. Peaks and valleys, but always trending upward.<\/p>\n\n\n\n

\u201cLast month alone,\u201d she said, \u201cacross the whole network, front-running and sandwich attacks extracted about two million credits from users. That\u2019s money that should have gone to creators and buyers, but ended up in the pockets of validators and bots.\u201d<\/p>\n\n\n\n

\u201cTwo million?\u201d<\/p>\n\n\n\n

\u201cTwo million. And that\u2019s just the transactions we can see. The real number is probably higher.\u201d<\/p>\n\n\n\n

Jesse turned from the window. \u201cHow do you live with that?\u201d<\/p>\n\n\n\n

Nia\u2019s face hardened. \u201cWhat do you mean?\u201d<\/p>\n\n\n\n

\u201cYou run a validator. You said you participate in front-running. How do you sit here, with your little computers and your sticky notes, and watch two million credits get stolen every month?\u201d<\/p>\n\n\n\n

\u201cI didn\u2019t say I was proud of it.\u201d Nia\u2019s voice was sharp. \u201cI said it\u2019s how we survive. There\u2019s a difference.\u201d<\/p>\n\n\n\n

\u201cIs there?\u201d<\/p>\n\n\n\n

They stared at each other. The validator nodes hummed in the silence.<\/p>\n\n\n\n

Then Nia looked away. She pulled off her glasses, rubbed her eyes, and put them back on. \u201cYou want the truth? I hate it. I hate watching the mempool every day. I hate seeing normal people get ripped off by bots that I could stop if I just\u2026 changed the rules.\u201d<\/p>\n\n\n\n

\u201cSo why don\u2019t you?\u201d<\/p>\n\n\n\n

\u201cBecause I\u2019m one validator. There are thousands. If I stop playing the game, I don\u2019t change the game. I just lose.\u201d She gestured to the mini computers. \u201cThose nodes? They cost money to run. Electricity isn\u2019t free. Internet isn\u2019t free. The hardware wasn\u2019t free. My brother took out a loan to buy this setup. We have<\/em> to earn enough to pay it back.\u201d<\/p>\n\n\n\n

Jesse didn\u2019t have an answer for that. He\u2019d never thought about the costs of running a validator. To him, the network had always been abstract\u2014just a system that worked, or didn\u2019t work, depending on his luck.<\/p>\n\n\n\n

But behind every transaction was a person. Behind every validator was a person. And behind every sandwich attack was a choice.<\/p>\n\n\n\n

\u201cI\u2019m sorry,\u201d he said finally. \u201cI didn\u2019t mean to\u2014\u201d<\/p>\n\n\n\n

\u201cYes, you did.\u201d Nia\u2019s voice was tired now. \u201cAnd you were right to. I am part of the problem. I just don\u2019t know how to become part of the solution.\u201d<\/p>\n\n\n\n

\n\n\n\n

Jesse sat back down. The whiteboard still showed the sandwich diagram\u2014three rectangles, three arrows, one ugly truth.<\/p>\n\n\n\n

\u201cYou said you\u2019ve been working on ideas,\u201d he said. \u201cShow me what you\u2019ve tried. And show me why it didn\u2019t work.\u201d<\/p>\n\n\n\n

Nia looked at him. For a moment, he thought she might tell him to leave. But instead, she picked up the marker and erased the sandwich diagram.<\/p>\n\n\n\n

\u201cOkay,\u201d she said. \u201cBut first, I need coffee. Real coffee, not energy drinks. And I need to get out of this apartment.\u201d<\/p>\n\n\n\n

She grabbed her jacket\u2014a thin denim thing with a validator pin on the collar\u2014and headed for the door. \u201cThere\u2019s a coffee shop two blocks away. They have terrible pastries and okay espresso. Let\u2019s go.\u201d<\/p>\n\n\n\n

\n\n\n\n

The coffee shop was called \u201cThe Daily Grind,\u201d which Jesse thought was either clever or lazy, depending on how much caffeine you\u2019d had. It was mostly empty\u2014a few students with laptops, an older man reading a newspaper, a barista who looked like she\u2019d rather be anywhere else.<\/p>\n\n\n\n

Nia ordered a double espresso. Jesse ordered a hot chocolate because he didn\u2019t trust the coffee.<\/p>\n\n\n\n

They sat at a table in the corner, away from the windows.<\/p>\n\n\n\n

\u201cOkay,\u201d Nia said, pulling out her laptop. \u201cYou want to know what I\u2019ve tried. I\u2019ll start with the simplest idea: time-based ordering.\u201d<\/p>\n\n\n\n

She opened a document on her screen\u2014a draft of a protocol she\u2019d been designing. \u201cWhat if validators agreed to order transactions strictly by timestamp? First come, first served. No gas fee priority at all.\u201d<\/p>\n\n\n\n

Jesse nodded. \u201cThat sounds fair.\u201d<\/p>\n\n\n\n

\u201cIt sounds fair. But here\u2019s why it fails.\u201d She flipped to a different page\u2014a simulation result. \u201cWhen my pool tried this for three days, our inclusion times went up by 40%. Users hated it. They wanted fast confirmations, not fair ordering.\u201d<\/p>\n\n\n\n

\u201cBut wasn\u2019t it still fast enough?\u201d<\/p>\n\n\n\n

\u201cFor some users, yes. But for anyone who needed speed\u2014like someone buying a limited-edition artifact\u2014our pool was useless. They went to validators who still prioritized by gas fee.\u201d Nia took a sip of her espresso. \u201cAnd here\u2019s the real killer: time-based ordering doesn\u2019t stop sandwich attacks. The Seeker can still submit its front slice and back slice with the same timestamps. It just has to be fast enough to beat you to the mempool.\u201d<\/p>\n\n\n\n

\u201cSo it\u2019s not enough to change ordering. You have to change what the Seeker can see.\u201d<\/p>\n\n\n\n

\u201cExactly.\u201d Nia pointed at him with her espresso cup. \u201cNow you\u2019re thinking like a cryptographer.\u201d<\/p>\n\n\n\n

\n\n\n\n

She pulled up another document. \u201cIdea two: commit-reveal schemes.\u201d<\/p>\n\n\n\n

\u201cWhat\u2019s that?\u201d<\/p>\n\n\n\n

\u201cInstead of submitting your actual transaction to the mempool, you submit a hash of your transaction. A fingerprint. The hash goes into the mempool for ordering. Later, after the order is locked, you reveal the actual transaction.\u201d<\/p>\n\n\n\n

Jesse thought about it. \u201cSo The Seeker sees the hash but doesn\u2019t know what it means?\u201d<\/p>\n\n\n\n

\u201cRight. It can\u2019t front-run what it can\u2019t understand.\u201d<\/p>\n\n\n\n

\u201cBut couldn\u2019t it just guess? Like, if it sees a hash at the exact moment of a sale, it could assume that hash is a purchase and try to front-run anyway?\u201d<\/p>\n\n\n\n

Nia set down her cup. \u201cThat\u2019s exactly what happened when I tested it. The Seeker\u2014or some version of it\u2014started guessing. It would see a hash, assume it was for a popular artifact, and submit its own transaction with a higher gas fee. Sometimes it guessed wrong. But sometimes it guessed right. And when it guessed right, it still won.\u201d<\/p>\n\n\n\n

Jesse frowned. \u201cSo commit-reveal alone isn\u2019t enough.\u201d<\/p>\n\n\n\n

\u201cIt\u2019s not enough. But it\u2019s part of the solution. You need something stronger. Something that hides the transaction completely until after ordering is finalized.\u201d<\/p>\n\n\n\n

Jesse leaned forward. \u201cLike encryption?\u201d<\/p>\n\n\n\n

Nia smiled\u2014the first real smile he\u2019d seen from her. \u201cLike encryption. But not regular encryption. Time-lock encryption. Transactions are encrypted when they enter the mempool. Validators order the encrypted bundles without seeing inside. Then, after the block is finalized, the encryption unlocks and validators execute the transactions in the already-determined order.\u201d<\/p>\n\n\n\n

Jesse\u2019s heart started beating faster. This sounded like something that could actually work. \u201cHas anyone built this?\u201d<\/p>\n\n\n\n

\u201cBits and pieces. There are research papers. Prototypes on test networks. But no one has put it all together into a system that\u2019s fast enough, cheap enough, and secure enough for real use.\u201d Nia pulled up a final document\u2014a list of requirements. \u201cWe would need three things: a verifiable random function for ordering, a commit-reveal scheme for hiding intent, and an encrypted mempool for complete privacy.\u201d<\/p>\n\n\n\n

\u201cThree things,\u201d Jesse repeated. \u201cThat\u2019s a lot.\u201d<\/p>\n\n\n\n

\u201cThat\u2019s everything. If we can build all three, The Seeker is blind. It can\u2019t see transactions. It can\u2019t guess hashes. It can\u2019t front-run what it can\u2019t see.\u201d Nia closed her laptop. \u201cBut I\u2019ve been trying to build this alone for six months, and I\u2019ve gotten exactly nowhere.\u201d<\/p>\n\n\n\n

\n\n\n\n

Jesse stirred his hot chocolate. The marshmallows had melted into a sweet sludge at the bottom of the cup.<\/p>\n\n\n\n

\u201cYou\u2019re not alone anymore,\u201d he said.<\/p>\n\n\n\n

Nia looked at him. \u201cYou\u2019re not a coder.\u201d<\/p>\n\n\n\n

\u201cNo. But I\u2019m a strategist. I play games where you have to think ten moves ahead. I know how to find weaknesses in systems.\u201d He set down his spoon. \u201cAnd I have something you don\u2019t have.\u201d<\/p>\n\n\n\n

\u201cWhat\u2019s that?\u201d<\/p>\n\n\n\n

\u201cI\u2019ve been the victim. I know what it feels like to lose to The Seeker. I know exactly what\u2019s at stake.\u201d He paused. \u201cAnd I\u2019m not going to stop until I can buy my sword without getting robbed.\u201d<\/p>\n\n\n\n

Nia was quiet for a long time. The coffee shop hummed around them\u2014the hiss of the espresso machine, the murmur of other conversations, the scratch of pens on paper.<\/p>\n\n\n\n

Finally, she said, \u201cYou\u2019re serious.\u201d<\/p>\n\n\n\n

\u201cI\u2019m serious.\u201d<\/p>\n\n\n\n

\u201cYou understand that this could take months. Maybe longer. And we might fail.\u201d<\/p>\n\n\n\n

\u201cI understand.\u201d<\/p>\n\n\n\n

\u201cAnd you understand that even if we succeed, The Seeker won\u2019t just disappear. It will adapt. It will find new exploits. We\u2019ll have to keep fighting.\u201d<\/p>\n\n\n\n

Jesse nodded. \u201cThat\u2019s fine. I\u2019ve got time.\u201d<\/p>\n\n\n\n

Nia stared at him. Then she laughed\u2014not the bitter laugh from before, but something lighter. Hopeful, almost.<\/p>\n\n\n\n

\u201cOkay,\u201d she said. \u201cOkay. Let\u2019s do this.\u201d<\/p>\n\n\n\n

She pulled out her laptop again and opened a blank document. At the top, she typed:<\/p>\n\n\n\n

PROJECT: FAIR SEQUENCING PROTOCOL<\/strong><\/p>\n\n\n\n

Underneath, she listed the three components:<\/p>\n\n\n\n

    \n
  1. VRF Ordering<\/strong>\u00a0(unpredictable, verifiable)<\/li>\n\n\n\n
  2. Commit-Reveal<\/strong>\u00a0(hide intent)<\/li>\n\n\n\n
  3. Encrypted Mempool<\/strong>\u00a0(hide everything)<\/li>\n<\/ol>\n\n\n\n

    Jesse pointed to the screen. \u201cWhere do we start?\u201d<\/p>\n\n\n\n

    Nia cracked her knuckles. \u201cWe start with the Fair Sequencing DAO.\u201d<\/p>\n\n\n\n

    \u201cThe what?\u201d<\/p>\n\n\n\n

    \u201cA group of validators who\u2019ve pledged to order transactions fairly. They\u2019re small, they\u2019re losing money, and they\u2019re desperate for a solution. If we can build something that works, they\u2019ll be the first to adopt it.\u201d<\/p>\n\n\n\n

    She pulled up a website\u2014a simple page with a logo of a balanced scale and the words ORDER WITHOUT EXPLOIT<\/em>.<\/p>\n\n\n\n

    \u201cThere\u2019s a meeting tomorrow night,\u201d Nia said. \u201cVirtual. I can get you in.\u201d<\/p>\n\n\n\n

    Jesse looked at the logo. The balanced scale. Justice. Fairness.<\/p>\n\n\n\n

    \u201cTomorrow night,\u201d he said. \u201cI\u2019ll be there.\u201d<\/p>\n\n\n\n

    \n\n\n\n

    They walked back to Nia\u2019s apartment in the fading afternoon light. Jesse\u2019s mind was racing\u2014VRF, commit-reveal, encrypted mempool, sandwich attacks, gas auctions, front-running. Words that had meant nothing a week ago now felt like weapons.<\/p>\n\n\n\n

    \u201cHey,\u201d Nia said as they reached her building\u2019s front door. \u201cI should warn you. The DAO meeting\u2026 it\u2019s not going to be easy. Some of those validators have given up. They don\u2019t think fairness is possible anymore.\u201d<\/p>\n\n\n\n

    \u201cThen we\u2019ll convince them.\u201d<\/p>\n\n\n\n

    \u201cAnd some of them might recognize your name from the Emberheart sale. The Seeker\u2019s victims are famous in those circles. Not in a good way.\u201d<\/p>\n\n\n\n

    Jesse shrugged. \u201cLet them recognize me. I\u2019m not embarrassed. I got robbed. That\u2019s not my shame to carry.\u201d<\/p>\n\n\n\n

    Nia looked at him for a long moment. Then she nodded.<\/p>\n\n\n\n

    \u201cTomorrow night,\u201d she said. \u201cEight o\u2019clock. I\u2019ll send you the link.\u201d<\/p>\n\n\n\n

    She disappeared into the building. Jesse stood on the sidewalk for a minute, watching the sunset paint the sky orange and red\u2014the same colors as Emberheart\u2019s blade.<\/p>\n\n\n\n

    He thought about the sword. About the empty frame on his wall. About The Seeker, still out there, still scanning, still taking.<\/p>\n\n\n\n

    Tomorrow, the fight would begin.<\/p>\n\n\n\n

    But tonight, for the first time in a week, he felt like he might actually win.<\/p>\n\n\n\n

    Table of contents:<\/em><\/strong>
    Introduction<\/a>
    Chapter 1: The Mempool<\/a>
    Chapter 2: A Transaction in the Dark<\/a>
    Chapter 3: The Gas Auction<\/a>
    Chapter 4: The Sandwich Attack<\/a>
    Chapter 5: The Priority Fee War<\/a> <<<<<< NEXT<\/strong>
    Chapter 6: A Fair Ordering Protocol<\/a>
    Chapter 7: The Commit-Reveal Scheme<\/a>
    Chapter 8: The Encrypted Mempool<\/a>
    Chapter 9: The Time-Weighted Consensus<\/a>
    Chapter 10: A Just Sequence<\/a><\/p>\n

    <\/div>

    <\/path><\/svg><\/i> \"Loading\"<\/p>

    <\/div>","protected":false},"excerpt":{"rendered":"

    Nia drew three rectangles on the whiteboard, stacked vertically like a sandwich. \u201cFront slice,\u201d she […]<\/p>\n

    <\/div>\n

    <\/path><\/svg><\/i> \"Loading\"<\/p>\n

    <\/div>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[60292],"tags":[60332,58994,60293,58992,60294,60295,60333,60335,60334,60297,60296,60336,61157,61158,61159,61160,61161,61163,61162,60330,60331],"class_list":["post-60860","post","type-post","status-publish","format-standard","hentry","category-science-fiction","tag-children-novel","tag-crypto","tag-crypto-story","tag-cryptocurrency","tag-cryptocurrency-story","tag-science-fiction","tag-science-fiction-novel","tag-science-fiction-novel-for-children","tag-science-fiction-novel-for-young-adult","tag-science-fiction-story","tag-science-fiction-story-for-children","tag-science-fiction-story-for-young-adult","tag-the-front-running-fencer","tag-the-front-running-fencer-science-fiction-novel","tag-the-front-running-fencer-science-fiction-novel-for-children","tag-the-front-running-fencer-science-fiction-novel-for-young-adult","tag-the-front-running-fencer-science-fiction-story","tag-the-front-running-fencer-science-fiction-story-for-children","tag-the-front-running-fencer-science-fiction-story-for-young-adult","tag-ya-novel","tag-young-adult-novel"],"_links":{"self":[{"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/posts\/60860","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/comments?post=60860"}],"version-history":[{"count":2,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/posts\/60860\/revisions"}],"predecessor-version":[{"id":60897,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/posts\/60860\/revisions\/60897"}],"wp:attachment":[{"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/media?parent=60860"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/categories?post=60860"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/tags?post=60860"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}