> For the complete documentation index, see [llms.txt](https://edgeverse.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edgeverse.gitbook.io/whitepaper/background/edgeware-ecosystems-highlights.md). # Edgeware ecosystem’s highlights: * High performant being a substrate solochain. Dual smart contract environments (EdgeEVM and EdgeWASM) to leverage the full potential. * The oldest substrate mainnet. (The second substrate mainnet launched right after kusama.) * The most fair distribution was achieved via the industry's first lockdrop mechanism, which airdropped 90% of the supply to the Ethereum holders. Binance, Coinbase Ventures, Framework Ventures, KR1, Waterdrip Capital, Hashkey Capital, LedgerPrime, and Aragon are the entities/VCs/DAOs that announced their lockdrop participation publicly. Every single Lockdrop participant had the same algorithmic participation methods and rules as others, irrespective of whether they were VCs or day-to-day enthusiasts. * Bootstrapped without any token sale or VC backing. * Decentralized in every aspect, being a true chainDAO. Completely community-owned and not just community-run. * It started as a governance experiment but became a self-sustainable ecosystem due to a community-governed balance between inflation and Treasury spending. (The community so far funded diverse types of proposals, like those for developments, integrations, incubations, even social goods and not-for-profit initiatives, through the on-chain treasury, which is accessible only through the on-chain democracy.) * Dramatic history where the community collectively voted against the founding team's over-budgeted treasury proposal and took over the ecosystem responsibility when the team moved away from responsibilities. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://edgeverse.gitbook.io/whitepaper/background/edgeware-ecosystems-highlights.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.