Quick Start
Follow the steps below to quickly set up your own Marble Digital Item Contract
Last updated
Follow the steps below to quickly set up your own Marble Digital Item Contract
Last updated
Navigate to the freshly cloned project directory: marble-digital-items/
The included build script will attempt to compile the Marble contract.
Ensure you have EOSIO CDT 1.6 or greater installed and included in your path.
After a successful build, the generated WASM and ABI files will be placed in the build/marble
folder. The deploy script will read these artifacts during deployment.
Deploy the built Marble contract to the given account
and network
.
In the commands below, replace the variables in curly braces with the appropriate values for your use case. Variables separated by bars require a selection, meaning choose one of the choices.
By default the mainnet and testnet endpoints are for the Telos Blockchain Network, but switching to a different EOSIO chain is as easy as replacing the default endpoints in the deploy script with ones from the desired network. The local network defaults to port 8888 on localhost (the default nodeos port).
The first action called on any Marble contract should be the init()
action. This will set the initial contract version and initial admin in the config
table. The admin is the only account that is authorized to create new groups.
Groups are collections of items that all share like behaviors. A single Marble contract can have any number of groups.
Group Examples: cards
, monsters
, dragons
, players
New digital items can now be created within the group. Every Marble item belongs to one and only one group.
Every Marble item can be customized by assigning properties to it. For the full list of available property types see the Marble Layers section of the documentation.
For example, give an item a title by simply assigning it a new Tag:
Or give it an item level with an Attribute:
Or give it a creation timestamp with an Event:
Or back it with fungible tokens using a Bond: