Topic: [ANN] Sia - Decentralized Storage - page 441. (Read 1382189 times)

Be sure to open it from the command prompt and it should work fine.    gpu-miner -I 22 -C 5 may work well for your card.

I don't think that worked for me..  I'll have a few tests later on..

Just a friendly reminder  

I am selling KS small blocks of SIA coin for those who need.

Please see: https://bitcointalksearch.org/topic/m.11629065

Trying to keep all this in the trading thread  

THX  
TM

I think that miner is geared at Nvidia (https://github.com/NebulousLabs/Sia-GPU-Miner/releases/tag/v1.0.1)

Can't do it, that would almost certainly violate the paypal TOS, and even if it didn't it would probably violate money laundering laws. We can't help people go from usd to crypto. There are too many very-high-barrier regulations.

Down the line though, we should be legally able to help people go btc<->siacoin. Some hosts/nodes will have both btc and siacoin and will serve as market makers, you can then use payment channels to trade with them. That's a long way down the line.

Like any major new technology, there are going to be barriers to entry and it's going to take time to bridge them. It's something that's heavily on our minds, but it doesn't matter how easy it is to get siacoins if the storage platform isn't very useful (if say, you're limited to 500mb files and can only upload 1 file at a time). So our biggest focus is making something that people will want to use. If it's worth the pain of getting siacoins, then that says great things about the platform and its future. The barriers to crypto are slowly being removed (Coinbase just announced an instant exchange platform, for example), and everyone benefits from that.

We'll be doing our part in the coming months, but our immediate goal is to make the storage platform better. Without a worthwhile storage platform, we're just another altcoin.

If you want a stable miner for your AMD card that reports accurately use the one Wolf0 posted. Just be sure to replace the .cl file like he instructs:

https://bitcointalk.org/index.php?topic=1060294.980

Chances are it will take weeks to find a block with your hashrate though.

The miner from the git (https://github.com/NebulousLabs/Sia-GPU-Miner/releases/tag/v1.0.1) instantly crashes , I'm not even sure what miner I have now...  this is a disaster.
Few people mine at 500-1000mhs , the rest are mining at 50-110mhs, and if I'm a new user coming here and want to mine the shit doesnt even work.

PayPal for Sia direct purchase would be great and very important! The "how to" queue is really crazy for somebody who wants only see how good and usable Sia is and then maybe consider move from old cloud system or not.

how to:
1) find fiat <--> BTC exchange
2) send Proof of Identity
3) send Proof of Residence
4) find BTC <--> altcoins exchange
5) start using password manager for the first time
6) how to transfer BTC to exchanges
7) learn selling BTC for Sia
8 ) learn withdraw Sia into Sia wallet
9) finally try sia

It is not Sia's fault but this is really extremely complicated once I see it in one place.

That is all I have ever seen while mining. Forget the 12 blocks. most likely false reporting from miner. Just have to wait 24 hours and hope you see a true block payout. What is your hash rate? I was using the old glitch'y software on my 7970's and saw at times 1,500 blocks mined, with a hash rate of 105 MH, but was lucky to see just 1 block actual payout. I have never found a block using the newer low demand software miner (less glitch'y) that produced around 60 MH

Miner says 12 blocks mined today.. but..

{"State":"Off","Mining":false,"Threads":1,"RunningThreads":0,"HashRate":0,"BlocksPerWeek":0,"BlocksMined":0,"OrphansMined":0,"Address":"eea951fa559d96ee40d70652e174158855169386f44b30de05bf7d63ca4cf456"}

mining with 280X..    wtf is going on?

thats actually a great idea ...

a mini sia market ...

#crysx

with a in wallet payment system i mean, users should be able to buy and sell sias in wallet without an exchange. you could implement a small marketplace for users to buy and sell sia via paypal for example.

think about a normal users. he downloads the app, want to place some files. now he has to learn crypto currencys, has to learn how to use exchanges, has to learn how to buy bitcoins, has to learn how to transfer bitcoins to exchanges, has to learn selling bitcoins for sias, has to learn withdrays sias into sia wallet... to complicated. without a easy solution for this, this will be only a plaything for techies.

I don't believe its a windows issue. I had no problems once I had the local ISP flash the firmware in my basic DSL phone line type modem (not cable) and get it hard written into their server. Once done, ports are open. They have to see the device (PC that's hosting) attached to the modem, and its mac address and IP.

