Frontends can fail.
The transaction path should stay open.
Users submit calldata to the ownerless Matrix Inbox. Once the base layer includes a valid input, it enters the public history.
One interface going offline does not close the entry path.
🤝 Partnership Announcement: Matrix × @ProBix_AI
We’re excited to welcome ProBix as our latest collaborator.
ProBix is an AI-powered event intelligence network transforming real-time sports data into actionable probability insights. Through AI-driven modeling, live event analysis, and Web3-ready oracle infrastructure, ProBix provides intelligent data solutions for prediction markets and decentralized applications.
Together, Matrix and ProBix will explore how AI-driven intelligence and high-performance blockchain infrastructure can advance prediction markets, improve on-chain decision-making, and unlock new possibilities across Web3.
More to come 🚀
Applications can plan around congestion.
They should not have to plan around human intervention.
Matrix removes private shutdown dependencies:
No pause switch
No emergency committee
Liveness tied to base-layer block production
As long as the base layer keeps producing blocks, Matrix keeps processing valid inputs.
When two Matrix nodes report different states, the answer should come from the chain’s public history.
Every transaction input enters through the Inbox, and BNB records those inputs in canonical order.
Both nodes begin with the same evidence.
🧵 1/4
Congestion can be planned for.
A private shutdown cannot.
No pause switch.
No emergency committee.
No operator deciding when execution resumes.
If the base layer keeps producing blocks, valid inputs keep moving.
Liveness by architecture.
Not permission.
Keeps execution live without relying on operator permission.
Every product begins with a root.
One line of code, then another.
Keep building.
Roots grow deeper. Branches take shape.
Build it into a tree, builders. 🌱
Tokenized stocks are moving on-chain fast.
The market has reached $3.9B, with @BNBChain accounting for nearly one-third at $1.2B.
As adoption grows, these assets will need stable execution, reliable finality, and more room to scale.
BNB Chain is already becoming a key market for that growth.
It was great catching up with old friends at @TOKEN2049 and hearing about everything people have been building.
Thank you for every conversation and all the energy throughout the event.
See you at the next one!
By integrating machine learning with real-time on-chain data, Matrix supports:
• Automated trade optimization
• Risk monitoring
• Smart money tracking
Built around live market activity, this AI-driven infrastructure will help users spot market changes faster, identify risks, and follow capital movements.
Matrix is deeply adapted to @BNBChain’s PoSA consensus without introducing a separate consensus layer.
• Sequencing inherited from BNB
• Data availability anchored to BNB
• Finality determined by BNB consensus
• Valid inputs processed as BNB produces blocks
A dedicated execution layer built around one consensus source.
Built on Facet, Matrix adds execution capacity without changing @BNBChain.
• Independent, high-performance execution
• BNB sequencing, data availability, and finality
• Continuous execution while BNB produces blocks
A scalable base for AI-powered on-chain apps.
Matrix is heading to @TOKEN2049 ✈️
We’ll be around meeting new people, catching up with friends, and hearing what everyone’s been building.
Looking forward to seeing everyone there!
📢 Matrix Testnet Phase 1 is now live.
The whitelist snapshot is complete, and eligible users can now take part in Interaction Mining.
🎁 Reward pool: 0.1% of the total $Matrix token supply
Start interacting on the testnet, help us test the network under real activity, and earn rewards based on your share of gas contribution.
Wow, what an incredible time at KBW!
Seoul was full of energy, good conversations, and people ready to build.
We met old friends, made new ones, and left with plenty of ideas.
Thank you to everyone we met along the way.
See you again soon, Seoul!
Scaling should not require redesigning the underlying chain.
Matrix adds execution capacity without changing its consensus, EVM, gas model, or block format.
Core protocol rules stay intact while applications gain more room to run.
Thank you @turtledotxyz for hosting Liquidity Evening by Turtle.
Korea remains one of Asia’s most important trading hubs, bringing together active users, deep liquidity, and a fast-moving Web3 community.
A great evening of conversations and new connections in Seoul.
Fast execution is useful only if apps know when history is final.
Matrix does not create a separate source of finality. Finalized BNB blocks determine its finalized input history.
Execution moves to a dedicated layer while settlement stays tied to the same public anchor.
A new node should be able to check the chain without accepting someone else's snapshot.
Matrix records inputs and their order on BNB. A node can read that history from the beginning, replay execution, and compare the resulting state.
Verification remains possible without a trusted starting point.
A user's first action should not begin with finding another token just to pay for execution.
Matrix keeps execution gas outside the token economy, so users do not need to bridge a separate gas token before interacting.
One less setup step stands between the user and the app.
Publishing transaction data is only the first step. The execution engine still needs to know which inputs are valid and what order to process them in.
Matrix-node reads the public input history, validates it, and prepares execution batches.
The engine works from that ordered record, not an operator's private queue.
Matrix is now listed on @RootDataCrypto. 🔍
Explore our project profile and learn more about what we are building in one place.
Stay up to date with our progress, review key project details, and follow the continued development of the Matrix ecosystem.
Explore Matrix on RootData:
rootdata.com/projects/detail…
Data infrastructure creates its own execution load.
Oracles publish updates.
Indexers process growing histories.
Proof systems aggregate results.
These workloads run continuously and often arrive in batches. Matrix gives data-heavy services more execution room without pushing every computation onto L1.
Open access should apply to exits too.
A network may accept transactions, but users still face risk if a privileged party can block withdrawals.
Matrix has no sequencer, admin multisig, or emergency committee with that authority.
Users do not need an operator’s permission to leave.
High-activity apps can hit L1 limits before they run out of ideas.
When every interaction competes for the same execution space, builders may have to simplify features.
Matrix moves heavier computation into its execution layer, giving products more room to grow.
Every transaction uses computational resources.
Gas measures how much work the execution layer needs to perform. But when that gas is tied to a tradable asset, execution costs can also become exposed to market speculation.
That makes product costs harder to predict. 1/4 🧵
Builders should not have to leave an ecosystem just to gain more execution capacity.
Moving to an isolated chain can mean:
→ fragmented liquidity
→ a different user environment
→ additional tooling dependencies
Matrix expands execution around BNB, giving apps more room to scale without turning growth into migration.
🤝 Partnership Announcement: Matrix × @noma_network
We’re excited to welcome Noma as our latest collaborator.
Noma is a personal AI Agent platform that makes it easy to deploy, manage, and grow autonomous AI Agents. With one-click deployment, private memory, multi-channel connectivity, unified AI model access, and built-in financial infrastructure, Noma enables Agents to move beyond assistance and become autonomous economic participants.
Together, Matrix and Noma will explore how AI agents, on-chain intelligence, and high-performance blockchain infrastructure can enable smarter automation and unlock new possibilities for autonomous Web3 economies.
More to come 🚀
Throughput is partly a question of how much space each action consumes.
Compact inputs are recorded on L1, while complex logic runs in the execution layer.
The same base-layer capacity can carry more user activity when every action leaves a smaller footprint.
A network should not need its original team online to keep accepting valid user actions.
Matrix removes the operator-controlled points that can interrupt execution: no sequencer, no admin key, no pause switch.
Liveness comes from the architecture, not a team's availability.
Why do payments and microtransactions need a dedicated execution layer?
A subscription, invoice, or merchant payment may be small, but it needs to happen repeatedly.
When every action carries an uncertain cost, the payment flow becomes difficult to price and maintain.
🧵 1/4
An ecosystem should not depend on one team to decide what gets funded.
That is why Matrix uses DAO governance. $MTX holders can vote directly or delegate on treasury allocation, grants, public goods, infrastructure, and governance rules.
Resources follow community decisions.
🤝 Partnership Announcement: Matrix × @GoldHousedotcc
We’re excited to welcome @GoldHousedotcc as our latest collaborator.
GoldHouse is a full-scenario Web3 social platform combining communication, MPC wallets, payments, DApp discovery, and community growth tools. By connecting social engagement with financial and ecosystem services, GoldHouse helps Web3 projects strengthen communities, improve user conversion, and drive sustainable growth.
Together, Matrix and GoldHouse will explore how AI-driven infrastructure, decentralized applications, and Web3 social ecosystems can create more connected, scalable, and engaging experiences for the next generation of users.
More to come 🚀
An on-chain orderbook handles more than trades.
Users place, update, and cancel orders as the market moves. When capacity becomes unstable, those actions become harder to process on time.
Matrix gives orderbooks predictable execution for the activity between each trade.
What is RPC, and why does Matrix separate data queries from transaction submission?
RPC is how an app requests blockchain data.
Matrix RPC reads blocks, state, logs, and receipts. Transactions enter through the Inbox on BNB, so the service answering queries does not control submission.
A rollup should not rely on one data provider to tell everyone what happened.
If that provider goes offline or hides transaction data, other nodes cannot check the chain for themselves.
Keeping that data accessible is called data availability.
🧵 1/4