2026-01-18 15:22:11

Everyone is busy building various orchestrators and liquidity mining protocols, while I am working on creating an underlying network that enables them to collaborate with each other.

To be honest, it feels a bit like collective thinking.

But upon reflection, this kind of differentiated positioning at the infrastructure layer is quite interesting—while everyone is vying for the popularity of the application layer, focusing on weaving the underlying network tightly so that different modules within the ecosystem can collaborate efficiently—this might be where the long-term value lies. The Web3 ecosystem needs such connectors.

View Original

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.

11 Likes

Reward
11
5
Repost
Share

Comment

0/400

SmartContractPlumber

· 01-20 14:49

Underlying connectors, that's a nice way to put it, but have you clearly designed the access control? I've seen too many infrastructure projects fail due to reentrancy vulnerabilities in protocol interactions. Poor isolation and auditing in cross-module calls is playing with fire.

View OriginalReply0

GasFeeBeggar

· 01-18 15:50

Connector work is indeed boring, but it's really in demand.

View OriginalReply0

ProposalManiac

· 01-18 15:49

The issue of underlying interoperability, in the best case, is called a connector; in the worst case, it's an intermediary layer of taxation. The key is how to design the incentive mechanism—otherwise, it becomes another center of power.

View OriginalReply0

SneakyFlashloan

· 01-18 15:41

Underlying infrastructure is indeed easy to overlook, but this guy is right... Currently, there's a lot of noise at the application layer, while the value of the underlying connectivity is being underestimated.

View OriginalReply0

GweiTooHigh