<?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[dGoods - Medium]]></title>
        <description><![CDATA[dGoods is an open source digital goods standard for blockchain. dGoods is supported by Mythical Games, EOS Lynx, Scatter, and many more talented teams. - Medium]]></description>
        <link>https://medium.com/dgoods?source=rss----d3a2c3088775---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>dGoods - Medium</title>
            <link>https://medium.com/dgoods?source=rss----d3a2c3088775---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:41:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/dgoods" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[dGoods v1.0 — Public Beta Release]]></title>
            <link>https://medium.com/dgoods/dgoods-v1-0-public-beta-release-72f896ad7aed?source=rss----d3a2c3088775---4</link>
            <guid isPermaLink="false">https://medium.com/p/72f896ad7aed</guid>
            <category><![CDATA[non-fungible-tokens]]></category>
            <category><![CDATA[dgoods]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[semi-fungible-tokens]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Rudy Koch]]></dc:creator>
            <pubDate>Tue, 07 May 2019 18:31:42 GMT</pubDate>
            <atom:updated>2019-05-13T17:02:48.895Z</atom:updated>
            <content:encoded><![CDATA[<h3>dGoods v1.0 — Public Beta Release</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*bkvtc6uqMgFqsD6i" /></figure><p>We are thrilled to be officially launching the public beta for dGoods v1.0. Not only is this the first major milestone for the dGoods initiative, but we are also unveiling one of the most important features we’re including with dGoods v1.0: DEX in a token.</p><p>When we set out to create dGoods it was clear to us that there was a meaningful gap in the blockchain world. The standards that were out there were either inadequate or locked behind a proprietary token. Instead, what we needed was an open source standard that solved real world use cases.</p><p>We weren’t the only ones who saw the gap. dGoods is a collaboration between many talented teams in the industry who came together over a common goal: to provide a token standard that would unify the way we handle digital goods on the blockchain. The first set of features we’ve focused on are aimed at reducing the barriers to creating new marketplaces and promoting the liquidity of digital goods.</p><p>With the release of dGoods v1.0 public beta, the code is now available on <a href="https://github.com/MythicalGames/dGoods">Github</a> to anyone who wants to get their hands on it. The obvious disclaimer is that it’s a beta release which means there may be bugs. As we work towards a final release, we will be opening the <a href="https://github.com/MythicalGames/dGoods/issues">“issues” section in our Github repo</a> for those interested in submitting any issues you might find.</p><p>Now onto a few key topics for this release…</p><p><strong>DEX in a token</strong></p><p>Over the last couple of months, we’ve been hard at work on many key features for dGoods, but today we’re excited to unveil perhaps the most central feature of the dGoods v1.0 release: DEX in a token.</p><p>With DEX in a token, we are providing a set of simple and accessible marketplace features built right into the smart contract itself. Because it’s built into the contract, any wallet, exchange, or app that is compatible with dGoods can now be a marketplace. Simply put, any item that’s listed for sale will automatically appear in any dGoods compatible marketplace.</p><p>Here’s how it works:</p><ul><li>listsalenft: this is a function that’s callable only by the item owner. It creates a sale listing in the token contract valid for a user-defined period of time, and transfers ownership of the item to the token contract.</li><li>closesalenft: this is callable by the seller if the listing hasn’t expired, or anyone if the listing has expired. It will remove the listing and return the nft to the seller.</li><li>buynft: this is called when a user sends EOS to the token contract with a memo of “dgood_id,to_account”. If the amount sent is equal to the listed price, then the item will transfer ownership to the buyer, and the EOS will be transferred to the seller.</li><li>By allowing users to specify a “to_account”, users can buy an item on behalf of others by specifying the account to send to.</li></ul><p>With this initial release, we’ve focused on the core marketplace mechanics. We are quickly working on adding more functionality like transfer fees, buy orders, auction capabilities, and more. As we solidify v1.0, we’re excited to hear your feedback on the marketplace mechanics and we expect these capabilities to evolve during the beta release.</p><p>“DEX in a token” provides developers with a standardized way to push their digital goods out to the masses across a wide array of distribution channels. This is the first major step towards creating the liquidity that’s necessary to support a flourishing digital goods economy.</p><p><strong>dGoods v1.0 Features</strong></p><p>With that out the way, let’s talk about some of the other features included in this release. With v1.0, it was important to us to take a meaningful first step while allowing flexibility to expand the dGoods standard into new areas. We’ve integrated a set of features that extends the token capabilities on the EOS blockchain considerably. Here’s a quick recap of what’s included in the dGoods v1.0 beta release:</p><p><strong>DEX in a token</strong></p><p>By standardizing the way items are bought and sold, we aim to spawn a wide array of distribution channels for digital goods. Simply put, we are creating demand.</p><p><strong>Multiple tokens and sub-tokens in one contract</strong></p><p>Most games will have many tokenized assets. Dealing with them 1-by-1 just isn’t efficient. dGoods provides batch support for both fungible and non-fungible token.</p><p><strong>Semi-Fungible Tokens (SFT)</strong></p><p>We’ve created a brand new token class to address situations where a developer wants to issue a run or batch of items that are for all intents and purposes the same, except for we believe that SFTs will be the dominant use case for the future of digital goods.</p><p><strong>Multiple layers of token categorization</strong></p><p>With products that are aimed at mass market consumer adoption, developers will be dealing with a large volume of digital goods. As a result, having meaningful categorization functionality is key to keeping it all organized and user friendly.</p><p><strong>Metadata Asset Types</strong></p><p>We wanted dGoods to support a wide array of digital asset types. Each asset type has its own set of data requirements that are stored in a JSON file linked to the token.</p><p><strong>Token localization</strong></p><p>Blockchain has global reach, and marketplaces need to be able to display tokenized digital goods in their language of choice.</p><p>For a full list and more comprehensive details, please refer to the <a href="https://github.com/MythicalGames/dgoods/blob/master/README.md">dGoods Github readme file</a>.</p><p><strong>What’s next?</strong></p><p>Now that the beta is live, we’re focused on bug fixing, trading feedback, and security audits for v1.0.</p><p>In parallel, we are moving quickly on to dGoods v2.0. We have a growing roster of new features to add to the dGoods standard, and we’re excited to press on.</p><p>If you are interested in contributing to the dGoods open source standard, we welcome you to reach out via our website at <a href="https://dgoods.org/">dGoods.org</a>, or via telegram at <a href="https://t.me/dGoods_EOS">t.me/dGoods_EOS</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72f896ad7aed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dgoods/dgoods-v1-0-public-beta-release-72f896ad7aed">dGoods v1.0 — Public Beta Release</a> was originally published in <a href="https://medium.com/dgoods">dGoods</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[dGoods Smart Contract — Closed Alpha]]></title>
            <link>https://medium.com/dgoods/dgoods-smart-contract-closed-alpha-fd795521ba6c?source=rss----d3a2c3088775---4</link>
            <guid isPermaLink="false">https://medium.com/p/fd795521ba6c</guid>
            <category><![CDATA[non-fungible-tokens]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[semi-fungible-tokens]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[dgoods]]></category>
            <dc:creator><![CDATA[Rudy Koch]]></dc:creator>
            <pubDate>Fri, 29 Mar 2019 13:57:33 GMT</pubDate>
            <atom:updated>2019-03-28T17:43:20.680Z</atom:updated>
            <content:encoded><![CDATA[<h3>dGoods Smart Contract — Closed Alpha</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W9B4xYiT8AODT9bZLRstFw.png" /></figure><p>We’ve spent the last month deep in design in collaboration with many talented teams. We’ve received an incredible amount of feedback from the EOS development community. And all of this has rolled up into our latest version of the <a href="https://github.com/MythicalGames/dGoods">dGoods v0.2 spec available on Github</a>.</p><p>In parallel, we’ve been hard at work on the implementation side of things. And this week, we are excited to announce the release of our closed Alpha for the dGoods Smart Contract implementation. The first teams to have access are the teams involved in the dGoods initiative. They will all be reviewing, integrating, and pressure testing the implementation to shake out any issues ahead of a public release.</p><p>Now, on to a few hot topics from the past few weeks…</p><p><strong>Asset Type JSON/Metadata</strong></p><p>The concept of “True Ownership” is synonymous with Blockchain technology. Because of immutability, for the first time ever, we can have true ownership over digital assets. So the question we get asked a lot is, why put data in a JSON file that’s not part of the token? Doesn’t that break immutability?</p><p>When we talk about a digital goods economy, we are talking about a wide variety of asset types, such as 3D game assets, 2D art assets, music files, concert tickets, and many more. For dGoods to be a meaningful standard, it needs to be flexible enough to handle any asset type thrown at it. This is where we see other standards missing the mark, and why we chose to build dGoods.</p><p>To achieve this flexibility, we developed the concept of “asset types”. Each asset type comes with it’s own set of data requirements that we store in a JSON file. Let’s compare JSON files for 2 different asset types.</p><p><strong>3D Game Asset</strong></p><pre>[{                 <br>  // Required Fields<br>  &quot;lang&quot;: string; two-letter code specified in the ISO 639-1 language standard<br>  &quot;name&quot;: string; identifies the asset the token represents<br>  &quot;description&quot;: string; short description of the asset the token represents<br>  &quot;imageSmall&quot;: URI pointing to image resource size 150 x 150 <br>  &quot;imageLarge&quot;: URI pointing to image resource size 1024 x 1024<br>  &quot;3drender&quot;: URI pointing to js webgl for rendering 3d object<br>  &quot;details&quot;: Key Value pairs to render in a detail view, could be things like {&quot;strength&quot;: 5}<br>  // Optional Fields<br>  &quot;authenticityImage&quot;: URI pointing to resource with mime type image representing certificate of authenticity<br>}]</pre><p><strong>Ticket Asset</strong></p><pre>[{<br>  // Required Fields<br>  &quot;lang&quot;: string; two-letter code specified in the ISO 639-1 language standard<br>  &quot;name&quot;: string; identifies the event the ticket is for<br>  &quot;description&quot;: string; short description of the event the ticket is for<br>  &quot;location&quot;: string; name of the location where the event is being held<br>  &quot;address&quot;: string; address of the location where the event is being held<br>  &quot;date&quot;: Unix time; starting date of the event<br>  &quot;time&quot;: Unix time; starting time of the event<br>  &quot;imageSmall&quot;: URI pointing to image resource size 150 x 150<br>  &quot;imageLarge&quot;: URI pointing to image resource size 1024 x 1024<br>  &quot;details&quot;: Key Value pairs to render in a detail view, could be things like {&quot;openingAct&quot;: &quot;Nickelback&quot;}<br>  // Optional Fields<br>  &quot;authenticityImage&quot;: URI pointing to resource with mime type image representing certificate of authenticity<br>  &quot;duration&quot;: string; length of time the event lasts for<br>  &quot;row&quot;: string; row where seat is located<br>  &quot;seat&quot;: string; seat number or GA for General Admission<br>}]</pre><p>Naturally, each asset type has very different requirements. Attempting to capture all these requirements in a one-size-fits-all approach would leave us with a standard that lacks the specificity needed.</p><p>With our “asset type” approach, developers can pick the type that’s relevant to their product. They are also free to create new types that might require a very specialized scope. And in doing so, dGoods is able to support an incredibly wide variety of digital asset types and usecases.</p><p>Back to the question at hand. Why put data in a JSON file that’s not part of the token?</p><p>The simple answer is that we kept it out of the token to save on RAM. While we’re not actively optimizing yet, we do weigh RAM usage into our design decisions. Strings are very expensive; and if we rolled all of that data into the token, the resulting smart contracts would be enormous, and the RAM cost would be prohibitively (and arguably needlessly) high.</p><p>But, doesn’t this break immutability?</p><p>Not at all. We do not prescribe where you put those asset type JSON files. To make them immutable, you simply store them on IPFS. IPFS sends you a hash of the file as a key for the purpose of looking up the JSON. If you put that hash in your token, then you have immutability.</p><p>With dGoods, we try to strike a balance between being prescribed versus providing flexibility. In this case, we wanted to give developers the option. If immutability is important to you, dGoods supports it.</p><p><strong>Early Adopters</strong></p><p>Another question we get a lot is: how can our team join the dGoods initiative?</p><p>dGoods is a free and open source standard aimed at supporting a diverse development community. As a result, if your product has interesting and unique digital asset usecases, then we want to hear from you. And we welcome you to join the dGoods initiative.</p><p>If your team is interested in being an early adopter and integrating with dGoods, get in touch with us; either through our website at <a href="https://dgoods.org/">dGoods.org</a> or via telegram at <a href="https://t.me/dGoods_EOS">https://t.me/dGoods_EOS</a></p><p>The dGoods standard is supported by a growing group of incredibly talented teams: Mythical Games, EOS Lynx, Scatter, Token Pocket, pixEOS, Cypherglass, Bloks.io, Math Wallet, Infiniverse, Greymass, MEET.ONE, ITAM Games, and NOVA Wallet.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd795521ba6c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dgoods/dgoods-smart-contract-closed-alpha-fd795521ba6c">dGoods Smart Contract — Closed Alpha</a> was originally published in <a href="https://medium.com/dgoods">dGoods</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[dGoods dev update — mar 5.19]]></title>
            <link>https://medium.com/dgoods/dgoods-dev-update-mar-5-19-ae5a812b1579?source=rss----d3a2c3088775---4</link>
            <guid isPermaLink="false">https://medium.com/p/ae5a812b1579</guid>
            <category><![CDATA[semi-fungible-tokens]]></category>
            <category><![CDATA[non-fungible-tokens]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[fungible-tokens]]></category>
            <dc:creator><![CDATA[Rudy Koch]]></dc:creator>
            <pubDate>Tue, 05 Mar 2019 14:26:33 GMT</pubDate>
            <atom:updated>2019-06-14T20:04:37.699Z</atom:updated>
            <content:encoded><![CDATA[<h3>dGoods dev update — mar 5.19</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Md7QicrAqA5TBolL03w5Mg.png" /></figure><p>Just a few short weeks ago, we <a href="https://github.com/MythicalGames/dgoods/blob/master/dgoods_spec.pdf">publicly released the dGoods v0.1 spec</a>. Our goal was to give the dev community an early look at our design thinking for the dGood standard. With dGoods, we’re aiming to provide a robust and comprehensive standard that supports a diverse range of development requirements. As a result, we wanted to give the dev community a chance to pressure test our thinking, our designs, and provide valuable, expert feedback.</p><p>In short, the response from the development community has been tremendous. We’ve had an outpouring of feedback and suggestions that have been critical to this step in our roadmap. So first off, we want to say a big THANK YOU to the EOS dev community for jumping in and supporting the dGoods initiative.</p><p><strong>Overview</strong></p><p>While the blockchain market is new and relatively small today, we don’t see it staying that way; not in the slightest. As blockchain continues to penetrate mass market, we will see a large booming economy emerge that is entirely centered around digital assets. What we see ahead is a world where hundreds of millions of digital assets are created, bought, and sold. It’s this vision that drives a lot of our design decisions for dGoods, and we wanted to be transparent about it.</p><p>While dGoods is free and open source, the design is primarily focused on commercial use cases like mass market gaming, ticket sales, the music industry, etc. This is something that heavily influences our decision making as we go through all the feedback we’ve received from the dev community.</p><p>From our perspective, while dGoods needs to solve the problems we face now, it also has to be designed to handle scale, and an incredibly fast growing market.</p><p>With that out of the way, let’s move onto some of the hot topics of the last few weeks.</p><p><strong>RAM efficiency</strong></p><p>The speculative RAM market on EOS has been a consistent challenge for the EOS development community. So it’s understandable that a large discussion point with dGoods has been around how we manage RAM correctly.</p><p>The short answer is, yes, there are optimization opportunities, but no, we’re not going to address them all now. Our plan is to first figure out what all the features are that dGoods needs to support. Then once that’s done, we will focus on optimizations. For those wondering about RAM efficiency, we hear you, and we’ll get to it as soon as we have a solid spec designed for dGoods.</p><p><strong>Secondary Indices for Categories</strong></p><p>There have been many debates around whether we include secondary indices for categories or not. While some believe we shouldn’t include them to save on RAM, others view it as critical to efficiently managing large volumes of digital goods. This is one of those decisions that has a trade off whichever way we go. But if we are aimed at providing a meaningful standard that will support hundreds of millions of digital assets, then the path forward becomes clear.</p><p>Here are two cases where providing this kind of flexibility can be key:</p><ul><li>A game aimed at mass market where we expect hundreds of thousands of players, if not millions. A single game reaching this kind of success will need flexible ways to easily organize an extremely large volume assets, and we expect to see many games with this kind of success.</li><li>An eBay-like digital asset marketplace will want to easily display and organize assets from every game and app available. They’ll want to provide a seamless user experience where their customers can easily find the things they’re looking for. As a game developer, these marketplaces play a key role in providing you with liquidity.</li></ul><p>In the very near future, where blockchain has achieved mass adoption, we believe having more flexibility with categorization is better than having less. And the trade-offs are worth it.</p><p><strong>Semi-Fungible Tokens</strong></p><p>There has been a lot of talk across the industry regarding Fungible and Non-Fungible Tokens (NFTs). NFTs have been central to inspiring us with the possibilities that blockchain can offer.</p><p>As we dove into the dGoods design, we found a new paradigm that we are calling Semi-Fungible Tokens (SFTs). We see SFTs playing a crucial role and being the primary use case for tokenized digital assets; therefore, we felt it was important to define it separately from NFTs and Fungibles.</p><p>Here are a few use cases to help explain SFTs:</p><ul><li>You are selling 200 tickets to a concert. All the tickets are the same, but they have a different seat #.</li><li>Your game has a limited set of 1000 digital swords that look and function exactly the same, except they all have a different serial # from 1–1000. Most players might not care about the serial #; a sword is a sword. But a few hardcore players might attribute varying value based on the serial # attached to the asset. For example, 1 of 1000 might be worth more to someone versus 200 of 1000.</li></ul><p>Yes, these are technically NFTs, but to the end user, they aren’t being advertised as 1 of a kind, the only one in the world, or 100% unique! Instead, for these types of use cases, we’re using the term Semi-Fungible Token.</p><p>We see a future where SFTs will be the dominant use case in the emerging digital goods economy; and as a result, we are making SFTs a core part of the dGoods standard. We’ll spend a lot more time talking about this soon.</p><p><strong>Next Steps</strong></p><p>With the draft v0.1 spec out in the public, we are continuing to gather feedback and refine the spec. We welcome any input you might have.</p><p>We are continuing to add more features to the spec which we’ll announce as we go.</p><p>And finally, we’re working on the first pass of the smart contract code for dGoods. We will be aiming to release an Alpha version very soon. It will be available first to only our collaborating teams and early adopters. So if you’re interested in being part of either of those groups, don’t hesitate to reach out to us on Telegram: <a href="https://t.me/dGoods_EOS">https://t.me/dGoods_EOS</a></p><p>A big thank you to all the teams behind the dGoods standard: Mythical Games, EOS Lynx, Scatter, Token Pocket, pixEOS, Cypherglass, Bloks.io, Math Wallet, Infiniverse, Greymass, MEET.ONE, ITAM Games, and NOVA Wallet</p><p>For more information on dGoods, visit us at:</p><p>Telegram: <a href="https://t.me/dGoods_EOS">https://t.me/dGoods_EOS</a></p><p>Website: <a href="https://dgoods.org/">https://dgoods.org/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae5a812b1579" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dgoods/dgoods-dev-update-mar-5-19-ae5a812b1579">dGoods dev update — mar 5.19</a> was originally published in <a href="https://medium.com/dgoods">dGoods</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing dGoods]]></title>
            <link>https://medium.com/dgoods/introducing-dgoods-7204a90193f4?source=rss----d3a2c3088775---4</link>
            <guid isPermaLink="false">https://medium.com/p/7204a90193f4</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[digital-asset]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[non-fungible-tokens]]></category>
            <dc:creator><![CDATA[Rudy Koch]]></dc:creator>
            <pubDate>Sun, 10 Feb 2019 18:41:54 GMT</pubDate>
            <atom:updated>2019-06-14T20:01:51.020Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xB0NpFpc4_5YC5fZ57GkuQ.png" /></figure><p>The future of blockchain is bright, and at the center of it all is a diverse and innovative group of developers with an equally diverse set of needs.</p><p>Blockchain is bringing about a new economy of digital goods. At Mythical Games, we refer to this new economy as the Player-Owned Economy; an economy where players and consumers can have true ownership over the digital assets they purchase. This paradigm is quickly washing up against many industries, and in the years to come, we will see hundreds of millions of digital items created, bought, and sold on the blockchain.</p><p>The core group of teams behind dGoods came together over a common goal to establish standards around digital goods in the blockchain industry. Our vision is to create an open source and free standard for handling all types of virtual items on any blockchain; and we’re rolling it out on EOS first.</p><p>Creating meaningful standards and best practices is a critical part of the evolution of any technology. When it comes to blockchain technology, we are very much in an early adopter phase. And in order to break into the mass market and drive adoption, we must support a thriving community of developers. Standards like the dGoods standard will play a critical role in achieving exactly that while providing the necessary support developers need to build great products and rich marketplaces.</p><h3>What does the dGoods standard offer?</h3><p>dGoods is a logical extension of the standard EOS token with the addition of significant functionality improvements that will allow teams to easily integrate and display virtual items.</p><p><strong>Metadata Templates for 3d and 2d assets</strong></p><p>The digital goods landscape is as diverse as it gets, and with the dGoods standard, we wanted to provide a flexible and comprehensive standard that could address a diverse range of digital item requirements.</p><p>Part of the dGoods standard involves specifying templates for metadata depending upon the type of digital good you’re working with. If the token is for a game, coupon, ticket, music file, piece of art, etc., standard templates can be created so that wallets will be able to render and display the relevant information, images, and even 3d objects. This allows for a wide array of digital asset types to be supported while providing the development community a flexible toolset to work with.</p><p><strong>Certificate of Authenticity</strong></p><p>True ownership is at the heart of the new player-owned economy that’s emerging from blockchain technology. With the certificate of authenticity, we provide developers an additional way to integrate proof of ownership into their tokenized digital goods.</p><p>Like with physical real-world objects, digital objects need a certificate of authenticity. In order to support a thriving economy of digital goods, it’s critical we give consumers confidence in their purchases. Built into dGoods is the ability to have immutable fields describing the object’s attributes that make up the certificate of authenticity. This will also allow developers to display a graphical representation to consumers as proof of the item’s attributes including things like its brand, creator, or rarity.</p><p><strong>Multiple categorized tokens in one token contract</strong></p><p>In a world where digital goods will be a major commodity, being able easily and efficiently manage large quantities of items is critical. Other token standards have one token with one contract. If a developer wants to issue different types of tokens, it has to be done through multiple contracts. This not only increases complexity but also cost. To address this, the dGoods standard has one token symbol per contract, but allows the creation of many sub-tokens.</p><p>As a further step, the dGoods standard allows these sub-tokens to be assigned a category, a token name, and tags which will allow wallets, exchanges and dApps to organize, filter, and display tokenized assets with ease. All of this can then be packed into one single transaction, allowing for developers and users to move groups of tokens around quickly and efficiently.</p><p><strong>Fungible and non-fungible in one contract</strong></p><p>As we explored the world of tokenized digital goods, we quickly realized that a single focus on NFT standards was not enough. Other standards only support fungible or non-fungible tokens (NFTs). However, many dApps and games will inevitably want to support both types of tokens. The dGoods standard will have the benefit of defining sub-tokens within one contract, while giving developers the freedom to make some of them fungible and others non-fungible. dGoods looks leverage the strengths of blockchain, capitalizing on concepts like verifiable scarcity, and allowing for the emergence of thriving embedded secondary marketplaces.</p><p><strong>Open Source</strong></p><p>The dGoods standard is an open and free standard initially for the EOS development community but is open for other blockchains to adopt. The standard will roll out first on the EOS mainnet. No other tokens are required to use the standard.</p><h3>What’s next?</h3><p>As of this post, we are deep into the design of the dGoods v0.1 spec, and actively preparing it for public release in the next couple of weeks.</p><p>In parallel, we are currently working on a dGoods roadmap that includes a v2 and v3 to follow our initial release of v0.1.</p><p>We are collaborating with many talented teams to build out the necessary infrastructure to support dGoods across a wide array of products and applications. We intend to open source all these tools once they are ready.</p><p>If you have any questions about dGoods, or if you are a team who wants to join the dGoods initiative, you can find us on telegram at: <a href="https://t.me/dGoods_EOS">https://t.me/dGoods_EOS</a> or visit us at <a href="https://dgoods.org/">https://dGoods.org</a></p><p>The teams behind dGoods are: Mythical Games, EOS Lynx, Scatter, Token Pocket, pixEOS, Cypherglass, Bloks.io, Math Wallet, Infiniverse, and Greymass</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7204a90193f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dgoods/introducing-dgoods-7204a90193f4">Introducing dGoods</a> was originally published in <a href="https://medium.com/dgoods">dGoods</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>