[ANN] Sia - Decentralized Storage - page 409.

ol92

sr. member

Activity: 445

Merit: 255

Quote from: Taek on September 02, 2015, 11:34:16 PM

Why is the price being hit so hard Huh

People are running away from Sia like it's a toxic investment, I just don't get it.

On the one hand, even good coins have highs and lows, pump and dump periods.

On the other hand, the unit of acount is on the low side (like coins such as mintcoin for instance : when you have total number of coins in few years more than the 10 billion range) : when the price is low it can go down to the 10 sat range. In this situation you have 10% difference at least between bid and ask for most exchage where the smallest unit of price is a satoshi, which is not healthy (for mintcoin there was some days when price was 1 satoshi : traders can manipulate the price and have huge profits : 100% difference between bid and ask!).

To my opinion, before sia became highly used and popular (therefore with a high price), it would be better to have exchange price in kilo sia instead of sia : with current price it would be around 10000 sat for a ksia : you will have a minimum difference of 1/10000 between bid and ask instead of 1/10!

tricass

sr. member

Activity: 394

Merit: 250

Crypto enthusiast

Quote from: chrysophylax on September 03, 2015, 01:19:47 AM

Quote from: Taek on September 02, 2015, 11:34:16 PM

Why is the price being hit so hard Huh

People are running away from Sia like it's a toxic investment, I just don't get it.

dumpers taek - dumpers ...

dont worry - its not all that its cranked up to be with 'price' ...

the value of sia is in the project - and the project is all about you and the team ...

keep at it mate - there will be accolades coin time later ...

#crysx

good chance for those who are finding it hard to mine sia to pickup some and at cheaper prices. i'm finding it difficult to mine so i'm forced to buy. the one block i supposedly found is no longer showing up as mined.

the other thing that is also impacting price is the inflation model. looks like about 280k sia per block so even at 10 sat that's around 4 btc per day that needs to be spent. it's held up but you'll need more buyers and that will come with time as word spreads.

agree with the others that you should focus on the project and leave the market to price sia accordingly.

chrysophylax

legendary

Activity: 2912

Merit: 1091

--- ChainWorks Industries ---

Quote from: Taek on September 02, 2015, 11:34:16 PM

Why is the price being hit so hard Huh

People are running away from Sia like it's a toxic investment, I just don't get it.

dumpers taek - dumpers ...

dont worry - its not all that its cranked up to be with 'price' ...

the value of sia is in the project - and the project is all about you and the team ...

keep at it mate - there will be accolades coin time later ...

#crysx

powersup

sr. member

Activity: 406

Merit: 250

Don't stress too much about the price. I think current trading reflects that of a relativity small group aware of the project. Personally I glanced over the OP back in May and thought of it as a game changer, but admittedly I was skeptical at the time. Sia only recently popped back on my radar after being mentioned on another site I visit frequently. Ive now jumped on board after seeing the great progress made. It's only a mater of time before other traders and investors become aware and see the potential in this project.

Roozy

newbie

Activity: 43

Merit: 0

Good. More SIA for me!

I actually happen to think this is a great investment... it's just that it isn't going to explode overnight. This is going to take some time but it will be well worth it.

The price of SIA is intrinsically tied to the price of storage/bandwidth and decentralization of data... What people are willing to pay for those is what the price of SIA will end up being.

This project has amazing potential and I for one believe it's going to be the next big thing.

Taek

hero member

Activity: 543

Merit: 501

Why is the price being hit so hard Huh

People are running away from Sia like it's a toxic investment, I just don't get it.

bitspill

legendary

Activity: 2087

Merit: 1015

Quote from: SalimNagamato on September 02, 2015, 01:45:40 AM

Quote from: bitspill on September 02, 2015, 01:44:55 AM

Quote from: SalimNagamato on September 02, 2015, 01:40:26 AM

Hi
i am running siad on one terminal, and on other terminal trying to run siac status:

sl@sl:~$ siac status
Could not get daemon status: Browser access disabled due to security vulnerability. Use Sia-UI or siac.

it gives me error to use siac..and i am using siac
how to solve this ?

Are you using Go 1.5?

There seems to be an issue with siac when run on 1.5, it should be fixed soon or in the meantime try Go 1.4 if you don't mind.

yes... go 1.5
will try with go 1.4
thanks

A pull request w a just merged that should resolve this issue and allow you to run go 1.5 if you wish.

Pito001

sr. member

Activity: 301

Merit: 250

Quote from: Taek on September 01, 2015, 03:29:01 PM

Quote from: Pito001 on September 01, 2015, 12:34:03 PM

"As a result, compatibility with the old wallet.dat files has been broken. To transfer funds from v0.3.3.3 to v0.4.0, you must send them from the v0.3.3.3 client to a v0.4.0 address. Note that you can run both clients at once (from different folders)"
For this I need my wallet to sync of course. Embarrassed

