## To SpaceKayak
GM folks, hope your weekend was going great. Just wanted to summarise the work accomplished previous week.

Work done so far:
- Work on a quick UI based implementation for the Wallet connect experience integrated with Metamask based on the current designs.
- Work back and forth on the scope of wallet connect widget
- Working on customizability of the UI of the current widget

Hoping to pick up better momentum this week, we have intially targeted to complete the wallet modal for this week. As we had discussed in the previous call we had a discussion about the dev docs as well as the multlichain approach.

We feel Family like dev tools is pretty good and sufficient for an intitial PoC and we could take things up from there.

We can certainly go multi chain with respect to connect wallet, or any other widget for the matter. The only question that matters is essentially, what to prioritise. To get more components done first or get few components with a multichain approach ready from the get go. We estimate that the amount of work required, if going with the multi chain approach from the get go is going to be 3-4x times on EVM compliant chain related component work. That is. w.r.t to connect wallet it would mean delaying the wallet modal by atleast 2 more weeks.

## To Paul

Hey Paul, hope you are doing good, just wanted to share some thoughts on previous few weeks of exploratory work:

Work done so far:
- Work on a quick UI based implementation for the Wallet connect experience integrated with Metamask based on the current designs.
- Work back and forth on the scope of wallet connect widget
- Working on customizability of the UI of the current widget

Really excited to see this pick steam and the direction it is headed. However was hoping to gain some clarity before proceeding further, with regards the working style and the overall aggregate scope that you forsee.

There are essentially two primary ways that I see us working.
- Either scope based - because we are heading into our first partnership building with valued people.
- Or exploratory - where we want to value each other's time and come out with productive outputs.

We believe in an efficient way of working towards a goal and then hope to find experimental goodness in the jouney. In terms of the latter we are of a very strong opinion that its best to make the leanest of the product, and iterate from there. Such that we can gather better feedback and not get stuck on an endless loop of creating the perfect product.

Adding more features(e.g. multichain, specific wallet integrations) makes the product flow complicated, thereby pushing our timelines. Thereby if we could nail these following pointers before we proceed I think it would help a lot

- Whether both UI and functionality will be customizable?
- Is multichain required for every component?
- Also more work on a functionality layer roughly 3-4x ( we also want to work on multi-chain, but I must precurse that it will take time. )
- UI for every component needs to be very well predefined & discussed thoroughly.

On a side note, I also think there is a strong market for a widget which can sort of plug into protocol data points. I think there aren't any good component libraries out there today which achieve this.
Imagine a developer like Liquity wants to hook their self-created smart contract to some good decent UI, it might take time & effort to build something that's reliable. Let's explore that as well.