Mythical Games, EOS Lynx, and Scatter Team up for dGoods Standard to      Set a New Benchmark for Virtual Items on the EOS Blockchain
January 23, 2019 09:00 AM Eastern Standard Time
LOS ANGELES--( BUSINESS WIRE )--Mythical Games ( https://mythical.games )      today announced a new industry-wide initiative that will help formalize      the fast-growing global marketplace of digital assets between creators,      consumers and studios. The dGoods standard (short for      “Distributed/Digital Goods”) was developed as a step towards a      commercially-endorsed benchmark for creating, managing and distributing      digital products. It will be made available as an open source software      license for developers at https://dgoods.org
This effort is a collaboration led by Mythical Games, EOS Lynx, Scatter,      and other key blockchain firms who saw the need for a robust digital      goods standard for the development community. Some of the key features      that developers can expect from the upcoming dGoods standard include:
Metadata Templates for 3d and 2d assets
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. Certificate of Authenticity
Like with physical real-world      objects, digital objects need a certificate of authenticity. Built into      dGoods is the ability to have immutable fields describing the object’s      attributes that make up the certificate of authenticity as well as the      graphical representation to display to consumers the proof of the item’s      attributes including its brand, creator, or rarity. Multiple categorized tokens in one token contract
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. These sub-tokens can be assigned a      category, a token name, and tags to allow wallets and dApps to organize      and filter tokens with ease. Fungible and non fungible in one contract
Other standards      only support fungible or non-fungible tokens (NFTs). However, many dApps      and games will want to support both types of tokens. The dGoods standard      will have the benefit of defining sub-tokens within one contract, giving      the developer the freedom to make some of them fungible and others      non-fungible. Open Source
The dGoods standard is an open and free standard      initially for the EOS development community but is open for other      blockchains to adopt. With dGoods rolling out first on EOSIO blockchain, the vision is to      support and promote an industry standard of practice as blockchain      technology adoption continues to grow in gaming, entertainment, and      beyond. “Digital assets are at the core of the new economy that is spawning from      blockchain technology. Hundreds of millions of digital items will be      created, bought, and sold in the years ahead. It’s critical that we      establish a meaningful digital goods standard that can support a diverse      and innovative development community. When we looked at what was out      there, we didn’t see anything that suited our needs at Mythical Games;      and we weren’t the only ones. We’re proud to be collaborating with EOS      Lynx, Scatter and many other great teams to bring the dGoods standard to      the blockchain industry. And we’re excited to roll it out on EOS first,”      commented Rudy Koch, Head of Blockchain for Mythical Games. Fred Krueger, CEO of Workcoin (EOS Lynx), added, "EOS Lynx is thrilled      to be working with Mythical Games, Scatter and the EOS community to help      build the first in-wallet standard for digital goods. This is a      watershed moment for blockchain games, coupons and ticketing      applications. It will change how we think of crypto." Headquartered in Los Angeles, Mythical Games is a next-generation game      technology studio that specializes in building major game IPs and a      digital ecosystem around player-owned economies. The team looks to      innovate technically and creatively to bring players, creators, brands      and studios even closer together within customizable game entertainment. Mythical recently announced its new release ‘Blankos Block Party’, a MMO      party game for mainstream audiences, will launch across multiple formats      later this year. For more information on this initiative and the dGoods platform, please      visit: https://dgoods.org

Mythical Games, EOS Lynx, and Scatter Team up for dGoods Standard to Set a New Benchmark for Virtual Items on the EOS Blockchain

Jan 8
We are going to build a simple Front End that will use Scatter for logging in and authorising actions on the EOS blockchain
Once upon a time, the only wallet I knew was the one that carries my lunch money. Today there are numerous wallets out there, but instead of keeping your money they keep your private keys. Now among all the wallets out there I have chosen to work with Scatter due to it’s popularity among the EOS community. Most of the EOS Dapps being built these days, almost all of them supports Scatter. Scatter has also become increasingly popular among Ethereum and Tron, making it a solid investment for your future Dapp development. Setting up Scatter
Scatter used to come in the form of a Chrome plugin, but now it has officially dropped that in favour of a full native app. If you have not installed Scatter, the first step you need to do is download it from its GitHub page here. For the purpose of this guide we are going to import our EOS account we created on the CryptoKylin testnet the other day into our Scatter wallet. If you have no idea on how to create a testnet account, I have already written about it on my first guide under the EOS Account section, click here. Now once you have your testnet account name and private key, fire up Scatter. On your first run it will ask you to create a password. You will need this password to unlock your wallet when ever you want to use it again at a later time. Since we are planing to import an EOS testnet account, we must add the testnet details to Scatter first. The way to do this is to go to the Settings -> Networks. You will find the Settings button (shape of a gear icon) on the top right corner. Once again you need to key in your password. CryptoKylin Testnet details
Under the “Your Networks” tab, click on the Add button. Key-in the details according to the screenshot above. At the time of this writing these inputs are still valid, however to confirm that you have the latest inputs you should always ask in their telegram group here. Import Keys
Ok now go back to the main interface of Scatter. Click on the “Add Keys” button on the bottom left corner. Add Keys menu
Import Key menu
Another 3 options will be shown, click on the first button “Text” since we have our private key in the text format. Go ahead and paste your testnet private key. Since every account you create on the testnet comes with an Owner and Active key, for simplicity sake you can just import your Active key. Linked Accounts
Since we have already added the CryptoKylin details under the networks settings, Scatter automatically links your private key to your account name on the CryptoKylin testnet. You can view this under the Linked Accounts tab. Optionally you can give a nicer name for this key under the “Key Name” text box above. I am going to name it youraccname1@active. At this point, we have completed all the setup necessary for Scatter to work with our Front End. Here is a summary of the main tasks we have accomplished so far:
Created a testnet account
Imported our testnet private key to Scatter
In the next section we will develop the Front End so it will talk with Scatter nicely. You will want to keep Scatter app running in the background so that our Front End detects it. Front End
In my previous guide , I have written about building a simple Front End for EOS. It was a simple Dapp that is able to login the user with their account name and private key. To make this Dapp more practical, we are going to modify it so that it can work with Scatter. When ever an action needs to be performed on the blockchain; for example logging in, with Scatter the user does not need to key in their private key every time. On the front-end side we do not need to cache their private key anymore, as this could cause vulnerability issues. By using Scatter, this is how it is going to work from now on: every time we need to perform an action, we invoke Scatter from it’s javascript API. Scatter will then request the user for their permission on which key to use to perform the action. After the user has authorised then Scatter will return us a signature object that we can use to sign the transaction on the blockchain. Super simple, clean and more secure! I have modified our previous front-end to now work with Scatter. Let’s get started by cloning my latest Github project and I will walk you through the main changes. Open terminal and type this:
Once all the files have been cloned to your local machine. Get into the project directory and install all the dependencies
$ cd eos-scatter
export default EosService;
To work with Scatter, we first need to import 2 libraries: ScatterJS and ScatterEOS. We then specify the constants to store the endpoint and network details, in our case we will be using the testnet details. We will be only needing to main methods here, which is the connect and transaction. Scatter: connect method
In the connect method we simply try to link a Scatter account with our Dapp. Scatter will then prompt the user to select an account they would like to use with our Dapp. Scatter: transaction method
In the transaction method, we are invoking an action on the EOS smart contract. What Scatter will do in this case is to prompt the user with a dialog to allow or deny this action. Wrapping Up
For the final section of this guide let’s have a look at the Login page where we use our EosService. 
</script>
Here we simply import our EosService, initialise our class and pass in the parameters into the class constructor. We then call the connect() method and the transaction() method passing in the name of the action we want to call on the smart contract and it’s input data. If it’s successful the method will return true and we change our loginStatus state to true and route the user to our main page. Dapp main page, console prints out the transaction details
If you open the chrome developer tools you should be able to see the transaction details printed out on the console. Congratulations! we have successfully integrated Scatter to your Dapp. We have reached the end of this guide, but I would love to hear what you guys are working on. If you need help don’t be afraid to reach me .

How to integrate Scatter with your EOS Front End

How to Integrate Scatter Desktop Wallet into your EOS Dapps using Reactjs
Dec 3
You might already be familiar with Scatter, a web/desktop wallet that makes it easy for ordinary users to store their private key and interact with apps. Integrating Scatter into apps can be tricky and, since Scatter is improving quickly, there have been some breaking changes introduced recently. I’ve had a bunch of people ask me about integrating Scatter, so I created this tutorial on how to integrate the latest version of Scatter Desktop into your distributed EOS application. Create your Scatter Integration
We’re going to start by setting up Scatter inside of a Component and creating a transaction method. We’ll be able to use this anywhere in our application to enable users to sign transactions with Scatter. Create Separate Scatter File and install dependencies
Make sure you import eosjs, scatterjs-core and scatterjs-plugin-eosjs2. Notice that we’re importing ‘scatterjs-plugin-eosjs2’ as our version of eosjs is greater than 16.
npm i -S eosjs
npm i -S scatterjs-plugin-eosjs2
I’d highly recommend breaking out your core Scatter functionality into a separate file, which I typically call eosio-client.js. import React from “react”;
import ScatterJS from “scatterjs-core”;
Set up your network and endpoint
Next, we’ll want to define an endpoint and network. Your endpoint will be the location of your eosio contracts. If you are using a contract on your local machine, it will probably be something like http://localhost:8888. If you’ve deployed to Jungle Net, you can choose an endpoint from here: http://jungle.cryptolions.io/#apiendpoints . On the mainnet, most of the block producers have an api endpoint available and you can choose from any of these: https://www.eosdocs.io/resources/apiendpoints/ . We’re going to be accessing a contract deployed to the Jungle net, so we’ll use the following endpoint:
const endpoint = " http://jungle2.cryptolions.io:8 0";
We’ll set up our network next. Networks reference certain blockchains so you can get accounts and build signature providers. Note that we’re going to use the Jungle (test net) chainId in this example. If we were using the Mainnet, we would use a chainId of “aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906”. We also specify the blockchain being used since you can actually use Scatter with other blockchains like Ethereum and Tron. const network = {
Set up your Component
We’ll be able to instantiate an instance of the EOSIOClient from anywhere in our app, which will give us access to the variables and methods we’re creating here. We’re going to set up our constructor to accept one parameter, contractAccount. This will enable us to interact with multiple contracts within our application by passing in whichever contract name we want to use for a particular EOSIOClient instance. export default class EOSIOClient extends React.Component {
constructor(contractAccount) {
this.contractAccount = contractAccount;
Set up ScatterJS from within our constructor function. Make sure to pass in new ScatterEOS(), which will tell Scatter that we’re using “scatterjs-plugin-eosjs2”. ScatterJS.plugins(new ScatterEOS());
Connect to Scatter and Create References
The last thing we’ll do within the constructor is connect to Scatter, create a reference to your account and create a reference to the fully initialized Scatter proxy. This is a lot of code, but it’s best to show it as a single block. Let me know in the comments if this needs more explanation. try {
} // Close the constructor function
Note that it’s incredibly important that you set this.accounts above rather than hardcoding your account information or asking your users for the information. Add a transaction method
You are now ready to sign transactions using Scatter. Whenever we call a transaction method on an EOSIOClient instance, we’re going to pass in an action name and data. This is a fairly simple transaction that we’ll use for basic interaction with our smart contracts. You can check out the eosjs documentation to structure more intricate (multiple action) methods, but this should work for most basic smart contract interaction. transaction = (action, data) => {
};
Congratulations, you have successfully set up your application so that users can sign transactions using Scatter. You can see a full version of this file here . Create an EOSIOClient Instance in your Application
Make sure you import EOSIOClient into your file. import EOSIOClient from "../utils/eosio-client";
Inside of your constructor, create a this.eosio reference. Make sure you head over too ScatterApps and add your app to the apps.json file. Pass that contract account name into your initializer. this.eosio = new EOSIOClient(“YOUR APP NAME”);
Create your first transaction
We’re ready to create our first transaction. In this example, a user is going to buy RAM. In our interface, a user can enter a number of bytes to buy and click ‘Buy Now’, which triggers this function call. handleBuyRam = async event => {

How to Integrate Scatter Desktop Wallet into your EOS Dapps using Reactjs

As virtual reality (VR) becomes more popular and recognised, a number of prestigious awards are beginning to include VR as part of its nominations, sometimes even creating entirely new categories to recognise the achievement of immersive media. In 2017 a VR experience was created and released by creative studio Scatter in collaboration with Oculus Studios. Based on the larger Zero Days documentary, Zero Days VR told the story of the Stuxnet malware. Now it has been revealed that the title has won an Emmy Award. Zero Days VR looks at the world of cyber security through the lens of Stuxnet, a type of malware generally recognised as the first cyber weapon to do damage in the real world. Viewers can experience how the Stuxnet virus was originally created as part of a secret mission developed by the governments of the USA and Israel in order to sabotage an Iranian nuclear facility. The audience can see the invisible worlds inside a computer in a new way in order to get a better understanding of how these ‘cyber weapons’ work. The VR documentary has now won the Emmy Award for Outstanding New Approaches: Documentary at the 39th News & Documentary Emmy Awards, beating out other nominees such as Finding Home from Time and We Are Witnesses from The Marshall Project. The co-founder of Scatter, Yasmin Elayat announced the win on Twitter . The Twitter post also included the full acceptance speech for the award, along with a following tweet acknowledging the work of the various people who had contributed towards the project. Zero Days VR is available on the Oculus Store for the Samsung Gear VR, Oculus Rift and Oculus Go and a version is also available on the HTC Vive, priced at $4.99 (USD). For future coverage of award-winning VR titles, keep checking back with VRFocus . Share
Staff Writer at VRFocus who helps bring the news to your screens. Rebecca comes from a background in technology and computing and has been a gamer and console collector since the days of the Commodore 64. She also hosts a weekly gaming related radio show on RadioSEGA.

VR Documentary Zero Days Wins an Emmy

During his band's performance in Brazil's São Lourenço do Oeste, one Tequila Baby member selected one fan to be the subject of a crowdsurfing experience. Unfortunately for everyone involved, the hand-picked fan gave the crowd a lot more than they were bargaining for once his pants fell down and showgoers scattered. Watch the fingers!

VIP Package? Audience Member’s Wardrobe Malfunction Causes Crowd to Scatter

EOS Lynx is a cryptocurrency payment platform.

EOS Lynx

Mythical Games develops game technology studios that focus on connecting gamers, creators, brands, and game developers through personalized experiences and content. It provides decentralized gaming applications that use blockchain technology to create games that allow players to own their developed assets. It was founded in 2018 and is based in Los Angeles, California.

Mythical Games

Mythical Games , EOS , and Scatter Team up for dGoods to Set a New Benchmark for Virtual Items on the EOS

GroupStream

The Potion

New York University

Mentor Graphics

Scatter is a blockchain platform that connects to applications on EOS, Ethereum, and Tron. Users can exchange tokens and manage assets.

Wells Fargo Success Story

Professional Services

Platform Overview

Scatter

Compete with Scatter?

Compete with Scatter?

Discover the right solution for your team