btw - on instructions (
https://github.com/shiftcurrency/shift/wiki/Mining ) says:
port 53901 but when I run "shift-windows-amd64 --rpc" it says:
Listening on [::]:53900Is that normal OK ?
C:\Shift>shift-windows-amd64 --rpc
I0918 10:26:14.120904 4492 database.go:73] Alloted 16MB cache to C:\Users\zonott\AppData\Roaming\Shift\chaindata
I0918 10:26:14.162907 4492 database.go:73] Alloted 16MB cache to C:\Users\zonott\AppData\Roaming\Shift\dapp
I0918 10:26:14.176907 4492 backend.go:301] Protocol Versions: [61 60], Network Id: 1
I0918 10:26:14.177907 4492 backend.go:338] Blockchain DB Version: 3
I0918 10:26:14.273913 4492 chain_manager.go:237] Last block (#76070) eb0f4fd93117a0d86c97b8f8d1bc4845787f1c670be90faa
b6baac4423f4a3e1 TD=12909820312602956
I0918 10:26:17.268084 4492 cmd.go:125] Starting SHIFT/v0.3.0/windows/go1.5.1
I0918 10:26:17.269084 4492 server.go:311] Starting Server
I0918 10:26:17.340088 4492 udp.go:207] Listening, enode://47e91621913440dcc3a307cbcb7cc8e7a5a9c04393cae07f8c32d1e9782
fe182121c901f2260841f85525bb88051d59fc1db49a5db6b3686011c8f3bc72c6068@0.0.0.0:53900
I0918 10:26:17.342088 4492 server.go:552] Listening on [::]:53900
I0918 10:26:17.342088 4492 backend.go:567] Server started
I0918 10:26:17.345089 4492 ipc_windows.go:724] IPC service started (\\.\pipe\shf.ipc)
I0918 10:26:28.665736 4492 chain_manager.go:661] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 25.0014m
s. #76071 [8067a970 8067a970]
53900 is the p2p port. The server.go is stating that it opens up the p2p socket, not the rpc socket. In other words, yes normal.
EDIT: saw your question about RPC. --rpc just enables the rpc-server on localhost. If you should explain so everyone understands, you could say that RPC allows remote execution of commands. Which means, there are some security implications. --rpc only enables it on localhost, as it should be.
The dangerous stuff begins when you add, --rpcaddr "yourexternalip" and that the rpc port is reached in public. but as stated, thats not the default behaviour.
Regards
