|
21
|
Local / Барахолка / Re: [Предзаказ] Bitfury ASIC 65nm
|
on: September 30, 2013, 10:57:24 AM
|
хотя думаю что после войны цен и финишного распределения хешей - ROI будет 2 года примерно. и это будет отличным достижением для биткоина - это будет как раз серьезный ROI. Так что зарабатывать как раз можно только сейчас
сейчас ROI уже <1. Про какой заработок речь? Я не против даже ROI == 1.1 в течение года, например. Или 1.2-1.3 в течение 2 лет (в биткоинах, естественно). Но их НЕТ, и я не уверен, что будут с такой скоростью роста сложности, благодаря вам. По крайней мере пока у вас не появится реальных конкурентов, с которыми вы не сможете договориться. По сути мы имеем обыкновенную монополию на данный момент, монополию на печать денег. |
|
|
|
|
24
|
Local / Майнеры / Re: Метабанк Bitfury Asic [Настройка]
|
on: September 27, 2013, 05:52:42 PM
|
Дает бОльший хешрейт, чем форк needbmw
На сколько больший? На тройном на 10ГГх больше показывает в веб-морде. Хотя я ей не очень доверяю. По пулу вроде тоже чуть больше, но сколько точно - не знаю. |
|
|
|
|
25
|
Local / Майнеры / Re: Метабанк Bitfury Asic [Настройка]
|
on: September 27, 2013, 05:24:47 PM
|
git clone https://github.com/luke-jr/bfgminer.git -b bitfury ~/bfgminer_luke
cd ~/bfgminer_luke
./autogen.sh
./configure --enable-bitfury --disable-opencl --disable-adl --disable-bitforce --disable-icarus --disable-avalon --disable-modminer --disable-x6500 --disable-ztex --enable-metabank
make
запускать так: sudo screen -dmS bfgminer /home/pi/bfgminer_luke/bfgminer -Q 256 -S metabank:auto -c /.cgminer/cgminer.conf
Дает бОльший хешрейт, чем форк needbmw, однако у Люка нет перезапуска чипов, поэтому со временем хешрейт сильно проседает - надо перезапускать вручную. |
|
|
|
|
26
|
Local / Майнеры / Re: Метабанк Bitfury Asic [Настройка]
|
on: September 26, 2013, 12:18:34 PM
|
Пробовал только что. Красные чипы остались красными, а зеленые (8-14 слот) стали серыми (т.е. ошибки увеличились). Выглядит странно, т.к. на первые 8 плат дует прямо из открытого окна, а они остались красными. Такое ощущение, что дело не в охлаждении или не только в охлаждении. Может быть цепочка на тройном устройстве получается слишком длинная. Edit: развернул вентиляторы обратно, 8-14 слоты опять позеленели. Короче, разворот вентиляторов лично у меня не влияет на кол-во ошибок на 0-7 слоте, но увеличивает ошибки на 8-14 слоте. |
|
|
|
|
27
|
Bitcoin / Development & Technical Discussion / Re: Bitcoin client with I2P patch
|
on: September 16, 2013, 05:53:49 PM
|
I've noticed that I frequently check my peer list and find no i2p peers unless I use -onlynet-native_i2p, but I'd like to also use other peer types.
If you run the patched client in mixed mode, most probably it will use only ip-addresses for outgoing connections. That's why. The bitcoin-client has a pool of known addresses. Selecting of address is a pseudorandom process. At now there are hundreds (at first start) and thousands (after syncing with other clients) known ip-addresses and only several I2P-addresses in the pool. By default only 8 outgoing connections are allowed. So probability of selecting an i2p-address is less than 1%.
If you want to run the program in mixed mode, but want to connect with some i2p-nodes (for tests or other purposes) you have to add an i2p-node manually with "-addnode=<node>" option. Also you may publish your i2p-address or PM me and others can connect to your client. In such case you will see his connections as incoming.
Of course, if your i2p-address changes you should publish the new address again. Obviously, it's inconveniently, so I suggest to use a static i2p-address in this case. Also if you use the '-tor'/'proxy' options (or appropriate settings in gui) you should use the '-listen' option if you want to accept incoming i2p-connections, because the '-tor'/'proxy' options disable the '-listen' option by default. |
|
|
|
|
29
|
Bitcoin / Development & Technical Discussion / Re: Bitcoin client with I2P patch
|
on: September 15, 2013, 08:40:04 AM
|
This update does not influence to connections. But last few days I has only 1-2 connections. I don't know what happened with other nodes, but my nodes are working fine. Try to rerun you client. If it doesn't help, try to manually add nodes by the 'addnode' command with the following addresses: bhqfvosghsfdbi3qubnk3ro6juklz5w7b6l3x6mibkxzzk3mob5a.b32.i2p
z5pg37axylu7wuncppbzvwxawb5mo3euxuwbyi2s2um7bhnl3caa.b32.i2p
ofa7kfuqewnxyqiadnsj6ibcwtj6ndcabwcfabljmuyol2pussaa.b32.i2p
mzvsw6bwae6ul33b5zege5xie2cevno6vgik6nrb6lw74cn3wmdq.b32.i2p
|
|
|
|
|
30
|
Local / Кодеры / Re: I2P & Bitcoin
|
on: September 13, 2013, 01:14:46 PM
|
|
Update 13.09.2013
Переход на 0.8.5
В версиях 0.8.4 и 0.8.5 были внесены важные исправления, поэтому обновитесь как можно быстрее
|
|
|
|
|
32
|
Bitcoin / Development & Technical Discussion / Re: Bitcoin client with I2P patch
|
on: August 22, 2013, 03:05:36 PM
|
Four nodes it is ok. Today I have only 4-5 nodes too. Of course the more peers the better, but 3-5 peers are enough to send/receive a transaction to the rest net with admissible speed. Judging by I2P stats your ports are still closed. If you open the ports you'll see smth like this: But if you can't open them it's nothing. Probably in this case your i2p-connection will be a little bit slower or less stable, but nothing serious. If your wallet is always running with a static i2p-address you can send your public i2p-address to me and I'll add it as seed-node in my code if you want. |
|
|
|
|
33
|
Bitcoin / Development & Technical Discussion / Re: Bitcoin client with I2P patch
|
on: August 19, 2013, 07:05:23 PM
|
For auto-starting the patched client try to delete the ~/.config/autostart/bitcoin.desktop file or open it in any text editor and fix a path to your client. If you will run the vanilla client after that it will rewrite this file again. I need output of bitcoind/bitcoin-qt to determine why you have only one connection. I have 4-6 peers for today in my wallet. Even if you connect to one node it should give addresses of other nodes to you. Oh, I see you have a few i2p-peers (Active: 14 / 113). Most probably your ports are closed. In this case I2P works very slow and unstable. You can see the port number at http://127.0.0.1:7657/confignet. Try to open the i2p-port in your firewall or router. |
|
|
|
|
36
|
Bitcoin / Development & Technical Discussion / Re: Bitcoin client with I2P patch
|
on: August 18, 2013, 03:57:55 PM
|
ok, i2p is working. Run the patched bitcoin-qt/bitcoind in console and post output (to this thread or to PM). I try running bitcoind from the command line but it says itys not installed even tho I've excuted bitcoind from your download and bitcoin-qt can connect to the normal network.
Seems like you trying to run default bitcoind. Try to run the patched bitcoind explicitly, smth like /path/to/the/patched/client/bitcond. It should work. If you run the patched client in mixed mode, most probably it will use only ip-addresses for outgoing connections. That's why. The bitcoin-client has a pool of known addresses. Selecting of address is a pseudorandom process. At now there are hundreds (at first start) and thousands (after syncing with other clients) known ip-addresses and only several I2P-addresses in the pool. By default only 8 outgoing connections are allowed. So probability of selecting an i2p-address is less than 1%. If you want to run the program in mixed mode, but want to connect with some i2p-nodes (for tests or other purposes) you have to add an i2p-node manually with "-addnode=<node>" option. Also you may publish your i2p-address or PM me and others can connect to your client. In such case you will see his connections as incoming. The client can accept incoming connections even it already has maximum of outgoing connections. If you have a permanent i2p-address and your wallet is running most time I can add your i2p-address to a source code as seed-node in the next releases if you want. |
|
|
|
|
37
|
Bitcoin / Development & Technical Discussion / Re: Bitcoin client with I2P patch
|
on: August 17, 2013, 09:01:51 PM
|
|
First of all, check that i2p is working, try to open any i2p-site. Then check that SAM is enabled and running. If it is ok, check the log at ~/.bitcoin/debug.log and check the output of bitcoind/bitcoin-qt. Which mode (i2p-only or mixed) do you use? Do you use any command-line options?
|
|
|
|
|
38
|
Local / Майнеры / Re: Avalon ASIC (китай)
|
on: August 05, 2013, 11:21:22 AM
|
Не смотря на все надежды, я около 90 минут назад получил трек-номер. Осталось до конца месяца подождать, и если устройство не заблудится, попадет для экспериментов в мои лапы. Надо успеть собрать всю мыслимую информацию по экстремальному разгону, этого кошмара инвестора.
Остается один вопрос, где можно купить вуду-куклы Йифу за биткоины? Хорошо-бы несколько комплектов с иголочками, газовыми горелками, концентрированными кислотами...
alpet, ты же вроде рефанд делал? |
|
|
|
|
39
|
Bitcoin / Development & Technical Discussion / Re: Bitcoin client with I2P patch
|
on: July 23, 2013, 01:31:42 PM
|
Any chance of a binary for OSX being released in the future?
I'm willing to beta test this if you need someone.
Sorry, but it's very unlikely. I don't have any Apple devices. But you can try to build a binary from the source files. My patch doesn't add any additional dependencies, so if you can build an original client, you can build a patched client. |
|
|
|
|
Show Posts
