Quadrant’s Testnet is Live!
As promised and on schedule, we are happy to announce that our Testnet is live!
Quadrant’s Testnet and our first feature -data stamping- has been operating successfully over the last few weeks, stamping a client’s live data feed. Data stamping is designed to provide data authenticity from the data source to the data consumer, which acts as the foundational layer of trust in the network. By putting the data signature on the block, the Quadrant Protocol will be able to track the movements of the data and understand where there have been manipulations. This is set up to ensure data authenticity and help track provenance for compliance applications.
We’ve reached our goals during the extended tests –working with a real prototype for one of our clients- so we’re very confident in being able to launch the mainnet as planned. If your company would like to be some of the first to be using Quadrant on launch reach out to use at our contact details below.
Facts related to Quadrant Protocol:
· Quadrant’s blockchain is up and running, with real client data being stamped
· Throughput tests show that Quadrant would enable tens of thousands of data feeds to stamp the signatures of 1.92 TB worth of data per minute onto the chain.
· The Producer Client is handling files upto 500MB per stamp.
· The Quadrant Producer Client is stamping a data pipe that has 300–400MB every 5 minutes.
· Depending on the data, clients could stamp their data at a cadence that best suits their needs. From our research we see feeds being at sizes of 50MB to 400MB being an ideal balance between # of stamps and data stamp processing rates.
· Quadrant is an Ethereum sidechain with Proof of Authority consensus
· It is a highly enterprise secured sidechain that combines speed, security, and cost efficiency.
Our Producer Client processes a data feed that delivers 300–400MB every 5 minutes.
When the data is saved into the S3 buckets, the Quadrant Producer Client is triggered and hashes the data
This data hash along with the meta data of the feed is combined and sent to be stamped into the Quadrant network.
The Data Consumer, upon receiving the data, runs the Quadrant Consumer Client, hashes the data, and verifies the data on the chain prior to consumption.
Quadrant Producer Client — Data Stamping
As soon our clients need to stamp and validate their data, they can execute our data stamping mechanism. Click to learn more about data stamping. A unique ‘transactionId’ is created to indicate the transaction, while a ‘blockHash’/’blockNumber’ is created as reference of the block which includes the stamping transaction which includes the hash and meta data, so it is allowing at a later stage to compare and conclude the authenticity of the data they have transitioned. As each block has a timestamp identifying the time the data have been stamped.
Blocks are created every five seconds. A user can search the unique block number/block hash/Transaction hash/Account address to proceed with the search feature. Upon exploring the blocks, users will be able to view all the transactions inside the block, the sending/receiving smart contract/account addresses and total gas consumption. For illustrative purposes, the above visual block explore is shown.
Data Consumer Client
The data can identify by running a Quadrant Consumer Client which searches the data hash to make sure that the stamping transaction is authentic, to which block stamp has been occurred and extensive details related to the transaction.
This simple yet powerful first feature of Quadrant is the base foundation what is to come ahead. Next, we will be enabling the next generation of Data Smart Contracts to be deployed into the network.
Technical Next Steps
With the throughput and real-client use case validated, our next steps will be to continue test the robustness of the Producer Client against other data feed scenarios and launch the Mainnet.
We will be releasing news soon on some major partnerships and first users of Quadrant. Stay tuned!
Official website: www.quadrantprotocol.com