People tried doing that, and a few of them ended up doing the steps out of order and losing coins. 0.4.1 (probably less than a week out) (will have a GUI as well) will have support in 'siac' (and maybe the GUI) to load old wallets in a safe way.

After 0.4.1 is released, there should be no need to open a 0.3.3.x wallet ever again.

The old wallets were just simply too hard to use correctly, and they've eaten too many coins. We've built tools to make this unnecessary, you will be able to get your old coins by using 0.4.1 'siac'. There will be instructions to help you do this. Really sorry about all of that.

Quote from: Pito001 on September 01, 2015, 12:34:03 PM

Same problem here, using 0.3.3-beta.2 b383.

Getting:
0 KS Peers: 0 Block Height: 1

Can you put your gateway.log on pastebin? It will help us make sure that we've solved the problem in 0.4.1

It can be found in app/resources/Sia/gateway/gateway.log

Great news, waiting for 0.4.1 to transfer balance then.

Here's my log, gui client is working now.

Code:

2015/09/01 18:40:38.210889 gateway.go:96: INFO: gateway created, started logging
2015/09/01 18:40:38.211889 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 18:47:32.783597 gateway.go:96: INFO: gateway created, started logging
2015/09/01 18:47:32.785099 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 18:50:09.766762 gateway.go:96: INFO: gateway created, started logging
2015/09/01 18:50:09.767763 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 18:57:15.983910 gateway.go:96: INFO: gateway created, started logging
2015/09/01 18:57:15.985412 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 18:58:41.066626 gateway.go:96: INFO: gateway created, started logging
2015/09/01 18:58:41.068627 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 19:02:42.485325 gateway.go:96: INFO: gateway created, started logging
2015/09/01 19:02:42.486828 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 19:07:54.516694 gateway.go:96: INFO: gateway created, started logging
2015/09/01 19:07:54.520199 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 19:11:08.518593 gateway.go:96: INFO: gateway created, started logging
2015/09/01 19:11:08.524567 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 19:11:26.466161 gateway.go:96: INFO: gateway created, started logging
2015/09/01 19:11:26.467664 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 19:11:59.671691 gateway.go:96: INFO: gateway created, started logging
2015/09/01 19:11:59.672692 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 19:14:11.997477 gateway.go:96: INFO: gateway created, started logging
2015/09/01 19:24:21.403172 gateway.go:96: INFO: gateway created, started logging
2015/09/01 19:24:21.405173 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 19:24:48.416702 gateway.go:96: INFO: gateway created, started logging
2015/09/01 19:24:48.418702 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 19:28:53.503649 gateway.go:96: INFO: gateway created, started logging
2015/09/01 19:28:53.504649 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 19:42:27.875141 gateway.go:96: INFO: gateway created, started logging
2015/09/01 19:42:27.876643 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 19:51:09.371538 gateway.go:96: INFO: gateway created, started logging
2015/09/01 19:51:09.373040 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 20:52:14.234152 gateway.go:96: INFO: gateway created, started logging
2015/09/01 20:52:14.235654 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 20:53:43.735806 gateway.go:96: INFO: gateway created, started logging
2015/09/01 20:53:43.736806 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 20:55:31.406835 gateway.go:96: INFO: gateway created, started logging
2015/09/01 20:55:31.407836 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 20:55:37.701907 rpc.go:129: INFO: broadcasting RPC "RelayTransaction" to 0 peers
2015/09/01 20:58:14.490848 gateway.go:96: INFO: gateway created, started logging
2015/09/01 20:58:14.492849 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 20:59:22.500819 gateway.go:96: INFO: gateway created, started logging
2015/09/01 20:59:22.501819 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 21:08:27.357994 gateway.go:96: INFO: gateway created, started logging
2015/09/01 21:08:27.358995 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 21:08:40.037650 gateway.go:96: INFO: gateway created, started logging
2015/09/01 21:08:40.039152 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 21:08:45.228464 rpc.go:129: INFO: broadcasting RPC "RelayTransaction" to 0 peers
2015/09/01 21:45:29.950225 gateway.go:96: INFO: gateway created, started logging
2015/09/01 21:45:29.951225 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 21:45:38.413324 gateway.go:96: INFO: gateway created, started logging
2015/09/01 21:45:38.415327 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 21:46:04.649083 rpc.go:129: INFO: broadcasting RPC "RelayTransaction" to 0 peers
2015/09/01 22:19:04.379866 gateway.go:96: INFO: gateway created, started logging
2015/09/01 22:19:04.381368 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 22:22:11.670188 gateway.go:96: INFO: gateway created, started logging
2015/09/01 22:22:11.672188 gateway.go:106: INFO: our address is 213.118.198.15:9981
2015/09/01 22:23:09.454132 peers.go:187: INFO: connected to new peer 45.79.132.35:9981
2015/09/01 22:23:09.572030 nodes.go:75: INFO: 45.79.132.35:9981 sent us 10 nodes
2015/09/01 22:23:09.817667 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 1 peers
2015/09/01 22:23:10.097610 peers.go:90: INFO: 85.26.164.119:39018 wants to connect
2015/09/01 22:23:10.104586 peers.go:149: INFO: accepted connection from new peer 85.26.164.119:39018 (v0.3.3)
2015/09/01 22:23:10.253123 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 2 peers
2015/09/01 22:23:21.678062 nodes.go:36: INFO: removed node 52.18.225.159:9981
2015/09/01 22:23:22.006721 peers.go:187: INFO: connected to new peer 70.119.172.103:9981
2015/09/01 22:23:22.166449 nodes.go:75: INFO: 70.119.172.103:9981 sent us 10 nodes
2015/09/01 22:23:31.861304 peers.go:90: INFO: 91.210.105.215:53404 wants to connect
2015/09/01 22:23:31.862305 peers.go:149: INFO: accepted connection from new peer 91.210.105.215:53404 (v0.3.3)
2015/09/01 22:23:31.961764 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 4 peers
2015/09/01 22:23:32.079847 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:23:41.396936 peers.go:90: INFO: 5.141.209.185:41674 wants to connect
2015/09/01 22:23:41.397936 peers.go:149: INFO: accepted connection from new peer 5.141.209.185:41674 (v0.3.3)
2015/09/01 22:23:41.523513 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 5 peers
2015/09/01 22:23:41.665325 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:24:08.180781 peers.go:90: INFO: 5.141.209.185:41010 wants to connect
2015/09/01 22:24:08.180781 peers.go:99: INFO: rejected connection from 5.141.209.185:41010: already connected
2015/09/01 22:24:08.451222 peers.go:90: INFO: 5.141.209.185:41349 wants to connect
2015/09/01 22:24:08.451222 peers.go:99: INFO: rejected connection from 5.141.209.185:41349: already connected
2015/09/01 22:25:53.621267 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 5 peers
2015/09/01 22:25:53.630494 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:25:53.686191 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:25:53.707168 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:25:53.723285 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:26:15.076749 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 5 peers
2015/09/01 22:26:15.215077 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:26:40.187089 peers.go:90: INFO: 82.117.247.11:49878 wants to connect
2015/09/01 22:26:40.188090 peers.go:149: INFO: accepted connection from new peer 82.117.247.11:49878 (v0.3.3)
2015/09/01 22:26:40.290131 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 6 peers
2015/09/01 22:26:40.448297 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:26:40.482364 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:26:45.677796 peers.go:90: INFO: 180.248.228.15:54561 wants to connect
2015/09/01 22:26:45.678796 peers.go:149: INFO: accepted connection from new peer 180.248.228.15:54561 (v0.3.3)
2015/09/01 22:26:46.024401 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 7 peers
2015/09/01 22:26:46.157892 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:26:46.159943 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:26:46.237278 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:26:48.542070 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 7 peers
2015/09/01 22:26:48.575295 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:26:48.588299 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:26:50.021790 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:26:58.025299 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:26:58.032309 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:26:58.063627 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:26:58.073880 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:26:58.074381 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:26:58.076384 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:26:58.202414 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:26:58.320067 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:26:58.590027 peers.go:90: INFO: 85.26.164.119:16057 wants to connect
2015/09/01 22:26:58.590027 peers.go:99: INFO: rejected connection from 85.26.164.119:16057: already connected
2015/09/01 22:27:12.987686 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:27:13.007695 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:27:13.022871 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:27:13.035078 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:27:13.038106 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:27:13.055302 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:27:13.073508 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:27:13.281331 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:27:18.370094 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 7 peers
2015/09/01 22:27:18.515045 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:27:38.246413 peers.go:90: INFO: 85.21.134.178:52699 wants to connect
2015/09/01 22:27:38.246413 peers.go:149: INFO: accepted connection from new peer 85.21.134.178:52699 (v0.3.3)
2015/09/01 22:27:38.333696 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 8 peers
2015/09/01 22:27:38.416303 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:27:38.461329 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:28:59.117274 peers.go:90: INFO: 5.141.209.185:41688 wants to connect
2015/09/01 22:28:59.117274 peers.go:99: INFO: rejected connection from 5.141.209.185:41688: already connected
2015/09/01 22:29:28.546094 peers.go:90: INFO: 5.141.209.185:41897 wants to connect
2015/09/01 22:29:28.546595 peers.go:99: INFO: rejected connection from 5.141.209.185:41897: already connected
2015/09/01 22:29:30.148018 peers.go:90: INFO: 5.141.209.185:41923 wants to connect
2015/09/01 22:29:30.148018 peers.go:99: INFO: rejected connection from 5.141.209.185:41923: already connected
2015/09/01 22:29:35.026305 peers.go:90: INFO: 5.141.209.185:41374 wants to connect
2015/09/01 22:29:35.026805 peers.go:99: INFO: rejected connection from 5.141.209.185:41374: already connected
2015/09/01 22:29:43.597191 peers.go:90: INFO: 5.141.209.185:41320 wants to connect
2015/09/01 22:29:43.597191 peers.go:99: INFO: rejected connection from 5.141.209.185:41320: already connected
2015/09/01 22:29:58.927344 peers.go:90: INFO: 5.141.209.185:41740 wants to connect
2015/09/01 22:29:58.927344 peers.go:99: INFO: rejected connection from 5.141.209.185:41740: already connected
2015/09/01 22:30:12.569520 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:30:12.581721 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:30:12.679923 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:30:12.680923 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:30:12.692953 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:30:12.699928 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:30:12.732462 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:30:12.814049 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:30:12.903878 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.945588 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.978667 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.979151 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:12.979151 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.979652 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.980152 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.980653 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.981154 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.981154 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.981655 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:12.981655 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.982155 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.982656 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.983174 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.984176 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.984176 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.987664 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.987664 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.988683 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.988683 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.989169 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.989169 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.990686 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.991672 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.991672 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.992173 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.992173 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.992675 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.992675 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.993172 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.993172 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.993172 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.993675 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.993675 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.994173 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.994674 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:12.994674 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.994674 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:12.994674 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.995175 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:12.995175 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.995675 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:12.995675 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:12.996179 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:12.996179 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:13.071685 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:13.120448 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:13.163861 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:13.255176 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:13.397320 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:13.547706 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:13.605995 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:13.703027 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:13.902408 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:14.039701 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:14.076999 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:14.172115 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:14.219833 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:14.329750 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:14.481112 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:14.666738 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:15.587209 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:15.833652 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:15.868306 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:16.003130 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:16.061450 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:16.062952 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:16.066458 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:16.067959 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:16.068461 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:16.095501 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:20.636411 peers.go:90: INFO: 5.141.209.185:41754 wants to connect
2015/09/01 22:30:20.636910 peers.go:99: INFO: rejected connection from 5.141.209.185:41754: already connected
2015/09/01 22:30:21.063287 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:21.096337 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:21.303503 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:21.393272 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:21.399272 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:30:21.598564 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:21.653578 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:21.692588 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:21.720597 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:21.750604 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:22.376267 rpc.go:119: WARN: incoming RPC "RelayTra" failed: file contract window has not yet openend
2015/09/01 22:30:23.044511 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:23.050475 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:27.716146 peers.go:90: INFO: 85.26.164.119:26021 wants to connect
2015/09/01 22:30:27.716146 peers.go:99: INFO: rejected connection from 85.26.164.119:26021: already connected
2015/09/01 22:30:28.325860 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:30.609264 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:35.315909 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:36.759460 peers.go:90: INFO: 5.141.209.185:41961 wants to connect
2015/09/01 22:30:36.759460 peers.go:99: INFO: rejected connection from 5.141.209.185:41961: already connected
2015/09/01 22:30:40.176028 rpc.go:119: WARN: incoming RPC "RelayBlo" failed: block has no known parent
2015/09/01 22:30:41.393721 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 8 peers
2015/09/01 22:30:41.518398 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:30:41.533397 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:30:44.427748 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:30:59.589110 peers.go:90: INFO: 217.118.83.153:40084 wants to connect
2015/09/01 22:30:59.602160 peers.go:149: INFO: accepted connection from new peer 217.118.83.153:40084 (v0.3.3)
2015/09/01 22:31:00.648089 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 9 peers
2015/09/01 22:31:00.736551 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:31:00.765735 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:31:00.787954 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:31:03.781578 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:31:15.070490 peers.go:90: INFO: 178.163.111.100:53352 wants to connect
2015/09/01 22:31:15.071492 peers.go:149: INFO: accepted connection from new peer 178.163.111.100:53352 (v0.3.3)
2015/09/01 22:31:15.201839 rpc.go:119: WARN: incoming RPC "RelayNod" failed: address is not routable:
429 - Too Many Requests

