The problem Payroll Protocol solves

The Payroll Protocol is designed to provide a permissionless, confidential payment solution within the Web3 ecosystem. Traditional payment gateways in Web3 struggle with user experience and confidentiality, especially when it comes to handling personal or sensitive financial information.

---

Problem Statement

In the traditional financial system, confidentiality of income and balances is a given. Our bank accounts keep our financial information hidden, ensuring privacy and security for individuals and organizations alike. This confidentiality is not only important for large distributors, venture capitalists, fund managers, and DeFi enthusiasts, but also for everyday users who value their privacy.

However, in the Web3 space, achieving this level of confidentiality is challenging. On-chain transactions are inherently transparent, making it difficult to keep financial information private. This transparency can lead to potential privacy breaches, financial exposure, and other risks associated with publicly visible transaction histories. This is where Payroll Protocol steps in.

Use Cases

For Individuals

• Confidential Payroll: Receive your salary or payments without exposing your financial details.
• Secure Savings: Store your funds securely and privately on the blockchain.

For Organizations

• Private Employee Payments: Distribute salaries and bonuses to employees without compromising confidentiality.
• Anonymous Fund Management: Manage and distribute funds privately while maintaining transparency for auditing purposes.

Architecture

Flow-Diagram:

Challenges we ran into

Issues Encountered with Biconomy SDK, Hyperlane Bridges, and Privy Smart Accounts

1. Biconomy Account Abstraction SDK:

   • We faced several challenges while integrating the Biconomy account abstraction SDK. These issues included difficulties with setting up and initializing the SDK, handling user transactions, and ensuring seamless integration with our existing application infrastructure.

2. Deploying Custom Hyperlane Bridges:

   • The deployment of custom Hyperlane bridges presented significant obstacles. We encountered issues related to configuring the bridge contracts, managing cross-chain communication, and ensuring the reliability and security of the bridge operations.

3. Privy Smart Account Integration Using Gmail:

   • Integrating Privy smart accounts using Gmail authentication posed several problems. We faced difficulties in setting up the authentication flow, linking Gmail accounts to the smart accounts, and managing user data securely and efficiently.