FREQUENTLY ASKED QUESTIONS

General

Any institution, may it be a public one, a local authority, or any private corporation that issues documents for which they wish to have an enhanced level of security and immutability.

We insert the metadata transaction ID and the Merkle proof back to certificate once the transaction is complete.

You can see examples of our validators as follows:

University of Nicosia: https://www.unic.ac.cy/verify/

University of Finance and Economics Mongolia: https://www.ufe.edu.mn/English/Default.aspx?page=9067

Ayia Napa Municipality: https://www.ayianapa.org.cy/validator.php

Block.co validators:

https://validator.block.co

https://testnet-validator.block.co

Please note that the list is not exhaustive as our technology is Open Source Code.

Copy and paste the transaction id on any public bitcoin block explorer to see all the details.

It has proved over the years to be the most secure blockchain.

We feel there is not much to gain by using Ethereum blockchain.For more insights regarding our design principles, please read the relevant article on our blog: http://blockco.kinsta.cloud/design-principles-future-directions/

With PDF signatures, one uses the traditional centralized Public Key Infrastructure (PKI). The issuers need to register with a Certificate Authority (CA) that will verify their signature and sign in turn that it is valid. This process is centralized and has several single points of failure that we want to avoid through decentralization. Please see article on our design principles.

Features

Yes. Thousands of documents can be issued in a single transaction.

Expiration dates can be set during the issuance phase as part of the embedded metadata. Therefore, when the validity period lapses, the verification process will indicate that the document has expired

Indeed. We have developed a methodology whereby documents can be revoked in case there is a need for that.

Any already issued document has no ongoing dependence on Block.co. These records are anchored on the blockchain that recipients own them for a lifetime.

Yes. Block.co allows you to upload and display all sorts of custom data on your document designs. In this case, you can use your unique number as a custom attribute on the document.

User Experience

ISSUANCE OF DOCUMENTS
Metadata relating to the document is attached to a PDF file.
A fingerprint of the whole document (PDF incl. the metadata) is included in a blockchain transaction.
The transaction details are added back to the metadata on the PDF file.
The vPDF documents are disseminated to owners.

VALIDATION OF DOCUMENTS
Go to an online validator found on issuer’s and other websites.
Upload the VPDF file.
Get an immediate response as to its validity including detailed information.

REVOCATION OF DOCUMENTS
An additional transaction is created on the Blockchain that
invalidates previous records without erasing audit trail. You may also set a date for an automatic expiry in the future.

Indeed, we do. We in fact consider this as a must for us to also get a better understanding of your company’s specific needs, requirements, and structure, so that we can deliver a product that best fits your profile.

No. Block.co makes it easy to anchor records on a blockchain and manages the transaction fees for you behind the scenes.

No. Our issuing system is a web-based application and can be used by anyone with basic administrative skills.

Through our platform you may easily issue a self-contained and self verifiable vPDF, the recipient would receive an email with a “call to action” to view their self-verifable document. Our documents are mobile friendly as well, so recipients can view them and verify them with one click, on their mobile devices.

Recipients receive their vPDF documents via email, and are able to share them for a decentralized and independent validation with whoever they choose to.

You have full control over the recipients, the appearance and other email settings through our platform.

Privacy – Data

The issue of Blockchain and GDPR compliance is one that will be discussed for some time still and until legislators decide to do something about it. GDPR legislation was passed in a pre-blockchain era and was fashioned with an implicit assumption that a database is a centralized mechanism for collecting, storing and processing of data. Which of course is no longer the case especially with public blockchains. In discussions we had with MEPs, they confirmed that GDPR legislation is meant primarily to protect against very large corporations exploiting their users’/clients’ personal data to make a profit. On the positive side, both GDPR and Blockchain at heart share the objective of data sovereignty, so blockchain could become a tool to achieve this objective. Blockchain could in theory make it easier for platforms and applications to become GDPR compliant by having this compliance inserted in the code, thus supporting data protection by design, one of the law’s primary objectives.

The identity of the issuer is important and needs to be verified. We deal with this by including several identity verification mechanisms. Right now, we support two such mechanisms. One is domain verification where the identity is proved by proving ownership of a specific Domain Name Server (DNS). Additionally, we provide a Block.co verification service where we take care of manually verifying the issuers. More verification methods will follow, like Keybase, Github or social media accounts

No. Our agreements clearly state that we’re not able to share your data with any third party that’s not bound by our data privacy agreement and that isn’t named on our data privacy agreement.

You’re always able to remove data you’ve provided to Block.co from our platform.

Yes, this may be easily done. You can export your issuance data as a spreadsheet, and your certificates as PDFs at any time, free of charge. You may also submit a request at any time to enquiries@block.co if you’d like Block.co to remove data that you’ve provided to our platform.

Your vPDF will be working fine, and vPDF recipients will be able to use them even if you stop using Block.co or even in the case that Block.co does not exist as an entity. You can visit or deploy the open source validating tool at any point and continue using the self-verifiable and self-contained digital documents at your will.

Getting Started

Block.co offers tailor made packages to accommodate your organization’s individual needs.

Talk with one of our client service officers.

Contact us today to discuss your requirements and provide you with a bespoke package.

Integrations

Yes, but extra charges will be levied.

Indeed. The product allows you to brand your records however you see fit.  Also, if you choose to disseminate your blockchain-anchored documents using our “public links” or “QR code” features, there’s the option to serve them under a subdomain of your organization.

All configuration work will be carried out by us, but we will, however, require a contact person in your IT department to work with during the setup/configuration process and also for any account maintenance work.

We provide access to our API so anyone interested can build an integration with their internal or external system of choice. You can find the API documentation here: https://api.block.co