429 T:9981
2015/09/01 22:31:44.914475 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 10 peers
2015/09/01 22:31:45.120527 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:31:48.271912 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:32:13.452016 rpc.go:87: WARN: lost connection to peer 180.248.228.15:54561
2015/09/01 22:32:13.452016 peers.go:224: INFO: disconnected from peer 180.248.228.15:54561
2015/09/01 22:32:13.452016 rpc.go:119: WARN: incoming RPC "SendBloc" failed: short write
2015/09/01 22:32:13.452016 rpc.go:119: WARN: incoming RPC "SendBloc" failed: short write
2015/09/01 22:32:13.528375 rpc.go:57: WARN: calling RPC "SendBlocks" on peer 180.248.228.15:54561 returned error: use of closed network connection
2015/09/01 22:32:18.475728 peers.go:90: INFO: 180.248.228.15:54597 wants to connect
2015/09/01 22:32:18.477728 peers.go:149: INFO: accepted connection from new peer 180.248.228.15:54597 (v0.3.3)
2015/09/01 22:32:18.807141 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:32:31.985054 rpc.go:57: WARN: calling RPC "SendBlocks" on peer 180.248.228.15:54561 returned error: use of closed network connection
2015/09/01 22:32:42.972512 peers.go:90: INFO: 5.141.209.185:40985 wants to connect
2015/09/01 22:32:42.973516 peers.go:99: INFO: rejected connection from 5.141.209.185:40985: already connected
2015/09/01 22:32:46.467086 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 10 peers
2015/09/01 22:32:46.557827 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:32:46.602997 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:32:46.716854 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:32:46.987079 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:32:47.187249 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:32:48.011061 peers.go:90: INFO: 5.141.209.185:41527 wants to connect
2015/09/01 22:32:48.011061 peers.go:99: INFO: rejected connection from 5.141.209.185:41527: already connected
2015/09/01 22:32:51.059963 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 10 peers
2015/09/01 22:32:52.669846 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:33:46.004593 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.006602 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.009575 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.029607 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.059589 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.065758 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:33:46.077868 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.156033 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.248055 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.249055 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.256057 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.299068 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.304070 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:33:46.321074 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.332077 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.376098 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.407248 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.536482 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.631703 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:46.632698 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:47.110850 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:33:47.110850 rpc.go:119: WARN: incoming RPC "RelayTra" failed: unrecognized siacoin input in transaction
2015/09/01 22:34:31.148414 peers.go:90: INFO: 5.141.209.185:40981 wants to connect
2015/09/01 22:34:31.148414 peers.go:99: INFO: rejected connection from 5.141.209.185:40981: already connected
2015/09/01 22:34:45.821991 peers.go:90: INFO: 5.141.209.185:41326 wants to connect
2015/09/01 22:34:45.821991 peers.go:99: INFO: rejected connection from 5.141.209.185:41326: already connected
2015/09/01 22:34:50.517078 peers.go:90: INFO: 5.141.209.185:41628 wants to connect
2015/09/01 22:34:50.518078 peers.go:99: INFO: rejected connection from 5.141.209.185:41628: already connected
2015/09/01 22:35:18.605671 rpc.go:129: INFO: broadcasting RPC "RelayTransaction" to 10 peers
2015/09/01 22:35:18.641879 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:35:32.084550 rpc.go:129: INFO: broadcasting RPC "RelayTransaction" to 10 peers
2015/09/01 22:35:32.108935 rpc.go:129: INFO: broadcasting RPC "RelayTransaction" to 10 peers
2015/09/01 22:35:32.168079 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:35:32.187084 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:35:33.557133 rpc.go:129: INFO: broadcasting RPC "RelayTransaction" to 10 peers
2015/09/01 22:35:33.593853 rpc.go:119: WARN: incoming RPC "RelayTra" failed: could not decode type types.Transaction: slice is too large
2015/09/01 22:37:37.340653 peers.go:90: INFO: 5.2.1.7:31014 wants to connect
2015/09/01 22:37:37.360662 peers.go:149: INFO: accepted connection from new peer 5.2.1.7:31014 (v0.3.3)
2015/09/01 22:37:37.553171 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 11 peers
2015/09/01 22:37:37.638039 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:37:37.640040 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:37:37.693201 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:37:37.701177 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:37:38.071279 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:38:11.206385 peers.go:90: INFO: 5.141.209.185:41830 wants to connect
2015/09/01 22:38:11.207385 peers.go:99: INFO: rejected connection from 5.141.209.185:41830: already connected
2015/09/01 22:38:13.683966 peers.go:90: INFO: 5.141.209.185:41855 wants to connect
2015/09/01 22:38:13.683966 peers.go:99: INFO: rejected connection from 5.141.209.185:41855: already connected
2015/09/01 22:38:32.353011 peers.go:90: INFO: 5.141.209.185:41767 wants to connect
2015/09/01 22:38:32.354012 peers.go:99: INFO: rejected connection from 5.141.209.185:41767: already connected
2015/09/01 22:39:19.379790 peers.go:90: INFO: 5.141.209.185:41819 wants to connect
2015/09/01 22:39:19.379790 peers.go:99: INFO: rejected connection from 5.141.209.185:41819: already connected
2015/09/01 22:39:25.997391 peers.go:90: INFO: 5.141.209.185:41338 wants to connect
2015/09/01 22:39:25.997391 peers.go:99: INFO: rejected connection from 5.141.209.185:41338: already connected
2015/09/01 22:39:41.162181 rpc.go:129: INFO: broadcasting RPC "RelayNode" to 11 peers
2015/09/01 22:39:41.285304 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:39:41.301321 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:39:41.316336 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:39:41.460459 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:39:41.514849 rpc.go:119: WARN: incoming RPC "RelayNod" failed: node already added
2015/09/01 22:40:44.922478 peers.go:90: INFO: 5.141.209.185:41262 wants to connect
2015/09/01 22:40:44.922963 peers.go:99: INFO: rejected connection from 5.141.209.185:41262: already connected

