# $RLC Catalyst Posts & Social Intelligence Recap — July 30, 2026 > **Asset:** $RLC > **Date:** 2026-07-30 (July 30, 2026) > **Canonical URL:** https://cryptitalk.com/tokens/rlc/2026-07-30 > **Token Profile:** https://cryptitalk.com/tokens/rlc.md > **Market Rankings:** https://cryptitalk.com/rankings.md --- ## Curated Viral Posts & Community Evidence ### Post #1 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 5 likes · 2 retweets · 1 comments · 782 views > **Posted:** 2026-07-30T08:00:06+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082737987872542817](https://x.com/iEx_ec/status/2082737987872542817) > **Visual Note:** A promotional graphic featuring a yellow hardhat with the Ethereum logo next to the text 'Nox Protocol', with the tagline 'Run the full Nox stack locally, test end-to-end, right inside Hardhat.' and 'Powered by iExec' at the bottom. > > "Confidential smart contracts, in Hardhat. Nox now ships with a native @HardhatHQ 3 plugin. One install. Three line config. Your usual test command spins up the whole confidential stack. Same Solidity you already write. Now confidential. docs.noxprotocol.io" ### Post #2 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 1 likes · 0 retweets · 1 comments · 778 views > **Posted:** 2026-07-30T12:32:13+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082806467816530276](https://x.com/iEx_ec/status/2082806467816530276) > > "It's going to be a great day !" ### Post #3 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 5 likes · 0 retweets · 3 comments · 698 views > **Posted:** 2026-07-30T12:30:03+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082805923136082031](https://x.com/iEx_ec/status/2082805923136082031) > **Visual Note:** A diagram titled "Inside a TDX quote" showing the three key fields—report_data (64-byte challenge), RTMR[0..3] (measurement registers), and event logs (replay RTMR3)—that Nox relies on, with the post emphasizing RTMR3's role in tying the quote to the app-id, os_image_hash, and compose-hash of the running workload. > > "Every TDX quote contains four RTMR registers. Each attests something different about the running workload. For Nox, one of them does most of the heavy lifting: RTMR3. Here's why it matters" ### Post #4 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 2 likes · 0 retweets · 1 comments · 110 views > **Posted:** 2026-07-30T12:46:49+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082810141246738607](https://x.com/iEx_ec/status/2082810141246738607) > > "Super cool ! Even cooler if the USDC were encrypted and private" ### Post #5 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 0 likes · 0 retweets · 1 comments · 74 views > **Posted:** 2026-07-30T12:30:07+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082805940198502628](https://x.com/iEx_ec/status/2082805940198502628) > **Visual Note:** A sequence diagram illustrating the attestation process between a User, Runtime Attestation UI (now attestation-perm), a new comp-aggregator (GET /certs), a new comp-supervisor (GET /certs), TDX Machine (drm-stash, tdx-parallel), distroless vmctx (bootd), and CNA quote-service (new per CNA). The diagram shows steps like generating a quote, posting to /dcap, fetching PCR data, retrying on errors, and merging instance IDs, ultimately producing a boot chain integrity verification result that aligns with the description of RTMR0-2 recording firmware, kernel, and kernel config while RTMR3 records application-specific measurements. > > "RTMR0-2 handle boot chain integrity: firmware, kernel, kernel config. RTMR3 records application-specific measurements: app-id, os_image_hash, compose-hash, instance-id, key-provider. These are the fingerprints of the exact code running inside the Trust Domain. Here's how we" ### Post #6 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 0 likes · 0 retweets · 0 comments · 36 views > **Posted:** 2026-07-30T12:31:56+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082806399008993730](https://x.com/iEx_ec/status/2082806399008993730) > > "@ethereum is for builders. Eth is Home" ### Post #7 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 0 likes · 0 retweets · 0 comments · 12 views > **Posted:** 2026-07-30T09:34:19+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082761700206354644](https://x.com/iEx_ec/status/2082761700206354644) > > "Privacy that SHOULD work for regulators" ### Post #8 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 0 likes · 0 retweets · 0 comments · 11 views > **Posted:** 2026-07-30T12:32:40+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082806583004647565](https://x.com/iEx_ec/status/2082806583004647565) > > "Come through to the community hub" ### Post #9 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 0 likes · 0 retweets · 0 comments · 11 views > **Posted:** 2026-07-30T09:34:46+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082761811313451171](https://x.com/iEx_ec/status/2082761811313451171) > > "Most people don’t realise it untill it’s too late" ### Post #10 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 0 likes · 0 retweets · 0 comments · 9 views > **Posted:** 2026-07-30T12:47:58+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082810430473334981](https://x.com/iEx_ec/status/2082810430473334981) > > "Thanks for covering us !" ### Post #11 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 0 likes · 0 retweets · 0 comments · 8 views > **Posted:** 2026-07-30T09:33:16+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082761433180192830](https://x.com/iEx_ec/status/2082761433180192830) > > "Man’s just rotating crashed companies" ### Post #12 by @iEx_ec > **Author:** iExec RLC ([@iEx_ec](https://x.com/iEx_ec)) > **Metrics:** 0 likes · 0 retweets · 0 comments · 7 views > **Posted:** 2026-07-30T12:30:10+00:00 > **Source Link:** [https://x.com/iEx_ec/status/2082805952634638546](https://x.com/iEx_ec/status/2082805952634638546) > > "Why it's the register we focus on: Because verifying RTMR3 is what ties an attestation to a specific Nox component and its docker compose. Boot integrity says the environment is legit. RTMR3 says the workload is Nox. Both are needed. Chain of Trust delivers both." --- *Generated by Context Pilot Social Intelligence Engine.*