# Looking Ahead: the Bondex Network L2 Option

A healthy ecosystem of interactions generates value which may be better captured by owning a proprietary Layer 2.

In the future, Bondex may explore developing and owning a proprietary L2 to help participants capture the value of their interactions.

\
In this scenario, all economic interactions on the Bondex L2 would require gas fees to be paid in $BDXN, making it the technical fuel of the network. This would modify some of the current economic flows and introduce key changes. The most significant change would be that the Bondex Sequencer would capture all generated revenue. A portion of these gas fees would be allocated to settling transactions on Ethereum Layer 1 in $ETH, while the remainder would be used to:

* Supplement the rewards pool
* Contribute to the deflationary mechanics of $BDXN by burning a variable amount of collected gas fees

![](/files/8ZMascF1aXaQJmrp4PNy)

Furthermore, owning the infrastructure layer underpinning the application creates more opportunity for value creation by fostering an external builder community. If other developers deploy applications on the L2, they will contribute value by enriching and consuming social graphs and utilizing the $BDXN token for gas. This, in turn, creates a powerful flywheel effect within the L2 ecosystem.

![](/files/amlW3BbkgqIIbkRR2pw2)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bondex.app/tokenomics-2.0/looking-ahead-the-bondex-network-l2-option.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.