$Qubic smart contracts are about to gain a new sense: reading events straight from other blockchains.
Two new Oracle Machine services are in review, readEVMLog and readQubicLog.
Both already proven on the dev testnet.
Here is what they do.

The readEVMLog lets any #Qubic #SmartContracts read any event log from an #evm chain.
#Ethereum , #BSC , Polygon, Base, Arbitrum, and more.
No trusted middleman.
No single oracle operator.
Every answer is independently fetched and byte-verified by the computor network.

The readQubicLog lets a contract, or a cross-chain relayer, read any event from Qubic's own history the same way.
That makes Qubic events provable to the outside world through a zero knowledge proof.
One reads in.
The other proves out.

What this unlocks:
Tracking money moved on other chains, the core primitive for a cross-chain bridge.
Price feeds read directly from on-chain sources like Chainlink aggregators.
Access to on-chain facts like credentials, allowlists, proof-of-humanity, and NFT ownership.

Both services are fully generic.
They carry no application logic.
They deliver raw event bytes, and each contract decodes its own meaning.
Adding a new use case needs no oracle code change at all.
Both are proven on the dev testnet with full decentralized commit-reveal rounds.

The pull requests are open now: init files for evm/qubic log service