Finding the entry point for developers' needs is far from enough for one click blockchain infrastructure protocols. Finding the entry point for user needs is the key to winning. The market does not lack BaaS/RaaS one click convenient L1/L2 chain infrastructure: Blockchain-as-a-Service: Cosmos SDK/Avalanche9000/@ fluentxyz Stack, etc Rollup-as-a-Service: OP Stack/ZK Stack/@ Calderaxyz/@ coinuitxyz/@ initia Interwoven Rollups, etc The above only lists some of the one click blockchain infrastructure protocols, and there are far more projects on the market than that. It only took about a year for this track to go from the blue ocean track to the red ocean track. The projects that entered earlier did indeed benefit from the segmented track, such as @ Calderaxyz, which made a lot of money by paying for RaaS demand side products, without the need for demand from C-end users. Because the Rollup track was not congested at the time, many dapps project developers transformed themselves into a prestigious app specific chair with the help of RaaS But now the L1/L2 chain is already very congested, so the public chain project team has started to create a word movement, advocating modularity, high TPS, higher-level stage parallelization (piping) than transaction parallelization, etc., as the core innovation point that distinguishes itself from similar competitors. Many projects may have been transformed from dapps to blockchain, and the user needs of dapps are still unclear. Can we really understand the user needs of blockchain? At present, if there is a lack of demand from C-end users, dapps naturally lack the need to transform into chains, and the demand for BaaS/RaaS will naturally be sluggish. At present, it seems unrealistic for the BaaS/RaaS project to directly replicate the path and core gameplay of predecessors. In my opinion, in order for such projects to succeed, they must have a strategy of "soldiers and cunning". At present, I think the most outstanding "trickery" strategy is @ initia: reverse deriving the requirements of the application from the C-end user demand side, and then launching Rollup sub chains for different application scenarios based on the user's needs. Such as @ milky_way_zone, which focuses on PoS asset re staking, @ blackwing_fi, which focuses on derivative trading, and @ intergaze_xyz, which focuses on NFT launch. Further implement VIP mechanism to strengthen the association between sub chains and @ initia parent chain, achieve feedback from sub chains, and form a community of shared interests. In summary, the path to success for BaaS/RaaS is to find the path to PMF, or more bluntly, to identify potential user demand scenarios and feedback patterns for sub chains. Image source:@ 0xJim