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.
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.
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.
With the release of dGoods v1.0 public beta, the code is now available on Github 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 “issues” section in our Github repo for those interested in submitting any issues you might find.
Now onto a few key topics for this release…
DEX in a token
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.
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.
Here’s how it works:
- 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.
- 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.
- 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.
- By allowing users to specify a “to_account”, users can buy an item on behalf of others by specifying the account to send to.
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.
“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.
dGoods v1.0 Features
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:
DEX in a token
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.
Multiple tokens and sub-tokens in one contract
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.
Semi-Fungible Tokens (SFT)
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.
Multiple layers of token categorization
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.
Metadata Asset Types
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.
Token localization
Blockchain has global reach, and marketplaces need to be able to display tokenized digital goods in their language of choice.
For a full list and more comprehensive details, please refer to the dGoods Github readme file.
What’s next?
Now that the beta is live, we’re focused on bug fixing, trading feedback, and security audits for v1.0.
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.
If you are interested in contributing to the dGoods open source standard, we welcome you to reach out via our website at dGoods.org, or via telegram at t.me/dGoods_EOS.
