Topic: 🌱[ANN] SOIL | Environmental | Agriculture | Smart Contracts | Sustainable - page 142. (Read 237628 times)
September 20, 2015, 05:14:55 PM
Can you please address my issue with running both Ethereum and Soil on the same Windows machine?
[/quote]
ill try out the situation this evening and see what i can do. as far as i know, you can mine ethereum, and thus soil, with two instances concurrently, both CPU with the geth (or gsoil) applicatoin and gpu mining with the ethminer software. it conceivably should work ining ETH with one instance, and SOIL with the other. both central programs would need to be running (geth and gsoil) but id think youd be able to CPU mine on one while GPU ming the other coin with ethminer. like i said, ill try it tonite and report my findings.
im really not a programmer, by ANY stretch of the imagination, im more an idea guy and outreach sorta fella. i understand the underlying principles behind the ethereum platform that we are building SOIL with, im frankly very excited by the possibilities with where we can take it, which is why i signed up with soil in the first place. i believe in the platform, and i believe in the core developers ability to achieve the vision he began with. im a good marketer, but up unti a few weeks ago, i was growing white hairs on my chest trying to get bfgminer to work for me. (chuckles)
i know that the innovations soil is working on, his GUI wallet and where he wants to take that will change things up and in that i think hes many phases beyond the ethereum team right now. we have the committment to take this thing on for the long term, and we're not premining 800 million coins (i know,i exaggerate the ethereum premine/presale thing) theres a long term vision for SOIL and development will continue long after the initial launch, its an evolutionary process.
anywho, ill let you know what im able to do regarding ETH and SOIL at the same time.
September 20, 2015, 05:09:45 PM
Ok finally found problem on windows. There was some winsock problems.
gsoil is running, wallet working...
now, how to test gpu mining?
gsoil is running, wallet working...
now, how to test gpu mining?
September 20, 2015, 05:08:44 PM
But now, what is surprising me is that I see
(a) all those 30303 on the other side. (Perhaps that is actually the reason for the above mentioned conflict when running ethereum & soil on the same machine?)
and
(a) very strange, could be that gsoil tries to connect eth peers (port 30303)? To be adapted in the eth sources. (a) all those 30303 on the other side. (Perhaps that is actually the reason for the above mentioned conflict when running ethereum & soil on the same machine?)
and
(b) all those ports 49295 46012 35640 55404 ... on my machine active. Haven't I only allowed 39338 ? Does every peer get a new port on my machine?
(b) port 39338 is only allowed for incoming connections. If your server connects other peers, the local port is random: all ok.Much appreciated, GoldenEye!
I also tried out a stricter chain policy "... -P OUTPUT DROP" - but then gsoil only started, and afterwards stayed silent, no sync connections. And no "gsoil attach" possible.
What would I do about random ports ... if I want to lock down the firewall completely, with
Code:
sudo iptables -P OUTPUT DROP
sudo iptables -A OUTPUT -p tcp --sport 39338 -j ACCEPT
Code:
sudo iptables -P OUTPUT ACCEPT
All not super-relevant right now, I know that.
But this is still on testnet - so why not also solve security questions, once and for all time ... right?
If you drop all outgoing connections, then your server cannot find any peer.
Because (normally) no one knows your server (except manually peers with admin.addPeer()), you will also have no connections from outside. "No connection" is the expected result.
If you allow only connections to port 39338, this could work, but I'm not sure.
I would not do this on a server, because system updates, etc will not work...
September 20, 2015, 05:02:29 PM
Anyways ...
During my firewall experiments I succeeded to lock myself out twice *g* so I had to start over
--> my address, and enode are different now. The old address is lost. These are the new values:
IP
enode
Please: can you try adding me, if you get a connection to my node?
address (has changed too)
Dev, please update your list, thx.
During my firewall experiments I succeeded to lock myself out twice *g* so I had to start over
--> my address, and enode are different now. The old address is lost. These are the new values:
IP
Code:
178.62.133.174
enode
Code:
enode://b991afe4cc439d3382b2502b7269ffe85289f5f0f2226c1bae698b5691314696243dbfe72917bbfd3fe56389732061720ecec3a4fa33581298677cecbec7725b@178.62.133.174:39338
Please: can you try adding me, if you get a connection to my node?
Code:
admin.addPeer('enode://b991afe4cc439d3382b2502b7269ffe85289f5f0f2226c1bae698b5691314696243dbfe72917bbfd3fe56389732061720ecec3a4fa33581298677cecbec7725b@178.62.133.174:39338')address (has changed too)
Code:
0xa182c58ee6c9f3f64dba468cbc7a4dbdcc654530
Dev, please update your list, thx.
September 20, 2015, 04:51:46 PM
But now, what is surprising me is that I see
(a) all those 30303 on the other side. (Perhaps that is actually the reason for the above mentioned conflict when running ethereum & soil on the same machine?)
and
(a) very strange, could be that gsoil tries to connect eth peers (port 30303)? To be adapted in the eth sources. (a) all those 30303 on the other side. (Perhaps that is actually the reason for the above mentioned conflict when running ethereum & soil on the same machine?)
and
Perhaps someone starts it without the / with a wrong --networkid=39338 ? Or is running older code?
(b) all those ports 49295 46012 35640 55404 ... on my machine active. Haven't I only allowed 39338 ? Does every peer get a new port on my machine?
(b) port 39338 is only allowed for incoming connections. If your server connects other peers, the local port is random: all ok.Much appreciated, GoldenEye!
I also tried out a stricter chain policy "... -P OUTPUT DROP" - but then gsoil only started, and afterwards stayed silent, no sync connections. And no "gsoil attach" possible.
What would I do about random ports ... if I want to lock down the firewall completely, with
Code:
sudo iptables -P OUTPUT DROP
sudo iptables -A OUTPUT -p tcp --sport 39338 -j ACCEPT
Code:
sudo iptables -P OUTPUT ACCEPT
All not super-relevant right now, I know that.
But this is still on testnet - so why not also solve security questions, once and for all time ... right?
September 20, 2015, 04:38:57 PM
But now, what is surprising me is that I see
(a) all those 30303 on the other side. (Perhaps that is actually the reason for the above mentioned conflict when running ethereum & soil on the same machine?)
and
(b) all those ports 49295 46012 35640 55404 ... on my machine active. Haven't I only allowed 39338 ? Does every peer get a new port on my machine?
(a) all those 30303 on the other side. (Perhaps that is actually the reason for the above mentioned conflict when running ethereum & soil on the same machine?)
and
(b) all those ports 49295 46012 35640 55404 ... on my machine active. Haven't I only allowed 39338 ? Does every peer get a new port on my machine?
(a) very strange, could be that gsoil tries to connect eth peers (port 30303)? To be adapted in the eth sources.
(b) port 39338 is only allowed for incoming connections. If your server connects other peers, the local port is random: all ok.
September 20, 2015, 04:30:06 PM
To the developers:
On Windows 8.1 I have Ethereum Go (geth.exe) wallet running and accepting RPC on default port.
When I start Soil Go wallet on the same computer it exits with an error:
If I stop ethreum (>exit) then gsoil starts without any issues.
I tried the same thing with Expanse and it starts just fine when Ethereum is already running.
So both wallets are running - you might want to fix that before launch.
On Windows 8.1 I have Ethereum Go (geth.exe) wallet running and accepting RPC on default port.
When I start Soil Go wallet on the same computer it exits with an error:
Code:
...
Fatal: Error String IPC: Access is denied.
Fatal: Error String IPC: Access is denied.
If I stop ethreum (>exit) then gsoil starts without any issues.
I tried the same thing with Expanse and it starts just fine when Ethereum is already running.
So both wallets are running - you might want to fix that before launch.
Please check the IPC path (settings tab). I'm pretty sure that you'll find there the IPC file from Ethereum. EDIT: which is in use by the geth process
The right setting should be
This will only help temporarily. The reason is, that the soil wallet uses the same configuration file as ethereum (~/.config/Etherdiene/Etherwall.conf).
If you change it in Etherwall (soil), it will be changed in Etherwall (eth) also.
September 20, 2015, 03:47:05 PM
Addendum:
... a while later
so some of those SYN_SENT connections switched to ESTABLISHED - and all on port 39338 on my side.
... a while later
Code:
web3.net.peerCount
5
Code:
netstat -atpn | grep gsoil
tcp 0 0 127.0.0.1:39339 0.0.0.0:* LISTEN 1466/gsoil
tcp 0 1 178.62.133.174:45305 167.160.161.127:42786 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:43383 51.254.34.117:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:40328 120.26.55.59:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:55098 45.32.232.65:39338 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:33540 68.110.70.120:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:34177 99.39.88.163:44444 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:38793 45.32.241.124:53900 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:59051 62.210.113.107:30301 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:53911 104.131.165.3:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:44145 37.48.87.120:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:48664 176.31.100.149:30303 SYN_SENT 1466/gsoil
tcp6 0 0 :::39338 :::* LISTEN 1466/gsoil
tcp6 0 0 178.62.133.174:39338 45.32.239.236:38874 ESTABLISHED 1466/gsoil
tcp6 0 0 178.62.133.174:39338 138.128.169.51:35512 ESTABLISHED 1466/gsoil
tcp6 0 0 178.62.133.174:39338 113.161.82.243:55668 ESTABLISHED 1466/gsoil
tcp6 0 0 178.62.133.174:39338 92.52.46.10:33470 ESTABLISHED 1466/gsoil
tcp6 0 0 178.62.133.174:39338 46.101.231.134:43934 ESTABLISHED 1466/gsoil
so some of those SYN_SENT connections switched to ESTABLISHED - and all on port 39338 on my side.
September 20, 2015, 03:35:37 PM
anyone experienced in iptables?
when I lock it down, with
and add the peers with
After a while, I get these connections
And it is syncing. So all good, in a way.
But now, what is surprising me is that I see
(a) all those 30303 on the other side. (Perhaps that is actually the reason for the above mentioned conflict when running ethereum & soil on the same machine?)
and
(b) all those ports 49295 46012 35640 55404 ... on my machine active. Haven't I only allowed 39338 ? Does every peer get a new port on my machine?
I want to lock down the droplet as much as I can (all DROP and then allow specific ports),
and I am wondering about the correct iptables command to do that.
Thanks to you experts - and sorry to you newbs for this post ;-)
when I lock it down, with
Code:
sudo iptables -A INPUT -p tcp --dport 22 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 39338 -j ACCEPT
sudo iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
sudo iptables -A INPUT -j DROP
sudo iptables -S
sudo invoke-rc.d iptables-persistent save
sudo iptables-save > /etc/iptables/rules.v4
and add the peers with
Code:
gsoil attach
admin.addPeer('enode://0c0ce5d1b95de13732faa98d0ea5d6acafabdf2ec56104a52ffb7f34ee2fa08bb09524cd6e9c28ba5a57a84ec0352fd52a3065ea6af51967afba78537412b3c4@45.63.84.6:39338')
admin.addPeer('enode://20b058d1e867b665f6e698100325f68e07ebface3ebef6aaacc5b00b7b77c10fc338e7863e933a497ae1b85d2f2a7b7b59d18d0eb48f05eb92d7d1a947399b31@113.161.82.243:39338')
admin.addPeer('enode://24e1e3b7bba2b0de7707dcc957faf541b87e99a665ff6cf93a1d6b60c2f65603dc69b14e97eb1e3219fa52bd26a27bb26957c0126da154a4895fc4ef873bac54@45.32.239.236:39338')
admin.addPeer('enode://a076e6e4f86f00074729a8473e3b3799208648f5952b1cd8df2c8b61816f44289b1cc6bb4d6116d0f48447f38540d5b2891aaea8062895c9867a0818bb6ec2f5@138.128.169.51:39338')
admin.addPeer('enode://2214963c7bb2fb98c0edefa09ebc46c5fbcb5055c7fdd884d90e6b8ed8acb6568f1f035b25e609346e09f681323be60b5998dc49f02582dd78f766e31679e2e5@45.32.232.65:39338')
admin.addPeer('enode://30bd5e679759792be064edef05d5195889337294af1788072e4ad8bed6ea8bb559f00e8a43f275e945aacc5aed8117d950f79057bc7675742eacbf937f68393e@52.25.0.225:39338')
admin.addPeer('enode://fb2bc8add1af21cb0f34710a3ded14a003da44a5e7cc80f963e46f417fc0a31d94bb5a25b62ff13b3e07df950028b85f0589e7eef3d46d5abeb2a32b0d051475@46.101.231.134:39338')
admin.addPeer('enode://d482c87d6085fe3f303d2a3a8d25937eda09f75713610dd68c475031c110e658da78fa207574c370e4f6121aed21d77a2e73a4ddab8af50aaeb6cf4672f5fe5c@178.62.133.174:39338')
admin.addPeer('enode://5daffbd838b3745d17b202505f3c5d89f4926e5b0642123c1fbd1f0ce655c83242514ce13dc9ab4d7a0fa612ab8934525eec6265eaf19c7b3c10a61f77869a1e@95.170.180.71:39338')
After a while, I get these connections
Code:
sudo netstat -atpn | grep gsoil
tcp 0 0 127.0.0.1:39339 0.0.0.0:* LISTEN 1466/gsoil
tcp 0 1 178.62.133.174:49295 195.212.29.91:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:46012 113.161.82.243:39338 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:35640 192.161.57.159:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:55404 139.162.14.216:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:39284 108.163.197.58:42786 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:46789 173.230.228.143:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:49814 99.44.217.202:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:59058 52.25.0.225:39338 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:38191 108.61.179.7:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:48598 45.56.93.253:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:44005 195.178.117.10:30303 SYN_SENT 1466/gsoil
tcp 0 1 178.62.133.174:32825 104.236.65.136:30303 SYN_SENT 1466/gsoil
tcp6 0 0 :::39338 :::* LISTEN 1466/gsoil
tcp6 0 0 178.62.133.174:39338 92.52.46.10:33470 ESTABLISHED 1466/gsoil
And it is syncing. So all good, in a way.
But now, what is surprising me is that I see
(a) all those 30303 on the other side. (Perhaps that is actually the reason for the above mentioned conflict when running ethereum & soil on the same machine?)
and
(b) all those ports 49295 46012 35640 55404 ... on my machine active. Haven't I only allowed 39338 ? Does every peer get a new port on my machine?
I want to lock down the droplet as much as I can (all DROP and then allow specific ports),
and I am wondering about the correct iptables command to do that.
Thanks to you experts - and sorry to you newbs for this post ;-)
September 20, 2015, 01:40:34 PM
So no one knows how to set this on windows ?
September 20, 2015, 10:58:34 AM
We offer a bounty for every community member who setup one node or more.
You will be part of the main-net genesis, because we will place the bounty direcly in there for you SOIL address!
You will be part of the main-net genesis, because we will place the bounty direcly in there for you SOIL address!
Do you need the soil address too?
September 20, 2015, 10:53:46 AM
Hi community,
if some one of you have a server on hand with a changeless ip address, please contribute to SOIL
in setting up a node for the test-net.
We offer a bounty for every community member who setup one node or more.
You will be part of the main-net genesis, because we will place the bounty direcly in there for you SOIL address!
...
Post your node string in our thread here, together with the ip address of the server
i.e.:
enode://[email protected]:39338
Thanks
if some one of you have a server on hand with a changeless ip address, please contribute to SOIL
in setting up a node for the test-net.
We offer a bounty for every community member who setup one node or more.
You will be part of the main-net genesis, because we will place the bounty direcly in there for you SOIL address!
...
Post your node string in our thread here, together with the ip address of the server
i.e.:
enode://[email protected]:39338
Thanks
one of my nodes here:
admin.addPeer("enode://45f3481f3fff1ec049f12970e2a62c659ee8d7339af7f3cb44d473b8424183346f5d72548a3341c93a6a197ea671ad1b9db0450a210fc5aac3f6b6923d83f852@52.28.46.180:39338")
September 20, 2015, 09:54:57 AM
Done everything and i simply cannot start gsoil on w7-64. What i am missing?
http://i.imgur.com/Lt2wwwc.png
Can you post your command?http://i.imgur.com/Lt2wwwc.png
September 20, 2015, 09:51:51 AM
Done everything and i simply cannot start gsoil on w7-64. What i am missing?
http://i.imgur.com/Lt2wwwc.png
http://i.imgur.com/Lt2wwwc.png
Can you post your command?
September 20, 2015, 09:50:36 AM
lol... you didn't announce the block reward yet.... if the block reward is 1 coin 200k premine is equal to 200000 blocks 
If the premine is 200k i vote for block reward of 1k coins
Who need yet another ETH clone with huge premine?
If the premine is 200k i vote for block reward of 1k coins
Who need yet another ETH clone with huge premine?
You are right - sorry!
I have 2 suggestions for the blockreward by now 5 and 7.
So, I would suggest a blockreward of 6.
Target Block Time: democratic vote
September 20, 2015, 09:47:03 AM
Done everything and i simply cannot start gsoil on w7-64. What i am missing?
http://i.imgur.com/Lt2wwwc.png
http://i.imgur.com/Lt2wwwc.png
September 20, 2015, 09:42:20 AM
lol... you didn't announce the block reward yet.... if the block reward is 1 coin 200k premine is equal to 200000 blocks
If the premine is 200k i vote for block reward of 1k coins
Who need yet another ETH clone with huge premine?
If the premine is 200k i vote for block reward of 1k coins
Who need yet another ETH clone with huge premine?
You are right - sorry!
I have 2 suggestions for the blockreward by now 5 and 7.
So, I would suggest a blockreward of 6.
September 20, 2015, 09:34:50 AM
Hi community,
if some one of you have a server on hand with a changeless ip address, please contribute to SOIL
in setting up a node for the test-net.
We offer a bounty for every community member who setup one node or more.
You will be part of the main-net genesis, because we will place the bounty direcly in there for you SOIL address!
....
Post your node string in our thread here, together with the ip address of the server
i.e.:
enode://[email protected]:39338
Thanks
My node: enode://5daffbd838b3745d17b202505f3c5d89f4926e5b0642123c1fbd1f0ce655c83242514ce13dc9ab4d7a0fa612ab8934525eec6265eaf19c7b3c10a61f77869a1e@95.170.180.71:39338if some one of you have a server on hand with a changeless ip address, please contribute to SOIL
in setting up a node for the test-net.
We offer a bounty for every community member who setup one node or more.
You will be part of the main-net genesis, because we will place the bounty direcly in there for you SOIL address!
....
Post your node string in our thread here, together with the ip address of the server
i.e.:
enode://[email protected]:39338
Thanks
Can you confirm that it is OK?
September 20, 2015, 08:40:59 AM
Can we use wallet address generated in testnet for mainnet?
It's possible, but we advise you not to do this.
There will be no support from us regarding this.
OK, Thanks!
September 20, 2015, 01:49:27 AM
How to check current ballance on testnet?
go to your wallet
Jump to: