npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@sandbox-smart-contracts/core

v0.0.1

Published

smart contracts for the sandbox

Downloads

4

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

felipeasffelipeasfwojciech-turekwojciech-turekatkinsonhollyatkinsonhollymvanmeerbeckmvanmeerbeckadjisbadjisb

Keywords

ethereumsmart-contractsThe Sandbox

Readme

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:

  • Website: www.sandbox.game
  • Discord: https://discordapp.com/invite/vAe4zvY
  • Telegram: https://t.me/sandboxgame
  • Medium: https://medium.com/sandbox-game

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.