Pito001

sr. member

Activity: 301

Merit: 250

Quote from: yeponlyone on September 01, 2015, 08:16:25 PM

Quote from: chanc3r on August 31, 2015, 03:31:41 PM

Quote from: WilderX on August 31, 2015, 01:54:13 PM

Quote from: yeponlyone on August 31, 2015, 07:06:18 AM

Is it possible to chose here sia stores the files? As I have many HDDs, I do not want them on C:/.

You can combine hard drives into one drive via software in example windows disk management and run Sia from there.

Yes create another disk/volume/partition and put the Sia folder there...
Sia will use storage from the volume that it is being run from...
So if you run it from Drive X then any storage you announce will be utilised from that drive

So the easiest would be to have a big NAS (where you also can use raid to protect content)?

Would it be possible to incorporate a feature where you point SIA to where you want it to save content..? I know you can combine drives, but it requires some technical knowledge in addition to that you risk lose the whole space if you use raid 1. The inability to not chose in fact makes SIA much less attractive to me (but still decent for my NAS).

NAS could prove useful. Only not because of raid, as all content will be available from 12 sources and compilable with 2 of those, random.

If SIA only uses the drive it's put on, it would be easiest to just create a partition you would like it to use. I'm sure as this is in early beta, the option to choose location will be added. From what I read you're kinda looking at this as a final product, which it's not.