*I am plugging directly in to the ISP issued DSL modem for my hosting PC only. My home router plugs into it as well, but allows me to have a separate network for all other computers as an added layer of security. Keep in mind I also have a static IP.

Also, if some have DHCP set in their personal routers (which most probably do) the IP will change to the PC doing the SIA hosting occasionally if they do a reboot on router and that could issue a new IP to their hosting PC and the ports may show as closed as a result. Best to add a "reserved DHCP IP address in your personal router making the hosting PC retain a permanent IP to their SIA computer.

But this will not open the ports in your DSL modem unless you are bridged with your personal router. Most ISP modems will not allow you to edit the ports freely or directly, and if you do or can, they may be reset by the ISP back to their default settings unless they are permanently flashed as mentioned earlier.

Never had to touch windows firewall. W7 64 bit

Now if someone is using Norton etc. with a firewall feature turned on that may change the equation some?

ok, Just food for thought   ya its a bit confusing.  

Obviously this is an issue going forward with using the wallet for hosting. At some point it will have to be made dummy proof for all users. Especially for large scale use as we all want and need it to be 

yeah im seeing

tcp4       0      0  192.168.1.5.9981       46-185-58-255-su.61547 ESTABLISHED
tcp4       0      0  192.168.1.5.9981       46.185.102.115.22983   ESTABLISHED

and
tcp4       0     12  192.168.1.5.9981       212-97-0-99.stat.12850 ESTABLISHED

but still showing errors in the app  and in siad

listen tcp :9981: bind: address already in use


https://www.dropbox.com/s/ul3sfqpwl1wcni6/Screenshot%202015-06-16%2021.45.00.png?dl=0

Well this is what I get so seems correct yes?

Active Connections

  Proto  Local Address          Foreign Address        State

  TCP    192.168.100.22:9981    p57A9A664:49299        ESTABLISHED
  TCP    192.168.100.22:9981    sokl-adm:54473         ESTABLISHED
  TCP    192.168.100.22:9981    194:52628              ESTABLISHED

I had the announce problem on two separate machines.

Both was due to my routers port forwarding & firewall settings.

Try running sia gui or siad then run netstat in cmd or terminal.

Look for sia on a local address like 192.168.0.5:9981

To the right of this it should have an foreign external (not local) ip address.

If this address is also a local one the fault it with your router settings.

It should look like this.

Riskys-iMac:~ Owner$ sudo netstat
Password:
Active Internet connections
Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)    
tcp4       0      0  192.168.0.4.9981       sokl-adm.cl.tks..50254 ESTABLISHED
tcp4       0      0  192.168.0.4.54845      ec2-54-167-105-1.9981  SYN_SENT  
tcp4       0      0  192.168.0.4.9981       212-241-15-196.s.27808 ESTABLISHED
tcp4      37      0  192.168.0.4.54741      d.v.dropbox.com.https  CLOSE_WAIT
tcp4       0      0  192.168.0.4.9981       pool-108-30-50-9.55980 ESTABLISHED
tcp4       0      0  192.168.0.4.54719      195-154-181-121..hylaf ESTABLISHED

Not like this

tcp4       0      0  localhost.9980         localhost.54650        ESTABLISHED
tcp4       0      0  localhost.54650        localhost.9980         ESTABLISHED
tcp4       0      0  localhost.9980         localhost.54649        ESTABLISHED
tcp4       0      0  localhost.54649        localhost.9980         ESTABLISHED
tcp4       0      0  localhost.9980         localhost.54648        ESTABLISHED
tcp4       0      0  localhost.9980         localhost.54647        ESTABLISHED

Some routers need to be restarted,before aplying the changes in configuration.If you restarted router,and still have problems with ports 9981 and 9982,then you need to change firewall settings.If you run windows,go to control panel/System and security/windows firewall/advanced settings,and create new inbound rule in left top corner.

I'm really curious as to why people are having these problems. Most of our testing is done on Linux so it could be a Windows problem. Hard to say for sure if I can't reproduce it locally.

Maybe until we have UPnP support we should just add a "--force" option that allows you to announce even if Sia doesn't think you're reachable. I'm not sure that's a great idea though.

While we're advertising stuff, I'd also like to invite you guys to #siatalk on freenode.

My router shows the IP for that PC on the connected equipments list. Also when I run ipconfig on that same PC it tells me IPv4 Address is that same one. So that has to be the correct local IP right? What else could it be?