Core/grin
0
0
Fork 0
mirror of https://github.com/mimblewimble/grin.git synced 2025-01-21 03:21:08 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions

advanced example wallet needs to point to node api

Browse source
This commit is contained in:
AntiochP 2017-11-12 13:58:51 -05:00 committed by GitHub
parent 04eb400422
commit 54dbda6bc2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/build.md
View file

@ -128,7 +128,7 @@ As before, node 1 will create the blockchain and begin mining. As we'll be runni
First, we run a wallet server to receive rewards on port 15000 (we'll log in debug mode for more information about what's happening)
node1$ grin wallet -p "password" -r 15000 receive
node1$ grin wallet -p "password" -a "http://127.0.0.1:10001" -r 15000 receive
Then we start node 1 mining with its P2P server bound to port 10000 and its api server at 10001. We also provide our wallet address where we'll receive mining rewards. In another terminal:
@ -152,7 +152,7 @@ Similar to Node 2, we'll set up node 3 as a non-mining node seeded with node 2 (
Node 3 is now running it's P2P service on port 30000 and its API server on 30001. You should be able to see it syncing its blockchain and peer data with nodes 1 and 2. Now start up a wallet listener.
node3$ grin wallet -p "password" -a "http://127.0.0.1:10001" -r 35000 receive
node3$ grin wallet -p "password" -a "http://127.0.0.1:30001" -r 35000 receive
In contrast to other blockchains, a feature of a MimbleWimble is that a transaction cannot just be directly posted to the blockchain. It first needs to be sent from the sender to the receiver,
who will add a blinding factor before posting it to the blockchain. The above command tells the wallet server to listen for transactions on port 35000, and, after applying it's own blinding factor to the transaction, forward them on to the listening API server on node 1. (NB: we should theoretically be able to post transactions to node 3 or 2, but for some reason transactions posted to peers don't seem to propagate properly at present)