Story code: ST-001181
Part 3: The Cryptographic Trace
The file on my terminal screen resolved into a clean, two-column database sheet. The left side displayed the cryptographic transaction ID of the redirected donation wallet; the right side listed the device authorization token. On the main chapel wall, Arthur’s frozen avatar remained locked in place, its digital hands outstretched in a halted gesture of accusation. The chat feed on the side monitor continued to scroll, though the speed of the incoming messages had slowed as family members waited for a response. Several remote users began typing questions about why the feed had suddenly stopped moving.
“Marcus,” Sarah said from the stage. She did not look at the camera now. She looked directly up at the tinted glass of my control booth. Her knuckles were still white around the plastic strap of her headset, but she remained motionless, her chest rising and falling in shallow, rapid breaths. “Can you reset the feed?”
“The feed is active,” I said into the local booth microphone, my voice level and dry. “I have locked the session termination command from user Arthur’s terminal.”
“This is illegal!” Arthur’s voice crackled through the audio monitor, his tone rising in pitch. The audio meter on my console bounced into the yellow zone, the indicator lights flashing rapidly. “You have no right to hold my connection. I am exiting the memorial. Sarah, you’re using your hired tech staff to cover this up because you know you’re guilty.”
I did not answer him. I opened the cryptographic key registration panel for the VR Memorial Link. Every user who registered to join the virtual lobby had to verify their identity through a two-factor token sent to a mobile device. The system log monitor tracked these registrations to prevent unauthorized access and maintain security.
I dragged the device authorization token from the diverted transaction log into the search field of the registration database. The system ran the comparison, the green status wheel spinning on my screen. In less than three seconds, the registration data for the token populated the system log monitor. The wallet that had received the family donations was registered under the recovery email address arthur.v.1968@familymail.com and matched the mobile number ending in 4491. Both belonged to the remote account currently broadcasting Arthur’s avatar.
On the chat monitor, a message from an aunt in Chicago appeared: “Why is Arthur frozen? Sarah, answer the question about the ledger. We deserve to know where the money went.”
Arthur’s avatar flickered again, the digital rendering straining against the administrator lock. “Unmute my controls, technician. I’m calling the police if you don’t release my device link right now. You are interfering with a family service.”
His voice carried a slight tremor that had not been there when he first interrupted the service. I moved my mouse cursor to the “Broadcast to Stream” button on the administrative console. If I clicked it, the raw verification log-including the matching email, phone digits, and device MAC address-would overlay the main video feed, replacing Arthur’s avatar with the system’s unalterable audit trail. Sarah took one step back from the camera, her eyes fixed on the blank projection screen behind her. Her hands had stopped shaking, but her fingers remained clenched into fists at her sides. The chapel was completely silent except for the faint hum of the server rack beneath my desk. My finger hovered over the mouse button, waiting for the final validation check to clear.