 Show Posts
|
|
Pages: « 1 2 [3] 4 5 6 »
|
|
apparently the hard fork is happening today I just saw that on siamining.com
"Reminder: Due to Sia's upcoming hardfork (expected on January 21), you must upgrade your Sia wallet software to version 1.3.1 or higher. You can continue to use the same address for mining, and no changes to your configuration are needed. For more information about the fork, click here."
|
|
|
|
|
People who bought the A3, know what they are doing. Now we will see the outcome of their investment in 5 days.. as China customer will get it within 4 days.
The story is Bitmain is killing all new Asics new players, they reduced the minimum order to 1 and they are shipping quickly and Sia developers aren't happy....
|
|
|
|
|
Do you still think it is profitable investment on an A3?
|
|
|
|
Official response from the SIA [SC] Dev Team
"Bitmain has announced an ASIC miner for Sia. This has made a lot of people uneasy, especially those who preordered Obelisk units. So I'll first address the Obelisk units in isolation. Though we don't have the full chips back yet, the chips are in production and we have our final simulations. We can confidently state that the bitmain unit is far less energy efficient, costs more money, and is an objectively worse miner than the SC1. So people who ordered Obelisk units will still be receiving hardware of substantial value.
As a developer, Bitmain moving into the Sia space makes me uneasy. Bitmain has historically been extremely greedy, and very willing to sacrifice the well being of the community, of their customers, and of the ecosystem if it means they can make a couple of extra dollars. The biggest way this has manifested for altcoins is that they will over-sell hardware. When a ton of miners suddenly join the network, the difficulty adjusts. If too many miners join the network, nobody is able to make any money, and everyone eats a loss on their hardware purchase.
Bitmain has no qualms about overselling their units to buyers. They take massive margins on their hardware (>50%) and make more money than the total block reward at the expense of their customers. They over-saturate the mining market in a way that hurts their buyers. I think we will see this with Sia. Bitmain will sell more units than the Sia ecosystem can sustain, and many people end up with large losses. Bitmain will not end up with losses, because they were paid up-front with non-refundable money.
Bitmain also has a history of doing things like mining empty blocks, and like refusing to activate soft-forks that are beneficial to the network. They were openly hostile to the Bhttps://bitcointalk.org/index.php?topic=2769785.120itcoin-core developers, and actively blocked the activation of a very valuable network feature (Segwit).
We, the dev team, are not happy that Bitmain has made an ASIC for Sia. We are not happy that many Sia supporters are at risk of losing money by buying these miners (from over-saturation), and we are not happy that Bitmain may choose to interfere with our network. This is not a commentary on general ASIC companies, this is a commentary on Bitmain specifically.
We did add an extra feature to the SC1 unit that would allow us to invalidate the Bitmain hardware without invalidating the SC1. The community would need to choose to adopt a soft-fork (it's not something we could just magically activate, we have to change the hashing algorithm slightly), and then we could get rid of this cycle of Bitmain hardware. Of course, they could just create another round of hardware (likely taking ~3 months). And, it would hurt Bitmain customers more than it would hurt Bitmain. Bitmain has already sold around $20 million of non-refundable hardware. They have made their profit, and a soft-fork wouldn't change that.
As much as I would like to punch Bitmain in the nose, I don't think a soft-fork achieves what we want. If the hardware is used to harm the Sia network, either by doing double spends, rejecting soft forks, mining empty blocks, we will invalidate it without hesitation. But for the time being, I think the best thing to do is to advise people not to buy the Bitmain hardware (to protect yourself from the oversaturation that Bitmain tries to create), and then to watch and wait, and respond more if it appears that the network is under attack. Overall though, I do not think Sia is in trouble.
I am looking forward to the thoughts from the community."
I love this response to the above letter costa1717 • Jan 17, 2018, 2:49 PM As long as they don't overflood and centralize the market its OK. After all that is what you guys wanted isn't it? A decentralized ASIC network. You wanted to sell 10k units in batch 1 and would have launched batch 2 with a similar amount soon afterwards. I do not believe Bitmain will sell such a high quantity, so as long as there is a quantity restriction on their orders its all good for the network. P.S. Activating such a soft fork would do HUGE harm on the SIA community and this harm will last. Like you said this will hurt the customers, not the corporation and will have a negative effect on the adoption of the network. |
|
|
|
Got one now and paid. Crossed my fingers about diff issues and I hope Bitmain will make an execuse for that D3 issues with A3  maybe they will issue B3+ after A3 and D3....like that you will claim ABC bitmain mania :-) they just released a new batch the sales are as for the difficulty.....in 15 days |
|
|
|
Whattomine show sia at $431 per day with network rate a 650TH/s. So if they release 500+ of these would go down to ~ $200/day right? Not sure about rollout of this or obelisk, but calculators show money in first few months before power goes crazy. sialytics.com profit estimator shows stupid money.
just curious where the estimate of 500 units comes from. I have no idea how many they would have so just wondering they released 1500 units it is going to be worse than that! |
|
|
|
very good one!! they have sold so fare 1500 units.... |
|
|
|
Just got one  congratulations do you think it is profitable? |
|
|
|
|
if they sold out 200 units. it will be a jackpot for those who ordered the machines......I didn't expect them to be sold out that fast either people are crazy or the quantity is limited......
|
|
|
|
|
will not go for it. I got my D3 from the first batch and the roi was crap! complete disaster! this is one coin that you will be mining
|
|
|
|
|
HI,
Need help. I would like to purchase 3PSUs for my 3L3+. Do you have an idea where to get them quickly.
I'm in France
Thanks,
|
|
|
|
|
thanks Theoulis we followed the instructions together with the video but it didn't work out....both of us it isn't working
|
|
|
|
|
is there any tutorial for setting up the masternode.
with my friend we bought vultr.com to upload 2 masternodes
we followed the instructions and since 5 days we didn't earny anything.
Do we have to keep our PC on?
how can I delete/remove/edit my masternode on syndicate wallet?
Thanks
|
|
|
|
Hi All, I'm trying to run Synx Masternode? I have followed the instructions from : https://github.com/u3mur4/syndicate.....but I'm stuck at 2.3: wget https://raw.githubusercontent.com/u3mur4/syndicate/master/synx.py && python synx.py it doesnt work I'm getting the bellow message * Documentation: https://help.ubuntu.com/New release '16.04.3 LTS' available. Run 'do-release-upgrade' to upgrade to it. Last login: Thu Oct 5 10:12:30 2017 from poi78-1-88-179-216-1.fbx.proxad.net root@vultr:~# wget https://raw.githubusercontent.com/u3mur4/syndicate/master/syn x.py && python synx.py --2017-10-05 10:17:05-- https://raw.githubusercontent.com/u3mur4/syndicate/mast er/synx.py Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.120.1 33 Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.120. 133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 10708 (10K) [text/plain] Saving to: 'synx.py.13' 100%[======================================>] 10,708 --.-K/s in 0s 2017-10-05 10:17:05 (126 MB/s) - 'synx.py.13' saved [10708/10708] Traceback (most recent call last): File "synx.py", line 12, in <module> NODE_LIST = urlopen(' https://transfer.sh/14vce1/nodelist_09_10.txt').read() File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen return _opener.open(url, data, timeout) File "/usr/lib/python2.7/urllib2.py", line 410, in open response = meth(req, response) File "/usr/lib/python2.7/urllib2.py", line 523, in http_response 'http', request, response, code, msg, hdrs) File "/usr/lib/python2.7/urllib2.py", line 448, in error return self._call_chain(*args) File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain result = func(*args) File "/usr/lib/python2.7/urllib2.py", line 531, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) urllib2.HTTPError: HTTP Error 500: Internal Server Error root@vultr:~# can you help please |
|
|
|
Hi All, I'm trying to run Synx Masternode? I have followed the instructions from : https://github.com/u3mur4/syndicate.....but I'm stuck at 2.3: wget https://raw.githubusercontent.com/u3mur4/syndicate/master/synx.py && python synx.py it doesnt work I'm getting the bellow message * Documentation: https://help.ubuntu.com/New release '16.04.3 LTS' available. Run 'do-release-upgrade' to upgrade to it. Last login: Thu Oct 5 10:12:30 2017 from poi78-1-88-179-216-1.fbx.proxad.net root@vultr:~# wget https://raw.githubusercontent.com/u3mur4/syndicate/master/syn x.py && python synx.py --2017-10-05 10:17:05-- https://raw.githubusercontent.com/u3mur4/syndicate/mast er/synx.py Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.120.1 33 Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.120. 133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 10708 (10K) [text/plain] Saving to: 'synx.py.13' 100%[======================================>] 10,708 --.-K/s in 0s 2017-10-05 10:17:05 (126 MB/s) - 'synx.py.13' saved [10708/10708] Traceback (most recent call last): File "synx.py", line 12, in <module> NODE_LIST = urlopen(' https://transfer.sh/14vce1/nodelist_09_10.txt').read() File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen return _opener.open(url, data, timeout) File "/usr/lib/python2.7/urllib2.py", line 410, in open response = meth(req, response) File "/usr/lib/python2.7/urllib2.py", line 523, in http_response 'http', request, response, code, msg, hdrs) File "/usr/lib/python2.7/urllib2.py", line 448, in error return self._call_chain(*args) File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain result = func(*args) File "/usr/lib/python2.7/urllib2.py", line 531, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) urllib2.HTTPError: HTTP Error 500: Internal Server Error root@vultr:~# can you help please |
|
|
|
We do not reveal the number of miners we are producing, or future production plansNo shady at all  they saw that our calculation was right and said that u cant trust us because they didnt disclose that information they had batch 2 days ago and it didnt sold that good and they got worried they are such a big pussies in 12 hours I have made 11USD with the first batch D3+......no comments |
|
|
|
"We are releasing new batches of the Antminer S9 and Antminer D3 DASH miner today (26 September)! Antminer S9 will be available here ( https://goo.gl/L1VJPg) after 2PM Antminer D3 will be available here ( https://goo.gl/wz4KNH) after 5PM today. All times are in GMT+8. BCC, BTC, LTC and USD will be accepted as payment methods for these batches." profitability is going to be in cents or not in dollars mid Jan. Good luck for those who are going to purchase them |
|
|
|
|
they are still available.....I can order more than 30...but I want!!! the ROI is crap and it is risky in the coming future.....I think they are trying to sell their stock before the new law in china
|
|
|
|
I received my D3 since Monday. I'm making 70USd per day......I wonder what will be the profit in December. I will be reselling my miner once I collect my investment. not worth it!! good luck November/December Batch
Its worth for only those who bought in the early batch, now profitability is going down each single day. Not really because the first batch was sold for $2699 much more than the later batches. My recommendation is NO GO for D3 even if the price of Dash increases...given the 3 batches on their way |
|
|
|
|
