probably they have just finished to deploy their on pool software and are slowly switching their miners... |
|
|
|
Is it either because many of you are too naive, or too stupid to understand the nature of Bitcoin. It's an anonymous virtual currency that's quite impractical and instable. As shown just this month with Mt.Gox, it's price jumped what, 30% in one day? I love how many of you are so against regulation, but without regulation is when there's a real problem. Illegal drug trafficking sites such as Silk Road made millions off people buying drugs through Bitcoin. There needs/will be regulation of a cryptocurrency in the future. The reason why the feds haven't bothered to regulate Bitcoin much in the USA, or completely ban it in other countries is because of it's price fluctuations, high transaction times, and high energy output to mine, which they know that after a while people will Move on to another more effiencet, more practical for daily use cryptocurrency . They know that in the future, a new cryptocurrency without all the flaws of Bitcoin will emerge, and WILL become mainstream which Bitcoin hasn't, still 5 years after it's release and never will become. Once that happens you can expect regulation no matter how "anonymous" you think it is.
Just giving you all naive suckers a heads up.
Pce.
So you're saying that instability and anonymity are the main flaws of btc, am I right? The former is due to the narrow liquidity intrinsic to any new-born market, the latter is simply false. Bitcoin is not anonymous. |
|
|
|
I went on vacation on the 21st. On 23rd I logged in to bitstamp because I thought one week of storage of bitcoin on an exchange were too much.
My balance was zero $ and zero bitcoins. From the history I saw someone (not me) made this astonishing things:
* 2014-02-22 19:56:08 109.163.234.9 Logged in using two-factor authentication
* 2014-02-22 20:01:39 109.163.234.9 Opened bitcoin withdrawal request for 23.83677391 BTC to 1PGPkndy1nYLUee3nKKLez8smjqK5zBNKE
* 2014-02-22 20:01:39 109.163.234.9 Bitcoin withdrawal request: email was sent to user
* 2014-02-22 20:02:00 109.163.234.9 Bitcoin withdrawal request: email confirmed by user
* 2014-02-22 20:09:33 161.53.74.122 Changed user password
* 2014-02-22 20:12:33 96.47.226.20 Opened instant buy order for $36.30
* 2014-02-22 20:13:38 96.47.226.20 Opened bitcoin withdrawal request for 0.05965404 BTC to 1PGPkndy1nYLUee3nKKLez8smjqK5zBNKE
* 2014-02-22 20:13:38 96.47.226.20 Bitcoin withdrawal request: email was sent to user
* 2014-02-22 20:15:35 96.47.226.20 Bitcoin withdrawal request: email confirmed by user
* 2014-02-22 20:24:24 141.212.108.13 Changed user password
if I read correctly it seems they managed to restore your usual password after the hack, am i right? |
|
|
|
Now why this Stamp bashing? Do I need to know something? Have a lot of Coins there...
Are you serious? It's not wise to keep a lot of value into an exchange account. And especially not in an exchange that is running such shoddy malfunctioning code as bitstamp. WTF everybody here was saying that Stamp is the best exchange and finaly we get rid of gox and hail Stamp... And now its bullshit code? My advice wasn't related to a particular exchange. IMHO it's a rule that you must follow to avoid painful losses and it applies to all the exchanges. |
|
|
|
Now why this Stamp bashing? Do I need to know something? Have a lot of Coins there...
Are you serious? It's not wise to keep a lot of value into an exchange account. |
|
|
|
2- make sure that you use one of the best antivirus programs on the computer you use to browse around and make sure it is up to date.
If I may I dare to expand this point a little. Please do not use windows. It implies an order of magnitude wider attack surface when compared to Linux, OpenBSD, etc. I'm not saying that the latter are better OS per se, I'm only saying that the more diffuse is an OS the higher the effort to hack that system. So ideally just try to compile your wallet on the less spreaded OS, ideally one should use plan9(*) or something like this. A good compromise in terms of usability could be Linux or FreeBSD. (*) No, I didn't try to compile bitcoind on plan9 but is should be feasable. |
|
|
|
I am still wishing for a day where I can buy my BTC and LTC at one professional exchange like Bitstamp...
Kraken has both BTC and LTC. and a monthly limit of 100K, I would do that if a week... you sure? from kraken site, if you bother/can get "Tier 4 Admiral" verification: Dailiy limits: Deposit $100,000.00 Withdraw $100,000.00 Monthly limits: Deposit $500,000.00 Withdraw $500,000.00 |
|
|
|
I also would like to buy some LTC, but sadly I did the mistake in using BTC-E. 13 confirms and counting. I hope that BTC won't drop back to 500 meanwhile  I guess that there has to be a delay on BTC deposits, so that "the right people" can all buy in, before all the deposits arrive at the same time creating a sudden surge upwards. One of the reason I left BTC-E, was because it reeked of insider trading with someone constantly playing with 2mil.$+ LTC buy/sell walls. Any recommendation on what is the most trustworthy place that also trades alts like LTC and PPC? dunno about PPC but you can trade LTC on kraken.com |
|
|
|
Auroracoin up 40% since this morning & still on a tear  Wow, buying Auroracoin must be one of the most ingenious methods of donating money to the people of Iceland as possible. I had no idea there was so much love for Icelandic people! : -) well, they are nice folks. but i think it is an interesting social experiment also, especially in light of what happened with their banks and currency during the big collapse a few years back. just another tendril in the crypto revolution. dunno if legit but seems that a pump'n'dump is goign on on AUR https://twitter.com/CryptoJapan/status/440627366759387136/photo/1 |
|
|
|
wan't to avoid the possibility of you deleting your own post. just a guess.
"wa not" - Bronstad  edit1: sure he would have sign the quote with one of his private key |
|
|
|
"$5500 this year is completely delusional. I hope really someone ends up posting my response to prove me wrong, but thinking that will happen is, again, delusional."
-chesthing
Wouldn't it make more sense to repeat my post after it has hit $5500? yep, but maybe proudhon wan't to avoid the possibility of you deleting your own post. just a guess. |
|
|
|
Hi,
does anyone know, if it is ok to flash the 99.2E FW and flash back to 99.2 oct unit FW with a 4vmrs asic board
the problem is, that i have 3x8vmrs and 1x4vrms boads after a RMA. And now i woul like to activate all 8 vrms on the 3 8vrms boards and do not know what will happen with the last 4vrm board.
yes but then you can't use 1.0 with 8vrms settings... Yes you can I will start with a warning. It is unknown if this is safe. KnC may have turned off the VRMs due to that there is a problem with the design.
You board might burn! On the other hand they ran with all VRMs turned on for a few weeks when they were new without any major issues. I have run a few machines with 8VRMs for almost 2 weeks without problems. Some machines will start buzzing pretty loud, I have no idea why. Suggested procedure to enable all 8 VRMs: 1. Change all voltage adjustment to at least -0.517. When all VRMs are turned on the adjustment will be from a base of ~0.9V, -0.517 will give a voltage of ~0.85V which works fine for 1Ghz. It may work fine with lower values, such as -1.0V at lower clocks. I have not experimented much. With -0.5V and 1Ghz the machine will pull over 900W from the PSU (~220W reported per board). 2. Stop cgminer/bfgminer Run on a shell: /etc/init.d/cgminer.sh stop 3. Run the enable.sh script. (see below) The script will take the voltage adjustments of the "official" 4 VRMs on each board and make sure that both VRMs for each die will have the same adjustment. It also turns on all VRMs. 4. reboot. Do not power cycle. The VRMs have a tendency to get upset when they are turned on the first time and set error flags and in some cases not start properly. A reboot cleans things up. 5. Verify on the advanced settings page that the current on each pair of VRMs is in the same ballpark. The pairs are 0+1, 2+3, 4+5 and 6+7. 6. Overclock as usual Each time you apply a voltage adjustment in the advanced page you have to run enable.sh again to make sure the pairs have the same adjustment. This is VERY important!. The script is safe to run on a machine with mixed 4 and 8 VRM boards. You may get some error message when the script tries to tank to the missing VRMs. If you powercycle the machine I am pretty sure all changes are gone. I haven't powercyled my machines since October when there was a storm and we lost power for a few minutes. The script (enable.sh):
#!/bin/sh
# Fetches the TRIM settings of the official 4 VRMs and sets the
# same value into each paired VRM.
for b in 3 4 5 6 7 8 ; do
v0=`i2cget -y $b 0x10 0x22 w 2>/dev/null`
if [ "$v0" != "" ] ; then
i2cset -y $b 0x11 0x22 $v0 w 2>/dev/null
fi
v1=`i2cget -y $b 0x12 0x22 w 2>/dev/null`
if [ "$v1" != "" ] ; then
i2cset -y $b 0x13 0x22 $v1 w 2>/dev/null
fi
v2=`i2cget -y $b 0x14 0x22 w 2>/dev/null`
if [ "$v2" != "" ] ; then
i2cset -y $b 0x15 0x22 $v2 w 2>/dev/null
fi
v3=`i2cget -y $b 0x17 0x22 w 2>/dev/null`
if [ "$v3" != "" ] ; then
i2cset -y $b 0x16 0x22 $v3 w 2>/dev/null
fi
done
# Turn On all VRMs using "on" in OPERATION
for b in 3 4 5 6 7 8 ; do
for d in 0 1 2 3 4 5 6 7 ; do
i2cset -y $b 0x1$d 1 0x80 >/dev/null 2>&1
done
done
What the script does is that it reads the voltage adjustment register (VOUT_TRIM, address 0x22) from the official VRMs (0x10, 0x12, 0x14 and 0x17) and writes the same value to the other VRM in each pair. And then it sets the "On" bit (0x80) in the OPERATION register, address 1. Excellent! Thanks for sharing this and for been the brave soul who studied GE VRMs manual and then applied the findings on his own miners. really appreciated. |
|
|
|
Looking at the source code for the 'Advanced' tab I find in line 44-46 the following: var dieFreqTemplate = $('<select/>'); $.each(config.valid_die_frequencies, function(i, frequency) { dieFreqTemplate.append('<option value="' + frequency + '">' + frequency + ' MHz</option>'); it looks like this is a lookup of valid die frequencies from a file named 'config.valid_die_frequencies'. Maybe we just have to find this file and amend it? In short the CGI backend calls "waas -i valid-config" to determine which settings the ASIC allows. "config.valid_die_frequencies" is the JSON element reqturned from waas that is used to populate the drop down. waas itself also applies all settings and it will not accept anything outside of the range supported, be it 775 on the October and 1000 on the November. I hacked up the firmware to allow settings outside of the range, I am working through one issue now and will post it when it's done.. Are you going to reverse-engineer the waas executable or are you modifying the cgminer init script to overwrite settings applied by the waas executable? |
|
|
|
I have inspected what the November firmware has actually changed.
What I can see it has changed a value in one of the registers in the VRMs. It has set the "ON" bit in the OPERATIONS register,changing what conditions are needed to turn the VRMs on.
This change will be permanent even if rebooted or power-cycled. It can be changed using i2c commands:
Turn all VRMs on:
#!/bin/sh
# Stop SPI poller
i2cset -y 2 0x71 2 0
for b in 3 4 5 6 7 8 ; do
for d in 0 1 2 3 4 5 6 7 ; do
i2cset -y $b 0x1$d 1 0x80 >/dev/null 2>&1
done
done
Restore to factory settings:
#!/bin/sh
# Stop SPI poller
i2cset -y 2 0x71 2 0
for b in 3 4 5 6 7 8 ; do
for d in 0 1 2 3 4 5 6 7 ; do
i2cset -y $b 0x1$d 1 0x0 >/dev/null 2>&1
done
done
I suggest stopping cgminer before doing this to limit the power when the operation is done.
Reading the datasheet for the VRMs I can see that when using them in pairs (as we do when all are turned on) there are some requirements on how they should be turned on. This method does not do that!
I have heard that hizzing sound as well. Some boards do that. They did that on 0.90 firmware too. No idea why.
I do not know if this is safe or not, it might be unsafe and burn your boards.
I was not referring to this particular script/functionality, i.e. enabling all VRMs. Bondus said that 1.00 do not apply voltage settings to all the VRMs even if they are all enabled, this is bad because the VRMs are supposed to work in couple by desing. Having different voltage settings on coupled VRMs could demage the HW. |
|
|
|
A warning:
For you brave souls that have enabled all 8 VRMS (early Octobers) I saw today that the 1.0.0 firmware does not apply the voltage adjustment to all 8 VRMs. It only applies it to the 4 that are officially enabled. The old FW applied this adjustment to all VRMs.
The VRMs work in pairs and if the voltage adjustment (VOUT_TRIM register) of the 2 VRMs in a pair is different things will go bad.
If you still want to use all 8 VRMs I suggest you read and understand the datasheet of the VRM.
The VRMs are very resilient to abuse, but they have limits.
Other than that FW 1.0.0 works very good. HW errors have dropped a lot for me. Good chips are close to 0% errors (2% before), bad chips still close to 2%.
THanks to his help via IRC I was able to update fw and still use my 2 8vrm boards...and my hw error droped down to .11% from .25% yay hopefully it stays that low as i just restarted...Thxs bondus do you care to share bondus help? i would post his script if he gave me permission too...he's not on IRC so i can't ask him  sorry don't worry. I appriciated your attitude, and obviously it would be amazing if bondus grant you the permission to share such a script |
|
|
|
A warning:
For you brave souls that have enabled all 8 VRMS (early Octobers) I saw today that the 1.0.0 firmware does not apply the voltage adjustment to all 8 VRMs. It only applies it to the 4 that are officially enabled. The old FW applied this adjustment to all VRMs.
The VRMs work in pairs and if the voltage adjustment (VOUT_TRIM register) of the 2 VRMs in a pair is different things will go bad.
If you still want to use all 8 VRMs I suggest you read and understand the datasheet of the VRM.
The VRMs are very resilient to abuse, but they have limits.
Other than that FW 1.0.0 works very good. HW errors have dropped a lot for me. Good chips are close to 0% errors (2% before), bad chips still close to 2%.
THanks to his help via IRC I was able to update fw and still use my 2 8vrm boards...and my hw error droped down to .11% from .25% yay hopefully it stays that low as i just restarted...Thxs bondus do you care to share bondus help? |
|
|
|
A warning:
For you brave souls that have enabled all 8 VRMS (early Octobers) I saw today that the 1.0.0 firmware does not apply the voltage adjustment to all 8 VRMs. It only applies it to the 4 that are officially enabled. The old FW applied this adjustment to all VRMs.
The VRMs work in pairs and if the voltage adjustment (VOUT_TRIM register) of the 2 VRMs in a pair is different things will go bad.
If you still want to use all 8 VRMs I suggest you read and understand the datasheet of the VRM.
The VRMs are very resilient to abuse, but they have limits.
Other than that FW 1.0.0 works very good. HW errors have dropped a lot for me. Good chips are close to 0% errors (2% before), bad chips still close to 2%.
many thanks bondus. very helpful as usual. So how did you manage to apply the advanced settings to all the VRMs after upgrading to the new firmware? did you just use the old fetch_advanced_settings.cgi or did you also use the old waas executable? |
|
|
|
It will crash hard, we won´t see 1000$ any time soon(if ever)
Did you ever run out of energies? Really, I'm impressed by your commitment |
|
|
|
|
Show Posts