Great project tho'. Keeping my eyes on this Cool

edit:

Quote from: SpeedDemon13 on September 02, 2015, 12:33:07 AM

Still doesn't work for me, gives me an error when trying to add gateways. I've tried everything I possible can think of and followed the step, even open ports on my router and computer. I guess I'll just wait for the upnp wallet, out of the 4 plus years in cryptos, this is like 3rd wallet that never worked for me from the get go.

Be sure to try them all. I've had an error with some of them, until one of them just worked and the wallet started to sync.

You need the GUI open for it work (deamon running) and give the command "siac.exe gateway add 45.79.132.35:9981" in the folder ...\resources\app\Sia through command line (cmd), ran as admin. But I'm sure you know that last part, maybe a little more details will help out others.

The peer I put in is the one that worked for me, list of peers are available on this thread. Good luck! Or just wait for upnp wallet. Wink

SalimNagamato

legendary

Activity: 924

Merit: 1000

Quote from: bitspill on September 02, 2015, 01:44:55 AM

Quote from: SalimNagamato on September 02, 2015, 01:40:26 AM

Hi
i am running siad on one terminal, and on other terminal trying to run siac status:

sl@sl:~$ siac status
Could not get daemon status: Browser access disabled due to security vulnerability. Use Sia-UI or siac.

