{"id":61411,"date":"2026-06-26T23:10:02","date_gmt":"2026-06-26T15:10:02","guid":{"rendered":"https:\/\/nightfame.com\/style\/?p=61411"},"modified":"2026-07-01T22:36:02","modified_gmt":"2026-07-01T14:36:02","slug":"chapter-2-a-trustless-bridge-the-bridge-collapse","status":"publish","type":"post","link":"https:\/\/nightfame.com\/style\/chapter-2-a-trustless-bridge-the-bridge-collapse\/","title":{"rendered":"Chapter 2: A Trustless Bridge – The Bridge Collapse"},"content":{"rendered":"
\n
\"\"<\/figure><\/div>\n\n\n

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

The morning light crept through the grime-caked windows of Remy’s apartment, casting pale yellow streaks across a chaos of data pads, empty energy drink containers, and tangled cooling cables. He hadn’t moved from his workstation in twelve hours. His eyes were bloodshot, his hair was a disaster, and his fingers were cramped from scrolling through endless lines of cryptographic data.<\/p>\n\n\n\n

But he had found something. Something that made his stomach churn with a mixture of vindication and dread.<\/p>\n\n\n\n

The timestamp anomaly from Validator #3 wasn’t an isolated incident. Over the past two weeks, Remy had identified four separate signatures signed during maintenance windows. Four impossible approvals. Four moments when someone\u2014or something\u2014had used Validator #3’s private key without the validator’s knowledge or consent.<\/p>\n\n\n\n

He had spent the night running every diagnostic tool in his arsenal, cross-referencing the signatures against network activity logs, validator status reports, and system uptime records. The evidence was incontrovertible.<\/p>\n\n\n\n

Validator #3’s private key was compromised.<\/p>\n\n\n\n

Remy leaned back in his creaking chair, rubbing his burning eyes with the heels of his palms. He had sent Tess a message hours ago, urging her to investigate. Her reply had been dismissive, reassuring, and utterly infuriating.<\/p>\n\n\n\n

“I’ll check the logs again later. But I’m sure it’s nothing. Get some sleep, Remy. You look like you need it.”<\/em><\/p>\n\n\n\n

“Nothing,” Remy muttered to himself, his voice hoarse from disuse. “She thinks this is nothing.”<\/p>\n\n\n\n

He stared at the data one more time, his jaw tightening. He knew Tess. He had worked with her for over a year, acting as a relayer for the Sylva Bridge, submitting transaction proofs and earning tiny fees for his trouble. He respected her intelligence, her dedication, her ability to build something genuinely revolutionary.<\/p>\n\n\n\n

But he also knew her flaw: she trusted too much. She believed in the system she had built, in the validators she had chosen, in the cryptographic guarantees that made the bridge possible. She couldn’t see\u2014or wouldn’t see\u2014that the system was only as strong as its weakest link.<\/p>\n\n\n\n

And right now, that weakest link was screaming for attention.<\/p>\n\n\n\n

Remy stood up, stretching his aching limbs. His joints popped in protest. He grabbed his hoodie from the back of the chair, shrugged it on, and grabbed his portable data device.<\/p>\n\n\n\n

He needed to talk to Tess in person. He needed to make her understand.<\/p>\n\n\n\n

\n\n\n\n

The Sylva Bridge Command Hub was quiet when Remy arrived. Tess was alone, hunched over her holographic interface, her brow furrowed in concentration. The main display showed the usual visualization\u2014the golden sphere of Chain A, the silver orb of Chain B, the pulsing blue connection between them.<\/p>\n\n\n\n

She didn’t notice him at first. She was too focused on a transfer in progress, her fingers guiding the system through the lock-and-mint sequence.<\/p>\n\n\n\n

Remy watched her work for a moment, his frustration tempered by a flicker of admiration. Despite everything, Tess was brilliant. The bridge was a marvel of engineering, a seamless fusion of cryptography and smart contract logic that made cross-chain transactions feel as natural as breathing.<\/p>\n\n\n\n

But even brilliant engineers could be blind.<\/p>\n\n\n\n

He cleared his throat. “Tess.”<\/p>\n\n\n\n

She jumped, her hands flying up in surprise. The holographic interface flickered momentarily before stabilizing.<\/p>\n\n\n\n

“Remy!” she exclaimed, spinning around. “What are you doing here? I thought you were sleeping.”<\/p>\n\n\n\n

“I couldn’t sleep,” Remy said flatly. “Because I found something. Something you need to see.”<\/p>\n\n\n\n

Tess’s expression shifted from surprise to wariness. “Remy, if this is about the timestamp thing again\u2014”<\/p>\n\n\n\n

“It is,” he interrupted. “And it’s worse than I thought.”<\/p>\n\n\n\n

He strode toward her, his portable device already glowing with the data he had compiled. He projected it onto the main display, overlaying his findings on top of Tess’s visualization.<\/p>\n\n\n\n

“Look,” he said, pointing to a series of highlighted entries. “Four signatures from Validator #3 over the past two weeks. All signed during maintenance windows. All cryptographically valid. All impossible.”<\/p>\n\n\n\n

Tess frowned, studying the data. “I told you, it could be a synchronization glitch\u2014”<\/p>\n\n\n\n

“It’s not a glitch.” Remy’s voice was sharp, urgent. “I checked the network logs, Tess. I cross-referenced the signatures against the validator’s node activity. During each of these windows, Validator #3’s node was completely offline. No network traffic. No outbound connections. Nothing.”<\/p>\n\n\n\n

Tess’s frown deepened. “That doesn’t make sense. If the node was offline, how could it sign anything?”<\/p>\n\n\n\n

“Exactly,” Remy said. “It couldn’t. Which means someone else signed these messages using Validator #3’s private key.”<\/p>\n\n\n\n

The words hung in the air, heavy and ominous. Tess stared at the data, her face unreadable.<\/p>\n\n\n\n

“That’s impossible,” she said finally. “The private keys are stored in secure hardware modules. They’re air-gapped. They can’t be accessed remotely.”<\/p>\n\n\n\n

“They can if someone has physical access,” Remy countered. “Or if the validator’s operator was tricked into giving up their credentials. Phishing attacks happen. Social engineering happens. People make mistakes.”<\/p>\n\n\n\n

Tess shook her head, her expression hardening. “You don’t know that. You’re jumping to conclusions based on circumstantial evidence.”<\/p>\n\n\n\n

“I’m not jumping to anything,” Remy said, his voice rising. “I’m looking at the evidence and drawing the only logical conclusion. Validator #3’s private key has been compromised. Someone is using it to approve bridge transfers without the validator’s knowledge.”<\/p>\n\n\n\n

“Who?” Tess demanded. “Who would do that? And why?”<\/p>\n\n\n\n

“I don’t know who,” Remy admitted. “But I know why. Because the bridge holds millions of tokens in its pools. If someone can control just one validator key, they can start approving fraudulent transfers. They can drain the bridge.”<\/p>\n\n\n\n

Tess’s face went pale. “Remy, that’s a serious accusation. You’re accusing one of the Validator Council of either being compromised or being complicit.”<\/p>\n\n\n\n

“I’m not accusing anyone,” Remy said, forcing himself to calm down. “I’m presenting evidence. Four impossible signatures. Four red flags. If I’m wrong, great. We investigate, we find a technical explanation, and we move on. But if I’m right…” He trailed off, letting the implication sink in.<\/p>\n\n\n\n

Tess was silent for a long moment, her gaze fixed on the data display. Remy could see the gears turning in her head\u2014the careful weighing of evidence, the reluctant acknowledgment that maybe, just maybe, he had a point.<\/p>\n\n\n\n

Finally, she spoke. “Show me everything. Start from the beginning.”<\/p>\n\n\n\n

Remy nodded, relief washing through him. He pulled up his data streams, organizing them into a coherent timeline.<\/p>\n\n\n\n

“It started two weeks ago,” he began. “The first anomalous signature appeared during a scheduled maintenance window for Validator #3. I didn’t notice it at first\u2014I only caught it because I was running a routine audit of my relay logs.”<\/p>\n\n\n\n

He highlighted the first entry. “See this timestamp? It shows the signature being generated at 2:47 AM. But Validator #3’s node went offline at 2:00 AM for maintenance and didn’t come back online until 3:30 AM. That’s a ninety-minute window where the node was completely dead. No signing keys in operation.”<\/p>\n\n\n\n

Tess studied the data, her expression troubled. “Could the signature have been cached? Generated earlier and submitted later?”<\/p>\n\n\n\n

“I thought of that,” Remy said. “So I checked the validation time. The signature was validated by the network at 2:48 AM, one minute after the signature timestamp. That means it was generated, signed, and submitted all within a minute. You can’t cache that and submit it later without the network noticing the delay.”<\/p>\n\n\n\n

Tess nodded slowly, her jaw tight. “Okay. What about the others?”<\/p>\n\n\n\n

Remy expanded the data, showing three more entries. “Here’s the second one. Five days later. Another maintenance window. Another impossible signature. And here’s the third and fourth, both within the past three days. Whoever is doing this is getting more frequent.”<\/p>\n\n\n\n

Tess was silent, her eyes scanning the data. Remy watched her, waiting for her to say something, to acknowledge the gravity of the situation.<\/p>\n\n\n\n

Finally, she spoke, her voice barely above a whisper. “Four signatures. Four impossible approvals. If someone has been using Validator #3’s key, they could have approved any number of fraudulent transfers without anyone noticing.”<\/p>\n\n\n\n

“Exactly,” Remy said. “We need to freeze the bridge. Now. Before they strike again.”<\/p>\n\n\n\n

Tess shook her head. “I can’t freeze the bridge without a valid reason. The users would panic. The value of the bridge would plummet. And if I’m wrong\u2014if this is just a technical glitch\u2014I’d be destroying my reputation for nothing.”<\/p>\n\n\n\n

“Tess, listen to me.” Remy stepped closer, his voice urgent. “I know you don’t want to believe this. I know the bridge is your life’s work. But the evidence is clear. Someone is using Validator #3’s key. If we don’t act, the attackers will strike, and it will be too late.”<\/p>\n\n\n\n

Tess’s face was conflicted, a storm of emotions playing across her features. Remy could see the war within her\u2014pride versus caution, trust versus suspicion, the desire to protect her creation versus the fear that it was already compromised.<\/p>\n\n\n\n

“Let me run a full diagnostic,” she said finally. “I’ll check Validator #3’s activity logs, their network connections, their key usage history. If there’s any sign of compromise, I’ll find it.”<\/p>\n\n\n\n

“How long will that take?” Remy asked.<\/p>\n\n\n\n

“A few hours,” Tess said. “Maybe a day. I have to be thorough.”<\/p>\n\n\n\n

“A day,” Remy repeated, his voice flat. “Tess, we might not have a day. The attackers could strike at any moment.”<\/p>\n\n\n\n

Tess met his gaze, her own eyes hardening. “I understand the urgency, Remy. But I can’t act on suspicion alone. I need proof. Concrete, irrefutable proof. Give me the time to find it.”<\/p>\n\n\n\n

Remy wanted to argue, to shake her until she understood the danger. But he could see the resolve in her eyes, the stubborn refusal to accept disaster without verification.<\/p>\n\n\n\n

He sighed, running a hand through his tangled hair. “Fine. A day. But I’m going to monitor the bridge in real-time. If I see anything suspicious, I’m coming straight to you.”<\/p>\n\n\n\n

“Agreed,” Tess said. “And Remy… thank you. For bringing this to my attention. Even if it turns out to be nothing, I appreciate your vigilance.”<\/p>\n\n\n\n

Remy nodded, but his mind was already elsewhere. He was thinking about the attackers, whoever they were, and what they might be planning. He was thinking about the millions of tokens sitting in the bridge’s pools, waiting to be stolen.<\/p>\n\n\n\n

And he was thinking about the four impossible signatures, each one a ticking time bomb.<\/p>\n\n\n\n

\n\n\n\n

The next twelve hours were a blur of data analysis and anxious monitoring. Tess worked from the Command Hub, her fingers flying across her interface as she delved into Validator #3’s activity logs. Remy worked from his apartment, running his own diagnostics, watching the bridge’s transaction streams for any sign of attack.<\/p>\n\n\n\n

Neither of them slept.<\/p>\n\n\n\n

By evening, Tess had compiled a comprehensive report. She had traced Validator #3’s network activity, verified their key usage history, and cross-referenced every signature they had generated over the past month.<\/p>\n\n\n\n

And she had found nothing.<\/p>\n\n\n\n

On paper, Validator #3’s keys were pristine. The signatures were valid. The cryptographic proofs were flawless. There was no evidence of compromise, no indication that anyone else had accessed the private keys.<\/p>\n\n\n\n

Tess stared at her findings, a knot of confusion and frustration tightening in her chest. The data was clean. Too clean. It was as if the impossible signatures had never happened.<\/p>\n\n\n\n

But they had happened. She had seen them with her own eyes.<\/p>\n\n\n\n

She pulled up the anomalous entries again, studying them with renewed intensity. The signatures were valid. The timestamps were impossible. There was no technical explanation that could reconcile the two.<\/p>\n\n\n\n

Except one.<\/p>\n\n\n\n

Remy was right.<\/p>\n\n\n\n

She didn’t want to believe it. She had built the Sylva Bridge on trust\u2014trust in the validators, trust in the cryptography, trust in the system. Accepting that one of those validators had been compromised meant accepting that everything she had built was vulnerable.<\/p>\n\n\n\n

But the evidence was staring her in the face, impossible to ignore.<\/p>\n\n\n\n

Tess leaned back in her chair, her heart pounding. She needed to tell Remy. She needed to make a plan.<\/p>\n\n\n\n

She reached for her device, her fingers trembling, and sent a message: “Remy. Come to the Hub. I found something.”<\/em><\/p>\n\n\n\n

\n\n\n\n

Remy arrived within twenty minutes, breathless and tense. He burst into the Command Hub, his eyes wild with anticipation.<\/p>\n\n\n\n

“What did you find?” he demanded. “Is it proof?”<\/p>\n\n\n\n

Tess nodded slowly, her expression grim. “I ran a deep diagnostic on Validator #3’s key usage history. The signatures are valid, but the timestamps are impossible. There’s no technical explanation.”<\/p>\n\n\n\n

Remy’s face lit up with vindication. “So you believe me now? The key is compromised?”<\/p>\n\n\n\n

“I don’t know,” Tess admitted. “But I can’t rule it out. The evidence is too compelling to dismiss.”<\/p>\n\n\n\n

“Finally,” Remy breathed. “Okay. So what do we do now?”<\/p>\n\n\n\n

Tess took a deep breath, steeling herself. “First, we need to contact the Validator Council. We need to inform them of the potential compromise and request a full investigation.”<\/p>\n\n\n\n

Remy shook his head. “No. That’s a mistake. If the council is involved\u2014if one of them is behind this\u2014contacting them will only tip our hand.”<\/p>\n\n\n\n

“You’re suggesting we keep this secret?” Tess asked, incredulous.<\/p>\n\n\n\n

“I’m suggesting we investigate privately first,” Remy said. “We need to identify the source of the compromise before we involve anyone else. If the attackers are part of the council, they’ll try to cover their tracks.”<\/p>\n\n\n\n

Tess hesitated, her instincts warring with her logic. Every part of her wanted to follow protocol, to inform the council, to trust the system.<\/p>\n\n\n\n

But Remy’s words echoed in her mind: “Trust is a vulnerability.”<\/em><\/p>\n\n\n\n

“Okay,” she said finally. “We investigate first. But we need to be careful. If the attackers are monitoring the bridge, they might notice us poking around.”<\/p>\n\n\n\n

“Already taken care of,” Remy said, pulling out his portable device. “I’ve set up a secure channel that bypasses the bridge’s standard monitoring. We can communicate without anyone knowing.”<\/p>\n\n\n\n

Tess nodded, a grudging respect for Remy’s paranoia taking root. “Then let’s get to work.”<\/p>\n\n\n\n

\n\n\n\n

They spent the next several hours analyzing Validator #3’s activity history, looking for patterns, anomalies, anything that might indicate the source of the compromise.<\/p>\n\n\n\n

Remy focused on the network side, tracing connections and authentication logs. Tess focused on the human side\u2014the validator’s operator, their daily routines, their potential vulnerabilities.<\/p>\n\n\n\n

“This is a phishing attack,” Tess said finally, pointing to a specific entry in the logs. “Look at this. Three weeks ago, the operator accessed a suspicious link via their personal device. The link led to a fake login page that harvested their credentials.”<\/p>\n\n\n\n

Remy studied the entry, his eyes widening. “You’re right. The timing matches. Three weeks after that login, the first anomalous signature appeared.”<\/p>\n\n\n\n

“So the operator was compromised,” Tess said, her voice heavy with regret. “They fell for a phishing attack, and the attackers stole their private keys.”<\/p>\n\n\n\n

“Or copied them,” Remy corrected. “The operator might still have their original keys. The attackers have a shadow copy.”<\/p>\n\n\n\n

Tess closed her eyes, the weight of the realization settling on her shoulders. The bridge was compromised. The attackers had access to Validator #3’s keys, and they could use them to approve fraudulent transfers at any moment.<\/p>\n\n\n\n

“We need to freeze the bridge,” she said, her voice firm. “Now. Before they strike.”<\/p>\n\n\n\n

“I agree,” Remy said. “But we need to do it carefully. If we freeze the bridge abruptly, it’ll cause chaos. The users will panic, and the attackers might use the chaos to cover their tracks.”<\/p>\n\n\n\n

“Then what do you suggest?” Tess asked.<\/p>\n\n\n\n

Remy thought for a moment. “We freeze the bridge gradually. Slow down transaction processing, increase review times, and put all transfers through manual verification. It’ll look like a technical issue, not a security breach.”<\/p>\n\n\n\n

Tess nodded slowly. “It could work. But it’s risky. If the attackers figure out what we’re doing, they might accelerate their attack.”<\/p>\n\n\n\n

“Then we need to act fast,” Remy said. “We freeze the bridge, identify the compromised validators, and rotate them out before the attackers can strike.”<\/p>\n\n\n\n

Tess took a deep breath, her mind racing. The plan was risky, but it was the only option they had.<\/p>\n\n\n\n

“Okay,” she said. “Let’s do it.”<\/p>\n\n\n\n

\n\n\n\n

The next hour was a whirlwind of activity. Tess implemented the gradual freeze, slowing transaction processing and flagging all transfers for manual review. Remy monitored the network for any sign of attack, his eyes glued to his data streams.<\/p>\n\n\n\n

The bridge’s users started noticing immediately. The community chat exploded with questions and complaints.<\/p>\n\n\n\n

“Why is my transfer taking so long?”<\/em>
“Is there a problem with the bridge?”<\/em>
“I’ve been waiting for twenty minutes. What’s going on?”<\/em><\/p>\n\n\n\n

Tess answered as best she could, posting vague messages about “technical maintenance” and “scheduled upgrades.” It was a fragile lie, and she knew it. But she needed time\u2014time to identify the attackers, time to rotate the validators, time to save the bridge.<\/p>\n\n\n\n

Then the first alarm sounded.<\/p>\n\n\n\n

Remy’s head snapped up, his face pale. “Tess. We have a problem.”<\/p>\n\n\n\n

“What is it?” Tess asked, her heart racing.<\/p>\n\n\n\n

“Validator #3 just signed another transfer,” Remy said, pointing to his display. “It’s a massive one. They’re trying to drain the pooled assets on Chain A.”<\/p>\n\n\n\n

Tess’s blood ran cold. She pulled up the transfer details, her eyes scanning the numbers.<\/p>\n\n\n\n

Transfer ID:<\/strong> #84903-X
Source:<\/strong> Chain A (Pooled Assets)
Destination:<\/strong> Unknown Wallet
Amount:<\/strong> 1,847,320 tokens<\/p>\n\n\n\n

All of it. The attackers were trying to drain the entire bridge.<\/p>\n\n\n\n

“Stop it,” Tess said, her voice a strangled cry. “Freeze the bridge. Now!”<\/p>\n\n\n\n

“I can’t,” Remy said, his voice shaking. “The transfer already has seven signatures. It’s going through.”<\/p>\n\n\n\n

Tess stared at the display, helpless, as the bridge’s pooled assets began to flow out of Chain A, disappearing into an unknown wallet on a different chain.<\/p>\n\n\n\n

1,847,320 tokens. Gone.<\/p>\n\n\n\n

The bridge was empty.<\/p>\n\n\n\n

The community chat exploded with panic. Users were screaming, demanding answers, blaming Tess for the disaster. The messages scrolled past faster than she could read, a torrent of anger and fear and despair.<\/p>\n\n\n\n

Tess felt the world tilt around her. Her masterpiece, her life’s work, was gone. The bridge she had built and nurtured and protected was empty.<\/p>\n\n\n\n

And it was her fault. She should have listened to Remy. She should have acted faster. She should have frozen the bridge the moment she saw the first anomaly.<\/p>\n\n\n\n

But she didn’t. She had trusted the system, trusted the validators, trusted the cryptography.<\/p>\n\n\n\n

And now she had nothing.<\/p>\n\n\n\n

Table of contents:<\/em><\/strong>
Introduction<\/a>
Chapter 1: The Connecting Chain<\/a>
Chapter 2: A Trustless Bridge<\/a>
Chapter 3: The Validator’s Keys<\/a> <<<<<< NEXT<\/strong>
Chapter 4: The Relayed Message<\/a>
Chapter 5: The Hacked Oracle<\/a>
Chapter 6: The Bridge Drain<\/a>
Chapter 7: The Forensic Audit<\/a>
Chapter 8: The Rotating Validator Set<\/a>
Chapter 9: The Decentralized Bridge Network<\/a>
Chapter 10: Interconnected, Not Interdependent<\/a><\/p>\n

<\/div>

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

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

The morning light crept through the grime-caked windows of Remy’s apartment, casting pale yellow streaks […]<\/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,61493,61494,61495,61496,61497,61499,61498,61500,61502,61501,61491,61492,60295,60333,60335,60334,60297,60296,60336,61226,61227,61229,61228,61231,61230,61232,60330,60331],"class_list":["post-61411","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-free-children-novel","tag-free-crypto-story","tag-free-cryptocurrency-story","tag-free-science-fiction","tag-free-science-fiction-novel","tag-free-science-fiction-novel-for-children","tag-free-science-fiction-novel-for-young-adult","tag-free-science-fiction-story","tag-free-science-fiction-story-for-children","tag-free-science-fiction-story-for-young-adult","tag-free-ya-novel","tag-free-young-adult-novel","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-bridge-collapse","tag-the-bridge-collapse-science-fiction-novel","tag-the-bridge-collapse-science-fiction-novel-for-children","tag-the-bridge-collapse-science-fiction-novel-for-young-adult","tag-the-bridge-collapse-science-fiction-story","tag-the-bridge-collapse-science-fiction-story-for-children","tag-the-bridge-collapse-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\/61411","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=61411"}],"version-history":[{"count":2,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/posts\/61411\/revisions"}],"predecessor-version":[{"id":61449,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/posts\/61411\/revisions\/61449"}],"wp:attachment":[{"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/media?parent=61411"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/categories?post=61411"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nightfame.com\/style\/wp-json\/wp\/v2\/tags?post=61411"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}