Skip to content
EOS smart contract for the cryptoship game
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.README
actions
contract
scripts
tests
utils
.babelrc
.env.template
.gitignore
LICENSE
README.md
config.js
package-lock.json
package.json

README.md

cryptoship

A battleship like game on the EOS blockchain.

State Machine

Edges are the possible contract actions available from each state.

State Machine

Template

Requires eosio-cpp (>= v1.4.0) to be installed from the eosio.cdt package to compile the smart contract. Also needs cmake for compiling the smart contract. (brew install cmake)

Compiling

This template uses cmake to build the contract. Run the following commands once to setup the process:

mkdir build
cd build
cmake ../contract

Now you can run npm run compile which will run make to create the .wasm and .abi in /build.

Deployment

Fill out the missing private key in .testnet.env, .production.env.

There's a npm run init script that sets up your contract account and test accounts by creating them and transferring them enough EOS + RAM/NET/CPU.

This should only be run on your local network to create accounts!

To deploy to the network specified in .<environment>.env, run:

NODE_ENV=testnet npm run deploy

Testing the smart contract

You can run the following scripts to automatically create scripts for your actions defined in the ABI file.

npm run create_actions

You can then invoke these scripts to push actions to your deployed smart contract without using cleos:

npm run action -- <actionName>

Inspecting the contract's table can be done by:

npm run table -- <tableName>
You can’t perform that action at this time.