it gives me error to use siac..and i am using siac
how to solve this ?

Are you using Go 1.5?

There seems to be an issue with siac when run on 1.5, it should be fixed soon or in the meantime try Go 1.4 if you don't mind.

yes... go 1.5
will try with go 1.4
thanks

bitspill

legendary

Activity: 2087

Merit: 1015

Quote from: SalimNagamato on September 02, 2015, 01:40:26 AM

Hi
i am running siad on one terminal, and on other terminal trying to run siac status:

sl@sl:~$ siac status
Could not get daemon status: Browser access disabled due to security vulnerability. Use Sia-UI or siac.

it gives me error to use siac..and i am using siac
how to solve this ?

Are you using Go 1.5?

There seems to be an issue with siac when run on 1.5, it should be fixed soon or in the meantime try Go 1.4 if you don't mind.

SalimNagamato

legendary

Activity: 924

Merit: 1000

Hi
i am running siad on one terminal, and on other terminal trying to run siac status:

sl@sl:~$ siac status
Could not get daemon status: Browser access disabled due to security vulnerability. Use Sia-UI or siac.

it gives me error to use siac..and i am using siac
how to solve this ?

chanc3r

sr. member

Activity: 952

Merit: 253

Quote from: SpeedDemon13 on September 02, 2015, 12:33:07 AM

Still doesn't work for me, gives me an error when trying to add gateways. I've tried everything I possible can think of and followed the step, even open ports on my router and computer. I guess I'll just wait for the upnp wallet, out of the 4 plus years in cryptos, this is like 3rd wallet that never worked for me from the get go.

