<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by CAP on Medium]]></title>
        <description><![CDATA[Stories by CAP on Medium]]></description>
        <link>https://medium.com/@cap_ois?source=rss-a4ee56a03e67------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7XYmU9j8K2IZP5Xxj5J7fw.png</url>
            <title>Stories by CAP on Medium</title>
            <link>https://medium.com/@cap_ois?source=rss-a4ee56a03e67------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:48:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cap_ois/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Scaling CAP from Now to Next]]></title>
            <link>https://medium.com/cap-ois/scaling-cap-from-now-to-next-7467473fd56a?source=rss-a4ee56a03e67------2</link>
            <guid isPermaLink="false">https://medium.com/p/7467473fd56a</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[dfinity]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[CAP]]></dc:creator>
            <pubDate>Thu, 25 Aug 2022 15:14:57 GMT</pubDate>
            <atom:updated>2022-08-25T15:14:57.489Z</atom:updated>
            <content:encoded><![CDATA[<h4>Explore CAP’s architecture and our plans to break free from its current scaling limitations through stable storage &amp; self-spawning buckets.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-J8vs8r357d5p76V.png" /></figure><p>TL;DR:</p><p>We’re taking a look at CAP’s architecture and its limitless scaling ability via new upgrades coming up in the next months:</p><ul><li><strong>By using horizontal scaling, CAP gets more scalable as more canisters get integrated.</strong></li><li><strong>Using stable storage as the primary transaction storage point will put an end to upgrade failures</strong></li><li><strong>Allowing buckets to spawn themselves will allow increasingly popular dApps to benefit from infinite transaction history being stored.</strong></li><li><strong>Stay tuned for our upcoming IC-kit toolchain, a Rust-based &amp; open-source canister development kit letting anyone write safe canister smart contracts.</strong></li></ul><p>Haven’t heard of CAP (Certified Asset Provenance) before? It is the transaction layer of the Internet Computer. Learn more about CAP <a href="https://medium.com/cap-ois/announcing-cap-asset-history-on-the-internet-computer-a6788283c8f3">here</a>.</p><p>With the Internet Computer’s recent growth, we wanted to give an in-depth <strong>technical explanation of the architecture</strong> that allows CAP to scale and <strong>outline the future steps we’re taking</strong> in order to further increase its scalability.</p><p>Read on for a deep-dive. 🤿</p><h3>CAP Scaling 101</h3><p>Currently, CAP uses horizontal scaling, meaning that it becomes more scalable as more canisters get integrated.</p><p>The entire canister interaction takes place under the hood, through the CAP Router, without requiring extra input from users or projects. The Router is CAP’s orchestration canister and is responsible for entry point interactions with the CAP network. When your token contract integrates CAP, it communicates with the Router during the handshake process and initiates a CAP (Root) Bucket to start storing transactions.</p><p>Keep in mind that we do require the token or NFT contract to call the management canister and spawn a new canister, which will end up on the same subnet as the token contract. <strong>This guarantees instant and low-cost insert delivery to the smart contracts.</strong></p><h3>Storage Limitation</h3><p>Currently, Cap Buckets can store up to 4GB of transaction history. This limitation comes from the heap storage provided to the canister. During upgrades, we write this data to the stable storage in a pre_upgrade, only to restore the data in a post_upgrade. However, the Internet Computer allocates 8GB of stable storage to canisters that we can take advantage of (hint, hint).</p><p>Despite the 4GB transaction history storage limit, the majority of dApp contracts integrated with CAP generally use only a fraction to store their transaction logs.</p><p>The only two canisters currently using more than 2GB worth of transaction history are the <a href="https://sonic.ooo/">Sonic</a> and <a href="https://dank.ooo/wicp/">WICP</a> buckets. With almost 2GB left to spare, our team of trip advisors (aka the Psychedelic core team) has already run into issues <strong>— these two buckets when we were unable to perform the upgrade during our most recent attempt last week</strong>.</p><p>In its current state, the <em>pre_upgrade</em> hook on the IC should be able to finish the transaction execution in one block. However, we have discovered during our latest upgrade that one block was <strong>not sufficient</strong> to encode and write the entire transaction batch to the stable storage.</p><h3>Scaling Solution</h3><p>We believe that we’ve cracked the code to break free from the current limitations… 🔐</p><p>… and the answer is <strong>stable storage</strong>!</p><p>We will be moving to a <strong>stable storage first architecture</strong> in the upcoming months — we will use the stable storage as the primary transaction storage point and the heap memory allocation mechanism to only cache the query results.</p><p>Our team is also planning a feature allowing buckets to spawn themselves, instead of first calling the management canister. This way, if your dApp skyrockets in popularity and ends up running out of the available 8GB worth of stable storage, it will have its transaction history stored to infinity and beyond.</p><h3>What’s Next?</h3><p>We (PsychedelicDAO) are continuing to build our own toolchain for the IC called the IC-Kit. It is a comprehensive Rust-based, open-source canister development kit for the Internet Computer.</p><p>Once ready, the toolchain will enable anyone to write safe canister smart contracts and will help facilitate the management of persistent stable storage data structures.</p><p>For more information on how to start integrating IC-Kit in your canister development, check out <a href="https://github.com/Psychedelic/ic-kit">our GitHub repo</a>.</p><p>Soon, we’ll be publishing a short report with learnings and takeaways from our recent WICP bucket upgrade failure.</p><p>Stay tuned for an update on our <a href="https://discord.com/invite/yVEcEzmrgm">Discord</a> and feel free to ping our teams for any questions, feedback, or to jam about CAP technicals 👋</p><p><a href="https://twitter.com/cap_ois">Twitter</a> <a href="https://discord.com/invite/yVEcEzmrgm">Discord</a> <a href="https://cap.ooo/">Website</a> <a href="https://docs.cap.ooo/">Docs</a> <a href="https://github.com/psychedelic/cap">Github</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7467473fd56a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cap-ois/scaling-cap-from-now-to-next-7467473fd56a">Scaling CAP from Now to Next</a> was originally published in <a href="https://medium.com/cap-ois">CAP — Certified Asset Provenance</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Release: Transaction Scaling ⚔️]]></title>
            <link>https://medium.com/cap-ois/new-release-transaction-scaling-%EF%B8%8F-8a901a02fa98?source=rss-a4ee56a03e67------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a901a02fa98</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[dfinity]]></category>
            <category><![CDATA[the-internet-computer]]></category>
            <category><![CDATA[release-notes]]></category>
            <category><![CDATA[cap]]></category>
            <dc:creator><![CDATA[CAP]]></dc:creator>
            <pubDate>Tue, 07 Jun 2022 14:11:58 GMT</pubDate>
            <atom:updated>2022-06-07T14:12:43.986Z</atom:updated>
            <content:encoded><![CDATA[<h4>We’re bringing you batch transactions and updates to our Rust SDK to increase the scalability of CAP alongside your dApp.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*22kl8ymu9O8wGQngkVMNyA.png" /></figure><p>Today, we’re introducing batch transactions, a fresh update to CAP that <strong>increases the throughput of transactions logged via a single insertion</strong>.</p><p>To make it all possible, we are updating all CAP Root Buckets and the CAP Rust SDK. While CAP’s Motoko SDK is not yet ready, we are actively looking for a community member to take this task on (if this sounds like you, <a href="https://discord.gg/yVEcEzmrgm">get in contact with us</a>).</p><p>This update sprouted from joint community and team feedback, and represents <strong>a maturation of CAP as the history &amp; provenance layer for the Internet Computer ecosystem</strong>.</p><p>Eager to start adding batch transactions to your dApp’s CAP integration? Jump straight to the <a href="https://medium.com/p/8a901a02fa98#cb5d">Making the Upgrade section.</a></p><h3>Throughput Scaling with Batch Transactions</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl2Jee5TqCSzVnClUY%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl2Jee5TqCSzVnClUY%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fl2Jee5TqCSzVnClUY%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/055446af042673424fb0da6a478a0c50/href">https://medium.com/media/055446af042673424fb0da6a478a0c50/href</a></iframe><p>Prior to this update, CAP was structured so that each inter-canister <em>insert</em> call for adding new transactions would only carry with it one transaction log.</p><p>This one transaction per inter-canister call quickly became limiting for dApps looking to scale their usage alongside their CAP history.</p><p>With this update, we’ve configured <strong>all current and future root buckets to handle insert calls loaded with more than one transaction log.</strong></p><p>This was done by adding a new method called ‘insert_many’ to the candid interface of all Root Buckets. More information is available in <a href="https://docs.cap.ooo/">our docs</a> &amp; <a href="https://github.com/psychedelic/cap">GitHub repo</a>.</p><p>Problem solved… right? Not so fast. More transactions per inter-canister call also means a larger possibility for errors. Fortunately, we’ve thought and acted on this issue as well, and are updating the CAP’s SDK.</p><h3>Failure Resistant Insertions With Cap’s SDK</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FnkInqmqG2hdS3VP8nD%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FnkInqmqG2hdS3VP8nD%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FnkInqmqG2hdS3VP8nD%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="247" frameborder="0" scrolling="no"><a href="https://medium.com/media/82abb462459a7f48af1f832b770b9c04/href">https://medium.com/media/82abb462459a7f48af1f832b770b9c04/href</a></iframe><p>We’ve updated CAP’s Rust SDK to add a new method called <em>insert_sync </em>(or <em>insert_sync_many </em>for batched transactions).</p><p>Insert_sync <strong>abstracts away the need for integrations to handle errors that might arise from an insert call</strong> to a root bucket (eg: an out of cycles error).</p><p>If an error occurs, insert sync indexes and stores the transaction log in the canister’s heap storage. When another insert_sync call is made, the backlog of indexed transactions are inserted in order alongside the new transaction(s) being submitted in a single batch transaction, thereby flushing the backlog.</p><p>Multiple errored calls continue to grow the indexed backlog.</p><p>This not only guarantees failure-resistant insertions, but also <strong>ensures that transactions are inserted in the proper order</strong>, thereby maintaining the integrity of all dApps transaction history.</p><p>For a more in-depth look at insert_sync and how to use it, read our <a href="https://docs.cap.ooo/integrate-cap/getting-started/#failure-resistant-insertions">SDK docs</a>.</p><h3>Making the Upgrade</h3><p>All Root Bucket transaction logs remained stable alongside this upgrade.</p><p>If you wish to add batch transactions to your dApp and continue to follow the best practices of CAP integrations, upgrade to the newest version of our CAP SDK (0.2.3) in your cargo.toml file.</p><p>Once done, edit your code as you see fit to implement <em>insert_sync</em> or <em>insert_sync_many</em>, and then upgrade your canister to reflect the changes on the IC mainnet.</p><ul><li><a href="https://docs.rs/cap-sdk/latest/cap_sdk/fn.insert_sync.html">insert_sync docs.rs</a></li><li><a href="https://docs.rs/cap-sdk/latest/cap_sdk/fn.insert_many_sync.html">insert_sync_many docs.rs</a></li></ul><h3>That’s a Wrap</h3><p>If you’re interested in learning more, need help with your CAP implementation, or just want to jam with the CAP team about future CAP updates (like infinite transaction scaling 👀), hop into our Discord!</p><ul><li><a href="https://discord.gg/yVEcEzmrgm">Discord</a></li><li><a href="https://twitter.com/cap_ois">Twitter</a></li><li><a href="https://cap.ooo/">Website</a></li><li><a href="https://docs.cap.ooo/">Docs</a></li><li><a href="https://github.com/psychedelic/cap">Main Repo</a></li><li><a href="https://github.com/Psychedelic/cap/tree/main/sdk">SDK Repo</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a901a02fa98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cap-ois/new-release-transaction-scaling-%EF%B8%8F-8a901a02fa98">New Release: Transaction Scaling ⚔️</a> was originally published in <a href="https://medium.com/cap-ois">CAP — Certified Asset Provenance</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crowns News  — 11/12]]></title>
            <link>https://medium.com/@cap_ois/crowns-news-11-12-2b0c35bf6b5b?source=rss-a4ee56a03e67------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b0c35bf6b5b</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[computers-internet]]></category>
            <category><![CDATA[announcements]]></category>
            <category><![CDATA[dfinity]]></category>
            <dc:creator><![CDATA[CAP]]></dc:creator>
            <pubDate>Fri, 12 Nov 2021 15:00:22 GMT</pubDate>
            <atom:updated>2021-11-12T15:00:22.459Z</atom:updated>
            <content:encoded><![CDATA[<h3>Crowns News 👑 — 11/12</h3><h4><strong>Quick roadmap update 📆 We’re adjusting our roadmap by one week so that the free raffle happens Nov 24th, and the Crowns drop on Nov 26th 🎉</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qTUd6TlJOKA3m6GQV56OFg.png" /></figure><p>Another Friday, another set of news! Once again, if you visit our website (<a href="https://www.crowns.ooo/">crowns.ooo</a>), and see roadmap sections, you’ll find some updates! 🔥</p><p>Today’s update will be quick and simple:</p><h3>📆 New Dates for the Crowns Drop 📆</h3><p>Since Crowns will be dropped for free we thought… 🤔 Why not do it on <strong>Thanksgiving and Black Friday</strong> to match the vibes and prepare the drop to be even better? ✨🎉</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fv2CaxWLFw4a5y%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fcat-thanksgiving-turkey-v2CaxWLFw4a5y&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2Fv2CaxWLFw4a5y%2Fgiphy.gif%3Fcid%3D790b7611a7633cf70f232a871d80bd99c0c02429628cbf62%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/ad26668ee3055fb3fb88b06c4acacb98/href">https://medium.com/media/ad26668ee3055fb3fb88b06c4acacb98/href</a></iframe><p>Therefore, the new dates for the Crown’s roadmap are:</p><ul><li>🎟️ The <strong>free raffle</strong> registration will now open<strong> Nov-24th</strong></li><li>🍾 The <strong>Crowns drop</strong> will now happen on <strong>Nov-26th</strong></li></ul><p>That means we’re also extending the registration period to 2 days (48hs), from the 24th when it opens to the drop on the 26th 😎 that way more people can participate in the raffle🎉 Rules remain the same:</p><ul><li>✅ Cost for 1 ticket = Free</li><li>✅ Max tickets per person = 1</li><li>✅ 1 Ticket = 1 chance to win a free Crown.</li></ul><h3>🌎 Community &amp; Events 🌎</h3><p>We’ve had another dope week playing Gartic Phone, Quizzes, doing AMA’s on CAP/Crowns, and hosting meme competitions with <strong>everyone on our Discord server.</strong> Here’s the winning entries on that last one:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tt3S6K1O_ORaZKHtFN4E9Q.png" /></figure><p>If you don’t want to miss any detail, alpha, or conversation on Crowns and all the events we’re hosting with the community, join the convo! <a href="https://discord.gg/psychedelic"><strong>We’re in the Psychedelic Discord.</strong></a></p><h3>That’s all news for the day! 👋</h3><p>Thanks again for another dope week! The server is growing and we’ve enjoyed chatting about CAP, Crowns, and sharing our vision behind the technology being built for them.</p><ul><li><a href="http://discord/">Discord</a></li><li><a href="https://twitter.com/cap_ois">Twitter</a></li><li><a href="https://crowns.ooo/">Crowns Website</a></li><li><a href="https://cap.ooo/">CAP Website</a></li><li><a href="https://docs.cap.ooo/">Docs</a></li><li><a href="https://github.com/psychedelic/cap">Github Repo</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b0c35bf6b5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CAP is Live on Mainnet!  Transaction History & Provenance on the Internet Computer.]]></title>
            <link>https://medium.com/cap-ois/cap-is-live-on-mainnet-transaction-history-provenance-on-the-internet-computer-85feb42fbb4e?source=rss-a4ee56a03e67------2</link>
            <guid isPermaLink="false">https://medium.com/p/85feb42fbb4e</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[computers-internet]]></category>
            <category><![CDATA[announcements]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[dfinity]]></category>
            <dc:creator><![CDATA[CAP]]></dc:creator>
            <pubDate>Tue, 09 Nov 2021 17:27:17 GMT</pubDate>
            <atom:updated>2021-11-10T14:03:20.937Z</atom:updated>
            <content:encoded><![CDATA[<h4>We’re excited to say that CAP as an open internet service is live on mainnet, and ready to be integrated into NFTs &amp; Tokens to power trustless transaction histories for them.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_xx1U4t6GPn2JJhxLh9_wA.png" /></figure><p>Last week we announced CAP 🚀 We’ve been overwhelmed by the community excitement, and are proud to say that today, <strong>CAP goes live on the Internet Computer mainnet!</strong></p><p>What does this mean? 🤔 It means that <strong>CAP as an open internet service is fully usable!</strong> Anyone who wants to start generating their own transaction/activity history to their NFT/Token can do so.</p><p>Plus, since CAP is an open internet service, there are zero barriers to entry. <strong>Visit our </strong><a href="https://docs.cap.ooo/"><strong>docs</strong></a><strong> to start implementing it yourself!</strong></p><p>Feel kind of lost on the what, why and how of CAP? Read the <a href="https://medium.com/cap-ois/announcing-cap-asset-history-on-the-internet-computer-a6788283c8f3">announcement blog</a> to get the full picture behind it!</p><h3>Need a TL;DR Reminder?📰</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3orifhln1wZJ7lTbyw%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fseason-16-the-simpsons-16x19-3orifhln1wZJ7lTbyw&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2F3orifhln1wZJ7lTbyw%2Fgiphy.gif%3Fcid%3D790b76117499ef6e012956e921ec85a27e48de3767bf57b5%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="328" frameborder="0" scrolling="no"><a href="https://medium.com/media/8c7353165f5fae41a828223599ca003d/href">https://medium.com/media/8c7353165f5fae41a828223599ca003d/href</a></iframe><p><strong>What is CAP?</strong> An open internet service for NTF / Tokens to log transaction history and asset provenance on the Internet Computer.</p><p><strong>How does it work?</strong> CAP can spawn histories for NFT/Token canisters, to which they can only send records to, giving them access to trustless transaction histories on the IC. It also acts a router for any UI/App that wants to consume and surface data from ANY of these histories.</p><p><strong>Why CAP?</strong> Provenance and historic data on assets is a key component of trust on blockchains; it is something that users expect and a decision maker in terms of trust.</p><h3>CAP on Mainnet — Start Integrating! 🚀</h3><p>Now that CAP’s main canister is live on the Internet Computer any NFT or Token developer that wants to give their asset a <strong>trustless &amp; low-maintenance transaction history</strong> can do so.</p><p><strong>How? </strong><a href="https://docs.cap.ooo/"><strong>By integrating their NFT/Token canister to CAP</strong></a><strong>.</strong> CAP 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 using the SDK!</p><p>We’ve prepared a couple guides on <a href="https://docs.cap.ooo/">our documentation</a> to help everyone get started with it! <strong>The CAP SDK will be the main tool NFT/Token developers </strong>will need to use to integrate to CAP.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F5UzXJ7lkarSxatMZ31%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fwork-handyman-toolbox-5UzXJ7lkarSxatMZ31&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2F5UzXJ7lkarSxatMZ31%2Fgiphy.gif%3Fcid%3D790b761133c1fe36d97e72178547c81d4fae0fd56b7224c3%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/946bade4576e21045e8284a5795e897b/href">https://medium.com/media/946bade4576e21045e8284a5795e897b/href</a></iframe><h3>Integrating NFT/Tokens to CAP — CAP SDK 🧰</h3><p>Where can you’ find what is necessary to integrate your NFT/Token canister with CAP, and start registering transactions?</p><ul><li>Get started on our <a href="https://docs.cap.ooo/integrate-cap/getting-started/"><strong>documentation </strong>for the CAP SDK</a>.</li></ul><p><strong>You will need to:</strong></p><ol><li>Use the SDK to spawn your Token/NFTs history in CAP (root bucket).</li><li>Connect your canister’s transfer method to CAP and start sending records.</li></ol><p><strong>As easy as that. </strong>We’ve designed the SDK to make things as easy as possible, and we will continue to develop it to help smoothen migrations, and other use cases!</p><p>There’s also an <a href="https://github.com/Psychedelic/cap-example/tree/jsonsivar/init">example repository</a> for an empty Rust project you can use to follow that same guide along! 👏</p><p>A cool thing to note is that <strong>you can still use your Token or NFTs native get_transaction method (or equivalent) </strong>to fetch its transactions! Using the SDK you’ll wrap it to query CAP and return the proper responses</p><p>Meanwhile <strong>Apps and UIs </strong>can easily query your Token or NFT’s history from <strong>CAP’s mainnet canister directly (the router), </strong>where they can also query any other project integrating CAP, instead of integrating them individually. Neat, right?</p><h3>Consuming CAP Data from UIs/Apps — CAP-js 📡</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FUEGwYCVTBFa9tJEf66%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Frainbow-computer-data-UEGwYCVTBFa9tJEf66&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2FUEGwYCVTBFa9tJEf66%2Fgiphy.gif%3Fcid%3D790b76115435e48dcc61fe69eb2b25077abfa1d1b1819664%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/b502bc9818d3127ba7cca28705cf23a4/href">https://medium.com/media/b502bc9818d3127ba7cca28705cf23a4/href</a></iframe><p>What if your are an UI that wants to show transaction data for NFTs traded in your platform (that use CAP), or an app (a wallet like Plug!) that wants to show your user’s history of transactions for their assets?</p><p>For this, you will use the <a href="https://docs.cap.ooo/surface-data/getting-started/"><strong>CAP-js library</strong></a>, which will allow you to <strong>query transactions data from CAP to:</strong></p><ul><li>Check all transactions of all projects using CAP</li><li>Check specific transactions (e.g. a user’s transactions, or a specific asset’s one)</li></ul><p>Visit our <a href="https://docs.cap.ooo/surface-data/getting-started/"><strong>documentation to get started and learn more about how to use CAP-js to do this</strong></a>.</p><p>The cool thing? Unlike before, where you needed to interact with each asset’s history individually, with CAP-js <strong>you can check ALL histories in CAP from one place.</strong></p><h3>CAP Ecosystem Update 🌈</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uaXXa2Vo5nPZNTrCViImZg.png" /></figure><p>We’re also happy to share that the ecosystem of projects who are integrating or plan to integrate CAP is growing! Since launch, we’ve partnered with the following NFTs to help them bring CAP to their projects soon:</p><ul><li><a href="https://twitter.com/pokedstudiouk">PokedStudio’s Poked Bots</a>: 3D Bots by PokedStudio.</li><li><a href="https://twitter.com/ICPuppies">ICPuppies</a>: Project with highest selling NFT on the IC.</li><li><a href="https://icpunks.com/">ICPunks</a>: First self-minted NFT drop on the IC.</li><li><a href="https://tbhsl-lqaaa-aaaaj-qagzq-cai.ic0.app/">IC Cards</a>: Bringing a forgeable NFT game to the IC.</li></ul><p><strong>Don’t see your favorite project? </strong>Send them this article and tell them to reach out to the CAP team! We’ll be happy to help integrate to give their asset provenance and history.</p><p>After all, transaction <strong>history isn’t something that should be optional</strong>. It’s an industry standard. It provides additional utility to any project that integrates it. It’s the way every other chain works.</p><h3>That&#39;s A Wrap! 🌯</h3><p>These are very early days for CAP but we are excited to bring blockchain-wide transaction history to everyone.</p><p>No more walled gardens of data, or black holes without information or provenance.</p><p>If you’re a project that is interested in implementing CAP or just want to come and jam out with the CAP team, join our Discord. We look forward to seeing you there! 👋</p><ul><li><a href="http://discord/">Discord</a></li><li><a href="https://twitter.com/cap_ois">Twitter</a></li><li><a href="https://cap.ooo/">Website</a></li><li><a href="https://docs.cap.ooo/">Docs</a></li><li><a href="https://github.com/psychedelic/cap">Github Repo</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85feb42fbb4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cap-ois/cap-is-live-on-mainnet-transaction-history-provenance-on-the-internet-computer-85feb42fbb4e">CAP is Live on Mainnet! 🚀 Transaction History &amp; Provenance on the Internet Computer.</a> was originally published in <a href="https://medium.com/cap-ois">CAP — Certified Asset Provenance</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crowns News  — 11/4]]></title>
            <link>https://medium.com/cap-ois/crowns-news-11-4-3bbc5e5f510f?source=rss-a4ee56a03e67------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bbc5e5f510f</guid>
            <category><![CDATA[announcements]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[computers-internet]]></category>
            <dc:creator><![CDATA[CAP]]></dc:creator>
            <pubDate>Thu, 04 Nov 2021 14:49:18 GMT</pubDate>
            <atom:updated>2021-11-04T14:49:18.944Z</atom:updated>
            <content:encoded><![CDATA[<h3>Crowns News 👑 — 11/4</h3><h4>We’ve got a couple of news incoming! 🚀 First, Crowns will be a free NFT drop, which means the raffle’s rules have changed! We’ve also decided on GIF as the format, and got more news regarding upcoming events.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z-zbiln7QZljQgkkfijZ3w.png" /></figure><p>If you visit our website (<a href="https://www.crowns.ooo/">crowns.ooo</a>), you will see some dope news and updates 🔥 We’re bringing a surprise to end the week with a bang!</p><h3>🎁 N°1: Crowns will be a Free NFT Drop🎁</h3><p>Remember that 1 ICP price per-ticket to participate in the raffle to win one of 10,000 crowns?</p><p><strong>Scratch that</strong>. Getting a ticket for the raffle/drop will be… 0 ICP. And winners will get the crown for free. We will only maintain the<strong> 2,5% royalty fee </strong>on transfers that will be built-into the Crowns contract.</p><p>The price we had set for Crowns was merely a preventive measure to avoid bots, but we will take other precautions explained below, as we want to focus on what Crowns are all about: showcasing the power of having a transaction history and full traceability, not profits.</p><h3>📓 N°2: That Means Different Raffle Rules 📓</h3><p>Since participating in the raffle has no cost anymore, we will change the rules to keep things clean and fair for everyone:</p><p><strong>❌ Before: </strong>1 ICP per raffle ticket, 3 tickets per Principal ID (3 chances to win a crown).</p><p><strong>✅ Now: </strong>0 ICP per raffle ticket, 1 ticket per Principal ID (1 chance to win a crown).</p><p>We will implement some layers of verification to ensure we tone down and avoid users making a ton of multiple submissions. Users will continue to need Plug to sign up for it.</p><h3>🎨 N°3: Confirmed Format for Crowns! 🎨</h3><p>We’ve also confirmed the first format of the Crowns! We’ve decided to drop them as animated GIFs, like the ones you’ve seen before when we shared early art.</p><p>These will be generated from 3D Animation, which leaves the door open for other formats in the future! After the Crowns drop we’ll see where it goes and could explore video or 3D raw assets as well.</p><h3>🥳 N°4: More Games &amp; Giveaways Coming! 🥳</h3><p>We had a blast this week, making giveaways with CAP-partners, and playing guessing games &amp; competitions (like Gartic Phone) on Discord to give away Crowns to our early community members. Thanks a lot for the support, it’s been great!</p><p>That’s why <strong>we’ll keep them coming. </strong>Expect more games, drops, quizzes, meme competitions and partnerships throughout the week and up until the drop!</p><p>Make sure you’re around in our <a href="https://discord.gg/yVEcEzmrgm"><strong>Discord</strong></a><strong> &amp; </strong><a href="https://twitter.com/cap_ois"><strong>Twitter</strong></a> for more of those events!</p><h3>That’s all news for the day! 👋</h3><p>Thanks again for the amazing support and feedback this week, keep it coming! We’ll be sharing more updates soon on Discord and Twitter so be sure to check in and say hi.</p><ul><li><a href="http://discord/">Discord</a></li><li><a href="https://twitter.com/cap_ois">Twitter</a></li><li><a href="https://crowns.ooo/">Crowns Website</a></li><li><a href="https://cap.ooo/">CAP Website</a></li><li><a href="https://docs.cap.ooo/">Docs</a></li><li><a href="https://github.com/psychedelic/cap">Github Repo</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bbc5e5f510f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cap-ois/crowns-news-11-4-3bbc5e5f510f">Crowns News 👑 — 11/4</a> was originally published in <a href="https://medium.com/cap-ois">CAP — Certified Asset Provenance</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CAP Crowns: A Collection of 10,000 Psychedelic & 3D Crowns on the Internet Computer ]]></title>
            <link>https://medium.com/cap-ois/cap-crowns-a-collection-of-10-000-psychedelic-3d-crowns-on-the-internet-computer-1df279bfcf1f?source=rss-a4ee56a03e67------2</link>
            <guid isPermaLink="false">https://medium.com/p/1df279bfcf1f</guid>
            <category><![CDATA[computers-internet]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[announcements]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[CAP]]></dc:creator>
            <pubDate>Fri, 29 Oct 2021 14:33:02 GMT</pubDate>
            <atom:updated>2022-06-10T13:43:34.580Z</atom:updated>
            <content:encoded><![CDATA[<h4>CAP Crowns are a collection of 10,000 NFTs on the Internet Computer. With a mix of traditional and psychedelic materials, and a CAP-powered transaction history for full provenance.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PMPAld7PwUTxtrPs6U6VLA.png" /></figure><p>Time for the reveal! We dropped some early alpha yesterday while announcing CAP, so you knew we had a special surprise coming with it! <strong>We’re building and dropping our own NFT collection on the Internet Computer</strong>:<strong> CAP Crowns</strong></p><p>Using CAP, of course, to showcase one of the first NFTs on the IC with a built-in transaction history and full provenance of all its transactions (mint, sales, transfers, etc.).</p><h3>Meet the CAP Crowns NFT collection 👑</h3><p>Crowns is a collection of 10,000 randomly generated 3D NFTs on the Internet Computer blockchain. Each NFT is 3D crown, uniquely assembled out of all the hundreds of thousands possible combinations, with dope <strong>psychedelic and traditional</strong> material combinations.</p><ul><li><strong>Crown’s website: </strong><a href="https://www.crowns.ooo/"><strong>https://www.crowns.ooo/</strong></a></li></ul><p>These crowns are not from this world. Or part of them at least. 🌌</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/1*4m3jxoJipP_hNV7DHjeatA.gif" /></figure><p>We worked with the amazing production team from Psychedelic Games to create a mix of <strong>terran, and otherworldly materials and jewels </strong>to bring a set of random psychedelic and space-bound crowns, with still some hints of local-planet-earth royalty in them 😉</p><p>Crowns will use a custom NFT standard interface we built to showcase how CAP can be integrated into an NFT canister to give full traceability of its transactions.</p><h3>How’s it going to go down? 🔥</h3><p>You can find all <a href="https://www.crowns.ooo/">details on the website</a> for the Crowns project (check its roadmap!), coming <strong>this November</strong> to the Internet Computer.</p><p>To keep things fair, we’re going to go with a raffle/draft style whitelist. Anyone will be able to enter <strong>the raffle for the chance to win one of the 10,000 Crowns:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*XDGihFD5smTfzHmDL068hQ.gif" /></figure><h3>The Timeline for Crowns ⏰</h3><ol><li><strong>Today </strong>— Crowns are revealed, and the website goes live!</li><li><strong>November 16th</strong> — The whitelist/draft registry will open for ~24 hours</li><li><strong>November 17th @ 5pm EST </strong>— Winners selected, crowns will be dropped.</li></ol><p>The drop will have a raffle ticket system, with a price of <strong>1 ICP (up to three tickets per Principal ID, using Plug wallet to sign up). </strong>Any number of people can participate in the raffle!</p><p>On the day of the drop, 9750 winners will be randomly selected out of all raffle tickets! Winners will get a randomly generated CAP Crown dropped directly into the Principal ID of their wallet! <strong>All raffle tickets that do not win will have the 1 ICP returned to the wallet used for the purchase.</strong></p><h4>👑 <strong>Crown Distribution Breakdown:</strong></h4><ul><li>9,750 crowns will be dropped to the community through the raffle! 🚀</li><li>100 crowns will be saved for community events &amp; drops 🎊</li><li>150 crowns will be shared to the team &amp; partners that helped build it 💪</li></ul><h3>What can you do to get ready? 🤩</h3><p><a href="https://www.crowns.ooo/"><strong>Visit the website</strong></a>, you can sign up to get a 24hs-before email reminder for when the whitelist/draft opens up for registration.</p><p>Make sure you have a <a href="https://plugwallet.ooo/">Plug wallet</a> ready for when the whitelist/draft opens, and follow CAP on <a href="https://twitter.com/cap_ois">Twitter</a> as well to make sure you don’t miss the event.</p><p>What else? Take some action to become apart of the Crowns community by hopping into our #crowns channel in the <a href="https://discord.gg/yVEcEzmrgm">Psychedelic Discord</a>, home of CAP &amp; Crowns!</p><h3>Why Hodl a Crown? 🔮</h3><p>Besides being dope accessories, as a 3D asset that you can import to your metaverse avatars in the future, Crowns can potentially in the future have utility within the CAP Protocol/DAO itself once it launches fully as an open internet service on the Internet Computer!</p><h3>What About Trading Crowns? 🚀</h3><p>Initially, Crowns won’t be transferable. We are building a marketplace that will be released soon after the drop, when we will also enable the feature to transfer them as well!</p><p>Crowns will have a 2,5% royalty fee included in the NFT’s contract itself.</p><h3>Join in &amp; Participate &amp; Stay Tuned 👸🤴</h3><p>Special announcement for us! Crowns are the first NFT we’re producing under the <a href="https://psychedelic.ooo/">Psychedelic collective</a>, in a tremendous team effort to bring cool examples to the IC community of what things can be done in the ecosystem.</p><p>So we <strong>welcome everyone to join the community and our Discord server! </strong>Because we’ll be sharing updates, making community events &amp; pre-drop games as well.</p><ul><li><a href="https://discord.gg/yVEcEzmrgm">Discord</a></li><li><a href="https://twitter.com/cap_ois">Twitter</a></li><li><a href="https://crowns.ooo/">Crowns website</a></li><li><a href="https://cap.ooo/">CAP website</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1df279bfcf1f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cap-ois/cap-crowns-a-collection-of-10-000-psychedelic-3d-crowns-on-the-internet-computer-1df279bfcf1f">CAP Crowns: A Collection of 10,000 Psychedelic &amp; 3D Crowns on the Internet Computer 👑</a> was originally published in <a href="https://medium.com/cap-ois">CAP — Certified Asset Provenance</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing CAP: Asset History on the Internet Computer ]]></title>
            <link>https://medium.com/cap-ois/announcing-cap-asset-history-on-the-internet-computer-a6788283c8f3?source=rss-a4ee56a03e67------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6788283c8f3</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[dfinity]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[computers-internet]]></category>
            <category><![CDATA[announcements]]></category>
            <dc:creator><![CDATA[CAP]]></dc:creator>
            <pubDate>Thu, 28 Oct 2021 13:37:39 GMT</pubDate>
            <atom:updated>2021-10-28T13:37:39.224Z</atom:updated>
            <content:encoded><![CDATA[<h4>Today we’re announcing CAP (short for Certified Asset Provenance), an open internet service that brings transaction history and asset provenance to the IC . Plus a BONUS announcement on our first (and very special) NFT collection: CAP Crowns.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zIR80vsTogUtJ4KChhfigg.png" /></figure><p>Internet Computer folk, today we’re excited to <strong>announce CAP (short form for Certified Asset Provenance)</strong>. CAP is an open internet service that brings transaction/activity history as a service for Tokens &amp; NFTs and any assets on the Internet Computer.</p><p>CAP is currently in the <strong>final stages of development/testing</strong> and today we’re sharing an early-access into <a href="https://github.com/psychedelic/cap">its repositories</a> so projects looking to use CAP can start preparing/integrating 🤙 (we already have some dope launch partners — details later in the blog), and also to start gathering technical/community feedback.</p><p>We expect to <strong>release the full V1 to IC mainnet next week!</strong></p><blockquote>As you might see, documentation in the repos is looking light at the moment (we’re a little behind, focused on testing!). But don’t worry, in the next days we will fill the gaps in with dope examples, and guides😉</blockquote><h3>Why build CAP for the IC? 🤔</h3><p>Unlike Ethereum, the Internet Computer does not have native transaction history. Hmmm, sounds like a potential issue 🤔 It is! Without transaction history, we lose a lot of the transparency that is defacto to web3 (and critical for assets like tokens &amp; NFT’s). This leads to sub-par experiences for IC users.</p><p>You’d never know if you were truly getting a good price for your favorite NFT, or be able to see the flow of tokens/NFT’s in and out of your wallet (trust us we know, it’s the main customer complaint we get from Plug users, which is how we came up with the idea for CAP in the first place) 😟</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxUOxeUVe3KAdekgxy0%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxUOxeUVe3KAdekgxy0%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FxUOxeUVe3KAdekgxy0%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="242" frameborder="0" scrolling="no"><a href="https://medium.com/media/bea4b1624a343a0119f98cd4ca52b579/href">https://medium.com/media/bea4b1624a343a0119f98cd4ca52b579/href</a></iframe><p>As it is right now (pre CAP), transaction history <strong>is being developed on a per-project basis</strong> (ex. each token or NFT would have to implement it themselves), and unfortunately not many projects are even bothering doing it (<strong>meaning their token or NFT has no history at all</strong>!). And for the few that are doing history themselves, <strong>every implementation is different</strong>.</p><p>With many different token standards (fungible and non-fungible), <strong>an app that wants to consume history data from multiple sources would have to implement each source by hand</strong>. This problem makes it increasingly difficult for projects, apps, assets, and history of those assets to interoperate at scale.</p><p><strong>There must be a better way!</strong></p><h3>CAP: Certified Asset Provenance for the IC 📖</h3><p><strong>Introducing CAP</strong>, a standard agnostic open internet service for fungible and non-fungible tokens to record Internet Computer wide transaction history and asset provenance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AE6fa7EDH8RXemR5wrLM-Q.png" /></figure><p>CAP as an open internet service works the following way. The main canister for CAP acts as an orchestrator that can <strong>spawn new history canisters for individual projects (NFTs, Token Canisters, DEX’s, etc.).</strong></p><p>This new history canister will<strong> only accept transaction submissions from the canister/asset that initialized it</strong>. In a nutshell, CAP deploys a transaction history infrastructure that only your canister/asset (NFT/token)can use!</p><p>And once you do so, <strong>you can connect your canister/asset by connecting the transaction method</strong> to your new canister/asset specific CAP history canister, <strong>automatically passing the transaction records </strong>when a transaction/event is executed.</p><p>Now that your CAP history canister is bustling with transaction data, and <strong>you can surface that transaction data directly from your NFT / Token’s canister, using the same methods as before</strong>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FtsgNNs93oIbwk%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fstar-trek-nod-tsgNNs93oIbwk&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExbmUxNjhzcGw1ZDhrYmhxYjBmMzhlbG0zdjh5ZjdtdzA1bHBucHhociZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FtsgNNs93oIbwk%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/de7492a8b00fdf097be3239c33c68055/href">https://medium.com/media/de7492a8b00fdf097be3239c33c68055/href</a></iframe><h3>Wait, How do UI’s &amp; Apps Surface Transactions? 🤔</h3><p>Thinking “but every app will have to call each individual NFT/Token canister to see transactions?”. Nope, <strong>any frontend &amp; UI can consume <em>any CAP transaction data</em> from the main CAP canister.</strong></p><p>It has a secondary purpose! It acts as a router, meaning <strong>UI’s and apps can just talk to one canister (CAP) to fetch data from ANY project using CAP.</strong></p><p>And voila! Provenance, history, and some much needed transparency restored to the Internet Computer ecosystem 🥳</p><p>The current transaction threshold for single history canister storage is 400,000 transactions on the conservative side. However, for projects that are transaction heavy (ex. fungible token projects), CAP will soon implement a <a href="https://medium.com/dank-ois/cycles-token-xtc-update-history-scaling-239778df2ad2">history scaling solution</a> that allows for infinite transaction storage.</p><p>Which is another awesome benefit of using CAP — rather than each project needing to worry about building, maintaining, and scaling their own history; now <strong>they can just seamlessly outsource that work to CAP and automatically benefit from any future improvements made to CAP</strong>!</p><h3>Early Data Redundancy Off-chain 🗄️</h3><p>We know that it’s still early days for the Internet Computer, and for CAP, so on release of CAP, Psychedelic will backup all CAP data off-chain for <strong>extra data security/redundancy, and at no cost to CAP or it’s users</strong>.</p><p>This is just to ensure that <strong>data can never be lost</strong>, and even in the unlikely event of an IC upgrade that corrupts canister data, we can always restore history and keep all the historical transaction data preserved. We will probably also periodically back it up to Filecoin starting shortly after launch.</p><h3>Integrating CAP 🛠</h3><p>As we said, <strong>CAP will release fully to mainnet next week</strong>, but we’re still <strong>open sourcing our repositories </strong>today so that any developer team wanting to be ready for integration can start seeing how CAP works, and provide feedback as we finalize its development.</p><p><strong>Once again, </strong>this is an early look at the interfaces/code pre-launch to mainnet. We’re light on documentation as we focus on testing, but we will add examples &amp; guides in the coming days!😉</p><ul><li><a href="https://github.com/psychedelic/cap">Main CAP Repository</a></li><li><a href="https://github.com/Psychedelic/cap/tree/cap-sdk/sdk/">CAP SDK</a></li><li><a href="https://github.com/psychedelic/cap-js">CAP-js</a></li></ul><h4>Adding CAP To a New or Existing Project 🧰</h4><p>Integrating CAP will be made especially easy with the help of the <a href="https://github.com/Psychedelic/cap/tree/cap-sdk/sdk/">CAP SDK</a>. Regardless of if you’re a new or existing project, the SDK will allow you to instantiate a CAP root canister, feed your transaction data to that canister, and begin populating your asset history.</p><p>For people who are comfortable integrating APIs into their canister, the process shouldn’t take more than 30 minutes. For the less technically experienced, please reach out on <a href="https://discord.gg/yVEcEzmrgm">Discord</a>, our team is happy to help you integrate CAP.</p><h4>Querying CAP Data 🛰️</h4><p>Consuming CAP transaction data will be just as easy, if not easier, than generating it! We’re developing <a href="https://github.com/Psychedelic/cap-js">CAP-js, a javascript library</a> for querying CAP data, for just this purpose.</p><p>While only the canister that initialized the history canister can write transactions, frontends will not be limited to what transaction data they can query. As a result, asset transparency becomes the default. 🤟</p><h4>Templates 📦</h4><p>Alongside the launch of the CAP SDK &amp; CAP-js, we’ll be launching NFT and Token templates that have CAP already built in. We do the heavy lifting, and you can focus on all the other logic that makes your project unique!</p><h3>Early Supporters in the Ecosystem Using CAP 🤝</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R_ymbnn4UD2ehY05VV_Y4A.png" /></figure><p>We have been jamming with <strong>several projects in the IC ecosystem</strong> to get early feedback on CAP, and start preparing to have the first NFTs and Tokens with CAP integrated and providing them with an activity history after the release arrives!</p><h3>Which projects are we talking about? ⭐</h3><ol><li><a href="https://twitter.com/ic_gallery">Moonwalkers</a></li><li><a href="https://dank.ooo/xtc/">Cycles Token (XTC)</a></li><li><a href="https://dfinance.ai/">DFinance</a></li><li><a href="https://twitter.com/PortalDapp">Portal</a></li><li><a href="https://xn--4n8h7h.ws/">ICSnakes</a></li><li><a href="https://plugwallet.ooo/">Plug</a></li><li><a href="https://twitter.com/ICPSquadNFT">ICPSquad</a></li></ol><p>We’ll be working hand-in-hand to integrate CAP and start bringing users the answers to the questions they got today: <strong>“where did my NFT go?”, “how much did this sell for last?”, “How can I see the history for my transactions?”.</strong></p><p><strong>Don’t see your favorite project on our early supporters list? </strong>Send them this article! And put pressure on them to add history to their token/NFT. Transaction history and asset provenance shouldn’t be something users need to ask for anyways. It’s an industry standard. It’s how things work on every other chain.</p><p>And once the initial hype dies down for IC assets and NFT’s just because it’s ‘new’ (which is already starting to happen), the only assets that will be taken seriously or retain any value long term <strong>are ones that have history / provenance</strong>. CAP will make it extremely easy and quick to do so there really is no reason for any project on the IC to not have transaction history for their token or NFT.</p><h3>Plug’s Integration and Role 🔌</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QF-pNQJY2N2TAQTIJMPRlw.png" /></figure><p>Wait, how’s <a href="https://plugwallet.ooo/">Plug</a> going to integrate CAP? In two ways. <strong>First, to show user’s the transaction history for integrated CAP assets in the activity tab, of course!</strong></p><p><strong>But, more importantly, </strong>Plug will also integrate CAP to play an important role in <strong>seeding the transaction history for any project that can be held/surfaced in Plug, whether it has already integrated CAP or not.</strong></p><p>This way, Plug can help create an early activity history for all projects, and provide users of the wallet a visible activity history in their “Activity” tab starting next week! And then when each new token/NFT fully integrates CAP it will already have some records to populate their history canister .</p><p>But, <strong>to be perfectly clear, we strongly recommend that projects fully integrate CAP directly</strong> into their canisters so all activity across the entire IC will be captured, and not just activity going through Plug.</p><h3>Wait, you mentioned a BONUS announcement about an NFT? What are CAP CROWNS? 👑</h3><p>Oh, yeah. You’re right. We almost forgot about that.</p><p>Time to drop some alpha.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/1*4m3jxoJipP_hNV7DHjeatA.gif" /></figure><p>In addition to the other projects in the space mentioned above who are CAP launch partners,</p><p><strong>We’re creating our own NFT collection to help set an example for best practices for an NFT on the IC as well as showcase the power of CAP: CAP Crowns.</strong></p><p>Stay tuned, because we’re making the full CAP Crowns reveal &amp; announcement tomorrow!</p><h3>Wrapping it up 🗞</h3><p>Asset provenance (or lack thereof) is something we’ve been working on (and dealing with) for a while and feel it’s a crucial missing piece for mass adoption of the Internet Computer.</p><p><strong>It starts with assets, and we hope to see it grow into “activity provenance” in the future. </strong>Where we can help build and develop a history/provenance system for any sort of IC canister events/interactions.</p><p>Thinking ahead, we also believe CAP could play an interesting role in the BTC/ETH integrations to the IC; helping to properly represent and utilize assets from other chains on the IC.</p><p>Look out for the V1 launch of CAP next week, and in the meantime would love to hear some feedback from the community. If you have any questions, ideas, or concerns, feel free to hop in our Discord to jam with some of our team members. 🤙</p><ul><li><a href="https://discord.gg/yVEcEzmrgm">Discord</a></li><li><a href="https://twitter.com/cap_ois">Twitter</a></li><li><a href="https://cap.ooo/">CAP website</a></li><li><a href="https://docs.cap.ooo/">Documentation</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6788283c8f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cap-ois/announcing-cap-asset-history-on-the-internet-computer-a6788283c8f3">Announcing CAP: Asset History on the Internet Computer 📜</a> was originally published in <a href="https://medium.com/cap-ois">CAP — Certified Asset Provenance</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>