The native verification protocol is a protocol that is completely verified by the verifier of the underlying chain for the data passed between the chains. This is usually done by running a light client of one chain in the Ethereum Virtual Machine (VM) of another chain, and vice versa

Examples include Cosmos IBC and NEAR RainbowBridge. Rollup entrance/exit is also a special form of it!

Advantage: • No need to trust the highest degree of interoperability, because the underlying verifier is directly responsible for the security of the "bridge"; • Achieve completely universal messaging between domains.

Disadvantages: • Rely on the underlying trust and/or consensus mechanism of the domain to operate, so it must be customized for each type of domain.

The Ethereum ecosystem is highly heterogeneous: we have many domains, from zk/optimistic rollups to side chains, to the basic chain running various consensus algorithms: ETH-PoW, Nakamoto-PoW, Tendermint-PoS, Snowball-PoS , PoA, there are many consensus mechanisms. Each of these domains requires a unique strategy to implement a natively verified interoperability system.