here is a list of a few peers that i can see

Code:

76.119.238.92:9981
85.21.134.190:9981
108.238.244.144:9981
5.9.11.88:9981
5.9.29.103:9981
47.16.232.92:9981
77.37.240.140:9981
149.18.49.90:9981
70.119.172.103:9981
94.23.7.123:9981
178.163.29.2:9981
79.51.183.132:9981
188.242.59.66:9981
217.65.8.75:9981
217.77.58.189:9981
74.72.150.222:9981
109.167.220.30:9981
108.61.157.174:9981
5.135.184.146:9981
76.119.238.92:9961

here is a little windows script that makes adding peers easy just put the peer list in siapeers.txt and make sure 'siac' is in your path or edit the location into the script.

Code:

@echo off
for /f %%i in (siapeers.txt) do (
echo trying peer %%i ... siac gateway add %%i
)

you should get some positives out of this list.

SpeedDemon13

hero member

Activity: 518

Merit: 500

Quote from: Pito001 on September 01, 2015, 12:34:03 PM

Quote from: tricass on August 28, 2015, 05:59:03 AM

Quote from: SpeedDemon13 on August 28, 2015, 04:32:26 AM

I can not get the wallet to sync, both CLI or GUI versions. I run the cmd prompt to get siad.exe to run and siac.exe, or I use the GUI instead of siac.exe. Am I doing something wrong? When I use the GUI version it just stays on block 1 with no connection, I've let it stay on for 3 hours with nothing going on. Any help is greatly appreciated in advance.

I bought some SC to play around with and thought I'd try out the wallet but I'm having the same problem. I'm using the GUI version. Hoping someone can help out.

Also, is there 0.4 windows compiled binary available as I can't find it on your main site.

Same problem here, using 0.3.3-beta.2 b383.

Getting:
0 KS Peers: 0 Block Height: 1

edit: /

second edit: fixed by adding gateways with cmd

Still doesn't work for me, gives me an error when trying to add gateways. I've tried everything I possible can think of and followed the step, even open ports on my router and computer. I guess I'll just wait for the upnp wallet, out of the 4 plus years in cryptos, this is like 3rd wallet that never worked for me from the get go.

mishax1

legendary

Activity: 2898

Merit: 1017

Quote from: ?? on ??

Quote

i believe amd still has the edge. i've read somewhere that an r9 290x should do 1000mhs. my 270s are reporting 270mhs each running at intensity 25 and seem to be pulling about 100W each. I have no idea what the expected rate my miners should be running at.

thanks,
my nvidia 650ti is pretty slow, been mining for 4 days and found 2 blocks....need to get an amd then.

Thats actually not bad at all... consider yourself lucky.

tricass

sr. member

Activity: 394

Merit: 250

Crypto enthusiast

Quote from: ?? on ??

Hello,
What is the best gpu for mining sia? Anyone has a comparison between amd - nvidia?
Thank you.

i believe amd still has the edge. i've read somewhere that an r9 290x should do 1000mhs. my 270s are reporting 270mhs each running at intensity 25 and seem to be pulling about 100W each. I have no idea what the expected rate my miners should be running at.

tricass

sr. member

Activity: 394

Merit: 250

Crypto enthusiast

Quote from: tricass on September 01, 2015, 09:55:46 PM

Quote from: Roozy on September 01, 2015, 09:52:14 PM

Quote from: tricass on September 01, 2015, 09:48:33 PM

trying out mining and am using the windows miner. it reports it has mined 1 block so far. I know there's a 144 confirmation requirement for new coinbase transactions but i'm pretty sure it has been over a day now. is there anyway to check on the blockchain for the two addresses I have, according to my 0.3.3 gui, so see if the coins have been in fact credited to one of these accounts albeit in an unconfirmed state? the current blockexplorer does seem to support queries by addresses and the windows miner output is very sparse so i dont even know what block height it successfully mined.

Blocks are coming in slow right now because of the difficulty explosion so it may not have reached the 144 blocks.

You can check out
explore.siacoin.com

for addresses but that's not going to give you much info about blocks you've mined (at least that I know of).

It's better if you go into the
resources>>app>>sia
folder

open command prompt in the folder and run the following

siac miner status

That will show you how many blocks you've mined along with any false positives

thanks! I'll give that a try now.

does report the 1 blocked mined but no other info on the actual block itself. i do think you are right about the slow block times and guess I'll need to wait a bit longer. how frequently does difficulty retarget itself? and anyone got a clear understanding about the use of "-C" switch in the windows miner? do i need to adjust this beyond the default value of 30? I'm playing around with 2 x r9 270 miners at the moment.

yeponlyone

hero member

Activity: 504

Merit: 500

Sorry if dubble posting but I just saw this:

Quote

Emek Sorek / Israel, September 1, 2015 at 17:34 BST

