 Show Posts
|
|
Pages: « 1 2 [3] 4 5 6 »
|
Has anybody set a static IP address for their SP20? I found the "Network" section of the Settings page. As you would expect, the "Use DHCP" box is checked. When I uncheck that box, all the usual items for the IP address and other usual IP addresses on my network are set as you would expect from when it got them as part of the DHCP exchange. I then just change the miner IP address and leave all the other stuff as it was since it's correct. I hit the "Save" button. Nothing obvious happens. When I do anything else, the Netwrok essentially reverts to "Use DHCP".
Is this something I need to do via SSH, or am I just missing something on the Settings page to actually make it "stick"?
I did and it worked. Are you sure that you don't have an IP address conflict? I am running 2.6.14 firmware. Does that match your SP20? When does the change seem to take effect on your system? Do you have to reboot, or what? I do appreciate the comment. Also of note, the primary Spondoolies thread appears to be unlocked now. I assume you mean the change from DHCP to static IP. It took effect as soon as you save it, if it can find your DNS server. Where is this primary SP20 thread  I want to vent my spleen on it. |
|
|
|
Has anybody set a static IP address for their SP20? I found the "Network" section of the Settings page. As you would expect, the "Use DHCP" box is checked. When I uncheck that box, all the usual items for the IP address and other usual IP addresses on my network are set as you would expect from when it got them as part of the DHCP exchange. I then just change the miner IP address and leave all the other stuff as it was since it's correct. I hit the "Save" button. Nothing obvious happens. When I do anything else, the Netwrok essentially reverts to "Use DHCP".
Is this something I need to do via SSH, or am I just missing something on the Settings page to actually make it "stick"?
I did and it worked. Are you sure that you don't have an IP address conflict? I had to enter my AT&T DNS server address and when I saved it the box displays #Your static network configuration instead of the actual DNS server IPs. Check to see if your ISP has its own required DNS servers. |
|
|
|
[We don't cut corners (e.g. embedded controller, etc) and we use dc2dc which means that the BOM is higher.]
If you don't cut corners then why didn't you install an internal microSD card I had to go buy one in an attempt to revive several DOA SP20s. I had to go to 3 stores before I found a card and reader ($19) for this thing I'll never use for any other purpose. AntMiners have an internal SD card so one can reset factory settings by pressing a button. |
|
|
|
|
The mining contracts are priced ridicuously high at about 3 times what it will ever earn. Buying a mintsy mining contract should be considered buying a lottery ticket on the future price of BTC.
I've mining with rented rigs at mintsy for a day and it sucks. I wouldn't even call this an alpha site much less a beta test.
|
|
|
|
|
I've mining with rented rigs at mintsy for a day and it sucks. I wouldn't even call this an alpha site much less a beta test.
The mining contracts are priced ridicuously high at about 3 times what it will ever earn. Buying a mintsy mining contract should be considered buying a lottery ticket on the future price of BTC.
|
|
|
|
Looks like the developers have reverted v1.2.0
Deposits and withdrawals will be back online at cryptsy shortly after a chain resync
Mullick, Glad to hear it, but, that was 12 days ago. I've got a bunch of eMarks burnin' a hole in my pocket. Hope it's working soon. |
|
|
|
[...] If my wallet was not corrupted by 0.10.0 I would definitely have gone back to an earlier version.
This is the first time you mention your wallet.dat got corrupted. Maybe a general HDD problem? I never said my BTC wallet was corrupted. As I understand it 0.10.0 alters it when it gets converted to headers first so one cannot use a 0.10.0 wallet in 0.9.x client. I used the same wallet when I reloaded the entire blockchain which took 3 days. It now works but I will not risk being a full node and I will only open it when I have to. I've emptied it and I'm going to use my CoinBase wallet from now on. |
|
|
|
I upgraded to BitCoin Core 0.10.0 64-bit Windows very shortly after it was released. I've been running a full node since it finished syncing after 2 days. I've had a couple days when it reindexed the blockchain, or something, that took a few hours but worked fine after that finished. Now it's frozen at block 346578 and will not sync up. I just reinstalled 0.10.0 and it reindexed blocks but has remained frozen at block 346578. When I check at getaddr.bitnodes.io it says my address is unreachable. I changed it to my IP address instead the address it defaulted to and it now says "23.119.56.197:8333 /Satoshi:0.10.0/." How can it be unreachable yet I have 10 connections in and 8 out with plenty of traffic I checked Windows Firewall Inbound Rules and verified that I have port 8333 open. I sure need to receive my BTC deposits from the last 3 days of pool mining. What can I do TIA Now I'm on the 4th day of being frozen at block 346578. Looks like upgrading to 0.10.0 was very premature as it freezes up. I gave up and removed all trace of the thing. I reinstalled it and will not wait another 2 days to see if it's capable of syncing up. If my wallet was not corrupted by 0.10.0 I would definitely have gone back to an earlier version. |
|
|
|
I upgraded to BitCoin Core 0.10.0 64-bit Windows very shortly after it was released. I've been running a full node since it finished syncing after 2 days. I've had a couple days when it reindexed the blockchain, or something, that took a few hours but worked fine after that finished. Now it's frozen at block 346578 and will not sync up. I just reinstalled 0.10.0 and it reindexed blocks but has remained frozen at block 346578. When I check at getaddr.bitnodes.io it says my address is unreachable. I changed it to my IP address instead the address it defaulted to and it now says "23.119.56.197:8333 /Satoshi:0.10.0/." How can it be unreachable yet I have 10 connections in and 8 out with plenty of traffic I checked Windows Firewall Inbound Rules and verified that I have port 8333 open. I sure need to receive my BTC deposits from the last 3 days of pool mining. What can I do TIA Now I'm on the 4th day of being frozen at block 346578. |
|
|
|
I upgraded to BitCoin Core 0.10.0 64-bit Windows very shortly after it was released. I've been running a full node since it finished syncing after 2 days. I've had a couple days when it reindexed the blockchain, or something, that took a few hours but worked fine after that finished. Now it's frozen at block 346578 and will not sync up. I just reinstalled 0.10.0 and it reindexed blocks but has remained frozen at block 346578. When I check at getaddr.bitnodes.io it says my address is unreachable. I changed it to my IP address instead the address it defaulted to and it now says "23.119.56.197:8333 /Satoshi:0.10.0/." How can it be unreachable yet I have 10 connections in and 8 out with plenty of traffic I checked Windows Firewall Inbound Rules and verified that I have port 8333 open. I sure need to receive my BTC deposits from the last 3 days of pool mining. What can I do TIA |
|
|
|
One of the biggest things is quality. The SP20's are rock solid with the metal case and I love them. I was running full blast since i got them. Now I have underclocked them. It is impressive to have such a wide range of power.
Also with them I never have had to babysit. It is pretty much set and forget until I want to change pools.
Are you same notlist3d that stole money from me at BTCjam.com https://btcjam.com/users/43568https://btcjam.com/listings/23012-upgrade-mining-capacityFunny that you brag about having miners running and you refuse to repay the money that bought them for you. |
|
|
|
Is there any benefit to including a NetCoin.conf file The older forums mentioned a conf file but there's only one mention in this forum and that's how to disable staking for pool operators. |
|
|
|
Anyone know when we might be able to convert DEM on an exchange which exchange doesn't convert DEM? Cryptsy. Which exchange does cryptsy converts the coins but you cannot withdraw DEM for the moment. I am not sure if you can deposit DEM to cryptsy. DEM wallet has been closed at Cryptsy for a long time. Sure would be nice if the eMark devs would say if they're going to fix it or not. |
|
|
|
Anyone know when we might be able to convert DEM on an exchange which exchange doesn't convert DEM? Cryptsy. Which exchange does |
|
|
|
Anyone know when we might be able to convert DEM on an exchange |
|
|
|
It appears the eMark dev team has abandoned the coin. I've emailed them with no response. Cryptsy has contacted them and apparently nothing.
If you mine DEM you cannot sell them. You risk having all new coins in your wallet invalidated.
Well thats not completely true. The devs are around. They did make the update after all. I think there is a language barrier that s holding things up. That's great news, I hope the fix is in soon. I have a lot of eMarks I'd like to sell. I do not see any news or a new version of the wallet on their website. Any ETA when the Cryptsy DEM wallet will open again |
|
|
|
|
It appears the eMark dev team has abandoned the coin. I've emailed them with no response. Cryptsy has contacted them and apparently nothing.
If you mine DEM you cannot sell them. You risk having all new coins in your wallet invalidated.
|
|
|
|
So Cryptsy says eMark is broken. Is anyone from the eMark team working on a fix i dont think, that eMark is broken. Thousands of User wallets running sucessful. Thats because they are not using the recent update. If the devs force this update as mandatory all coins mined since the update are invalid. I will not take that risk with our customers funds Build the new wallet and run it for 24 hours. It will crash on a non standard transaction tyoe My wallet is eMark Version v1.1.0.0-oro. Is that the new version It's accepting the DEM I've mining. I sure hope they're not all trash. |
|
|
|
eMarks current repository seems to be broken. The update to a different database should have been a mandatory update as it could cause a fork in the network. But in its current state it only seems to make our node crash every few blocks or so with the following as the last output the the debug log. This is after a fresh resync and removing all transaction data from the wallet ERROR: CTxMemPool::accept() : nonstandard transaction type
CommitTransaction() : Error: Transaction not valid
CWalletTx::GetAmounts: Unknown transaction type found, txid fcca66178ed8088e63e35b318aabf6da50de9f973448691bfa97ca1964ebea3a Once either the repository is fixed or the decision to revert back to the previous version is made we will once again enable deposits and withdrawals So Cryptsy says eMark is broken. Is anyone from the eMark team working on a fix |
|
|
|
Is the purpose of POS to stagnate coins |
|
|
|
|
