From 16e4addca05efb76bc284a2b7e407237e34fcebc Mon Sep 17 00:00:00 2001 From: crStiv Date: Mon, 13 Jan 2025 16:38:06 +0100 Subject: [PATCH 1/3] Update example_usage.md --- example_usage.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/example_usage.md b/example_usage.md index 0502943..274bd4a 100644 --- a/example_usage.md +++ b/example_usage.md @@ -1,11 +1,11 @@ Example dGoods Usage ==================== -The following tutorial walks through an example creating, issuing, selling, and buying a +The following tutorial walks through an example of creating, issuing, selling, and buying a hypothetical ticket (semi-fungible asset). This assumes access and understanding regarding EOSIO software -- as this tutorial is designed to explain the dGoods contract and not how to use EOSIO. Specifically, all of the following actions are called from a command line environment and should be -straight forward translating these actions to their corresponding rpc calls. +straightforward forward translating these actions to their corresponding rpc calls. If a more basic understanding is needed first, visit https://developers.eos.io/. Additionally, there will be future tutorials aimed at beginning EOS developers. @@ -51,8 +51,8 @@ cleos get table dgood.token dgood.token tokenconfigs Now that we have set the tokenconfig data, we are free to create and issue tokens. Before actually issuing tokens to an account, we must first create the token type. This allows us to set properties -such as if the token will be fungible, transferable, burnable etc and what the max supply should be. -Note we are not doing time based mintint, but if we wanted to we would set `max_issue_days` to some +such as if the token will be fungible, transferable, burnable etc, and what the max supply should be. +Note we are not doing time-based minting, but if we wanted to we would set `max_issue_days` to some value other than 0 and set max_supply to 0. Alternatively, you can set a max issue time and a max supply. @@ -286,7 +286,7 @@ Now querying the asks table shows that both dgoods are listed in one batch. } ``` -Something interseting to note is that for a listing of a single dgood, the `batch_id` will be the +Something interesting to note is that for a listing of a single dgood, the `batch_id` will be the `dgood_id`. However, if the batch size is greater than 1 then `batch_id` will be the first `dgood_id` in the batch. There is no way to directly query if a dgood is in a specific batch without indexing all of the data in the asks table. @@ -295,7 +295,7 @@ indexing all of the data in the asks table. Finally to make a purchase, a user sends EOS to the dgoods contract with a memo in the form of "batch_id,to_acount". That is, you may buy on behalf of others as long as you specify which account -you want the dgood to be transfered to -- of course in most cases the `to_account` will be your +you want the dgood to be transferred to -- of course in most cases the `to_account` will be your account. Using a shorthand for EOS transfers built into cleos: From 4396b3d8b7d8f8461fb9d6853603b16b497a6fb2 Mon Sep 17 00:00:00 2001 From: crStiv Date: Mon, 13 Jan 2025 16:39:09 +0100 Subject: [PATCH 2/3] Update dgoods_spec.md --- dgoods_spec.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dgoods_spec.md b/dgoods_spec.md index fa5b6e8..c23dfdb 100644 --- a/dgoods_spec.md +++ b/dgoods_spec.md @@ -16,7 +16,7 @@ Cameron Thacker, Stephan Cunningham, Rudy Koch, John Linden Introduction ============ -dGoods is an open source and free standard for handling the virtual +dGoods is an open-source and free standard for handling the virtual representation of items, both digital and physical, on the EOS blockchain. While our initial focus is on assets for video games, we are designing something that does not preclude use for other types of goods. @@ -30,7 +30,7 @@ be fungible or semi-fungible while others are non-fungible. What really separates this standard from other NFT standards that exist is the hierarchical naming structure of the token. Fungible tokens are identified by symbol:category:name and NFTs have an extra token id -associated. This allows for unprecedented organization of tokens. It +associated. This allows for the unprecedented organization of tokens. It also enables wallets and dApps to surface tokens by category or name, providing search and filtering functionality. From 8160789c455f5df7e422440aa1206b12cc9e9361 Mon Sep 17 00:00:00 2001 From: crStiv Date: Mon, 13 Jan 2025 16:40:31 +0100 Subject: [PATCH 3/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7abbcd7..21ee212 100644 --- a/README.md +++ b/README.md @@ -61,7 +61,7 @@ one may set both a max issue time and max supply. v1.0 ---- -Many changes have occured since v0.4 that made it into the 1.0 release. Some of these changes are +Many changes have occurred since v0.4 that made it into the 1.0 release. Some of these changes are not backwards compatible since changes were made to multiple tables' structure. It is recommended to start from a fresh contract rather than try and migrate data to the new version.