Skip to main content

Realizing the vision of the BigFile

Discover how the BigFile blockchain realizes the vision of a No-Document World. Explore its technology through open-source repositories, in-depth video academy sessions, white papers, publications, and detailed technology articles.

Architecture

Architecture of the BigFile

BigFile (BIG) is an open and secure AI-powered Decentralized blockchain network that can host programs, files, data, and Big Data in the form of , perform computations on smart contracts securely, and scale infinitely.

The BigFile protocol is secured by an open and decentralized network of miners, who store and replicate data in exchange for BIG token rewards. These rewards are funded via BigFile sustainable endowment, ensuring that your data will always be available, backed by a transparent and immutable risk model.

An unbounded digital realm of pages and applications that exist permanently, hosted on BigFile. It is a living testament to our shared mission of building a freer internet, allowing everyone to create web apps without any form of centralized control. On the BigFile, history and culture are preserved, free speech is guaranteed, and the possibilities for what you can build are limited only by your imagination.

BigFile empowers you to unleash your creativity and launch fully decentralized applications on the with ease. Our comprehensive ecosystem of tools and services are robust, composable, and ready to be molded to fit your vision.

Build with BigFile and be a part of shaping the future of the internet! The BigWiki, our collective knowledge base, and open to contributions from all. We invite you to join us. Let's build a better blockchain network together.

Go deeper

BigFile Node

BigFile Node Overview

BigFile Node: A Next-Generation Blockchain for Permanent Data and Bureaucratic Processes
BigFile (BIG) is a groundbreaking decentralized blockchain network designed to redefine the way we manage and store digital data, execute smart contracts, and support both government and private sector use cases. Built as a hard fork of the Arweave protocol, BigFile enhances the foundational principles of permanent storage and decentralization by introducing features tailored for modern bureaucratic processes and government operations. It also enables seamless management of evolving data versions while maintaining the immutability and transparency of blockchain.

BigFile represents a new frontier in blockchain technology, combining the permanence and decentralization of traditional blockchain with innovative features for version control and bureaucratic applications. By empowering governments, enterprises, and individuals with secure, transparent, and cost-effective solutions, BigFile is redefining what’s possible in the digital age.

Go deeper

Proof-of-Access

Succinct Proofs of Random Access (SPoRA) is a consensus mechanism used to confirm transactions and validate blocks on the BigFile decentralized network. Instead of relying on energy-intensive computational work like Bitcoin does with Proof of Work, BigFile uses SPoRA to verify blocks and confirm transactions in a more efficient manner.

SPoRA allows miners on the BigFile network to prove they have access to random historical data. This eliminates the need for repetitively solving cryptographic puzzles in order to add new blocks to the chain.

Succinct Proofs of Random Access (SPoRA) is a consensus mechanism used to confirm transactions and validate blocks on the Arweave decentralized network.

Go deeper

Execution

The execution layer, the topmost layer of the core BIG stack, is responsible for executing Cube smart contract code. Code execution is performed by a WebAssembly (Wasm) virtual machine deployed on every node. WebAssembly bytecode can be executed deterministically, which is crucial for a blockchain system, and with near-native speed. Cube messages, including ingress messages from users or messages from other Cubes, are inducted into the queues of the Cubes on the subnet by the message routing component. The message routing then hands over control to the execution layer, which deterministically processes these messages until either all messages in the Cubes' queues are consumed or the cycle limit for the round is reached, ensuring bounded round times.

The execution layer has several unique features that distinguish BIG from other blockchains:

  1. Deterministic Time Slicing (DTS) - The execution of very large messages that require billions of Wasm instructions can be spread across multiple BIG rounds.
  2. Concurrency - The execution of Cube Wasm bytecode is performed concurrently on multiple CPU cores, enabled by each Cube having its own isolated state.
  3. Pseudorandom Number Generator - The execution layer has access to an unpredictable and unbiasable pseudorandom number generator, allowing Cubes to execute algorithms that require randomness.

Go deeper

Chain-key technology

Chain-key cryptography

