Zinc - putting trust back at the heart of hiring

The mission

To become the world’s first proven careers ledger & trusted hiring network.
Empowering workers as the rightful owner & controller of their career & skills data.
Creating an ecosystem without prejudice, one which you’re solely judged on proven skills.


Former recruiter and Zinc co-founder, Luke Shipley, was so frustrated by the state of affairs that he decided to find a better way. Envisaging a recruitment journey that empowers workers and levels the playing field, the idea for Zinc was born. It’s a platform that brings transparency and privacy back to recruitment, protecting workers data and giving them ownership of their work identity. For the first time, recruitment has an ecosystem where individuals, companies and recruiters can interact fairly and make hiring decisions based on real, trusted insights / work proof.

  • Every individual has the right to fully own data on their skills and experience. Nobody should be tied to centralised platforms, where data ownership lies with a third party.
  • No worker should be subject to prejudice over age, gender, nationality, race or the university they went to. Recruiters should adopt anonymised recruitment practices wherever possible.
  • Workers should be judged on their personal attributes and skills only.
  • Workers should have control over when they interact with employers and recruiters, and not be subject to data abuse.
  • As a legal right, every worker should have a platform to access and own their work data and control their professional identity.
  • In a tokenised world, everyone should be rewarded for sharing data.
  • Referencing and background checks should be standard practice for all hiring journeys, giving employers verified evidence of employee skills and experience, via streamlined referencing tools.
  • Employers should be able to trust, and have a way of verifying, candidate claims regarding work experience, skills and qualifications.
  • Employers should have access to a wider range of work proof relating to candidates, including previous test results, interview feedback and background checks — where authorised by the candidate.


Zinc, the blockchain based hiring platform, is one of the first companies in the UK to secure funding through a crowdsale, raising £2.2 million in one month. Transparent and authenticated proof of career experience and qualifications. Hiring tools to make better decisions every time. Zinc mainnet was going live 17 september. The product is on the website.

Zinc is a FORBES contributor

Zinc are thrilled to announce that Co-founder, Luke Shipley will be a regular Forbes contributor to the crypto & blockchain section, submitting 3–5 articles per month. This is an amazing opportunity for Zinc and will give them substantial brand exposure in a relevant field.

Zinc Smart Contracts Architecture

Zinc contracts are inspired by the ENS architecture where the upgradability is left for the user to decide and users may be perfectly happy with the current logic and are free not to upgrade and still use the system. The philosophy of the contract is very simple: every user will have an Identity Contract which only they control and can revoke permissions of other apps as they wish. The idea is that dApp contracts can ask the user for permission to interact with their identity contract and the user can allow for certain permissions. The dApp contract’s address gets added to the users Identity Contract. One important thing to note here is that interaction among contracts is encouraged in this framework as we can have well-defined behaviours within the contracts which can be audited by the community.

More about it in the article.

Entering the world of IPFS

IPFS — Interplanetary File System is awesome for storing data in a decentralised fashion and it’s one of the most commonly used tools for storing data within the blockchain space. Storing data within a Blockchain is expensive and slow, storing in IPFS is free and fast. IPFS does not allow duplication of data by hashing it and hashing the same data twice will give back the same hash.

IPFS seems to work really well. You can add data and it stays in this global network of nodes. Anyone with a hash can access the data (note that all data on IPFS is public unless you use a private IPFS node) and the same data is not duplicated. The question that you might be asking at this point is, “Can I change my database with IPFS and become fully decentralised?”

While IPFS is great at storing your data, it does not give any guarantees of the data being available if your IPFS node goes down. Confused? Imagine this. You start your IPFS node, run it for a month and have very important data within it. Your machine breaks, you’re thankful it’s a public network so other people will have your data, right? Not quite, IPFS never guaranteed your data will always be available. No other node was interested in it and therefore no one else pinned your data except your loyal node. Consequently your data is lost since no other node has it.

More about it in the article.

Keith Teare’s take on Zinc (formerly R_Block)