bougainvilleCrowdmuse: Turning creations into connections
The drop platform with the potential to become the go-to launchpad for creators worldwide.
bougainvilleAbstract: A collegial Layer 2 for consumer crypto
The most hyped chain abstraction actor is about to enter the arena. Is this the final frontier?
bougainvilleRhinestone: The marketplace Web3 builders need
Rhinestone raised $5 million in seed funding led by 1kx, with further support from CoinFund, Lattice, Heartcore, Circle Ventures and others.
bougainvilleCrowdmuse: Turning creations into connections
The drop platform with the potential to become the go-to launchpad for creators worldwide.
bougainvilleAbstract: A collegial Layer 2 for consumer crypto
The most hyped chain abstraction actor is about to enter the arena. Is this the final frontier?
bougainvilleRhinestone: The marketplace Web3 builders need
Rhinestone raised $5 million in seed funding led by 1kx, with further support from CoinFund, Lattice, Heartcore, Circle Ventures and others.
Subscribe to bougainville
Subscribe to bougainville
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
In this post, we will dive into Peanut Protocol's unique value proposition and why I think it could have a tangible impact on payments as a protocol for generational trust.
You don't stumble often on a company with such a straightforward yet revolutionary vision. Peanut Protocol primary mission is alleviating all the hassles and risks surrounding crypto transfers to become the evolution of a Stripe or Cash.app. I see it as the equivalent of a Venmo for the Web3 world.
The most pressing issues Peanut is solving are:
Complex wallet address management and associated security risks
Necessity for test transactions before significant transfers
Chain-specific considerations that confuse users
Lack of intuitive, consumer-friendly interfaces
Many actors have pushed for account abstraction, which is now mainstream thanks to Privy, Rhinestone (see my article here), or Abstract. However, the space lacks a user-friendly and intuitive way to send funds without worrying about and performing test transactions. Character-sensitive transfers are things of the past. It is time to revamp them with familiar yet powerful tools that move from Account Abstraction to Address Abstraction.
What's more familiar in Web2 than a URL? It is accepted as the ID for any website you want to visit, or you want your friend to visit by sharing it. You know some URLs are sketchy, and you have learned to (most of the time) detect those.
So few things are more familiar than a link in our Web2 world; hence, piggybacking on this architecture seemed the most straightforward yet elegant way to create a cross-border payment system for Konrad and Hugo. People talk about generational wealth, but I'd like to think of a better, more enthralling goal: generational trust. Generational trust will specifically make sense in a multi-AI agent world where trust will matter more than anything else, and the number of transactions will undeniably explode.
Their innovation lies in three key areas:
Trustless Architecture: The protocol operates on a fully trustless, non-custodial model. Funds are secured in smart contracts and can only be accessed with a secret embedded in the Peanut link. This maintains the core ethos of cryptocurrency, self-custody, while dramatically simplifying the user experience.
Link-Based Transfer System: Instead of dealing with wallet addresses, users share a simple link. This link contains all the necessary information for fund retrieval, eliminating the need for complex wallet interactions.
Security-First Design: The protocol implements a sophisticated security model where:
All link information remains local to the browser session
The frontend app is completely open-source
Smart contracts are permissionless and independently auditable
A 24-hour safety window allows link creators to withdraw funds if needed
The basic primitive of Peanut Protocol is a cryptographically secure smart contract that relies on an offchain message, usually shared in a link or QR code. The protocol holds the deposited token from the sender and can only be unlocked by a secret. This has a simple workflow. First, the sender deposits tokens to the vault smart contract, then Peanut send the URL to their recipient, and finally the recipient withdraws the funds with the secret within the URL.
There are several options for creating a link:
Peanut App
SDK
An integration (e.g. wallet or app)
Smart contract
To do so, go to the Peanut Send Page and start imputing the amount you want to send.
Once you connect your wallet and sign the transaction, the asset and the public key will be stored in the Peanut smart contract. Then, a unique link will be created along with a deposit on the Peanut Vault.
The sender part is done. Note that all the links are in the same format:
/https://peanut.to/claim?c=CHAIN&i=INDEX&v=VERSION&p=KEYThere is nothing to do on the receiver end but hit the claim button. Note that it is gasless for the receiver. Just one click, and you're good.
Here are the core features they are focusing on at the moment and a few use cases:
Address Abstraction: No need to use wallet addresses or ENS names. They let you send and request funds via links/QRs which and it can be shared via email, WhatsApp, Telegram, in IRL.
You are in charge of a group payment.
In a group chat on Telegram discussing a gift for a colleague, one person offers to organize the funds. Instead of requesting crypto wallet addresses or sending an awkward ENS name, they generate a Peanut link.
The link is shared in the group chat, and everyone can contribute directly in a few clicks.
Chain-Abstracted Payments: Payments work across different blockchains. For example, you can send $1,000 on Optimism, and the recipient can receive it on Arbitrum.
Stablecoin-Abstracted Payments: They allow for flexible stablecoin conversions. You can send 1,000 USDT, and the recipient can receive 1,000 USDC.
Fiat/Crypto Abstracted Payments: Peanut introduces Ethereum’s first self-custodial offramp. You can send USDC, and the recipient can claim it as USD directly from their bank account without ever needing to touch the crypto or create a wallet.
You hire a freelancer from another country to work on a project.
Instead of using platforms that charge high fees for currency conversion and payouts, you pay the freelancer in USDC via Peanut.
The freelancer receives a payment link and claims the funds in their local bank account, bypassing the need to interact with cryptocurrencies directly.
There is one space in which I am incredibly excited to see the Peanut team in action: e-commerce.
One can imagine a world where merchants can generate payment links on the fly, enabling crypto payments without wallet integration or address management complexity. Every time a purchase is made online, the merchant can give some cash back through a link as a crypto or fiat payment. On the other hand, satisfied customers can send some payment as a tip to a merchant. As counterintuitive as it sounds, if you think deeply about the future of e-commerce, we could see the emergence of microtransactions, such as tipping a merchant online for the quality of its goods, or even crypto crowdfunding, such as the one that already occurs on Crowdmuse (our next article).
While innovative, the protocol could raise some concerns:
Link Security: The self-contained nature of Peanut Links means they must be treated with the same security as private keys. Anyone with access to the link can claim the funds.
Withdrawal Window: While the 24-hour withdrawal window provides safety, it could also create uncertainty for recipients. Users must understand that link receipt doesn't guarantee fund availability until the window expires.
The first aspect is probably the most crucial to address (the team could easily circumvent the second). How can we deter security breaches to ensure users aren't afraid of sharing links since they contain the private key?
My suggestion would be to implement on-chain verification mechanisms. Here’s how it could work:
When a user receives funds, and before claiming them, a smart contract could retrieve the recipient's X, WhatsApp, or Telegram account and verify if it matches the account specified by the sender. Conditional triggers, managed either by a smart contract or an AI agent governing the contract, could streamline the process and enhance the security of these smart links through proof of ownership or digital identity verification.
Peanut Protocol abstracts away the intimidating complexity of Web3 payments, using familiar elements like URLs and QR codes.
This evolution could dismantle ossified monopolies in the global payment sector, opening the door for individuals and small businesses to thrive without exorbitant fees or barriers, a world where Remitly or Western Union are obsolete and where context-aware microtransactions are trivial.
Peanut isn’t just solving today’s payment challenges; it’s building the infrastructure for a frictionless, interconnected economy, and I am excited to see the team empowering the fundamental layer of payment and trustless collaboration at a scale we’ve yet to imagine
For more details about Peanut Protocol, visit their official site Peanut.to or the Peanut Notion here.
In this post, we will dive into Peanut Protocol's unique value proposition and why I think it could have a tangible impact on payments as a protocol for generational trust.
You don't stumble often on a company with such a straightforward yet revolutionary vision. Peanut Protocol primary mission is alleviating all the hassles and risks surrounding crypto transfers to become the evolution of a Stripe or Cash.app. I see it as the equivalent of a Venmo for the Web3 world.
The most pressing issues Peanut is solving are:
Complex wallet address management and associated security risks
Necessity for test transactions before significant transfers
Chain-specific considerations that confuse users
Lack of intuitive, consumer-friendly interfaces
Many actors have pushed for account abstraction, which is now mainstream thanks to Privy, Rhinestone (see my article here), or Abstract. However, the space lacks a user-friendly and intuitive way to send funds without worrying about and performing test transactions. Character-sensitive transfers are things of the past. It is time to revamp them with familiar yet powerful tools that move from Account Abstraction to Address Abstraction.
What's more familiar in Web2 than a URL? It is accepted as the ID for any website you want to visit, or you want your friend to visit by sharing it. You know some URLs are sketchy, and you have learned to (most of the time) detect those.
So few things are more familiar than a link in our Web2 world; hence, piggybacking on this architecture seemed the most straightforward yet elegant way to create a cross-border payment system for Konrad and Hugo. People talk about generational wealth, but I'd like to think of a better, more enthralling goal: generational trust. Generational trust will specifically make sense in a multi-AI agent world where trust will matter more than anything else, and the number of transactions will undeniably explode.
Their innovation lies in three key areas:
Trustless Architecture: The protocol operates on a fully trustless, non-custodial model. Funds are secured in smart contracts and can only be accessed with a secret embedded in the Peanut link. This maintains the core ethos of cryptocurrency, self-custody, while dramatically simplifying the user experience.
Link-Based Transfer System: Instead of dealing with wallet addresses, users share a simple link. This link contains all the necessary information for fund retrieval, eliminating the need for complex wallet interactions.
Security-First Design: The protocol implements a sophisticated security model where:
All link information remains local to the browser session
The frontend app is completely open-source
Smart contracts are permissionless and independently auditable
A 24-hour safety window allows link creators to withdraw funds if needed
The basic primitive of Peanut Protocol is a cryptographically secure smart contract that relies on an offchain message, usually shared in a link or QR code. The protocol holds the deposited token from the sender and can only be unlocked by a secret. This has a simple workflow. First, the sender deposits tokens to the vault smart contract, then Peanut send the URL to their recipient, and finally the recipient withdraws the funds with the secret within the URL.
There are several options for creating a link:
Peanut App
SDK
An integration (e.g. wallet or app)
Smart contract
To do so, go to the Peanut Send Page and start imputing the amount you want to send.
Once you connect your wallet and sign the transaction, the asset and the public key will be stored in the Peanut smart contract. Then, a unique link will be created along with a deposit on the Peanut Vault.
The sender part is done. Note that all the links are in the same format:
/https://peanut.to/claim?c=CHAIN&i=INDEX&v=VERSION&p=KEYThere is nothing to do on the receiver end but hit the claim button. Note that it is gasless for the receiver. Just one click, and you're good.
Here are the core features they are focusing on at the moment and a few use cases:
Address Abstraction: No need to use wallet addresses or ENS names. They let you send and request funds via links/QRs which and it can be shared via email, WhatsApp, Telegram, in IRL.
You are in charge of a group payment.
In a group chat on Telegram discussing a gift for a colleague, one person offers to organize the funds. Instead of requesting crypto wallet addresses or sending an awkward ENS name, they generate a Peanut link.
The link is shared in the group chat, and everyone can contribute directly in a few clicks.
Chain-Abstracted Payments: Payments work across different blockchains. For example, you can send $1,000 on Optimism, and the recipient can receive it on Arbitrum.
Stablecoin-Abstracted Payments: They allow for flexible stablecoin conversions. You can send 1,000 USDT, and the recipient can receive 1,000 USDC.
Fiat/Crypto Abstracted Payments: Peanut introduces Ethereum’s first self-custodial offramp. You can send USDC, and the recipient can claim it as USD directly from their bank account without ever needing to touch the crypto or create a wallet.
You hire a freelancer from another country to work on a project.
Instead of using platforms that charge high fees for currency conversion and payouts, you pay the freelancer in USDC via Peanut.
The freelancer receives a payment link and claims the funds in their local bank account, bypassing the need to interact with cryptocurrencies directly.
There is one space in which I am incredibly excited to see the Peanut team in action: e-commerce.
One can imagine a world where merchants can generate payment links on the fly, enabling crypto payments without wallet integration or address management complexity. Every time a purchase is made online, the merchant can give some cash back through a link as a crypto or fiat payment. On the other hand, satisfied customers can send some payment as a tip to a merchant. As counterintuitive as it sounds, if you think deeply about the future of e-commerce, we could see the emergence of microtransactions, such as tipping a merchant online for the quality of its goods, or even crypto crowdfunding, such as the one that already occurs on Crowdmuse (our next article).
While innovative, the protocol could raise some concerns:
Link Security: The self-contained nature of Peanut Links means they must be treated with the same security as private keys. Anyone with access to the link can claim the funds.
Withdrawal Window: While the 24-hour withdrawal window provides safety, it could also create uncertainty for recipients. Users must understand that link receipt doesn't guarantee fund availability until the window expires.
The first aspect is probably the most crucial to address (the team could easily circumvent the second). How can we deter security breaches to ensure users aren't afraid of sharing links since they contain the private key?
My suggestion would be to implement on-chain verification mechanisms. Here’s how it could work:
When a user receives funds, and before claiming them, a smart contract could retrieve the recipient's X, WhatsApp, or Telegram account and verify if it matches the account specified by the sender. Conditional triggers, managed either by a smart contract or an AI agent governing the contract, could streamline the process and enhance the security of these smart links through proof of ownership or digital identity verification.
Peanut Protocol abstracts away the intimidating complexity of Web3 payments, using familiar elements like URLs and QR codes.
This evolution could dismantle ossified monopolies in the global payment sector, opening the door for individuals and small businesses to thrive without exorbitant fees or barriers, a world where Remitly or Western Union are obsolete and where context-aware microtransactions are trivial.
Peanut isn’t just solving today’s payment challenges; it’s building the infrastructure for a frictionless, interconnected economy, and I am excited to see the team empowering the fundamental layer of payment and trustless collaboration at a scale we’ve yet to imagine
For more details about Peanut Protocol, visit their official site Peanut.to or the Peanut Notion here.
A clawback period for "safety" does not make sense, and is only necessary in lieu of stronger trust factors than a bearer token can ever be. This will be exploited immediately because a significant percentage of recipients will not understand the funds can be clawed back, so they will release goods and render services immediately, to their detriment. Reflexively, I'd expect these unexpected, exploitative clawbacks to be so numerous and problematic that they would undermine Peanut's credibility. I'm unsure if the early adopters are a meaningful counterpoint to my skepticism. I think you're on the right track with the idea of sourcing trust factors from social media accounts, which can be cryptographically signed by implementing a web of social trust factors, a la Keybase.io, or something similar. For example, I can PROVE I own any number of social accounts if I have any ONE private key. A single, strong trust factor can attest to several trust factors that are, collectively, also a trust factor that can be independently verified without involving their owner. A representative scenario: Expand the Peanut contract to embed ANY recipient identifier, and require a certain degree of verification. For example, the recipient's social account must be signed by the same key that signed N additional social accounts from a list of allowed providers. This way, an attacker would need to compromise N+1 of the victim's social accounts to divert the funds from the Peanut contract vault.
1 comment
A clawback period for "safety" does not make sense, and is only necessary in lieu of stronger trust factors than a bearer token can ever be. This will be exploited immediately because a significant percentage of recipients will not understand the funds can be clawed back, so they will release goods and render services immediately, to their detriment. Reflexively, I'd expect these unexpected, exploitative clawbacks to be so numerous and problematic that they would undermine Peanut's credibility. I'm unsure if the early adopters are a meaningful counterpoint to my skepticism. I think you're on the right track with the idea of sourcing trust factors from social media accounts, which can be cryptographically signed by implementing a web of social trust factors, a la Keybase.io, or something similar. For example, I can PROVE I own any number of social accounts if I have any ONE private key. A single, strong trust factor can attest to several trust factors that are, collectively, also a trust factor that can be independently verified without involving their owner. A representative scenario: Expand the Peanut contract to embed ANY recipient identifier, and require a certain degree of verification. For example, the recipient's social account must be signed by the same key that signed N additional social accounts from a list of allowed providers. This way, an attacker would need to compromise N+1 of the victim's social accounts to divert the funds from the Peanut contract vault.