Blockchains are inherently transparent, with Zcash accounts have an extra ability — Shielded transactions. With this release, Amberdata supports RPC, REST & Websockets, enabling all the features you need without running expensive infrastructure.
Zcash now available in Amberdata.io
As stated by their website “Shielded Zcash transactions are completely private”, a technology made possible by specific zero-knowledge proofs called zk-SNARKs (zero-knowledge succinct non-interactive arguments of knowledge).
“Zero-knowledge” proofs allow one party (the prover) to prove to another (the verifier) that a statement is true, without revealing any information beyond the validity of the statement itself. For example, given the hash of a random number, the prover could convince the verifier that there indeed exists a number with this hash value, without revealing what it is. — Zcash
With shielded transactions comes a few scenarios that are worth noting. There are four cases or types of transactions that can occur:
NOTE: While it is possible to do all the above examples in direct requests without a library, it is faster and simple to show code with the SDK.
Go to Amberdata.io to Get Started.
Using the following code, we are able to configure requests for Zcash using a simple namespace variable. This configures the x-amberdata-blockchain-id under the hood, and instantiates all available methods. Click here to edit example →
The portfolio and address data is by far the most valuable information available. This is accessible either with individual address requests, or by passing multiple addresses and getting many balances at once.
For ongoing development, we’ve created a postman collection that covers all of our features and utilizes simple parameters so you can focus on building. Click here to download the collection directly, or go here for tons of resources: