Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
294d1d2
commit 69792cb
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Demo | ||
|
||
## Getting Started | ||
|
||
See "Running the demo" in `README.md`. | ||
|
||
## Behind the scenes | ||
|
||
The demo webapp is made with a lightweight node.js webserver called `lite-server`. Once the `demo` | ||
command is called, a new tab should open in your default browser to a splash screen called "Signal | ||
Token Protocol Demo". | ||
|
||
On load, the webapp will attempt to connect to a local Ethereum net at `localhost:9545` and deploy a | ||
`SignalTokenProtocol` contract to it. It will also grant the first address in your local net | ||
500000 SIG tokens. | ||
|
||
Enter an "Amount per Referral". On submit, a campaign is created and stored in the | ||
`SignalTokenProtocol` contract. The contract then queries the `TokenStub` contract and retrieves | ||
balances for the relevant accounts. | ||
|
||
Click the "spectiv" banner. When you do, the campaign you created in the previous step will be | ||
executed by the executor (in this case, the web application) and you should see the address | ||
balances update as the advertiser sends the agreed upon sum of SIG tokens to the publisher. |
69792cb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
69792cb