# WTMP with L3

I agree, having L3 with LIF as a native token is good but only when this L3 is trustless. In a trusted system, the LIF token balance is just a record in the database. A lot of risks. Trusted L3 is a fake. Even if we will agree on a trusted solution for L3 it will not dramatically reduce time to market. We still are required to spend time on solving security issues.

Ok, we can go straight and set up a ready-made EVM-compatible chain and use it as L3. What about the performance of such a solution? Can it satisfy market expectations? The current TPS of the Polygon is about 7000 (in theory they can be 100000 but no one is sure it is true). If we just copy their network sources is it satisfy us and the market?

How to make payments inside the L3? Of course, all stablecoins must be bridged there from L1/L2. On-ramp solutions also should be there but they are also will require to bridge tokens. Or on-ramp can create its own stablecoins based on fiat currencies but only for our L3. This is possible technically but will require a lot of legal work. I guess that the creation of stablecoins without legal formalization is criminal.

Ok, we need a bridge for our L3. The development of a reliable and secure bridge can take about 2 years. This is approximately, I do not really how much time it takes but I know a guy from [allbridge.io](https://allbridge.io/) and I know that their time to market was about 2 years.

By the way, allbridge.io has a BaaS solution compatible with all popular EVMs. So, technically it is possible to buy their ready-made bridge solution but how much it costs I do not know. We need to contact them directly and ask for a price.

Ok, what is next? Requests, offers and orders. Requests and offers are limited in TTL. When they are expired they are useless. So it does not make sense to handle them via a blockchain. Once they are published on pub/sub server they should live there until expire and then they should be cleared up.

What about the pub/sub for coordination of buyers and suppliers? In my proposal, I have mentioned some possible solutions. The most reliable and production ready is nats.io but it is not so flexible and may not allow us to implement the required use case in the full range. But we will still be able to take as a base a good known Socket.Io and build all that we want in about one month.

Orders. I think my proposal about the handling of deals is a good fit. Orders (deals) and stablecoins (bridged) are the only entities that we should handle via our L3 blockchain. My estimation on the smart contract development is about 1-1.5 months.

And the last - suppliers and their business logic. I am still sure that the SaaS way is wrong. Centralizing business logic dramatically affects flexibility, censorship, and security. It is not possible to develop a solution that satisfies all the needs of all travel industry (not only) players. So. I suggest sticking to my proposal of nodes and SDK. This way in the frame of WidingTree we can implement a reference solution that can be customized by real businesses.

**So, my compromise proposition on WT market protocol now looks like this:**

- L3 build on the most stable EMV with POS/POA there LIF will be a native token
- Blockchain explorer based on [Blockscout](https://www.blockscout.com/). We can use their [Explorer as a service](https://www.blockscout.com/#explorer-as-a-service) solution
- Ready-made bridge for stablecoins based on BaaS solution. This solution must include: a fully worked bridge for selected stablecoins (+LIF) with the possibility to extend in the future + SDK for integration of the bridge features into Dapps
- Smart contract for orders (deals) as proposed in [my initial proposal](https://www.notion.so/Winding-Tree-Market-Protocol-WTMP-c748cbf4e036421b995da5e32bc72e9f)
- Custom pub/sub server based on Socket.Io
- “Node” that can be started inside node.js app, electron app or react-native app + SDK for customisation as proposed [in my initial proposal](https://www.notion.so/Winding-Tree-Market-Protocol-WTMP-c748cbf4e036421b995da5e32bc72e9f). In the frame of WindingTree, we should develop and support only the reference node as an example of the protocol implementation
- Dapp for buyers integrated with tokens bridge and our L3 chain. This is also should be only a reference implementation. Not for real business.