Es werden die Komponente durch eBay verkauft.

Ich möchte es lieber als gesammt verkaufen.

Preisvorschlag habe ich hinzugefügt...

Ich verkaufe eine Rig (für z.B. Litecoin's zu erstellen):

Thermaltake Toughpower Grand 1200W
5 x Sapphire RADEON HD 5850 Xtreme - Grafikkarte - Radeon HD 5850, 11162-15-20G
MSI Big Bang-Marshal (B3) Socket1155 DDR3 XL ATX 8xPCIe
Intel Quad Core Prozessor (Intel Core i5-2500, 3,3GHz, 6MB Cache, 1155 Sockel)
Kingston HyperX PC3-12800 Arbeitsspeicher 4GB (1600 MHz, 240-polig) x 4 = 16 GB
Arctic Freezer 13 Pro CPU-Kühler 120mm
Festplatte mit Debian+cgminer installiert.

Ohne Gehäuse - auf einem Akazie-Holzblatt und Aluminium-Kunstoff Rahmen montiert.

Es wurde 2011 erstellt, wurde damit ~100 BTC erstellt, dann abgeschaltet (wegen Wärme und Lärm), dann selten benutzt (für Bitcoin, Litecoin und Rucoin).
Bis Heute funktioniert es einwandfrei und stabil.

Abholung/Lieferung in gegend Freilassing (München) möglich. Per Post versende ich es ungern.

Preis: 900 EUR + Lieferkosten

Bild (noch mit 4 Grafikkarte):



Bild (schon mit 5 Grafikkarte - von "Hinten"):

I started an auction (100 rucoin) at https://www.bitmit.net/en/item/49466-100-rucoin

Source seems to be free yet!!!

"Скачать исходные коды
Исходники для версии 0.4.0.1_beta

Инструкция для начинающих: Как скомпилировать rucoind под Debian / Ubuntu

1. качаем исходники в рабочую папку:

cd ~
wget --no-check-certificate https://www.rucoin.org/rucoin-0.401.tar.gz

2. Распаковываем архив

tar -zxvf rucoin-0.401.tar.gz

3. Входим в полученную папку с исходниакми:

сd rucoin-0.4.0.1/src

4. редактируем файлик makefile.unix

В строке USE_UPNP:=0 отрезаем нолик, оставляем USE_UPNP:=

5. подтягиваем нужные пакеты:

apt-get install build-essential libgtk2.0-dev libssl-dev libdb4.8-dev libdb4.8++-dev libboost-all-dev

6. выполняем компиляцию rucoind

make -f makefile.unix rucoind

в текущей папке должен появиться файл rucoind
В принципе, всё готово.

Теперь можно переместить файл rucoind в папку, где он будет жить и работать. А ненужные файлы - удалим:
7. Перекладываем файл например в /etc/rucoin

mkdir /etc/rucoin
mv rucoind /etc/rucoin/
удаляем исходники:
rm -R ~/rucoin-0.4.0.1
можно заодно удалить пакеты, которые ставились для компиляции:
apt-get purge build-essential libgtk2.0-dev libssl-dev libdb4.8-dev libdb4.8++-dev libboost-all-dev


8. Теперь попробуем запустить rucoind. Для начала выполняем:

./etc/rucoin/rucoind

В ответ будет нечто вроде:

Warning: To use rucoind, you must set rpcpassword=<password>
in the configuration file: /root/.rucoin/rucoin.conf
If the file does not exist, create it with owner-readable-only file permissions.

То есть нужно создать файл rucoin.conf с настроойками.
В минимальном варианте это может быть одна строка:
rpcpassword=любойпароль
Создадим файл rucoin.conf в папке ~/.rucoind/
и присвоим ему права:
chmod 600 ~/.rucoind/rucoin.conf

Теперь запускаем демона, он должен нормально заработать:

/etc/rucoin/rucoind&

Проверяем работоспособность:

/etc/rucoin/rucoind getinfo
в ответ должно выдать несколько строк информации

Останавливаем демона командой:

/etc/rucoin/rucoind stop

Можно попробовать другие команды, по аналогии с getinfo и stop:
 getbalance – просмотр баланса
 listaccounts – показывает список «аккаунтов»
 getaddressesbyaccount "" – просмотр списка адресов на аккаунте ""
 getnewaddress – генерирует новый адрес
 getconnectioncount – показывает текущее кол-во соединений
 listtransactions – показывает список транзакций


Теперь о том, как можно прописать rucoind в автозапуск.

Для начала - сделаем, чтобы демон работал не от имени root, а от имени специально созданного пользователя с более скромными правами:

Создаём пользователя "rucoin":
adduser rucoin
При создании задаём ему какой-нибудь пароль.

Останавливаем демона, если он запущен:
/etc/rucoin/rucoind stop

и пробуем запустить его от имени пользователя "rucoin"
su rucoin -c /etc/rucoin/rucoind

В ответ получаем уже знакомое:
Warning: To use rucoind, you must set rpcpassword=<password>
in the configuration file: /home/rucoin/.rucoin/rucoin.conf
If the file does not exist, create it with owner-readable-only file permissions.
То есть необходим файл с настройками для пользователя "rucoin"
Можно его просто скопировать файл настроек с текущего пользовтеля:
cp ~/.rucoin/rucoin.conf /home/rucoin/.rucoin/
и, разумеется, сменить владельца файла:
chown rucoin:rucoin /home/rucoin/.rucoin/rucoin.conf
После запустим демона от имени пользователя "rucoin":
su rucoin -c /etc/rucoin/rucoind&
Если пароль в файлах rucoin.conf у пользователя root и rucoin одинаков,
то посылать команды демону мы можем и от имени root, например:
/etc/rucoin/rucoind getinfo

Чтобы прописать демона в автозапуск, сделаем следующее:
1. откроем файл /etc/inittab
2. добавим куда-нибудь в конец строку
ru:23:once:su rucoin -c /etc/rucoind/rucoind&
3. записываем файл.
4. после перезагрузки демон должен запуститься сам, под пользователем "rucoin"
5. проверяем его командой /etc/rucoin/rucoind getinfo

И в заключении немного "волшебства":
поскольку пиринговая сеть rucoin пока ещё не велика,
то установка соединений бывает происходит довольно долго.
Если долго ждать не хочется, можно прибегнуть к такому трюку:
останавливаем демона
/etc/rucoin/rucoind stop
запускаем с ключиком -irc0
su rucoin -c "/etc/rucoin/rucoind -irc0"&
как правило, после этого соединения устанавливаются быстро.

Полезные ссылки
Русская биржа, где меняют криптовалюту
btc-e.com
Крупнейшая биржа по торговле BTC
mtgox.com
« ещё ссылки"

Thank you for feedbacks and votes!

If you didn't do it then

Please, vote, post...

What are you thinking about this ideas?
What to do, implement first?
What is important for you?

I just try p2pool... See https://bitcointalk.org/index.php?topic=18313.0
...
2012-01-13 07:28:19.188111 Average time between blocks: 0.88 days
2012-01-13 07:28:19.189053 Pool stales: 10% Own: 22±9% Own efficiency: 87±10%
2012-01-13 07:28:25.394099 New work for worker! Share difficulty: 149.261210 Payout if block: 0.381068 BTC Total block value: 50.035421 BTC including 13 transactions
2012-01-13 07:28:28.206763 Pool: 71643MH/s in 17322 shares (11958/17326 verified) Recent: 2.53% >1813MH/s Shares: 79 (16 orphan, 0 dead) Peers: 10
2012-01-13 07:28:28.208500 Average time between blocks: 0.87 days
2012-01-13 07:28:28.209375 Pool stales: 10% Own: 22±9% Own efficiency: 87±10%
2012-01-13 07:28:28.986495 New work for worker! Share difficulty: 144.975156 Payout if block: 0.380885 BTC Total block value: 50.035421 BTC including 13 transactions
2012-01-13 07:28:31.215252 Pool: 70741MH/s in 17323 shares (11959/17327 verified) Recent: 2.53% >1790MH/s Shares: 79 (16 orphan, 0 dead) Peers: 10
...
It is a very clever concept, and seems to be a very good implementation yet.

It is very interesting. I have Ideas (greencoin) to use less computing power for mining - the remainder 95% is usable for a "cloud". It isn't implemented yet. It is just in a phase "brainstorming".

I think current Bitcoin-System will have a central authority - it's needed only some time... See my post:


I will that the Bitcoin (or Greencoin) - community do not lose later the control.
Please, see my first post too... I change it continuously.
This posts are a kind of 'Brainstorming', it is not about a real or implemented money. But it will be later implemented, I hope.

Thanks for criticism, and questions.

Satoshi' paper (only the first paragraph "Abstract") criticism:

"Abstract. A purely peer-to-peer version of electronic cash would allow online
payments to be sent directly from one party to another without going through a
financial institution. Digital signatures provide part of the solution, but the main
benefits are lost if a trusted third party is still required to prevent double-spending.
We propose a solution to the double-spending problem using a peer-to-peer network.
The network timestamps transactions by hashing them into an ongoing chain of
hash-based proof-of-work, forming a record that cannot be changed without redoing
the proof-of-work. The longest chain not only serves as proof of the sequence of
events witnessed, but proof that it came from the largest pool of CPU power. As
long as a majority of CPU power is controlled by nodes that are not cooperating to
attack the network, they'll generate the longest chain and outpace attackers. The
network itself requires minimal structure. Messages are broadcast on a best effort
basis, and nodes can leave and rejoin the network at will, accepting the longest
proof-of-work chain as proof of what happened while they were gone."


"Digital signatures provide part of the solution, but the main benefits are lost if
 a trusted third party is still required to prevent double-spending."

- A trusted third party (in greencoin) isn't required for prevent double-spending, it is required
to prevent 50%+1 attack. The trusted third party should be the community
of users/miners/guests/moderators of greencoin... The community of our money.

"The longest chain not only serves as proof of the sequence of events witnessed,
but proof that it came from the largest pool of CPU power."

- The longest chain not only serves as proof of the sequence of events witnessed,
but proof that it came from the largest pool of trusted miners. "power" is
a possible means of a "centralised authority" - please, do not use it for prevent double-spending

"The network itself requires minimal structure. Messages are broadcast on
a best effort basis, and nodes can leave and rejoin the network at will,
accepting the longest proof-of-work chain as proof of what happened while they were gone."

- "best effort" = "power" => The network should be redesign too.

Info from github:

https://github.com/bitcoin/bitcoin/pull/574

"gavinandresen merged 5 commits into bitcoin:master from sipa:dumpprivkey 9 days ago

sipa (re)opened this pull request October 07, 2011
Dumpprivkey

Introduces three new RPC calls:
* dumpprivkey: retrieve the private key corresponding to an address
* importprivkey: add a private key to your wallet
* removeprivkey: delete a private key from your wallet" - It isn't active yet.

I am a fan of this pull request! One requirement of greencoin was inspired by this...

Congratulation sipa, jgarzik and gavinandresen!

I think, it is a must, that the miners personally identified. Think an history of bitcoin - and a possible future:

• firstly CPU mining. (technology A - public)
• then GPU mining. (technology B - public (fortunately) but technology A not an opponent)
• ... some other public technology, pools, merged mining, and so on...
• in future: technology X coming - (not published - owned by some (or one) persons/firms/...) AND (technology A and technology B and other public technologies aren't an opponent) - the controll of members of Bitcoin forum over bitcoin (and our "money") loosed!

And about some possible identification attribute of a person (or a computer):

• http://en.wikipedia.org/wiki/Personally_identifiable_information
• a fingerprint of a person, a computer, a cpu id or special HW
• I am identified in mtgox through a yubikey (+ some personal data - see wikipedia link)
• I am identified in Bitcoin forum through my activity (+ some personal data - e-mail, ...)

I think not a 100% identifying - I am engineer and not a Mathematicians - me enough for example the last in the list...

and

• Guest
• Newbie
• Jr. Member
• Full Member
• Miner - Full Member + an trusted public key
• Sr. Member
• Hero Member
• + Moderators

Sorry for a little pause - I am a human too

"drawing": yes, it is a lottery...

I think it is better, if a miner is an identified person - so it is not possible anonym attack the system, and it is not possible more than one miner computer pro person.

If you think a "central authority" - Yes, we will have - in a form of a peer-to-peer net

And that computer is a computer, that is used for an another (daily job, hobby) purpose too. (And not only for "mining"...)

The german translation coming soon - please be patient.
For Idea "garanteer" I have new Ideas too.

I removed some text/picture... Thanks for a hint.