Contact us for a free demonstration and integration consultation.

A special driver developed by GRACE, when installed on two or more servers, dramatically increases the speed of data transfer between them. The effect reaches 30% for servers physically located near each other and over 100% for physically distributed servers. Any server carrying a GRACE NET driver instance can communicate at high speeds with any other server with the driver installed.

GRACE NET integrates seamlessly with Web3 and Web2 network infrastructures, requiring only minimal adjustments like installing a driver and configuring a firewall. GRACE NET operates alongside regular transport protocols, bypassing unnecessary routes and reducing the number of levels through which data packets must pass.

Yes! GRACE NET can speed up any kind of app or network in Web3 and Web2. It’s a core-level solution, both industry-agnostic and chain-agnostic, meaning that it integrates well with just about any project.

Yes, the solution is live and has passed dozens of speed tests and a security audit. GRACE NET will be ready for the first wave of partner integrations by Q2 2025, but we can already onboard projects and start working on customizations.

Of course! We offer remote server demonstrations to showcase the capabilities of our technology. Click on the button at the bottom of the page to schedule a free demo and consultation.

GRACE NET supports all existing operating systems and can be integrated with any blockchain. The driver for Linux is already available, while versions for Windows, iOS, and Android are coming soon.

Not at all. GRACE NET operates in parallel with or on top of other transport protocols, ensuring interoperability without interference.

Once we have specified the transmission speed, the integrity of the packet is controlled by cyclic redundancy check code (CRC32) that prevents accidental data changes. Quality is maintained through retransmission or recovery using FEC encoding.

Once the transmission speed is set, a specially designed scheduler deterministically distributes the total bandwidth among applications, thereby eliminating interference between different traffic streams.

For the time being, we don’t use blockchain for this purpose, as it would be expensive and inefficient. Instead, a key counter is saved, and the following session begins with the latest value of the key counter. We will consider blockchain for this in the future, though, as long as a fast and cheap enough solution can be found.

For connections, GRACE uses a two-way handshake process. It’s a simple protocol that’s widely used in TCP: the client sends a synchronisation message and the server accepts it and sends an acknowledgement message.

All incoming data packets are placed in a ring buffer and linked to the connection service. After the handshake process is completed, the packets are passed on for further processing. This ensures sufficient protection against DoS and DDoS attacks.

We use UDP solely to bypass firewalls and NAT. GRACE NET forms a header when it transmits files and discards it once data they have been received, but the use of the port 3000 in itself doesn’t make GRACE NET faster.