Topic: 🌱[ANN] SOIL | Environmental | Agriculture | Smart Contracts | Sustainable - page 141. (Read 237628 times)

Ok, my "SoilWallet"
https://github.com/soilcurrency/SoilWallet.git
looks like this new one.

But jjjordan is right: It is not the wallet itself, only the GUI  

Will this wallet be able to work simultaneously with ethereum?

No change:

ubuntu@ip-172-31-17-16:/opt/soil$ sudo netstat -tapn | grep gsoil
tcp        0      0 127.0.0.1:39339         0.0.0.0:*               LISTEN      5570/gsoil     
tcp        0      1 172.31.17.16:36820      84.110.80.85:30303      SYN_SENT    5570/gsoil     
tcp        0      0 172.31.17.16:43781      45.63.120.163:30303     ESTABLISHED 5570/gsoil     
tcp        0      0 172.31.17.16:53163      45.32.239.236:39338     ESTABLISHED 5570/gsoil     
tcp6       0      0 :::39338                :::*                    LISTEN      5570/gsoil     
tcp6       0      0 172.31.17.16:39338      45.63.84.6:34432        ESTABLISHED 5570/gsoil     
tcp6       0      0 172.31.17.16:39338      46.101.231.134:59494    ESTABLISHED 5570/gsoil     

pff DAGs are in ethash folder..
.. http://i.imgur.com/nuwAum9.png

Of course you are absolutely right. Etherwall is the GUI to the wallet, not the wallet itself.

By the way,
your problem is really windows specific. I think the mechanism for inter process communication (NamedPipe pipe or whatever) was not changed in the soil sources, so it conflicts to a running geth process.

Here is a screeny:

Here finally all works and running. Testing one 280x blocks are flying. Except i usually get 26MH/s and now i am looking at ~20.

If I meant GUI, I would've said so...
And by the way, as far as I know there is no GUI wallet - there is GUI to the gsoil.exe, am I correct?

So short answer - console.

ok Thanks... need to find that v4 (found it) and check. Cpu mining working just testing my 3 of 4 cores and all is fine. No block yet tho...

[/quote]

it took me a long time to find a block, too. even with a brand new computer with quad-core and a radeon r5 graphics card, i cant normally find a block of ANYTHING. ive had my soil instances running on my computer for an hour right now, and havent found one. yesterday, i found two in the first five minutes. i dont have a mining rig, cant afford one just now (ive got a five year old with a yen for hockey thats eating away at my budget) and once we launch, ill probably just mine on the suprnova pool. ive been mining SHF and EXP there and making enough to make me content.

Do you mean the GUI wallet or the gsoil console?

Ok, my error. This are unix sockets, not available on windows. Can you post a screenshot of the Etherwall (EDIT: Soil GUI) settings tab?

No. It is a VPS, in the cloud. With 'cpulimit -b -e gsoil -l 50'. And this time it took even longer *g*
And I have a an impressive CPU-mining hashrate:
so at difficulty
every 201396th block should be mine *g*

Someone out there must be using GPUs for mining  ...

ok Thanks... need to find that v4 (found it) and check. Cpu mining working just testing my 3 of 4 cores and all is fine. No block yet tho...

You are welcome

im running win 10, so unsure how this would work on win7, but in the V4 package, there should be a "start_gpu_mining.bat" in the main directory. start gsoil up first, let it load up to the line that starts out with "modules:" and then launch the gpu mining .bat file. you can start your cpu mining in gsoil concurrently with "miner.start(#)" in the console, with # being the number of threads you want to work with (as far as i understand it, and remember im less than technically savvy) the number of threads is the same as the number of processors your CPU possesses. i have a quad core processor so i usually put a 4 in there. experiment with it a bit. hope that helps.

One day, someone (or me) will find a solution, I am sure :-)
Perhaps I could open a range of 100 ports, that gsoil also knows about ... or something like that.


Oh, I actually solved all that.  Even with "sudo iptables -P OUTPUT DROP".
Was a bit of puzzling, but found a nice script that I could adapt, make a bit less restrictive, and then extend.

Now only specific outgoing connections are allowed - and their return packets, too.
And all (e.g. apt-get update, etc) is still working!

Of course, I need quite a few
- but that's what for-loops are for :-)



Having said all that, with that restricted approach ... I cannot get soil running yet,
Giving up for now. To be solved later :-)

Thanks a lot, GoldenEye!



Yippieh :-)

Thx!

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.

I'm connected to your server  
{
    Caps: "eth/60, eth/61",
    ID: "b991afe4cc439d3382b2502b7269ffe85289f5f0f2226c1bae698b5691314696243dbfe72917bbf d3fe56389732061720ecec3a4fa33581298677cecbec7725b",
    LocalAddress: "172.31.17.16:39338",
    Name: "Gsoil/v1.1.3-7443f0f8/linux/go1.4.2",
    RemoteAddress: "178.62.133.174:48599"
}