Dapplets: call for related works

dapplets

#1

Hello all,

We have implemented #dapplets proposal as very early stage PoC in ETHParis Hackathon.
See this video for details.

Now I am trying to review existing proposals and other things that could be related to dapplets in order to take a broader look and define a roadmap for further development.

I have identified following items:

Is there a good implementation of the three EIPs above available?
Is there any other related items that could be important?

please let me know,


#2

Thank you for the ping. I’m involved more in NatSpec than 712. I have made some minor updates on NatSpec last month and I maintain it.

But if we are going to have actual change here then we will require implementation from MetaMask or a competitor.

It’s not like other core EIP initiatives where somebody has an idea and Vitalik pays for its implementation out of the fund.


#3

Thank you for reply!
I am not going to change standards right now. Just exploring the space currently.
I have no much doubts on adoption because there are clear business incentives for wallets to go this way (if we provide sufficient level of security, of cause).


#4

@fulldecent,
Even more because you may have different opinion on how current challenges in secure signing may be solved, I would very appreciate your opinion on the draft of the Dapplets article I have wrote in medium.

Could you take a look? The scope of the article is to define the problem and outline possible solution without going into deep technical details. Any critic is appreciated.


#5

Hi, I don’t have a Medium account but I read the TL;DR and the proposed picture at the bottom.

Two issues:

  1. Removing Web3 from the dApp and adding a specific vendor… I think this is moving backwards. We should encourage the visitor (and the browser on their behalf) to have web3 services available. Just like we depend on them to have XMLHttpRequest available.

  2. You are proposing MetaMask to make changes. This is fun but it wont happen. MetaMask /still/ doesn’t support ERC-721, a large application class on the blockchain. And right now the way the ecosystem works is that everybody wants to reinvent the wheel. Just look at the number of ERCs created. That paper proposes adding a 2+ year delay for the user interface to update every time somebody wants to update a new application.

    2a. One solution is to make the creation of the Signer UI customizable. As in you can design new forms (they can be responsive) and layout the elements on the page. Boom, then you just reinvented what we have today.

But don’t let me stop you! I think all this is good ideas, and I’d love to see you try. But the most likely way to make this reality is for you to fork MetaMask and implement this stuff. If your vision requires you wait for other people to implement this stuff then that is unlikely to ever happen.


#6

You are proposing MetaMask to make changes.

not the case any more. ETHParis implementation was WalletConnect based.

Hi, I don’t have a Medium account

challenge accepted… I should think how to share the draft without expecting medium account.