Encrypted Finance

Executed the first private transfer on @FlareNetworks testnet powered by TEE (one of the firsts) both sender and receiver are hidden alongside the amount, just the token shows and our platform relayer wallet which submits all transactions That’s the transaction info which no one can find Onchain. Sender: 0xdb4034fA3829B488eFc1FC0f01F5F1Af722562Df Recipient: 0x0F5ddCFA6b2BbD7E24f8B98a3634273A4B5a834C Amount: 2.000000 FXRP We also successfully compute the users balance locally Tx : coston2-explorer.flare.network/tx/0x7f8376e02…

@EncryptedFi web wallet is looking amazing right now. With just a few more additions, the public will be able to transact privately here. Privacy ☀️☀️☀️☀️on @FlareNetworks

@KeneEzeala @FlareNetworks Full stack privacy on flare is looking good

@FlareDevHub @FlareNetworks @HugoPhilion Definitely, our technical docs would be built for techies only. 😅

@EncryptedFi @FlareNetworks @HugoPhilion Make sure to highlight how you are using Flare's stack behind the scenes 🙌

Encrypted Finance’s web wallet is looking amazing right now… just a few more additions, and the public will be able to transact privately here. 😊 The features available at launch include confidential balances, confidential transfers, confidential swaps, and confidential lending (with many more to come). We’ll also be publishing our developer SDK, making it easier for any developer who wants to build in the private DeFi direction for the Flare Summer Signal Hackathon to integrate privacy into their stack in just a few lines of code. Stay tuned for more information regarding the release date.

We are a step away from encrypted finance on coston2 🤗😊

It’s a new month, and Encrypted Finance’s CTO is celebrating another year 🎂 Here’s an encrypted birthday wish for the technical team: 01001000 01100001 01110000 01110000 01111001 00100000 01000010 01101001 01110010 01110100 01101000 01100100 01100001 01111001 Only the tech team can claim they decoded that instantly. Happy Birthday to our CTO. Wishing you many more years of impact, innovation, and success.

Projects like @EncryptedFi are building on Flare Confidential Compute (FCC) to bring confidential finance to Flare, allowing users to interact with DeFi while keeping sensitive financial data private, instead of exposing it to the entire world. Public blockchains don’t have to mean public data. The future isn’t just decentralized. It’s confidential, verifiable, and on-chain. Docs: encrypted.finance Current Price: $0.00667 flare-networks:native #Flare #FLR #XRPFi #eFXRP #ConfidentialCompute #DeFi #Web3

Most blockchains expose your transaction data to everyone. Flare Confidential Compute changes that. 🔒 by @FlareNetworks Sensitive transaction data is processed inside a Trusted Execution Environment (TEE), so validators, MEV bots, and blockchain observers can’t see the plaintext while the computation remains verifiable.💎 This unlocks a new era of on-chain privacy for DeFi, AI, and real-world financial applications. 🚀 Want to see it in action? Check out @EncryptedFi, which is building confidential financial applications powered by Flare Confidential Compute. Their website: encrypted.finance flare-networks:native ripple:native Privacy 🤝 Verifiability. #Flare #ConfidentialCompute #EncryptedFinance #Web3 #DeFi #USDT0

Real soon you would put your private XRP to work 😊

@TheGrungieNFTs @FlareNetworks We should give you early access already 👀

No more would this happen on public chains starting with @FlareNetworks

We've seen a lot of talk around onchain privacy these past months. Most projects ship confidential transfers or a mixer and stop there. That works, but it leaves a lot untouched. At Encrypted Finance, we spent months working on something that goes further. CONFIDENTIAL DEFI, where your swaps, lending, and staking stay private without locking you out of real functionality. We're demoing to the Flare DevRel team on the last Friday of this month. Right after that, we're opening things up to the community. You'll get to see what we've been building, try it, and share honest feedback. Looking forward to it.

@maddeningsmart 👀

@EncryptedFi Bring it onn🤔

Who would like to test Encrypted Finance with us 👀

Why Flare Confidential Compute is the foundation of private DeFi on Flare, and why Encrypted Finance is built on it. Privacy on chain is one of the hardest problems in the space. There are many beautiful approaches being researched and shipped today. Zero knowledge, fully homomorphic encryption, secure multi party computation, ring signatures, and confidential compute are all valid paths, and the ecosystem is better for having all of them. Different chains have different strengths, and the right privacy primitive is the one that matches what the chain natively offers. For our Flare deployment we chose Flare Confidential Compute because of what it lets us build for users today, on a live L1, at production scale. FCC runs the privacy critical code inside attested Trusted Execution Environments. The TEE is a sealed enclave on the CPU itself. Only the code that matches the published attestation hash can ever decrypt the data inside. The chain knows which TEE versions are valid. The chain knows which machines are currently attested. The chain enforces a quorum of these machines for every privileged action. This is part of the consensus surface, not bolted on infrastructure. That is what makes Flare uniquely powerful for private DeFi. The primitive is already there, ready to use. When you wrap a token with Encrypted Finance, your real address pays into our vault and an encrypted note is emitted on chain. That note is a ciphertext that only you can decrypt. The chain sees a commitment hash. Nothing else. When you act on that note, you sign an EIP 712 instruction and hand it to the FCC dispatcher. The dispatcher fans your instruction out to a quorum of attested TEEs. They must agree on the resulting state transition before anything touches the chain. No single TEE can move your funds. No single operator can collude their way to your balance. The math of the quorum is what protects you. Inside the enclave we run the actual privacy logic. We decrypt your note. We verify the commitment matches what is on chain. We construct the new note. We sign the resulting on chain call. The enclave then forgets everything. Your spending key never touches our servers in cleartext, and never will. Flare ships FCC as a first class primitive. The infrastructure is already deployed and live. We do not have to ask permission to run TEEs. We do not have to spin up our own attestation server. We do not have to invent a quorum scheme. The chain already has one. That is a year of infrastructure work we did not have to do, and it lets us focus on the part that matters. Building actual private financial primitives. Beta lands on Coston2 soon.

Welcome to the team @KeneEzeala 🫡

@GOTXRP @XRPapiCrypto For the team yes, opening it to the public soon

@EncryptedFi @XRPapiCrypto Is this in testing in coston2?

🫡

@FlareNetworks June looks good 😊

@EncryptedFi Hi June, welcome to Flare

Welcome To June Everyone

Don’t wanna share to much info but June looks great 👀