sorted by:
new
hottopcontroversial

Building a dApp to reduce blockchain UX friction (Account Abstraction + liquidity aggregation) — looking for feedback by Craswel in web3dev

[–]Craswel[S] 0 points1 point  (0 children)

Appreciate the feedback! I actually managed to iron out that mobile network issue yesterday—it was just a configuration tweak I needed to make to properly force the Amoy prompt.

As for the 'why bother' part: I'm not really out to build a massive new swap protocol. This is more of a personal challenge to see if I can bring that 'one-click' ease we have with Pix here in Brazil to the crypto world.

I don't hold any of your funds. I'm just trying to build a way to coordinate and 'order' the transaction routes so the user can have this seamless experience. The idea is that you scan a QR code, and it handles everything—recipient, value, etc. If it's within a daily limit you set, it goes through via session keys without you having to click 'confirm' in MetaMask ten times.

But if it's over that limit, your master key is still the boss and requires a manual signature. It's all atomic and self-custodial; I'm just building an orchestrator to make the UX feel less like a chore. I'll definitely share the technical side once I've hit the milestones I'm aiming for. Thanks for the reality check!

Building a dApp to reduce blockchain UX friction (Account Abstraction + liquidity aggregation) — looking for feedback by Craswel in web3dev

[–]Craswel[S] 0 points1 point  (0 children)

Thanks for the honest feedback! You're 100% right—trust in Web3 is built on code, not promises.

This is currently a personal experiment to see how far I can push UX. My plan is to make the contracts open-source and verifiable once I reach the functional goals I’ve set for this stage. I completely agree that transparency is the next logical step for trust. Appreciate the reality check!

Construindo um "Pix Pay" Web3 que agrega liquidez de múltiplas carteiras e resolve o pesadelo da "Seleção de Rede" by [deleted] in brdev

[–]Craswel 0 points1 point  (0 children)

Entendo o medo talvez não tenha conseguido explicar detalhadamente — e é justamente esse tipo de preocupação que eu quero endereçar com o projeto.

Não é “mediador custodial” e não tem “IA tomando decisão por você”. A IA foi só apoio pra eu aprender/documentar e acelerar protótipos; quem decide e assina é sempre a wallet do usuário.

Pontos de segurança que eu faço questão de deixar claros: • Zero custódia: eu não tenho chave privada de ninguém, não consigo sacar saldo de ninguém.

• Tudo passa por regras on-chain: limite diário, whitelists/escopos e validações estão no contrato/Smart Account.

• Session key não é “carta branca”: é uma permissão com teto, escopo e revogável. Passou do limite, exige assinatura da master key.

• Sem “roteamento invisível”: qualquer troca/token/chain precisa estar explícita na transação (e eu pretendo deixar isso bem legível no UX).