This whitepaper describes Endurance, a BAS-based blockchain ecosystem launched by Fusion Interactive for gaming and social applications. It covers EVM-compatible infrastructure, modular architecture, native asset bridging, PoSA consensus, validator selection, staking, governance, transaction fees, and runtime upgrades. It also outlines the ACE token's stated 147 million total supply, allocations, rewards, and burning mechanisms, alongside developer tools, mainnet connection details, and legal disclaimers.
Free preview text
The first 5 pages, shown as text so search engines and readers can find this document.
Page 2
1. Summary
Endurance is a high-performance digital entertainment-focused sidechain built on top of a
proven, fully EVM Compatible blockchain infrastructure BAS. Launched by Fusion
Interactive, the leading web 3.0 gaming studio created by gaming industry veterans,
Endurance optimizes instant transactions and ultra-low fees, enabling millions of
in-game/social transactions to be executed seamlessly. After 3 months of launch since Jan
2023, the Endurance network has had 50mm transactions and 1.4mm of total active users
(source).
2. Abstract
Endurance is a blockchain ecosystem offering high-performance, cost-effective gaming, and
social networking application solutions. With a focus on optimizing network performance and
reducing storage requirements, Endurance aims to create a fast and efficient blockchain
infrastructure for developers to build decentralized applications. The protocol supports
various use cases, with a focus on gaming applications and social networking platforms.
Endurance enables innovations in the blockchain space by providing a scalable and reliable
blockchain solution and aims to become a leading player in the digital entertainment
industry.
3. Motivation
The Endurance team has two main motivations to build the Endurance network:
● The blockchain industry lacks a sustainable and scalable gaming+social ecosystem.
Endurance offers a faster and more efficient blockchain infrastructure for developers
to build decentralized applications, with a focus on gaming applications to social
networking applications.
● As of today, BNB Chain is the largest chain by active users, but it is experiencing
network scalability problems. The core developers have proposed using Binance
Application Sidechain (BAS) in their Outlook 2022 paper to solve this problem;
Endurance network is built based off of the BAS design, it offers much higher
throughput, lower gas fees, and a predictable and stable fee system for users.
4. Structure
Endurance blockchain offers a multi-layer architecture to provide scalability and facilitate the
reuse of existing modules. This architecture is composed of infrastructure, client interface
execution engines, network protocols, and storage. In addition, this architecture makes it
possible to modify existing smart contracts easily and efficiently.
The Endurance chain consists of multiple layers:
Page 3
● API and Tooling: Endurance provides a complete set of APIs and tools to enrich the
blockchain ecosystem.
● Explorer: Endurance's explorer allows real-time analysis of blocks, transactions,
contracts, and accounts on the blockchain.
● Governance/Staking App: Allows validators to easily propose, vote, and delegate
through a user-friendly interface.
● APIs: Provides valuable information on NFTs and DeFi through RPC and Websocket.
● Client Interface: Offers Web3 JSON-RPC with 100% compatibility with the Ethereum
network.
● Governance Modules: Enables chain governance, including staking and slashing.
● Execution Runtime: 100% EVM compatibility and smooth migration of existing Smart
Contracts.
● Consensus: Endurance adopts a Proof-of-Stake consensus algorithm that combines
a hybrid mechanism of Proof-of-Stake (PoS) and Proof-of-Authority (PoA).
● Network Protocol: Implements a P2P communication protocol between validators and
nodes.
● Storage & State: Provides key-value storage and Merkle Tree State, Tx & Block
storage optimized for high-capacity processing.
5. Specification
Endurance is a modular framework designed to create BSC (Binance Smart
Chain)-compatible sidechains with optimized performance and improved scalability.
Endurance brings development-ready features like staking, RPC-API, and smart contracts to
the BSC ecosystem. Instead of relying on the BSC security model, Endurance provides
protocols and standards for integrating third-party bridges that the Endurance validator set of
other projects can manage. In addition, it offers several programmable and configurable
modules like networking, blockchain & EVM, Web3 API, transaction pool, PoA & PoS
consensus, and storage & state, that developers can use or modify to reach their business
goals.
Page 4
Endurance brings several programmable and configurable modules that developers can use
or modify to reach their business goals.
Here is an example of such modules:
● Networking - for p2p communication between different Endurance nodes;
● Blockchain & EVM - for block producing and EVM transaction execution, of course,
each Endurance can define its runtime execution environment based, for example,
on WebAssembly;
● Web3 API - for essential compatibility with the Web3 ecosystem, including MetaMask
and other applications;
● Transaction Pool - for managing internal Endurance policies for transaction filtering
and for charging fees for the system operations;
● PoA & PoS Consensus - for users to be able to vote for the honest validators in the
Endurance network and guarantee the safeness of actions applied on the chain;
● Storage & State - for persisting local data.
5.0 Circulation Model and Native Asset Bridge
The critical components of each Endurance application are the native token circulation
model and cross-chain bridge for native assets. Native assets of the Endurance chain are
located within the Endurance application and managed directly by the sidechain. Endurance
is designed to provide cross-chain functionality for the native assets, which Endurance
developers fully manage. However, we leave decisions on token supply manipulation or
minting/burning tokens to the developers' discretion, as they bear the risk of damaging their
reputation.
To ensure active validator sets and verify the correctness of cross-chain transactions, we
require block header verification for the native cross-chain bridge. Although Endurance is a
technology-agnostic solution not designed to have a BSC-compatible consensus or EVM
execution environment, we offer basic functionality for Endurance applications to help them
set up their work and be part of the ecosystem. We trust Endurance developers, but we must
ensure validator transition integrity. Therefore, we introduce a block header verification
function (BHVF) that the Endurance development team must specify. BHVF, written in
Solidity, verifies block headers from Endurance applications and validator transitions, but it
cannot prove the correctness of state transitions. BHVF is a required parameter to register
Endurance in BSC's smart contract for native cross-chain functionality.
Block header verification is not complicated; we only need to verify block headers to ensure
validator transition accuracy. We can use BLS/BN to publish only epoch blocks containing
new validator sets and signatures from all previous validators without passing all block
headers into it to achieve confirmation.
interface IProofVerificationFunction {
function verifyValidatorTransition(bytes[] calldata proofs, uint256
chainId, address[] calldata existingValidatorSet) external view returns
(address[] memory newValidatorSet);
}
Page 5
If we assume that block verification consumes ~50k gas (w/ state modification), then we
have the following calculations:
● Per block: 50k gas/block, then its ~16k gas/sec
● Per epoch: 50k gas/epoch (epoch can be from 5 minutes up to 1 day), then it's
between ~160 gas/sec (for 5 min epoch) and 0.57 gas/sec (for one-day epoch)
Of course, the gas consumption for cross-chain operations will depend on the epoch length,
but Endurance doesn't need very short epochs. We recommend using an epoch length of
one day for validator transition, which can be reduced to 6-12 hours based on the
application's needs without significantly changing gas consumption.
Our native asset bridge supports the following user flows:
Deposit (Endurance -> BSC): When a user calls the deposit function, their native tokens will
be locked in the smart contract, and an event will be emitted. The user must then generate
proof containing information about the transaction receipt (including the emitted events) with
a Merkle Patricia trie proof to mint peg tokens in the BSC chain. This proof should be
uploaded into the BSC chain, where the EnduranceValidatorHub smart contract can verify it
and validate the signatures from the Endurance chain.
Withdrawal (BSC -> Endurance): The withdrawal of funds is the opposite of the deposit flow.
The user must burn their pegged tokens in the BSC chain to use this proof to withdraw
tokens from the native asset bridge smart contracts. Validators in the Endurance network will
verify the correctness of this operation and prevent double-spend attacks.
Endurance developers can specify fees for cross-chain operations between the Endurance
and BSC chains, and these fees or fine-related mechanisms should be specified in the
Endurance smart contract rather than the BSC smart contracts or block verification
functions.
5.1 Endurance Validator Hub
Endurance provides native asset cross-chain functionality to BAS applications by default. In
order to register with Endurance, each application must specify the block header verification
function (BHVF) and is assigned a chain ID by the Endurance smart contract. BHVF verifies
block headers without state transitions and must be written in Solidity to check the block
header, the correctness of the chain for N blocks, and signatures. Endurance supports
default chain implementation with the Endurance Validator Hub. Still, other developers can
write their own verification function, provided that they pass code auditing to be trusted by
the community and avoid malicious functions or vulnerabilities.
The system contract address of the Endurance Validator Hub smart contract:
0x0000000000000000000000000000000000007000
5.2 Fast-finality and BLS cryptography
Parlia is a BFT-like consensus where only one Validator produces a block. To ensure the
correctness of this operation, we must wait for the confirmation time, which is usually
2/3*N+1, where N is the number of active validators (15 blocks for the current configuration).
Page 6
We must upload at least 15 blocks to the blockchain to prove one block. BLS cryptography
with Parlia's fast finality can solve this problem because we can collect one aggregated
signature and send only this signature to BSC. However, we need to know the BLS public
keys of each Validator. Currently, BLS cryptography is merged into the official geth
repository, but BSC does not yet support it. Applying these changes to the Parlia consensus
engine may take some time. Additionally, it is not strictly required to use BLS; geth has
support for the BN256 curve since the Byzantium fork, which can be used as a replacement
for BLS aggregated signatures.
Here are some possible solutions:
● Break compatibility with Parlia and implement fast finality in the Endurance version of
Parlia using the BN256 curve.
● Wait for BSC's version of fast-finality and BLS support.
● Given the many moving parts involved, consider fast finality as an optional solution
for Endurance.
5.3 System Smart Contracts
Each Endurance sidechain is also technology-agnostic, allowing developers to modify or
include any module within Endurance and use any consensus or runtime execution
environment. By default, Endurance provides an EVM execution environment with a set of
system smart contracts for platform operation. However, developers want to add more
functionality to their sidechain. In that case, they can implement it themselves or contribute it
to the official Endurance template to extend the default module set with additional extensions
that other developers can utilize in the future.
Predefined BSC-compatible system smart contracts:
● Staking (0x0000000000000000000000000000000000001000) - for managing
validator delegations and active validator set
● SlashingIndicator (0x0000000000000000000000000000000000001001) - for
slashing not active validators
● SystemReward (0x0000000000000000000000000000000000001002) - treasury for
the system rewards to cover relay fees and others
Endurance-defined smart contracts:
● StakingPool (0x0000000000000000000000000000000000007001) - a staking pool
that helps to aggregate stakes and optimize gas consumption for the reward
calculation
● Governance (0x0000000000000000000000000000000000007002) - default on-chain
implementation by Compund's Alpha governance
● ChainConfig (0x0000000000000000000000000000000000007003) - configuration
for the consensus that is managed by on-chain governance
● RuntimeUpgrade (0x0000000000000000000000000000000000007004) - smart
contract for managing runtime upgrades in the chain
● DeployProxy (0x0000000000000000000000000000000000007005) - a proxy for
managing ACLs for deploying and doing calls (under development, address is
reserved for future needs)
Endurance Whitepaper: summary, contents and background
This guide helps you understand the scope of Endurance Whitepaper before or alongside reading the original document. It is based on the catalogue record, credited creator, source, classification and topics shown on this page. It does not replace the original work and does not invent claims about passages that Doxxly cannot verify.
Summary and overview
Endurance Whitepaper is a 16-page documentcredited to Kaya G. Zephyr. This whitepaper describes Endurance, a BAS-based blockchain ecosystem launched by Fusion Interactive for gaming and social applications. It covers EVM-compatible infrastructure, modular architecture, native asset bridging, PoSA consensus, validator selection, staking, governance, transaction fees, and runtime upgrades. It also outlines the ACE token's stated 147 million total supply, allocations, rewards, and burning mechanisms, alongside developer tools, mainnet connection details, and legal disclaimers. It appears in the Technology & Security collection, which groups it with other material that readers may use for comparison and further study.
The item can be approached in several ways. A reader looking for a quick orientation can begin with the free five-page preview, inspect the page structure and use the metadata to judge relevance. Someone undertaking deeper research can work through the complete file, search its indexed text, record useful page references and compare its treatment of Endurance, Blockchain, Web3 gaming, Social applications, EVM, BAS, PoSA, ACE, Tokenomics, Staking, On-chain governance, Smart contracts with the related resources linked below.
Rather than reducing the work to a single claim, this page treats it as a source that should be read in context. The title, creator, publication source, licence and format all help explain what kind of evidence it may offer. Readers should distinguish the original author's statements from Doxxly's catalogue description, and should cite the original edition when using the material in academic, professional or published work.
Key topics and reader takeaways
The catalogue connects this document with Endurance, Blockchain, Web3 gaming, Social applications, EVM, BAS, PoSA, ACE, Tokenomics, Staking, On-chain governance, Smart contracts. These terms offer practical entry points rather than a substitute for close reading. Start by identifying the definitions, examples, arguments, tables or visual explanations attached to each topic. Then note where the creator draws connections, makes distinctions or moves from background material to a conclusion, recommendation, calculation or narrative development.
A useful reading method is to separate description from interpretation. First record what the item actually presents: names, headings, figures, formulas, quotations or stated propositions. Next consider why those details matter within the whole work. Finally compare them with another source from the same subject area. This process helps turn a long digital file into evidence that can be evaluated rather than merely skimmed.
Table of contents and reading guide
The following is an editorial content guide based on the verified catalogue topics. It is not represented as the original author's formal table of contents. Use it to organise notes while moving through the 16 pages in the player.
Part 1
Endurance
Use this section of the reading guide to identify how Endurance appears in Endurance Whitepaper, note important terms, and connect the subject to the wider purpose of the work.
Part 2
Blockchain
Use this section of the reading guide to identify how Blockchain appears in Endurance Whitepaper, note important terms, and connect the subject to the wider purpose of the work.
Part 3
Web3 gaming
Use this section of the reading guide to identify how Web3 gaming appears in Endurance Whitepaper, note important terms, and connect the subject to the wider purpose of the work.
Part 4
Social applications
Use this section of the reading guide to identify how Social applications appears in Endurance Whitepaper, note important terms, and connect the subject to the wider purpose of the work.
Part 5
EVM
Use this section of the reading guide to identify how EVM appears in Endurance Whitepaper, note important terms, and connect the subject to the wider purpose of the work.
Part 6
BAS
Use this section of the reading guide to identify how BAS appears in Endurance Whitepaper, note important terms, and connect the subject to the wider purpose of the work.
Part 7
PoSA
Use this section of the reading guide to identify how PoSA appears in Endurance Whitepaper, note important terms, and connect the subject to the wider purpose of the work.
Part 8
ACE
Use this section of the reading guide to identify how ACE appears in Endurance Whitepaper, note important terms, and connect the subject to the wider purpose of the work.
When a heading in the original differs from this guide, follow the original heading in your citation. Page numbers can also vary between editions. Doxxly's direct page field is useful for navigation, but formal references should include the title, creator, source and edition details available in the file itself.
About Kaya G. Zephyr
Doxxly credits Kaya G. Zephyr as the author or creator of Endurance Whitepaper. This page does not add an unverified biography, job title or institutional affiliation. The attribution is preserved so readers can distinguish the creator from the hosting library and follow the original record when an external author link is available.
Author context matters because a work reflects a particular purpose, audience and point of view. Before relying on the material, consider what the creator set out to explain, when the source was produced and whether later research or revised guidance should also be consulted. For literature and philosophy, compare translations and editions; for technical material, check whether a newer version has superseded the one shown here.
About the source organisation
The recorded source for this item is fusionist.io. Doxxly provides access and discovery tools but does not claim to be the original publisher unless explicitly stated. Source links, creator attribution and the recorded Publicly available file collected for editorial review licence are displayed to help readers assess provenance and permitted use.
Provenance is especially important for reports, standards, presentations and working spreadsheets. Check the original source for amendments, supporting files and current policy. A trustworthy research workflow keeps the source URL with any notes or downloaded copy, verifies important figures against the original, and avoids treating an archived document as automatically current.
Begin with the title and opening pages, then use the guide above to decide whether to read sequentially or move to a particular topic. The Doxxly player provides previous and next navigation, a direct page field, zoom steps, fit-to-width and fit-to-page modes, rotation and fullscreen. These controls are useful when a page contains small type, a wide table, an image, a scanned layout or a dense sequence of notes.
The first five pages are open to every visitor. A plan unlocks the complete item and full-document search. Search is best used for distinctive names, technical terms or short phrases; broad words can produce too many possible contexts. When you find a useful passage, read the surrounding pages so that a sentence, chart or formula is not separated from its explanation.
If downloading is enabled, members can obtain the original PDF file. Keep the original format when formulas, slide sequencing, pagination or layout carries meaning. Respect the Publicly available file collected for editorial review terms displayed on this page, and use the rights-report link if you believe the attribution or availability needs review.
Research questions to consider
As you read Endurance Whitepaper, ask which audience the creator addresses, what problem or idea organises the work, what evidence is presented, and which assumptions remain unstated. Note whether important terms are defined consistently and whether examples represent a broader pattern or a narrow case. For quantitative material, record units, time periods, formulas and data sources. For interpretive material, separate the creator's language from your own summary.
A second set of questions concerns relevance today. Which parts remain durable, which depend on their historical or institutional setting, and what would need confirmation from a newer source? Following the tags and the Technology & Security collection can reveal useful comparisons. Agreement between sources can strengthen confidence, while disagreement can point to changing definitions, methods, evidence or priorities.
Finally, decide what you need from the item: background knowledge, a quotation, a worked example, a model, a visual explanation or a starting bibliography. That purpose should guide the depth of reading and the notes you keep. Doxxly helps locate and navigate the source; careful interpretation remains the reader's responsibility.