{"id":60872,"date":"2026-06-21T22:55:15","date_gmt":"2026-06-21T14:55:15","guid":{"rendered":"https:\/\/nightfame.com\/style\/?p=60872"},"modified":"2026-06-21T23:05:43","modified_gmt":"2026-06-21T15:05:43","slug":"chapter-8-the-encrypted-mempool-the-front-running-fencer","status":"publish","type":"post","link":"https:\/\/nightfame.com\/style\/chapter-8-the-encrypted-mempool-the-front-running-fencer\/","title":{"rendered":"Chapter 8: The Encrypted Mempool – The Front-Running Fencer"},"content":{"rendered":"
\n
\"\"<\/figure><\/div>\n\n\n

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

The emergency DAO meeting was the most crowded Jesse had ever seen.<\/p>\n\n\n\n

Every validator who had ever shown interest in fair sequencing seemed to be there. Forty-three avatars filled the virtual room\u2014more than double the usual attendance. Even BlockGuild had shown up, his brick-wall icon looming in the corner like a storm cloud.<\/p>\n\n\n\n

But the mood wasn’t hopeful. It was frantic.<\/p>\n\n\n\n

Cipher opened the meeting without any pleasantries. \u201cYou\u2019ve all seen the reports. The Seeker is now actively breaking commit-reveal on the testnet using machine learning. We have approximately six weeks before it becomes fully effective.\u201d<\/p>\n\n\n\n

\u201cSix weeks?\u201d ValleyValidator\u2019s voice cracked. \u201cWe don\u2019t even have commit-reveal deployed yet.\u201d<\/p>\n\n\n\n

\u201cExactly.\u201d Cipher\u2019s voice modulator made their words feel cold, clinical. \u201cWhich is why we\u2019re skipping commit-reveal as a standalone layer. We\u2019re going straight to the encrypted mempool.\u201d<\/p>\n\n\n\n

The room erupted.<\/p>\n\n\n\n

\u201cStraight to encryption? That\u2019s years of research!\u201d<\/p>\n\n\n\n

\u201cWe haven\u2019t even agreed on a scheme!\u201d<\/p>\n\n\n\n

\u201cThis is suicide.\u201d<\/p>\n\n\n\n

Nia unmuted herself. \u201cIt\u2019s not suicide. It\u2019s the only option left. The Seeker has proven it can crack hashes at scale. Commit-reveal alone is dead. We need full transaction privacy from the moment of submission.\u201d<\/p>\n\n\n\n

BlockGuild\u2019s avatar pulsed. \u201cAnd how do you propose we build that in six weeks? Do you have a time machine, Nia?\u201d<\/p>\n\n\n\n

\u201cNo. But I have a design.\u201d She shared her screen. The document she and Jesse had been working on\u2014the emergency implementation plan\u2014appeared. \u201cTime-lock encryption. Transactions are encrypted when they enter the mempool. The encryption key is released only after the block is finalized. Validators order the encrypted bundles without seeing inside. Then they decrypt and execute in that order.\u201d<\/p>\n\n\n\n

Another validator, CryptoSage<\/em>, spoke up. \u201cTime-lock encryption isn\u2019t new. The challenge is making it fast enough and cheap enough for a high-throughput network. The decryption overhead is enormous.\u201d<\/p>\n\n\n\n

\u201cWe\u2019ve identified a scheme based on verifiable delay functions,\u201d Nia said. \u201cIt adds about two seconds to block finality, but it\u2019s provably secure and doesn\u2019t require trusted setup.\u201d<\/p>\n\n\n\n

\u201cTwo seconds?\u201d BlockGuild laughed. \u201cUsers won\u2019t wait two extra seconds. They\u2019ll go to QuickPath.\u201d<\/p>\n\n\n\n

\u201cThey\u2019ll go to QuickPath and get sandwiched,\u201d Jesse cut in. He\u2019d been muted, but Nia unmuted him. \u201cYou keep talking like speed is the only thing that matters. It\u2019s not. Trust matters. Safety matters. If you build a network where people don\u2019t get robbed, they will wait two extra seconds.\u201d<\/p>\n\n\n\n

A murmur rippled through the room. Some validators nodded\u2014their avatars tilting slightly. Others remained still.<\/p>\n\n\n\n

Cipher spoke again. \u201cWe need a vote. Not on implementation\u2014that will take weeks of work. But on direction<\/em>. Does the DAO commit to building an encrypted mempool as the foundation of our fair ordering protocol?\u201d<\/p>\n\n\n\n

The voting interface appeared on everyone\u2019s screens. Green for yes. Red for no.<\/p>\n\n\n\n

Jesse held his breath.<\/p>\n\n\n\n

\n\n\n\n

Scene 2: Time-Lock Encryption Explained<\/strong><\/p>\n\n\n\n

While the votes trickled in, Nia pulled Jesse into a private side channel.<\/p>\n\n\n\n

\u201cThey\u2019re not going to understand the cryptography,\u201d she whispered. \u201cI need you to explain it in plain language. Use your strategy game metaphors.\u201d<\/p>\n\n\n\n

Jesse nodded. He unmuted himself in the main room. \u201cCan I say something?\u201d<\/p>\n\n\n\n

Cipher granted him speaking permission.<\/p>\n\n\n\n

\u201cEveryone here is thinking about the technical challenge. How do we encrypt without slowing down? How do we decrypt without failing? Those are real problems. But the bigger problem is that The Seeker can see everything you do. Right now, it\u2019s like playing a strategy game where your opponent has a map hack. They see your units, your resources, your every move.\u201d<\/p>\n\n\n\n

He paused. \u201cTime-lock encryption is like fog of war. For the first few seconds\u2014until the block is finalized\u2014the battlefield is dark. The Seeker can\u2019t see your transaction. It can\u2019t copy it. It can\u2019t sandwich it. By the time the fog lifts, the battle is over. You\u2019ve already won.\u201d<\/p>\n\n\n\n

ValidatorMom\u2019s avatar lit up. \u201cI like that. Fog of war.\u201d<\/p>\n\n\n\n

\u201cIt\u2019s not a perfect analogy,\u201d Jesse admitted. \u201cBut it\u2019s close enough. The point is, we don\u2019t need to make front-running impossible forever. We just need to make it impossible during the window when ordering happens<\/em>. Once the order is locked, The Seeker can see everything\u2014but it can\u2019t change anything.\u201d<\/p>\n\n\n\n

\u201cThat\u2019s the key insight,\u201d Cipher added. \u201cWe don\u2019t need permanent secrecy. We just need temporary secrecy. Just long enough to finalize the block.\u201d<\/p>\n\n\n\n

The voting window closed.<\/p>\n\n\n\n

Yes: 27<\/strong>
No: 16<\/strong><\/p>\n\n\n\n

The encrypted mempool had passed.<\/p>\n\n\n\n

\n\n\n\n

Scene 3: The DAO Votes<\/strong><\/p>\n\n\n\n

BlockGuild\u2019s avatar flickered. \u201cTwenty-seven votes. That\u2019s not a mandate. That\u2019s barely a majority.\u201d<\/p>\n\n\n\n

\u201cIt\u2019s a majority,\u201d Nia said. \u201cAnd it\u2019s enough to move forward.\u201d<\/p>\n\n\n\n

\u201cMove forward to what? We don\u2019t have the code. We don\u2019t have the funding. We don\u2019t have the expertise.\u201d BlockGuild\u2019s voice was sharp. \u201cI\u2019ve been in this DAO for eight months. I\u2019ve watched us spin our wheels on one failed experiment after another. I\u2019m done.\u201d<\/p>\n\n\n\n

The room went silent.<\/p>\n\n\n\n

\u201cI\u2019m leaving the DAO,\u201d BlockGuild announced. \u201cAnd I\u2019m taking my pool to QuickPath. At least they pay.\u201d<\/p>\n\n\n\n

His avatar disappeared. Then another validator\u2019s avatar faded. And another. One by one, the red voters dropped out. Within thirty seconds, the room had lost sixteen members.<\/p>\n\n\n\n

Twenty-seven remained.<\/p>\n\n\n\n

\u201cGood riddance,\u201d Nia muttered under her breath.<\/p>\n\n\n\n

But Jesse saw her hands shaking. Sixteen validators lost. A huge blow to the DAO\u2019s credibility and resources.<\/p>\n\n\n\n

Cipher spoke calmly. \u201cThe DAO is smaller now. But it\u2019s also more committed. We know what we need to build. Let\u2019s build it.\u201d<\/p>\n\n\n\n

\n\n\n\n

Scene 4: The Blind Spot<\/strong><\/p>\n\n\n\n

After the meeting, Cipher, Nia, and Jesse stayed behind in the virtual room.<\/p>\n\n\n\n

\u201cBlockGuild is going to be a problem,\u201d Cipher said. \u201cNot because he left, but because he\u2019ll actively work against us. QuickPath will use his inside knowledge of our design to anticipate our moves.\u201d<\/p>\n\n\n\n

\u201cCan we change the design?\u201d Jesse asked.<\/p>\n\n\n\n

\u201cNot fundamentally. The core components\u2014VRF, commit-reveal, time-lock encryption\u2014are fixed. But we can add obfuscation. Make it harder for them to know exactly when and how we deploy.\u201d<\/p>\n\n\n\n

Nia was already typing. \u201cI\u2019ll start a new code repository. Private. Only the remaining DAO members get access.\u201d<\/p>\n\n\n\n

\u201cAnd me?\u201d Jesse asked.<\/p>\n\n\n\n

Nia looked at him. \u201cYou\u2019re not a validator. But you\u2019re the reason we have a user perspective. You\u2019re in.\u201d<\/p>\n\n\n\n

Cipher nodded. \u201cAgreed. Jesse, you\u2019ll handle documentation and user outreach. When this goes live, we need people to actually use<\/em> it. That\u2019s your job.\u201d<\/p>\n\n\n\n

Jesse felt a weight settle on his shoulders. He wasn\u2019t a coder. He wasn\u2019a cryptographer. But he could tell a story. He could explain why this mattered.<\/p>\n\n\n\n

\u201cI\u2019ll do it,\u201d he said.<\/p>\n\n\n\n

\n\n\n\n

The next three weeks were a blur of late nights and early mornings.<\/p>\n\n\n\n

Nia coded. Cipher reviewed. The remaining DAO members tested. Jesse wrote\u2014user guides, FAQ documents, forum posts, and a growing collection of stories from other collectors who had been victimized by The Seeker.<\/p>\n\n\n\n

The encrypted mempool took shape slowly, painfully.<\/p>\n\n\n\n

The first version was too slow. Decrypting a block of one hundred transactions took nearly eight seconds\u2014four times the target.<\/p>\n\n\n\n

The second version was faster but had a security flaw. A sharp-eyed validator found that the time-lock key could be derived early if an attacker controlled enough network nodes.<\/p>\n\n\n\n

The third version fixed the flaw but introduced a new bug: occasionally, decryption would fail for random transactions, causing them to be dropped from the block.<\/p>\n\n\n\n

\u201cWe\u2019re never going to get this right,\u201d Nia said one night, her head in her hands. The validator nodes hummed around her, indifferent to her despair.<\/p>\n\n\n\n

Jesse sat on the floor, back against the wall, notebook open. \u201cYou said failure is not an option.\u201d<\/p>\n\n\n\n

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

\u201cNo, you didn\u2019t.\u201d He stood up and walked to her desk. \u201cWe\u2019re not failing. We\u2019re iterating. Every bug we find is one less bug in production.\u201d<\/p>\n\n\n\n

Nia laughed\u2014a hollow, exhausted sound. \u201cThat\u2019s what my brother says. \u2018Every bug is a learning opportunity.\u2019 I hate it when he\u2019s right.\u201d<\/p>\n\n\n\n

\u201cHe\u2019s not right. He\u2019s optimistic. There\u2019s a difference.\u201d Jesse pulled up a chair next to her. \u201cShow me the decryption failure. Let\u2019s walk through it together.\u201d<\/p>\n\n\n\n

For the next two hours, they debugged. Nia explained the cryptographic primitives\u2014the verifiable delay functions, the time-lock puzzles, the threshold decryption schemes. Jesse asked questions, took notes, spotted a pattern that Nia had missed.<\/p>\n\n\n\n

\u201cThe failures only happen when the block has more than fifty transactions,\u201d he said. \u201cThat\u2019s not random. That\u2019s a scaling issue.\u201d<\/p>\n\n\n\n

Nia stared at the log files. \u201cYou\u2019re right. The decryption algorithm has an O(n\u00b2) bottleneck. It\u2019s fine for small blocks, but it explodes as block size increases.\u201d<\/p>\n\n\n\n

\u201cCan you fix it?\u201d<\/p>\n\n\n\n

\u201cI can rewrite it. But that\u2019s another week of work.\u201d<\/p>\n\n\n\n

Jesse looked at the calendar. The Seeker\u2019s deadline\u2014six weeks from Cipher\u2019s warning\u2014was now only three weeks away.<\/p>\n\n\n\n

\u201cThen we work faster.\u201d<\/p>\n\n\n\n

\n\n\n\n

They finished the rewrite in five days.<\/p>\n\n\n\n

The new decryption algorithm was elegant\u2014a parallelized scheme that scaled almost linearly. Blocks of one hundred transactions decrypted in under two seconds. Blocks of two hundred in under four.<\/p>\n\n\n\n

\u201cIt\u2019s not perfect,\u201d Nia said, running the final benchmark. \u201cBut it\u2019s good enough.\u201d<\/p>\n\n\n\n

\u201cGood enough is all we need,\u201d Jesse replied.<\/p>\n\n\n\n

Cipher joined their virtual room. \u201cThe testnet is ready. We\u2019re deploying the encrypted mempool tomorrow. Full production simulation. Real transaction loads. Real bot traffic.\u201d<\/p>\n\n\n\n

\u201cReal The Seeker?\u201d Jesse asked.<\/p>\n\n\n\n

\u201cWe\u2019ve captured The Seeker\u2019s behavior patterns from the main network. We\u2019ll run a simulation with those patterns. If our protocol survives, we go to mainnet.\u201d<\/p>\n\n\n\n

Nia took a deep breath. \u201cAnd if it doesn\u2019t?\u201d<\/p>\n\n\n\n

Cipher was quiet for a moment. \u201cThen we try again. But we may not get another chance. QuickPath has been recruiting aggressively. BlockGuild has already switched his pool. They\u2019re processing more transactions than ever.\u201d<\/p>\n\n\n\n

Jesse looked at Nia\u2019s validator nodes\u2014the three little computers that had started this whole journey. They seemed so small now. So fragile.<\/p>\n\n\n\n

\u201cIt\u2019s going to work,\u201d he said. \u201cIt has to.\u201d<\/p>\n\n\n\n

\n\n\n\n

The testnet deployment began at 8:00 AM on a Saturday.<\/p>\n\n\n\n

Jesse had never been so nervous in his life. Not before the Emberheart sale. Not before the DAO meeting. Not before anything.<\/p>\n\n\n\n

He sat in Nia\u2019s apartment, watching the dashboard on her monitor. The testnet was live. Transactions were flowing. The encrypted mempool was accepting encrypted bundles, ordering them with VRF, and decrypting after finalization.<\/p>\n\n\n\n

For the first hour, everything worked perfectly.<\/p>\n\n\n\n

Then the bot traffic started.<\/p>\n\n\n\n

The simulation injected The Seeker\u2019s behavior patterns into the testnet\u2014thousands of fake transactions designed to probe for weaknesses, to guess at encrypted contents, to flood the mempool with garbage.<\/p>\n\n\n\n

Nia watched the logs like a hawk. \u201cIt\u2019s trying to brute-force decryption. Running through possible keys.\u201d<\/p>\n\n\n\n

\u201cCan it succeed?\u201d<\/p>\n\n\n\n

\u201cNot with time-lock encryption. The keys are mathematically guaranteed to be unreachable until the block finalizes. It\u2019s wasting its time.\u201d<\/p>\n\n\n\n

The bot traffic intensified. The mempool swelled to ten thousand pending transactions. The VRF ordering handled the load gracefully. The decryption layer kept up, processing blocks every four seconds.<\/p>\n\n\n\n

\u201cWe\u2019re holding,\u201d Jesse said.<\/p>\n\n\n\n

\u201cWe\u2019re holding,\u201d Nia repeated, almost disbelieving.<\/p>\n\n\n\n

The testnet ran for twelve hours. Twenty-four. Forty-eight.<\/p>\n\n\n\n

Every time The Seeker\u2019s simulation tried a new attack\u2014hash guessing, timing analysis, mempool flooding\u2014the protocol absorbed it and kept going.<\/p>\n\n\n\n

On the third day, Cipher sent a single message:<\/p>\n\n\n\n

\u201cTestnet passed. Mainnet deployment scheduled for next Thursday. Prepare for war.\u201d<\/em><\/p>\n\n\n\n

\n\n\n\n

Nia closed her laptop and leaned back in her chair. The validator nodes hummed softly, their LEDs blinking in steady rhythm.<\/p>\n\n\n\n

\u201cWe did it,\u201d she said.<\/p>\n\n\n\n

\u201cWe did the easy part,\u201d Jesse corrected. \u201cNow we have to convince people to use it.\u201d<\/p>\n\n\n\n

\u201cThat\u2019s your department.\u201d<\/p>\n\n\n\n

Jesse pulled out his notebook. He\u2019d been working on a document for weeks\u2014a user manifesto, a call to action, a promise that the network could be fair again.<\/p>\n\n\n\n

\u201cI\u2019m ready,\u201d he said.<\/p>\n\n\n\n

Nia smiled. \u201cThen let\u2019s go to war.\u201d<\/p>\n\n\n\n

\n\n\n\n

Scene 5: The Fork<\/strong><\/p>\n\n\n\n

Thursday arrived faster than anyone expected.<\/p>\n\n\n\n

The mainnet deployment was scheduled for 2:00 PM. The Fair Sequencing DAO had coordinated with a dozen other validator pools\u2014not all of them, but enough. Enough to create a viable alternative to QuickPath.<\/p>\n\n\n\n

At 1:55 PM, Nia\u2019s dashboard showed the final preparations. The encrypted mempool code was signed and ready. The VRF ordering parameters were set. The time-lock encryption keys were generated.<\/p>\n\n\n\n

\u201cAny last words?\u201d Nia asked.<\/p>\n\n\n\n

Jesse thought about the empty display frame on his wall. The sword he still didn\u2019t have. The thousands of other collectors who had lost to The Seeker.<\/p>\n\n\n\n

\u201cLet\u2019s make front-running extinct,\u201d he said.<\/p>\n\n\n\n

At 2:00 PM exactly, Nia pressed the deploy button.<\/p>\n\n\n\n

The network forked.<\/p>\n\n\n\n

On one side, QuickChain\u2014the old system, with gas fee priority, visible mempools, and front-running allowed. On the other side, FairChain\u2014VRF ordering, encrypted mempool, time-lock privacy.<\/p>\n\n\n\n

For the first few minutes, nothing happened. The network was quiet, uncertain.<\/p>\n\n\n\n

Then the first user transaction arrived on FairChain. A small purchase\u2014a common artifact, nothing rare. But it went through. No front-running. No sandwich. Just a clean, fair transaction.<\/p>\n\n\n\n

Then another. And another.<\/p>\n\n\n\n

Jesse watched the dashboard as the transaction count climbed. Ten. Fifty. Two hundred. A thousand.<\/p>\n\n\n\n

\u201cThey\u2019re coming,\u201d he whispered.<\/p>\n\n\n\n

\u201cThey\u2019re coming,\u201d Nia agreed.<\/p>\n\n\n\n

But QuickPath wasn\u2019t idle. Within an hour, they had launched a propaganda campaign\u2014posts on forums, messages to validators, claims that FairChain was slow, untested, dangerous.<\/p>\n\n\n\n

\u201cIgnore them,\u201d Cipher advised. \u201cLet the results speak.\u201d<\/p>\n\n\n\n

The results were good. FairChain\u2019s block times were slightly longer\u2014about four seconds compared to QuickChain\u2019s two. But the front-running rate was zero. Zero sandwiches. Zero failed purchases due to bots.<\/p>\n\n\n\n

Users noticed.<\/p>\n\n\n\n

\u201cI didn\u2019t get robbed!\u201d one collector posted on a forum. \u201cFirst time in months. I actually got the artifact I wanted.\u201d<\/p>\n\n\n\n

The post went viral.<\/p>\n\n\n\n

By the end of the first week, FairChain was processing thirty percent of the network\u2019s transactions. By the end of the second week, fifty percent.<\/p>\n\n\n\n

QuickPath started losing revenue. Their front-running profits dried up as users fled to the fairer network. BlockGuild, who had so confidently defected, began sending desperate messages to Nia.<\/p>\n\n\n\n

\u201cCan we come back?\u201d he asked.<\/p>\n\n\n\n

Nia showed the message to Jesse.<\/p>\n\n\n\n

\u201cWhat do you think?\u201d she asked.<\/p>\n\n\n\n

Jesse thought about BlockGuild\u2019s behavior\u2014the opposition, the defection, the active work against them.<\/p>\n\n\n\n

\u201cNo,\u201d he said. \u201cHe made his choice.\u201d<\/p>\n\n\n\n

Nia nodded. She deleted the message without replying.<\/p>\n\n\n\n

\n\n\n\n

The empty display frame on Jesse\u2019s wall didn\u2019t stay empty for long.<\/p>\n\n\n\n

A week after the fork, a new sale was announced\u2014the Emberheart Third Edition. The creator had seen the news about FairChain and decided to host the sale exclusively on the fair network.<\/p>\n\n\n\n

Jesse prepared just like before. The countdown. The click. The transaction.<\/p>\n\n\n\n

But this time, everything was different.<\/p>\n\n\n\n

His transaction was encrypted. The Seeker\u2014still active on the old network\u2014couldn\u2019t see it. The VRF ordering placed it fairly among the other purchases. The block finalized in four seconds.<\/p>\n\n\n\n

And when Jesse checked his inventory, the sword was there.<\/p>\n\n\n\n

Emberheart. Glowing orange and red. Finally his.<\/p>\n\n\n\n

He stared at the screen for a long time. The empty frame on his wall seemed to pulse with anticipation.<\/p>\n\n\n\n

\u201cGot it,\u201d he said to no one.<\/p>\n\n\n\n

His phone buzzed. A message from Nia: \u201cI saw the block. Congratulations. You earned it.\u201d<\/em><\/p>\n\n\n\n

Jesse typed back: \u201cWe earned it.\u201d<\/em><\/p>\n\n\n\n

He walked to the wall, removed the empty frame, and inserted the digital display. Emberheart materialized\u2014a blade of molten light, beautiful and finally, fairly won.<\/p>\n\n\n\n

He smiled.<\/p>\n\n\n\n

The war wasn\u2019t over. The Seeker was still out there, still scanning the old network, still extracting value from anyone foolish enough to stay. But FairChain was growing. More validators were switching every day. The encrypted mempool was holding.<\/p>\n\n\n\n

And Jesse had his sword.<\/p>\n\n\n\n

That was enough for now.<\/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>
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> <<<<<< NEXT<\/strong>
Chapter 10: A Just Sequence<\/a><\/p>\n

<\/div>

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

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

The emergency DAO meeting was the most crowded Jesse had ever seen. Every validator who […]<\/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-60872","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\/60872","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=60872"}],"version-history":[{"count":2,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/posts\/60872\/revisions"}],"predecessor-version":[{"id":60901,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/posts\/60872\/revisions\/60901"}],"wp:attachment":[{"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/media?parent=60872"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/categories?post=60872"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/tags?post=60872"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}