<?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 JAM ON BREAD on Medium]]></title>
        <description><![CDATA[Stories by JAM ON BREAD on Medium]]></description>
        <link>https://medium.com/@jamonbreadofficial?source=rss-dca582622ab8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*utzfrEhmwVz608e9VZkOTw.png</url>
            <title>Stories by JAM ON BREAD on Medium</title>
            <link>https://medium.com/@jamonbreadofficial?source=rss-dca582622ab8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:23:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jamonbreadofficial/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[Hunting the exploits in the Cardano NFT ecosystem]]></title>
            <link>https://jamonbreadofficial.medium.com/hunting-the-exploits-in-the-cardano-nft-ecosystem-6e1af0828545?source=rss-dca582622ab8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e1af0828545</guid>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[nft-marketplace]]></category>
            <dc:creator><![CDATA[JAM ON BREAD]]></dc:creator>
            <pubDate>Fri, 20 May 2022 19:06:09 GMT</pubDate>
            <atom:updated>2022-05-20T19:06:09.528Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Hello, we are JAM ON BREAD, the fastest decentralized NFT marketplace built on Cardano, powered by Vacuumlabs. We want to contribute to this amazing ecosystem as much as possible, so we decided to bring you this article.</blockquote><p>To spread awareness and to help developers, we’ll describe the most common critical exploit we have found in multiple NFT marketplaces on Cardano. We’ll go through the whole story of how the form of this exploit evolved as it appeared in newer and newer marketplaces. We first found this problem back in 2021 in three CNFT marketplaces. From there, similar exploits appeared in different forms in two others, the most recent one being epoch.art marketplace in April 2022. We contacted all affected marketplaces.</p><p><em>All of them except epoch.art reacted promptly to protect their users, which we greatly appreciate. Sadly, we have to do the exploit announcement instead of epoch.art themselves, as it is taking them too long and we want to protect their users. We describe their exploit at the end of the article. Let’s dive into the story!</em></p><h3>Introduction</h3><p>As smart contract capabilities arrived to Cardano, developers started working on the first decentralized applications on our beloved blockchain. Cardano’s eUTxO model is novel, and a different type of thinking needs to be put into the design of smart contracts. A few attack vectors are well known to developers with a deep understanding of the eUTxO model but are not known to newcomers and are easy to miss for them. As we have years of experience building on Cardano, we were able to identify three similar exploits that appeared across multiple NFT marketplaces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KVinvj5wSZiT6O8ucfSufQ.png" /></figure><p>After discovering the problem in <strong>jpg.store</strong>, <strong>genesishouse</strong> and <strong>adapix</strong> NFT marketplaces back in 2021, we immediately let them know. We also agreed on not explaining how the attack works to the general public for some time. We did it to give people an opportunity to delist their NFTs from vulnerable smart contracts without bad actors trying to take advantage of the situation.</p><h3>How exploitable NFT marketplaces work</h3><p>What flow should we expect while interacting with a smart contract that lets users list and buy NFTs for a fixed price set by sellers?</p><p>A seller chooses an NFT from their wallet and specifies a price for which they want to sell this NFT. Then, they create a transaction with an output that is locked under the smart contract. This output stores the NFT and information about the seller and the price.</p><p>When someone wants to buy this NFT, they need to create a transaction that gets multiple inputs and outputs:</p><blockquote>The first input is from the smart contract and holds the NFT (with seller and price information). The second input is from the buyer and contains enough ADA to pay for the NFT.</blockquote><blockquote>The first output is an NFT going to the buyer and the second output is ADA going to the seller.</blockquote><p>For the transaction to be valid, both inputs have to have the right to be spent in it. The ADA input can only be spent if the buyer signs the transaction. What about the smart contract input? The smart contract needs to approve this transaction. It has to check that there exists an output that goes to the seller and contains enough ADA to pay for the NFT. It does not necessarily have to check whether the NFT goes to the buyer because we know that the buyer signed the transaction and therefore approves it as it is.</p><p>Seems secure enough, right? The buyer has to pay enough to the seller. What could possibly go wrong?</p><h3>Double satisfaction</h3><p>The problem is not in ordinary transactions assembled by marketplaces themselves. Instead, the problem is that anyone can assemble a transaction with arbitrary inputs and outputs and submit it. If such a transaction validates, inputs get spent, and outputs are created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h3aHuZah6r5HRcyuvBYFvA.png" /></figure><p>Imagine a situation where a seller, let us call them A, sells multiple NFTs on the same marketplace. Each of those NFTs, together with information about seller A and a price, is locked under the same smart contract. As a result, a bad actor could create the following transaction. As inputs, they put:</p><blockquote>- All of the NFTs that A sells</blockquote><blockquote>- Enough ADA to pay for the most expensive of A’s NFTs</blockquote><p>As outputs, they put:</p><blockquote>- All of the NFTs that A sells going the bad actor</blockquote><blockquote>- Enough ADA to pay for the most expensive of A’s NFTs going to A</blockquote><p>For each of the smart contract inputs, a validation is performed. Each of these NFT inputs checks whether an output with enough ADA exists to pay for this particular NFT going to seller A. As the single output that goes to seller A contains enough ADA to pay for the most expensive NFT, all of the NFT inputs are satisfied with this single output and approve the transaction.</p><p>This way, a bad actor could only pay for one NFT and get other, cheaper NFTs from the same seller for free. This attack has been known for years. It is described in the <a href="https://ergoplatform.org/docs/ErgoScript.pdf">ErgoScript whitepaper</a> from 2019. It was also mentioned in a <a href="https://spacebudz.medium.com/spacebudz-market-71e79d1bbf34">blogpost</a> from our beloved pioneers in the space: Spacebudz. Yet, we found this exploit in all Cardano NFT marketplaces with open source code in 2021. Likely, this problem was also present in marketplaces that did not have their smart contracts published, but we could not verify that.</p><p>All platforms affected during 2021 reacted promptly and fixed their contracts after we approached them and helped some of them with the fix. Yet, this was not the end of the story…</p><h4>The exploit returns</h4><p>After some time passed, we decided to review all the contracts we could find again. As most of the marketplaces unpublished their code after the first exploit, we were only able to find one — Martify.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CVxtNJx6xPAXpmVTWEMeug.png" /></figure><p>Martify’s contract tried to fix the problem by limiting the number of script inputs that are locked in <strong>this</strong> marketplace’s contract to 1. This way, the transaction constructed by a bad actor in the previous example fails to validate because it has more than one input from <strong>this</strong> marketplace’s contract. Do you see a problem there?</p><p>The added check is too weak, and it only partially fixes the problem. Let’s call this marketplace X. Imagine that there is another marketplace called Y. This Y uses a similar smart contract with the same fix. There is a seller B that sells one NFT on marketplace X and one NFT on marketplace Y. A bad actor could assemble a transaction similar to the previous one. This time, the inputs will be A’s NFT from marketplace X, A’s NFT from marketplace Y, and enough ADA to pay for the more expensive of those two. The outputs will be both NFTs going to the bad actor and ADA going to the seller. Again, both NFT inputs are satisfied because an output containing enough ADA exists. The fix does not help here because the NFT inputs are from different smart contracts.</p><p>The working fix to this problem is to limit the number of smart contract inputs to 1, regardless of the smart contract that the input comes from. This mitigates the risk to a lower level, as the contract only allows the most restrictive input configurations. This is also a reason why buying multiple NFTs in one transaction is not supported by most marketplaces right now. There could also be some limitations of outputs added for further security.</p><h4>The exploit returns once again</h4><p>Some time passed, and we thought there was no general NFT marketplace with an open-source contract left to check. Then we noticed that <strong>epoch.art </strong>marketplace published their contract.</p><p>Of course, we decided to check it out. We immediately spotted a problem. It was less severe than the original one, but it allowed an attacker to steal NFTs worth thousands to tens of thousands of ADA.</p><p>This smart contract did not check for a single script input. It looks like its authors were not even aware of the original exploit. Luckily, they managed to make the possible damage smaller. Their check was whether there is an exact price of the NFT present amongst outputs going to the NFT seller. Therefore, each NFT needed to be bought by paying the exact price. This is different from previous contracts, as they were checking whether the seller receives **at least** the price.</p><h4>Epoch.art exploit</h4><p><em>This allows the attacker to buy multiple NFTs and only pay for one if purchased NFTs are from the same seller and are listed for the same price. We found multiple “exploitable groups” of NFTs listed for the same price by the same seller worth thousands of ADA. We contacted epoch.art and let them know about this exploit. After some talking, the contract’s author understood how the exploit works. We advised them to hide the contract from their GitHub until the fix is done and users have time to relist their assets to a new contract. The fix is trivial and it should take just 1 day to prepare it. Epoch.art paid us a bounty of 500 ADA and 2 Mutant NFTs. When we asked epoch.art when they will announce the exploit, they said 2–3 days. This time limit passed and no announcement has been made. Instead, they told us that they decided to add new features into the contract alongside the fix and that it will take them 2 weeks. We found it irresponsible of them, but we did let them do it. We were waiting for them to finish the new contract for some time. After 3 weeks, it still wasn’t ready. When we asked them what was happening they said that they are working on it. We told them that we give them 5 days to push the trivial fix and then we will push the announcement if they don’t do that. So, this is our announcement. As the Cardano community is one of the most transparent ones out there, we believe that this is the </em><strong><em>right thing</em></strong><em> to do. All users that have multiple NFTs listed for the same price on epoch.art are affected and should delist their assets as soon as possible.</em></p><p>We hope this spreads awareness about this common issue, but this is a mistake that eUTxO newcomers will probably keep on making. We need to avoid this as much as possible to repeat this again and again from time to time.</p><h3>Conclusion</h3><p>The Cardano smart contract space is still evolving and needs time so these simple exploits will be well known among developers. We found an exploit in most live dApps with public smart contracts. However, the biggest exploit, the <strong>Minswap</strong> one, has been found by our <strong>partners</strong> <strong>from</strong> <strong>WingRiders DEX</strong>. Our partners from WingRiders DEX helped us review our smart contracts too, to make sure they are safe. As we want to help the community grow and make the life of new developers easier and the lives of users calmer, we are open-sourcing our instant-buy smart contract and thus becoming a truly decentralized marketplace, unlike the ones with closed-source contracts.</p><p>We are JAM ON BREAD, a new NFT marketplace <strong>and aggregator</strong> built on Cardano, offering sales of NFTs for a fixed price and placing offers on all NFTs or even on entire collections. We are trying to be the fastest NFT marketplace on Cardano and have many more features coming. You can support us by following our Twitter account or using our marketplace. Thanks for reading, and have a great day!</p><blockquote>Fun fact: If you list an NFT on jpg.store, it is usually available on JAM ON BREAD a few minutes sooner than on jpg.store at the time of publishing this article.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e1af0828545" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rarity ranking on Jam On Bread]]></title>
            <link>https://jamonbreadofficial.medium.com/rarity-ranking-on-jam-on-bread-bcd21fd7d53b?source=rss-dca582622ab8------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcd21fd7d53b</guid>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[nft-marketplace]]></category>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[cnft]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[JAM ON BREAD]]></dc:creator>
            <pubDate>Sat, 30 Apr 2022 16:02:41 GMT</pubDate>
            <atom:updated>2022-04-30T16:02:41.298Z</atom:updated>
            <content:encoded><![CDATA[<h3>How we calculate rarities on JamOnBread</h3><p>There are multiple approaches to calculating rarities. Different<br>websites use different ways. We at JAM ON BREAD decided to explore<br>all resources on rarity calculation we could find and select the way<br>that was the most reasonable according to our opinions.</p><p>The approach we chose is, we believe, the most independent method to calculate rarity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*CuPFQqNfnIdnmbVM1ibtJQ.jpeg" /></figure><h3>Possibilities</h3><p>To understand why we chose our approach, we need to throw some shade on other rarity calculation methods. So that you know why they are inferior to our solution :)</p><p>The most straightforward approach to calculating rarity is simply looking at the rarest attribute. This is usually not a good metric, as an NFT with many common traits and one ultra-rare trait will be rarer than an NFT with all attributes rare.</p><p>Another common approach is to look at the rarity of all attributes of a<br>specific NFT and multiply these rarities together to get a rarity score<br>for this particular NFT. You can see this approach used on many rarity ranking sites.</p><p>When counting rarity this way, the lower the score, the rarer the NFT. Such an approach might not treat different NFTs the same way; some NFTs might be favored. The problem is the number of traits. An NFT with 3 traits will probably have a very different score than an NFT with 7 traits because, in the case of the first NFT, only 3 numbers are multiplied, but in the other case, 7 numbers are multiplied.<br>In these approaches, a normalization of rarity scores might be needed.</p><h3>Our approach</h3><p>We decided to use the Jaccard distance of NFTs to order a collection. This is a statistical approach that measures similarities between two sets of data. The Jaccard distance of 2 NFTs is calculated using the following formula:</p><p>dist(NFT_1, NFT_2) = 1 — (num_of_common_traits / num_of_all_traits)</p><p>Let’s look at an example. Let’s consider an NFT_1 and NFT_2 with following traits:</p><p><strong>| | **NFT 1** | **NFT 2** |</strong></p><p><strong>| — — — — — — — — | — — — — — — | — — — — — — |</strong></p><p><strong>| **Background** | Blue | Orange |</strong></p><p><strong>| **Eyes** | *Scared* | *Scared* |</strong></p><p><strong>| **Mouth** | Smiling | Sad |</strong></p><p><strong>| **Body** | *Muscular* | *Muscular* |</strong></p><p><strong>| **Nose** | Long | Short |</strong></p><p>In this case, our NFTs have 2 common traits (*Scared* eyes and *Muscular* body). In total, they have 8 traits (Blue background, Orange background, Scared eyes, Smiling mouth, Sad mouth, Muscular body, Long nose, and Short nose). Therefore, their Jaccard distance is 1–2 / 8 = 0.75.</p><p>We do this calculation for each NFT pair in the collection we are calculating rarity for. For each NFT, we take the average distance between this NFT and the rest of the collection. Now we have a relative rarity order for each NFT.</p><h3>Is this ranking accurate?</h3><p>Calculating an accurate rarity for each collection using a single approach is very difficult. Some attributes are subjectively considered rarer by the<br>collection’s creators or by the community. In addition, many aspects are difficult to catch by a mathematical model. For example, a combination of<br>matching attributes that are common individually can be considered rare.<br>Such subjective factors make it practically impossible to calculate rarities<br>exactly as collection creators intended them.</p><p>We wanted a consistent and straightforward way to calculate rarities for all collections. Jaccard distance does this well. However, it doesn’t answer the question of how rare people believe the NFT to be. Instead, it shows how rare a particular NFT is, compared to the whole NFT collection.</p><p>This approach penalizes common attributes. For example, an NFT with one ultra-rare attribute and many common ones will be considered common. On the other hand, an NFT where all attributes are relatively rare will be regarded as rare.</p><h3>How we display rarity on JAM ON BREAD</h3><p>We calculate the rarity for most of the collections automatically. However, it is not calculated for collections that are too big or the ones where statistical rarity does not make much sense (such as virtual land plots).</p><p>If a collection has a rarity calculated, a rarity badge will be present next</p><p>to each NFT from this collection. All NFTs in the lower half of the collection’s rarity ordering are labeled as COMMON. All other ones have a TOP X% displayed beside them. So, for example, if an NFT from a 10k collection is considered 150th most rare, there will be a TOP 1.5% badge displayed.</p><p>Badges are divided into classes, and each class is color-coded, so it is simple to spot rare NFTs easily.</p><h3>Filtering by rarity</h3><p>There is an option on the collection’s detail page to only display NFTs up to some rarity. So, for example, you can choose only to see NFTs in the TOP 20%. Besides that, it is possible to order by rarity in both ascending and descending order.</p><p>In the end, rarity ranking is still very subjective. Some collections might prefer to be ranked using different methods, so we are considering adding support to sort rarities by various calculation algorithms. Let us know if this is something you would like to see, even if you are not a collection creator.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcd21fd7d53b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Invite]]></title>
            <link>https://jamonbreadofficial.medium.com/how-to-invite-4995a54b2af4?source=rss-dca582622ab8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4995a54b2af4</guid>
            <category><![CDATA[nft-collectibles]]></category>
            <category><![CDATA[nft-marketplace]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[cardano]]></category>
            <dc:creator><![CDATA[JAM ON BREAD]]></dc:creator>
            <pubDate>Fri, 08 Apr 2022 12:35:58 GMT</pubDate>
            <atom:updated>2022-04-11T09:06:34.377Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Our Discord Community</strong></p><blockquote>Why you need to be there and how to invite your friends</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l2P9ahN2rQtuAL4IwxMrdg.jpeg" /></figure><p>Our plans are reaching far into the future. We will be launching subprojects connected to our marketplace. <strong>Some of them might get a lot of attention. One of them might even not be too far in the future.</strong></p><p>This launch we are talking about… we might do an allowlist for it. So you’ll want to be in the Discord early. And you’ll want to invite people.</p><p>Invites are not mandatory. We recommend inviting friends to be extra sure, just in case there is massive interest in our future launches. Any invited person that is not a bot who joins and stays on our Discord is counted to your leaderboard score.</p><p><strong>The higher the score, the higher chance of getting on the allowlist. </strong>We don’t like gatekeeping stuff, but we dislike overloading the blockchain even more. Some launches are better when spaced out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/1*NaFq9_Sma-xP0EJuPhoV_g.png" /></figure><p>First, find the server menu in the top left corner of the Discord window here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*rp67n9PJq9ivdVfWhdrI6g.png" /></figure><p>Second, click on Invite People here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/1*CVkAe9Y41nCmHiQAzW5AkQ.png" /></figure><p>Third, find the tiny blue link saying “Edit invite link” and click it here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*mK_Uk7wrdYgwHudxlEie-w.png" /></figure><p>Then, in the next window, you’ll want to change the EXPIRE AFTER to “Never” and then click the “Generate a New Link”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*cGwsPw13Upymjo_FC6W9Gw.png" /></figure><p>After that, Copy your new link and share it with your friends and family. They will soon want to be with us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*Omqb2zdbJ8_oR6XTHcoaPQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4995a54b2af4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JAM ON BREAD]]></title>
            <link>https://jamonbreadofficial.medium.com/jam-on-bread-51ecb9ed941f?source=rss-dca582622ab8------2</link>
            <guid isPermaLink="false">https://medium.com/p/51ecb9ed941f</guid>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[nft-marketplace]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[cryptocurrency-investment]]></category>
            <dc:creator><![CDATA[JAM ON BREAD]]></dc:creator>
            <pubDate>Thu, 31 Mar 2022 07:39:28 GMT</pubDate>
            <atom:updated>2022-03-31T07:39:28.074Z</atom:updated>
            <content:encoded><![CDATA[<h4>The fastest and safest CNFT marketplace</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C7xwz1IuoYDR9y1zJSIKnA.png" /></figure><h3><strong>Who are we?</strong></h3><blockquote>JAM ON BREAD is our favorite snack</blockquote><p>Also, it’s our decentralized CNFT marketplace that we built here in Vacuumlabs because we love NFTs, we love Cardano, and over the years we got really good at building for Cardano.</p><p>As we value a “<em>build first</em>” principle, we’ve been quietly developing this platform for the past six months without announcing anything publicly.</p><p>Our main goal is to <strong>create a marketplace that is lightning fast, easy to use, and completely secure.</strong> We believe we’ve fulfilled this goal and made a marketplace that’s a joy to use.</p><h4><strong>We ❤ CNFTs</strong></h4><p>We value the Cardano ecosystem as a whole, and that’s why we’ve also been helping other big players among CNFT marketplaces by notifying them about critical exploits we found in their smart contracts. <strong>We especially liked the reaction of Blakelock from jpg.store,</strong> who managed to notify users immediately and was very kind to us. Thanks!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DEQgmkJ4EquEvQfVHg4Fkw.png" /></figure><h3><strong>But why put the JAM on the BREAD?</strong></h3><p><em>Well, it just makes the bread better.</em></p><p>It’s the same with us. <strong>We wanted a better marketplace so we built it ourselves.</strong> And, what’s more, we added all the functionality that was missing in the Cardano ecosystem.</p><p>What was missing was <strong>the option to filter NFTs</strong>, so we built it into JAM ON BREAD. All collections can be filtered by traits and price and<strong> sorted in multiple different ways, making them discoverable like never before.</strong> The detail page of an NFT offers a table with traits of the respective NFT, where each row is clickable and leads to a list filtered by that specific trait.</p><blockquote>We wanted the most secure marketplace in the ecosystem, so we went ahead and built it. Thanks to our deep understanding of Cardano’s eUTxO model, all exploits are avoided. <strong>We’ve tested all possible hacks on our contracts and iterated until we were sure of their safety.</strong></blockquote><p>We have no time for spinning loaders, so <strong>we made the fastest marketplace we could.</strong> The speed of our platform speaks for itself — see what we mean at <a href="https://www.jamonbread.com/?utm_source=medium&amp;utm_medium=aboutus"><strong>jamonbread.com</strong></a>. Quick loading of all NFT images from all collections makes our marketplace also<strong> usable as an CNFT explorer.</strong> The images we display aren’t limited to ones that have interacted with our smart contract in the past.</p><blockquote>One more thing: we don’t like to pay fees when buying low cost NFTs. At JAM ON BREAD, <strong>you won’t pay any fees for any sales under 50 ADA.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8QpabzcGjRtR1HbShGTYoQ.png" /></figure><h4><strong>Vacuumlabs …sounds familiar, right?</strong></h4><p>It should, as we’ve been part of the Cardano ecosystem for years. We’re the group behind the <strong>AdaLite wallet</strong>, the great <strong>WingRiders DEX</strong>, <strong>NuFi’s new multi-chain wallet</strong> and the Cardano applications for <strong>Ledger</strong> and <strong>Trezor</strong> hardware wallets.</p><p>We understand the Cardano blockchain better than most, and our smart contracts are battle-tested and reviewed by the most experienced Cardano developers. <strong>It’s our mission to prove that Cardano is a capable and competitive network</strong>, and we’re striving <strong>to create the best products that will attract users from other blockchains.</strong></p><h4><strong>There’s much more to come</strong></h4><p>Visit <a href="https://bit.ly/35oAiRD"><strong>project.jamonbread.com</strong></a> to see the features we’re implementing next. We’ll keep building until we have the functionality that we and our users want.</p><blockquote>In the near future, we’re adding <strong>offers</strong> and <strong>auctions.</strong></blockquote><p>We’ve already developed smart contracts and we’re now testing and reviewing them. After we implement this functionality on both the backend and frontend, <strong>you’ll be able to make offers for NFTs or entire collection floors, and participate in auctions that utilize the security and convenience of smart contracts.</strong></p><p>As auctions are much more complex than instant buys, there needs to be a thorough smart contract security review performed, which we are working on right now. After we finish offers and auctions, we’ll add an option for smart contract-powered NFT swaps.</p><blockquote>What else?<strong> Oh yes, <em>rarity ranking</em>!</strong> That’s right, built into the marketplace.</blockquote><p><em>Note: To interact with the JAM ON BREAD marketplace, you need to have Nami or CCVault wallet extension downloaded.</em></p><p><strong>We want your feedback!</strong> Go to<strong> </strong><a href="https://www.jamonbread.com/?utm_source=medium&amp;utm_medium=aboutus"><strong>jamonbread.com</strong></a> and play around with your collection. Explore listings, discover new collections and come let us know your opinion in our <a href="https://bit.ly/3Nw0tXN"><strong>Discord</strong> </a>or <a href="https://t.me/jamonbread"><strong>Telegram</strong></a>. And don’t forget to follow us on <a href="https://bit.ly/3JVipsu"><strong>Twitter</strong></a> for that weekly dose of juicy alpha.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51ecb9ed941f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>