Since a token or NFT is minted, the records of transfers, sales, burns, listings, etc., are precious information that should be stored in the blockchain. This information ensures the traceability of digital assets and provides transparency, security, the origin of the property, and many other benefits.
Traceability is a process in which information is recorded to show the trajectory of a digital asset over time. This feature allows expanding the use cases of NFTs in sectors such as logistics, food and manufacturing, among others.
So far, each token and NFT on the Internet Computer needed to build, maintain, and pay for its own custom history integrations. CAP has created a standard for transaction history/provenance that any experienced developer can integrate through an API (Application Programming Interface) into their project's canister in a process that should take no more than 30 minutes.
CAP, the digital footprint of the Internet Computer
CAP (short for Certified Asset Provenance) is a project that is part of the Psychedelic collective; a decentralized product studio focused on building products on the Internet Computer.
This tool is an Open Internet Service (OIS) on the Internet Computer that developers can utilize to give traceability and provenance with a transaction/history service to their fungible and non-fungible tokens.
Integrating CAP will be made especially easy with the help of the CAP SDK (Software Development Kit). Regardless of if you’re a new or existing project, the SDK will spawn a transaction history (Root Canister) for the NFT/Token and start receiving/storing records from these assets with only a couple of lines of code. CAP's main canister (Root Canister) acts as an orchestrator that can generate new history canisters for individual projects (NFTs, Token Canisters, DEX's, etc.).
Learn how to use CAP SDK in the following user guide.
Now that your CAP history canister is bustling with transaction data, consuming it will be just as easy, if not easier, than generating it. Uis (User Interface) and apps will query any Token or NFTs transaction history and surface it for its users. This will be done using the CAP-js, a javascript library that will allow any frontend (part of the software that interacts with users) to communicate with CAP's main canister to query data from any integrated asset.
Learn how to use CAP-js in the following user guide.
CAP does the heavy lifting so you can simply register, insert and query records to focus on your application.
Official Channels: Website | Twitter | Discord | Github | Documentation
CAP Crowns: NFT Collection
Imagine owning a 3D crown that in the future could be brought into the metaverse to royal-up avatars or be used as props/accessories for other NFTs.
The crowns in this collection are an unbeatable opportunity of 10,000 unique NFT that showcase a design with different forging themes. Lava, ice, galactic elements, or gold, among others, are combined with a wild mix of rare jewels and materials to design animated 3D crowns that are minted into GIFs.
In addition, these NFTs can potentially have future utility within the CAP/DAO Protocol itself once it is fully launched as an open internet service on the Internet Computer!
The great incentive of this project is to show the potential of CAP, where it shows the power of having transaction history and full traceability. Since its launch, the ecosystem of projects integrating or planning to integrate CAP has been growing steadily, as can be seen below:
Crowns won't be initially transferrable, but shortly after the collection's release, a marketplace will be launched, and transfers will be enabled. The NFTs in this collection will have a built-in 2,5% royalty fee.
For additional information, please visit the NFT collection website, the following article, and this announcement.
Conclusion
Projects developing on the Internet Computer had no standard for recording digital asset data, so transaction history was developed individually by projects (each token or NFT would have to implement it on its own). With many different token standards (fungible and non-fungible), an application that wants to consume history data from multiple sources would have to implement each source by hand.
CAP solves the above problem by creating a standard through an API that allows it to be used by any Internet Computer project to facilitate the work of software developers and the interoperability of the records of different digital assets.
Connect With Dfinity Community:
Twitter | Telegram | Instagram | Facebook | Email
More on Psychedelic DAO
Daniel James
Connect with Psychedelic DAO
Twitter | Discord | Website | GitHub | Medium
- Disclaimer: The views and opinions expressed on this website are solely those of the original author and other contributors. These views and opinions do not necessarily represent those of the Dfinity Community staff and/or any/all contributors to this site.
Comments are for members only. Join the conversation by subscribing 👇.