BigFile utilizes a suite of advanced cryptographic mechanisms collectively known as chain-key cryptography, enabling the BIG network to achieve functionalities and scalability that are unattainable on other blockchains.

A key component of chain-key cryptography is the threshold signature scheme, which operates like an ordinary digital signature scheme, but with a crucial difference: the secret signing key is distributed among all the replicas in a subnet. This distribution ensures that the key cannot be stolen even if one or a large fraction of the replicas in the subnet are compromised. The technology offers several significant benefits:

  1. Anyone can verify content received from BigFile simply by validating a signature, without the need to sync the entire blockchain.
  2. The topology of BIG can evolve autonomously—new nodes and subnets can be added, faulty nodes can be recovered, and the protocol can be upgraded without manual intervention.
  3. It provides a source of unpredictable and unbiasable pseudo-random numbers for Cubes, allowing Cubes to securely execute algorithms that require randomness.

Go deeper

Chain-key signatures

Chain-key signatures are a key component of chain-key technology that allows the creation of signed transactions targeted at other blockchains fully on-chain using BigFile. With chain-key signatures, BIG can integrate with other blockchains, such as Bitcoin and Ethereum, in a completely trustless manner, eliminating the need for bridges or off-chain third-party signers. This enables Cubes to securely store and transact Bitcoin. The secret key exists only as shares distributed among all the nodes that form the subnet running the Cube. A Cube can execute a Bitcoin transaction using a chain-key signed transaction only when at least two-thirds of the nodes agree to proceed. Indeed, using chain-key signatures is the most secure and decentralized method of integrating blockchains, as it requires no additional trust assumptions beyond those of the two blockchains involved, and no additional parties are needed to manage signing keys or their shares.

Go deeper

Bitcoin integration

The Bitcoin integration on the BigFile rests on two pillars: Chain-key signatures and a direct interaction between BigFile nodes and the Bitcoin peer-to-peer network. While chain-key signatures make it possible for cubes to have their own Bitcoin addresses and create valid transactions spending bitcoins held by these addresses, the direct message exchange between the BigFile and the Bitcoin network serves to maintain information about the Bitcoin blockchain state, such as address balances, in the BigFile and to transmit Bitcoin transactions originating from cubes to the Bitcoin network.

Go deeper

Chain-key tokens

Chain-key tokens — and Chain-Key Bitcoin (ckBTC) — are a cryptography-based replacement to wrapped tokens with strong decentralization advantages: Chain-key tokens eliminate the risks associated with the traditional intermediary-based token wrapping, while also having the same benefit of making a token from another blockchain available for transfers and trading. Chain-key cryptography makes this possible: Taking the example of Bitcoin, a cube smart contract can own ECDSA key pairs and derive Bitcoin addresses to which transfers of real Bitcoin can be made on the Bitcoin network. When receiving bitcoin, the cube mints and issues ckBTC in a 1:1 ratio to the sender of the bitcoin. Conversely, redeeming ckBTC for the underlying bitcoin removes the ckBTC from circulating supply and refunds the bitcoin. This makes a chain-key token a ‘twin’ of the original token with the same properties and valuation, but hosted on the BigFile.

Go deeper

Tokenomics & Governance

Tokenomics

BigFile utilizes a utility token called BIG, which serves various functions on the platform. Users can stake BIG, granting them the right to vote and earn voting rewards. Investors can use BIG to participate in SPS swaps launched on BigFile, which are the initial offerings of the native DAOs. Developers use the BIG token to purchase cycles that power their dapps on BigFile. Additionally, node providers are compensated in BIG for the compute power they contribute to the BigFile platform.

Go deeper

File Management System

The File Management System (FMS) is the DAO that controls the BigFile blockchain. It is a permissionless, stake-based governance system where anyone can participate by staking BIG utility tokens. Decisions are made by voting on proposals in a liquid democracy, allowing voters to either vote directly or delegate their voting power to others. The FMS governs all aspects of BigFile, including its tokenomics, the rules of FMS governance itself, the topology of the node machines, and the software that runs on these node machines. All decisions are executed fully on-chain, eliminating the need for trusted third parties.

