Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
0x666c6f
@0x666c6f
Hey hey based people ! Looking for advices! I’m currently building a dApp aimed at non web3 people. The project could be built without blockchain, but we want it to have transparency, and audibility. It will evolve towards a full web3 project. I can’t disclose the use case yet unfortunately. More below ⬇️
1 reply
0 recast
0 reaction
0x666c6f
@0x666c6f
We have a few requirements: - We don’t want our users to manage seed/private keys or even wallets - We don’t want them to have to deal with gas or crypto - We don’t want to use wallet as a service solutions - The contracts need to be centralized as KYC is legally required for our use case
1 reply
0 recast
0 reaction
0x666c6f
@0x666c6f
Right now the aim is to be fully centralized, and progressively evolve towards a completely decentralized solution that will be more crypto native.
1 reply
0 recast
0 reaction
0x666c6f
@0x666c6f
Currently, I imagined a solution with the following stack: - web3auth for the walletless solution using social providers - Safe for the AA + easy tx crafting and execution - Home made relayer I would be interested in using AA not requiring EOAs but I did not find anything satisfying.
1 reply
0 recast
0 reaction
0x666c6f
@0x666c6f
For the contracts design, as we need to be centralized, we need to whitelist people. i thought about multiple ways to do that, and the cheapest and most scalable seems to be using an authority signature for all contracts calls.
1 reply
0 recast
0 reaction
0x666c6f
@0x666c6f
The whitelist management would be off chain. Same for permissions. Using merkle trees, or on chain whitelists are not viable as it would be quite expensive.
1 reply
0 recast
0 reaction
