Skip to content

Latest commit

 

History

History

core

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
.openzeppelin
.openzeppelin
 
 
.vscode
.vscode
 
 
asset-snapshot-data
asset-snapshot-data
 
 
asset_snapshot-data-rinkeby
asset_snapshot-data-rinkeby
 
 
data
data
 
 
deploy
deploy
 
 
deploy_polygon
deploy_polygon
 
 
deploy_utils
deploy_utils
 
 
deployments
deployments
 
 
docs
docs
 
 
documentation
documentation
 
 
imports
imports
 
 
lib
lib
 
 
scripts
scripts
 
 
setup
setup
 
 
src
src
 
 
test
test
 
 
utils
utils
 
 
.docs.example
.docs.example
 
 
.editorconfig
.editorconfig
 
 
.env.example
.env.example
 
 
.eslintignore
.eslintignore
 
 
.eslintrc.js
.eslintrc.js
 
 
.gitignore
.gitignore
 
 
.mocharc.js
.mocharc.js
 
 
.prettierignore
.prettierignore
 
 
.prettierrc.js
.prettierrc.js
 
 
.readthedocs.yaml
.readthedocs.yaml
 
 
.release-it.json
.release-it.json
 
 
.setup.js
.setup.js
 
 
.solcover.js
.solcover.js
 
 
.solhint.json
.solhint.json
 
 
.solhintignore
.solhintignore
 
 
CHANGELOG.md
CHANGELOG.md
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
codechecks.yml
codechecks.yml
 
 
hardhat.config.ts
hardhat.config.ts
 
 
mkdocs.yml
mkdocs.yml
 
 
package.json
package.json
 
 
pull_request_template.md
pull_request_template.md
 
 
scripts.js
scripts.js
 
 
tsconfig.json
tsconfig.json
 
 

README.md

Smart-Contracts for The Sandbox

www.sandbox.game

The Sandbox is a user-generated content (UGC) gaming platform that will empower creators through digital ownership and monetization of 3D voxel creations made and shared by users around the world.

Learn more:

Blockchain Features

We’re adopting the best standards to reach to players who are not familiar with Blockchain and Web3 technologies, simplifying the UX and on-boarding

  • Dual token structure smart-contract: ERC-721 / ERC-1155
  • Escrowless Auctions
  • Meta-Transactions
  • EIP-712 DRAFT for Human-Readable signature messages
  • EIP-1776 DRAFT submitted by Pixowl to Ethereum for Native Meta-Transactions

More detailed information can be found on our Medium article: https://medium.com/sandbox-game/blockchain-features-in-the-sandbox-7db91fcc615c

Get Started Instructions

If you want to check out our contracts and run the test follow these instructions :

SETUP :

yarn

RUN TESTS :

yarn test

ENVIRONMENT VARIABLES :

The root of this repo contains a example.env file. You can copy this to your own .env file and populate the FIELDS with your own values. We use the MNEMONIC field to hold your seed-phrase. Alternately, if you want to use an HD-Wallet, the buidler-docs have a section on configuration here: https://buidler.dev/config/#hd-wallet-config

Technical Documentation

You can explore here the documentation of our tokens and blockchain featurs:

Your First Pull Request

We are using feature branches to host the code of an upcoming feature. All feature branches start with "feat/" prefix, each feature branch is intended for a single purpose. The following branches will reject direct pushes:

  • master branch
  • "feat/" prefixed branches

So, in order to commit your changes to master you will have to

  • git checkout master
  • git checkout -b feat/exampleFeature
  • git push --set-upstream origin feat/exampleFeature
  • git checkout -b exampleFeature
  • git push --set-upstream origin exampleFeature

Now you can write your code and push your changes to the exampleFeature branch, once your'e done you need to open a pull request from exampleFeature to feat/exampleFeature, and then another pull request from feat/exampleFeature to master.