Hugo Philion

Cofounder of @flarenetworks.

[Hugo Philion @HugoPhilion]

Almost all future usecases of the blockchain (AI, Gaming, Identity, Real World Assets etc) will require some amount of external data attested onto chain. Decentralisation (without it there is no safety), scalability and low latency are key. Flare is the blockchain for data. #connecteverything

[Flare ☀️ @FlareNetworks]

Flare Summer Signal: Office Hours https://t.co/7QJM2KOFxr

[XRPL Commons @xrpl_commons]

https://t.co/YO3bbYiDmQ

[Flare Devs @FlareDevHub]

Flare Summer Signal: Office Hours https://t.co/n4HEDXSNSc

[Quantic @0xQuantic]

A lot of energy has gone into growing and sustaining the TVL Flare has built over the past few months.

That is great. The chain needed it, and there is still room for it to keep growing.

But it is worth keeping in mind that under FIP.16, incentives are broader than TVL alone.

Overall ecosystem activity matters too: attestations, transaction fees, usage, and the real demand generated across the network all count.

[Flare Devs @FlareDevHub]

AI systems often depend on private inputs, prompts, user data, API keys, model logic, scoring rules, or agent workflows that cannot be exposed publicly.

Flare Confidential Compute gives developers a way to run that logic off-chain in a more controlled environment, while still making the output usable by blockchain applications.

[Flare ☀️ @FlareNetworks]

Same pattern for money markets. Borrow/lend terms stay private in TEEs; only solvency and risk proofs hit-chain.

PMWs handle cross-chain execution when collateral or settlement lives elsewhere.

[Flare ☀️ @FlareNetworks]

Building on Flare?

You'll want to tune into this X space and play it back ☀️

[Flare Japan Community🇯🇵☀️ @flarejapangroup]

Flare主催のサイドイベントの登録が順調に増えてきています！

ウォレットパートナーさんと共同開催なので、ハードウェアウォレットも実物見れたりしますよ！(Xamanはアプリです)

FlareがXRPにどんな選択肢を提供できるのか？ぜひお気軽に見に来てください👀

参加登録は👇️

[Flare Devs @FlareDevHub]

https://t.co/TF8l7xblGA

[zerolore @zerolore]

I have to admit, it’s been pretty cool watching crosschain activity pick back up after the challenges of Q1 and Q2.

@USDT0_to alone:

- Yesterday was the highest volume day since April: $221M
- Third consecutive week of growing weekly volume
- Crossed $100B in total volume moved
- $854M moved in the last 7 days

The headlines come and go. The infrastructure people actually rely and build on stay. Higher.

[Hugo Philion @HugoPhilion]

@Zedzies Being ill informed hasn’t stopped you from commenting before so I suppose it’s no surprise that you have chosen again to make another comment that has no basis in reality.

[Hugo Philion @HugoPhilion]

We aren’t going after their price oracles. I’m not going to say anything more on this subject. You can watch instead.

[👑 𝕂𝕚𝕟𝕘 𝕂𝕒𝕣𝕒𝕟 👑 @KingKaranCrypto]

Chainlink Community Liaison Zach Rynes wishes @FlareNetworks good luck in its mission to eat Chainlink's lunch and become the leading oracle network.

Let the battle of the oracles begin.. 🤝

[G will❤️‍🔥 @Big14teru]

Confidential by default, verifiable by anyone.

That is the FCC thesis and it is how Torch already runs.

The key that signs every fill was generated inside an Intel TDX enclave and has never existed outside it.

Not even I have seen it.

You verify it, not trust it: the enclave publishes its executor address and the vault on the explorer points at the same one.

[Flare ☀️ @FlareNetworks]

Public coordination on Flare. Private execution in the TEE.

Users and smart contracts start the flow; relayers augment and sign; the TEE verifies, runs logic, and signs back.

That's the Flare Confidential Compute flow.

[Flare Devs @FlareDevHub]

Reminder for builders: two useful Flare Summer Signal sessions this week.

📆 Thursday, July 9 at 1 PM UTC:
Shipping on Flare: Builders & Infrastructure

Live conversation with @ankr and @TenderlyApp on the tooling, infra, and support available to help you move from idea to working product.

📆 Friday, July 10 at 1 PM UTC:
Flare Summer Signal Office Hours

Bring your product idea, technical blocker, architecture question, or half-built project. Mentors and builders will be there to help you move forward.

Useful week to show up, ask questions, and ship better!

- Spaces: https://t.co/Lo8sGOvtQM

- Office Hours: https://t.co/hWvqi6kztv

[Quantic @0xQuantic]

This would actually work:

Stake capital + prove real affiliation/credentials + accept slashing conditions for abuse.

That creates an onchain trust layer where badges are backed by verified claims and real economic accountability.

With FDC, external data from Web2 sources or other chains can be attested on Flare and made usable by smart contracts.

With FCC, the credential proof can go further: users can prove they meet certain conditions privately, without exposing sensitive personal data.

The result is a decentralized, verifiable, and optionally private affiliation system.

Very practical approach to reducing impersonation.

[Hugo Philion @HugoPhilion]

The impersonation problems on https://t.co/5UASHKU2Cb are so bad it gives me an idea:

Start an X organisation.
Allow people to stake some amount of money - say $25k
Use the FDC and conventional means to prove credentials.
This allows you to receive an affiliate badge on X.

Lose the stake via a governance process that votes on wrongdoing.

Imperfect but it’s got to be better than what we have today.

[Hugo Philion @HugoPhilion]

Another fake but verified Firelight account @nikitabier

[Firelight @Firelightfi]

Firelight is not launching a token at this time.

This is the only official Firelight account on X.

⚠️ Verify announcements on our channels, and be cautious of impersonators, phishing links, and other scams.

[Flare ☀️ @FlareNetworks]

FCC didn’t appear overnight.

Research began in 2024. Architecture was published with the Flare 2.0 vision in March 2025.

Now it’s ready for its first real deployment on Songbird.

It’s arriving at a time when the market is increasingly asking for confidentiality + verifiability together.

This is infrastructure for the next stage of on-chain finance.