penumbra

Penumbra is now supported as a destination on Noble Express, with full account and ephemeral address support

Penumbra is now supported as a destination on Noble Express, with full account and ephemeral address support

UM is now live on Keplr Wallet

UM is now live on Keplr Wallet

Join the penumbra Discord Server! Check out the penumbra community on Discord - hang out with 70308 other members and enjoy free voice and text chat.

Join our Discord server here: discord.gg/penumbrazone

Penumbra's 2nd community call would be held this Thursday, 1pm ET, on Discord.

Hear directly from the Penumbra Labs team on the work that is being done on the protocol, alongside other exciting updates.

it just keeps getting better

why does privacy matter to you?

the glorious future is here, now

the way it should always have been built

built-in privacy by default

no tracking, no cookies, no forced data consent

shield, swap, LP, stake, marketmake

defi on stealth mode

privacy
|
penumbra

Penumbra Labs will also be at the Shielding Summit to give a product demo as well as connect with fellow builders looking to learn more about utilising Penumbra

Parallel Society Congress | Shaping the Future of Human Governance In a swiftly evolving world, our conventional understanding of the nation state is increasingly challenged. Join global thought leaders, passionate founders and builders to design humanity’s future th...

Catch Penumbra's founder, Henry, at both Parallel Society Congress (psc.logos.co) and Shielding Summit (shieldingsummit.org)

Penumbra will be at Devcon

Penumbra is now live on mainnet: penumbra.zone

hello world

To test it out, install the extension, use the Discord faucet to request testnet tokens, and let us know what's broken in the web-ext-feedback channel!

And, because the extension performs local indexing, most RPC requests are processed locally, so the demands on fullnodes are lightweight.

To support decentralization, our goal is that any `pd` node should be able to serve a frontend, out-of-the-box, with no configuration.

This design means that spending or viewing keys never leave the extension, so users can grant viewing permissions to web interfaces and revoke them later, and see exactly what they're authorizing before they approve.

These services are first-class interfaces used throughout the Penumbra ecosystem.

For the web, we provide them through a browser extension, using a custom transport object allowing frontend code to make GRPC requests to the extension the same way it would call a remote server.

The Custody service handles auth requests, allowing the user to review and authorize a TransactionPlan describing a proposed transaction, and returning a bundle of auth data needed to build the transaction.

The View service is a personal indexer, providing read access to all private data visible to a given wallet. It scans for relevant transactions, downloads them, and decrypts and indexes them locally.

Our approach to solving this problem is to provide a "local RPC" in a browser extension that restores the programming model for frontends for transparent chains.

We define two GRPC services, for "read" and "write":

We need to rethink data management because privacy means no centralized server with access to all of a user's data. So we have to think holistically about how the protocol reaches all the way out to end-user devices.

Privacy forces us to build a truly decentralized system.

Frontends can operate on pre-interpreted views that show exactly what data is visible and what is opaque.

To do this, we've built first-class modeling of data visibility through the entire transaction lifecycle, which you can read about here:

penumbra.zone/blog/how-to-...

We need to rethink data modeling because introducing privacy -- control over information disclosure -- requires being able to model what information is visible to whom. We need to show users what they see and what others see.

Shielded chains achieve privacy by moving end-user data off the chain and onto end-user devices, and that means those end-user devices must be responsible for scanning and processing that data.

This requires rethinking both data modeling and data management.