BigFile Private Testnet

Roadmap
,
1

The BigFile Project operates as a limited-access development network ahead of the beta testnet release. Detailed updates, announcements, and explanations will be regularly shared on our Forum page. We welcome community contributions and encourage interested developers to contact us for access.

BigFile Node Test Server Announcement

Please note that during the test phase, block data may be reset continuously. We strongly advise against uploading any data to the network with the intention of storing it permanently at this stage.

Currently, the node software is activated solely for testing purposes during the development phase. These nodes are operating as secure peers across multiple servers to ensure reliable network testing and stability.

Below are the details of the test server addresses and IPs for your reference:

  • Test Server 1: IP: http://thebigfile.info:1984 - 65.108.0.39:1984
  • Test Server 2: IP: 213.239.206.178:1984
  • Test Server 3: IP: 185.234.70.205:1984

We appreciate your participation in this phase and welcome any feedback or bug reports you may encounter. Please share your observations in the designated testing feedback channel or contact us at team@thebigfile.com.

Thank you for supporting the development of BigFile.

2

Test Node Update:

After three days of monitoring, the test node has shown excellent performance. The node is producing healthy blocks, and the mining node is operating efficiently. We’ve successfully conducted data upload tests, including documents and images, to the network.

While many operations are running smoothly, we’ve observed a significant increase in data upload fees as the block count grows. To address this, we will restart the private test network with updated pricing parameters.

Stay tuned for more updates!

3

The BigFile network’s Private testnet seems to be successful. The operations performed on the Private testnet are listed below.

Private testnet termination block information.

{"version":1,"release":1,"queue_length":0,"peers":4,"node_state_latency":1,"network":"BigFile.V1","height":5818,"current":"774lIm_55qzW-tLuSl-J4mUz7zSvXIKOM5he3eeOWzFarRZhoQTKLRlFCJycd0L1","blocks":5819}

BigFile Network Test Results and Status Report

1. Basic Transaction Tests

:white_check_mark: Successful Tests:

  • Blockweave architecture working successfully
  • Inter-node communication stable
  • Hash verification mechanism working smoothly

:arrows_counterclockwise: Ongoing Tests:

  • Rapid synchronization of new nodes
  • Optimization of Blockhash and Wallet lists

2. Data Query and GraphQL

:white_check_mark: Working Features:

  • Network status can be queried successfully
  • Recent transactions and blocks can be monitored
  • :warning: Query delays experienced on some nodes

3. Large File Operations

Status:

  • :white_check_mark: Chunk-based upload system working
  • :warning: Upload speed optimization needed for large files
  • :white_check_mark: Progress tracking successful
  • :warning: Chunk synchronization issues in some cases

4. ANS-104 Protocol Test

Results:

  • :white_check_mark: Protocol implementation working
  • :white_check_mark: Chunk calculations accurate
  • :warning: Performance improvement needed for large files

5. Network Stress Test

Findings:

  • :white_check_mark: Node synchronization generally stable
  • :warning: Some peers may drop under high load
  • :warning: Fluctuations in block production rate

6. NFT and Collection Tests

Status:

  • :white_check_mark: NFT creation and metadata operations successful
  • :white_check_mark: Collection management working
  • :warning: Indexing delays experienced with large collections

7. Data Indexing

Results:

  • :white_check_mark: Transaction indexing working
  • :white_check_mark: Tag-based querying successful
  • :warning: Indexing performance needs improvement for large datasets

General Assessment

Strengths:

  • Basic block operations stable
  • Chunk-based upload system functional
  • NFT and metadata management successful
  • Transaction verification mechanism reliable

Areas for Improvement:

  1. Large file upload performance
  2. Node synchronization speed
  3. Stability under high load
  4. Indexing performance
  5. Peer management optimization

Next Steps:

  1. Optimize chunk upload algorithm
  2. Strengthen node synchronization mechanism
  3. Improve peer management system
  4. Enhance indexing performance
  5. Expand stress test scope

Technical Details

Upload System:

// Chunk upload implementation
while (!uploader.isComplete) {
    await uploader.uploadChunk();
    console.log(`Upload: ${uploader.pctComplete}%`);
    await new Promise(r => setTimeout(r, 500));
}

Node Synchronization:

// Node sync check
const peers = await arweave.network.getPeers();
for(let peer of peers) {
    try {
        const peerInfo = await arweave.api.get(`http://${peer}/info`);
        console.log(`Peer ${peer}:`, peerInfo.data.height);
    } catch (err) {
        console.log(`Peer ${peer}: Unreachable`);
    }
}

Performance Metrics:

  • Average upload speed: 2.5 MB/s
  • Node sync time: ~15 minutes
  • Block production rate: 2.1 blocks/minute
  • Transaction confirmation time: ~3 minutes

Current Status

Production Ready:

  • Basic transactions
  • File uploads < 100MB
  • NFT operations
  • Basic querying

Under Development:

  • Large file optimization
  • Advanced indexing
  • Peer management improvements
  • Performance optimizations

Known Issues:

  1. Chunk upload timeouts on files > 1GB
  2. Peer list synchronization delays
  3. Indexing bottlenecks on large datasets
  4. Memory usage optimization needed

Community Feedback

We welcome community input on:

  • Performance optimization suggestions
  • Feature requests
  • Bug reports
  • Integration experiences

Note: These test results are continuously updated. Community feedback and contributions are valuable. Please share any issues or improvement suggestions through the forum.