The Crypti Foundation, the team behind the next generation crypto-currency Crypti, today announced an official partnership with Sia, the decentralized blockchain based cloud storage platform.

Last week, the Crypti Foundation unveiled its first video preview of their forthcoming decentralized application (Dapp) platform which aims to provide thousands of Node.js developers with a full stack (consensus, hosting, storage and computing) solution for launching decentralized applications onto the blockchain.

Viewers paying close attention to the video would have quickly noticed Sia, the decentralized cloud storage platform, being used as a storage solution for Crypti’s first ever decentralized application: “Encrypti”.

The Crypti Foundation’s Community Manager, Max Kordek said: “Using Sia as a cloud storage solution was an easy decision. They have a very well developed and easy to integrate system that goes hand-in-hand with what Crypti is all about; putting the user and user experience first.”

Kordek added: “We are very optimistic that once people get their hands on the system and start integrating with Sia they will be pleasantly surprised at just how easy it really is.”

Building upon their initial success, Sia and the Crypti Foundation have decided to form a premium partnership between the two blockchain 2.0 based projects that would make Sia a primary solution for cloud storage on the Crypti Dapp platform.

Sia’s Project Founder, David Vorick said: “We are very happy to announce this official partnership. Crypti provides a full stack solution for deploying truly decentralized applications onto the blockchain, while also providing an excellent user experience for anyone looking to make safe and easy transactions within seconds.”

Vorick added: “For the progressive startup looking for the perfect platform on which to launch their first Dapp, Crypti along with Sia should be seen as their number one choice.”

About Crypti

Crypti is a blockchain 2.0 technology dedicated to allowing fast, easy, and cost effective deployment of decentralized applications (Dapps). By utilizing Node.js and incorporating consensus, hosting, storage, and compute modules into the core technology, along with a custom built decentralized application store, Crypti is able to provide a complete solution for the entire Dapp development cycle.

About Sia

Sia is a new blockchain based decentralized storage platform that allows users all over the world to contribute available storage space from their computers to form a decentralized network.

Using “siacoins” as the Sia network’s own currency. Users can rent storage from hosts on the network. This is accomplished via "smart" storage contracts stored on the Sia blockchain, which provide a payment to the host only after the host has kept a file for a given amount of time. If the host loses the file, the host does not get paid.

The distributed nature of the Sia network enables many optimizations in latency, throughput, reliability, and security. Furthermore, the decentralized nature of the Sia network enables anyone with storage to earn revenue, lowering the barrier to entry and reducing the overall price of cloud storage.

https://crypti.me/
http://siacoin.com/

(@m3ta: do not destroy this thread also, please. You can PM me if you want something

)

tricass

sr. member

Activity: 394

Merit: 250

Crypto enthusiast

Quote from: Roozy on September 01, 2015, 09:52:14 PM

Quote from: tricass on September 01, 2015, 09:48:33 PM

trying out mining and am using the windows miner. it reports it has mined 1 block so far. I know there's a 144 confirmation requirement for new coinbase transactions but i'm pretty sure it has been over a day now. is there anyway to check on the blockchain for the two addresses I have, according to my 0.3.3 gui, so see if the coins have been in fact credited to one of these accounts albeit in an unconfirmed state? the current blockexplorer does seem to support queries by addresses and the windows miner output is very sparse so i dont even know what block height it successfully mined.

Blocks are coming in slow right now because of the difficulty explosion so it may not have reached the 144 blocks.

You can check out
explore.siacoin.com

for addresses but that's not going to give you much info about blocks you've mined (at least that I know of).

It's better if you go into the
resources>>app>>sia
folder

open command prompt in the folder and run the following

siac miner status

That will show you how many blocks you've mined along with any false positives

thanks! I'll give that a try now.

Roozy

newbie

Activity: 43

Merit: 0

Quote from: tricass on September 01, 2015, 09:48:33 PM

trying out mining and am using the windows miner. it reports it has mined 1 block so far. I know there's a 144 confirmation requirement for new coinbase transactions but i'm pretty sure it has been over a day now. is there anyway to check on the blockchain for the two addresses I have, according to my 0.3.3 gui, so see if the coins have been in fact credited to one of these accounts albeit in an unconfirmed state? the current blockexplorer does seem to support queries by addresses and the windows miner output is very sparse so i dont even know what block height it successfully mined.

Blocks are coming in slow right now because of the difficulty explosion so it may not have reached the 144 blocks.

You can check out
explore.siacoin.com

for addresses but that's not going to give you much info about blocks you've mined (at least that I know of).

It's better if you go into the
resources>>app>>sia
folder

open command prompt in the folder and run the following

siac miner status

That will show you how many blocks you've mined along with any false positives

Topic: [ANN] Sia - Decentralized Storage - page 409. (Read 1382227 times)