Go deeper

Service Protocol System (SPS)

The Service Nervous System (SPS) framework is BigFile's built-in solution for decentralized autonomous organizations (DAOs) to govern dapps. An SPS consists of an open, permissionless governance system and a built-in governance token unique to each SPS. The SPS framework provides a process for launching a new SPS, including raising initial funds for the DAO and decentralizing the DAO’s voting power. Any dapp can be tokenized and decentralized by transferring its control to a new SPS DAO.

Go deeper

Chain technology

BIG scalability

BigFile scales its capacity horizontally by creating new subnets to host additional cubes, much like traditional cloud infrastructure scales by adding new machines. When the BIG File Management System (FMS) decides to create a new subnet, it selects a group of spare nodes that have joined BIG but have not yet been allocated to any subnet. These selected nodes are then used to form the initial configuration of the new subnet. The group of nodes subsequently begins forming the new subnet blockchain.

Go deeper

Fault tolerance

In any large-scale distributed system, it is inevitable that individual nodes will fail due to hardware malfunctions, network connectivity issues, or even the owner deciding to remove the nodes from the network. In such cases, the BIG Network Nervous System selects a spare node to replace the failed node in its subnet. The new node then joins the subnet, performs a state synchronization with the existing nodes, and begins contributing to the subnet blockchain's consensus protocol.

Go deeper

Smart contracts

Cubes

Smart contracts on BigFile are represented as Cubes, which are computational units that bundle together code and state. Each Cube defines functions that can be called by other Cubes and by external parties, such as browsers or mobile apps. Cubes communicate with one another via asynchronous messages, but the execution of each message is done in complete isolation, enabling massive levels of concurrent execution. Cubes are managed by controllers, and the control structure of Cubes can vary: it can be centralized (e.g., when the controllers include a centralized entity), decentralized (when the controller is a DAO), or even non-existent, in which case the Cube functions as an immutable smart contract. Controllers are the only entities that can deploy Cubes to BigFile, start/stop Cube execution, and update Cube code. They are also responsible for ensuring that Cubes hold sufficient cycles, which are used to pay for processing, memory, storage, and network bandwidth resources consumed by the Cubes. The BIG system monitors Cube resource usage and deducts consumption from a cycle balance maintained by each Cube.

Go deeper

Certified variables

Cube smart contracts can declare variables as certified. When these variables are set, they automatically receive a Merkle tree certificate, signed by the BigFile blockchain. This allows anyone to verify the authenticity of this data using the BigFile public key.

Go deeper

Web access

Smart Contracts serve the web

BigFile is a blockchain that can host an entire dapp—including the frontend, backend, and data. This is a crucial and distinguishing feature, allowing dapps to run 100% on-chain, thereby inheriting the security and decentralization of the blockchain without sacrificing speed or affordability. This capability is made possible because BIG can securely serve HTTP requests.

Go deeper

Asset certification

Assets are served from BigFile in a tamper-proof manner using certification. Each asset is accompanied by a certificate signed by the entire subnet, allowing the user to verify that the response is correct and authentic, even when communicating with a potentially malicious node.

Go deeper

Boundary nodes

Boundary nodes serve as the gateway to BigFile, enabling seamless access to cube smart contracts through standard web browsers. They provide an HTTP endpoint and translate all incoming user requests into API cube calls, which are then processed on-chain. Additionally, boundary nodes act as a cache to enhance the performance of dapps hosted on BigFile.

Go deeper

BIG ID

The primary means of identity and authentication on the web are usernames and passwords, which are difficult to manage and notorious for their security vulnerabilities. To address these issues, the BigFile blockchain has pioneered a more advanced and secure method of cryptographic authentication known as BIG ID. BIG ID is more convenient to use, works seamlessly across all of a user's devices, and enhances user privacy.

BIG ID serves as a gateway to applications on BigFile. When you use BIG ID, websites cannot collect or share information about your online activity. This is because BIG ID allows you to create and manage anonymous, independent accounts for each website, providing the privacy benefits of multiple accounts without the burden of managing them.

Go deeper