Inspiration

Since our team truly believes that Crypto's mass adaptation will come, we wanted to contribute to the ecosystem by accelerating it. We came to the conclusion that if Crypto Payroll became more popular, it would contribute greatly to mass adaptation.

What it does

Although they are not the majority, in fact, quite a few people in the Web3 scene were already paid with crypto, and statistics show that the amount of crypto paid as wages is expected to increase. In this context, solutions that make crypto payroll easier were also emerging recently.

However, the biggest problem with all of these services is that all transactions are inevitably transparent due to the characteristics of the existing blockchains, and all the salary amount, timing, and recipient's wallet address are disclosed.

In fact, most companies are reluctant to disclose the amount of wages employees receive due to their advantage in salary negotiations and relationship issues between employees.

So existing crypto payroll services do not meet the company's needs regarding this privacy issue, and this is one of the biggest reasons why crypto wage payments are not becoming popular.

GRIFFIN solves this problem via Polygon Nightfall.

Despite Griffin's use of Legit Layer 2 on Ethereum, All payroll transactions through Griffin remain non-transparent and private.

_ Figma Prototype (design demo)

How we built it

Nightfall supports privately transferring ERC20 /ERC721 / ERC1155 tokens with Optimistic rollups instead of ZKP for lower gas costs In our global payroll systems, Transfers are confidential and anonymous "ZKP for privacy, optimistic rollup for scalability" Nightfall is designed to have Shield Contract deployed at Ethereum Layer 1. Proposers, Challengers to roll up transactions into blocks. Front-end is written in NextJs with styled components. It connects with backend and visualize payroll related data. Our Backend server, written in Golang, will be providing API for employer and employee data, balances and prices. It fetches and caches price data from a 3rd party token price services for conversion. In the scenario of transactions, backend interacts with the dockerized polygon client, it furthers talk to SDK which abstracts ZKP artefacts with a token API L2 state is created by series of L1 transactions and held off chain, Current version use MongoDB and RabbitMQ Future production versions of nightfall are expected to be launched soon.

Challenges we ran into

First of all, Polygon Nightfall is a very new chain. Since the SDK is not completely created at the moment, in order to create a DAPP, we had to actually run the Proposal and Client from Nightfall directly on our local computer. Also there were no documents or tutorials for development, so we solved all the errors and debugging by asking the Polygon Nightfall team directly via Telegram everytime.

The installation of Nightfall on the local computer took almost two days to resolve the error. In the process, we learned that the nightfall works on the docker, and that the docker specification needs to be maximized to run the nightfall. In addition, in the process of connecting Griffin Web Front and Nightfall, we tried various things such as putting it directly into the node module with npm link, and found that the Nightfall SDK was not optimized for browsers, so we had to apply the Web3 Provider to the SDK.

Accomplishments that we're proud of

We made the First Private crypto payroll all-in-one solution for web3 organizations. It is also the first DAPP project based on Polygon Nightfall.

What we learned

We deeply felt the importance of teamwork. Time was running out & Dev environment was really new to us but we managed to do it somehow, trusting each other as a team.

What's next for GRIFFIN

We will find the organizations (ex. investment DAOs) that will best utilize privacy, while also finding another edges other than privacy. The goal of the GRIFFIN team is not just to build a tool. True goal is to make Crypto Payroll a natural thing.

Built With

Share this project:

Updates