Snippet of deployed (testnet) chainlink contract and a few transactions
Creating an external adapter to encapsulate API logic outside of chainlink contract
Adapter wraps a custom error response around the actual phone number API lookup
theGraph deployment process
Another view of validating the phone number and seeing the last phone validated event
Newly upload Phone Validator graph
Veriphone - Chainlink-backed phone validation
Yellow books are a thing of the past.
Veriphone is a project with the goal of creating the largest index of chainlink-validated phone numbers.
Not a DeFi or currency app, but a useful service.
Marketers and sales people have huge incentives for getting and checking for valid phone numbers to close deals. In the non-business world, it can also feel like the amount of spam phone calls have reached an all time high. Robocalls that originate from telephony (nonphysical address) services who act as imposters of people and locations has boomed due to an addition of services like twilio.com and bandwidth.com, for better or for worse.
Veriphone is a Chainlink app centered around a 'PhoneValidator' smart contract. This contract stores and emits events for phone validations whenever the contract validate method is invoked. Every update is tracked - phone numbers may be spam at one time and may later become a valid number.
The Veriphone contract service is currently free, and returns valid / isValid becased on the phone number entered.
Uses the APIFEX phone validation API in combination with Chainlink and theGraph.
Uses thegraph service to index the events emitted whenever a phone number is validated. Use graphql to find the history of a given phone number by entering it in the graphql interface.
The phone validation API currently returns an internal error whenever an invalid phone number is provided, making the API difficult to directly insert into a chainlink contract and work correctly. To bypass this, I set up an external adapter to proxy the chainlink API calls (via a lambda function) and process the event such that a consistent response could be delivered back to the smart contract.
Chainlink API calls were key to wire in the external phone validation data into the smart contract.
Every requested validation (as of the last deployed contract) is emitted as part of the smart contract and ready to be indexed by theGraph. See the attached schema and graphql interface. Using this service can open up possibilities for indexing and providing hosted / blockchain-backed phone records.
An event is broadcasted from the PhoneValidator chainlink contract every time a validation or lookup of a phone number is made:
event LastPhoneValidated( bytes32 indexed requestId, string indexed phone, bool valid, string location );
These are later indexed via thegraph.com
What's next for Veriphone:
- Add support for pulling more data out of the API response
- Could add paid validations in the future.
- Expand to support international numbers (US only).
Project is open source.
Chris Buonocore Prototyped for the Chainlink Hackathon 2020.