Technical framework and features

Connect to each other and enjoy fast data transfers.

One can think of a connection to GRACE NET as similar to a VPN, in the sense that an additional server (driver) is inserted between the user and the wider internet. However, instead of concealing the user’s IP address, the GRACE driver in the middle speeds up data transmission (as opposed to a VPN, which usually makes it slower).

The driver is already available for Linux systems and will soon be available for Windows, iOS, and Android.

The more servers in a network are connected via the driver, the faster the connection. To enjoy all the benefits of GRACE NET, an organization needs to install the driver on all of its servers, even if they are positioned in the same room. However, the further the servers are from each other geographically, the larger the difference in speed between GRACE and traditional protocols. The tests already performed by the GRACE team have shown an increase in the average speed between 2x (transfers within Europe) and 50x (between London and Sydney).

GRACE partners that help develop the network will be rewarded with $GRACE tokens. It’s an attractive proposition for any individual or organization with computational resources, from a data center to a crypto miner.

Speed and efficiency

GRACE NET relies on a pioneering data packaging method to guarantee that all data packets arrive at a predetermined time and in the original sequence in which they were sent. This is particularly important for real-time applications, as well as blockchain networks and Web3 applications with their transaction data.

Bandwidth can be allocated and customized separately for each project or stream of traffic to make sure that its needs for scaling are met. GRACE NET also ensures that separate traffic streams don’t interfere with each other or create bottlenecks.

GRACE NET works parallel to DNS, aiming to establish direct connections that bypass unnecessary routes. By reducing the number of layers information must traverse, our approach ensures faster more efficient data transmission.

Most importantly, speed is maintained regardless of latency - a unique feature by GRACE as part of its IP. The actual transfer speed will keep growing as the GRACE network acquires more servers with the driver installed on them. However, already at this early stage, tests have shown at least a 30-50% improvement over regular data protocols on short-to-medium distances and an even larger effect for transfers across continents. The general rule is that the further two ecosystem participants are from each other, the higher the difference (in %) of transfers using GRACE over transfers with TCP/IP.

In our tests, GRACE NET using our innovative data packaging mechanism Packet 2.0 (see below) has consistently demonstrated higher bandwidth (for the same latency) than the data solutions by leading providers like Panasas, Aspera, and Fujitsu.

Security

Security is ensured through robust cryptographic methods, consensus mechanisms, and mathematical models, and cryptography to ensure fast and precise data transfers that don’t compromise security. At the same time, CI/CD (Continuous Integration/Continuous Delivery) practices enable automated and efficient deployment.

Data transmission with GRACE NET leverages TLS 1.3 for security, while Forward Error Correction (FEC) is employed to mitigate data loss without the need for additional transmissions. The protocol is fully resistant to L3 and L4 DDoS attacks.

Connections are established only between authenticated participants, and any attempts at unauthorized access are prevented.

Transfers with GRACE NET do not lead to data quality reduction, data duplication, or splitting down packets into multiple parts.

How did the system achieve "No sensitivity to DoS and DDoS attacks (L3, L4)"

All incoming packets to the server are placed in a ring buffer and connection service. After the handshake process is completed, the packets are passed on for further processing. This ensures no sensitivity to DoS and DDoS attacks (L3, L4).

Last updated