Last updated: 12 August 2022 04:22 PM
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.
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.
Despite Griffin's use of Legit Layer 2 on Ethereum,
All payroll transactions through Griffin remain non-transparent and private.
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.