Built to promote the development of a Security Token Standard . Web page forked from and inspired by erc721.org using Gulp.js for automation and Bootstrap CSS and FontAwesome Icons.

The source code for this page is kept at https://github.com/SecurityTokenStandard/sts-website

1. Please create a new directory on your computer for the Security Token Standard Website (STS)
2. To clone repo to your local development environment e.g. git clone [email protected]:SecurityTokenStandard/securitytokenstandard.github.io.git to your newly created STS folder.

1. Create a new/seperate github issue on the Security Token Standard repo (securitytokenstandard.github.io) : https://github.com/SecurityTokenStandard/securitytokenstandard.github.io/issues

1. Description of the addition/bug location and potential beneficial impact/negative impact of the vulnerability you discovered.
2. Observed behavior
3. Expected behavior
4. If it is a bug to be fixed, please describe how to replicate — A detailed description of the steps required to reproduce the vulnerability — POC scripts, steps taken, and screenshots will all be helpful.

The Security Token Standard community will respond to Issues or PR's within 96 hours from the time of submission. We will review each report and remain responsible for deciding whether is it a good addition to the standard. High quality, easy to read reports are very much appreciated.

If you are submitting a report on a discovered bug, please reference the rules on https://bounty.ethereum.org as they stand for this project as well:

Specifically:

1. First come, first serve.
2. Issues that have already been submitted by another user or are already known to the Polymath team are not eligible for bounty rewards. (Make sure that the issue has not been previously submitted or fixed in other more recent commits)
3. Public disclosure of an actively exploitable vulnerability makes it ineligible for a bounty.

Sponsored by Polymath (https://polymath.network)