|
You should play around with live-build. You could make an xubuntu livecd with bitcoind and p2pool thats installs in just a few clicks. You could even include the blockchain to rapidly speed up deployment. If people don't want to trust your copy of the blockchain (not sure why, but I'm sure someone can figure out some obscure attack), they could just delete it and start fresh. You could even have a first run script that does this and sets up some other configuration.
If LinuxCoin would just release the source, it probably wouldn't be to hard to tweak for just this purpose, although xubuntu should work fine as a base, too.
EDIT: actually, why even install a GUI? Neither p2pool not bitcoind need it. p2pool also seems to have problems with bitcoin-qt.
|
|
|
|
|
I'm not sure how you could handle payouts on the merged mine chain. Some sort of monitoring of the workers would be needed to do this I think.
I guess wou could trade the merged coins for BTC and then donate that to all the p2pool miners, but that doesn't reward just the people on your node.
|
|
|
|
I have 7 rigs and will soon have 9. I can easily set up a main rig as a control center, but honestly i am struggling just to run my set up stable for more than 4-5 days without restarts or constant reloads of linuxcoin. The damn thing is f'in killing me right now.
I had neck surgery which has slowed me down, but finally I am recovered enough to start working on this again. I just feel like the whole miner thing is such a clusterfuck unless you have pre-existing knowledge of linux.
i have plenty of hardware experience as an overclocker and system builder. I was just too naive about what it was going to take to run everything through linux.
I believe in the purpose of bitcoin and didn't get into it to make a quick buck, but I also don't want to lose my ass and it feels like that is the way things are going at this point.
If people want true adoption, they need to create a linux based OS that is stable and doesn't require one to be an expert on linux programming and coding.
Bitcoin is NOTHING without miners. A 51% attack will happen soon enough if the network is not strengthened as there is enough money involved in the current amount of bitcoin to make this possibility worthwhile. Nevermind how easily the speculators manipulate the market like vultures.
I love the project and concept, but I believe the direction is not properly managed it makes logical sense to me that the miners need to become strong first so the network is safe. There is too much focus on adoption and not enough on protecting the network.
The focus should be on making it easy for people to add hashing power to the network without these convoluted programming nightmare schemes.
Just make a simple, stable fucking distro with a simple mining set-up and stop with the complicated bullshit. This will add a horde of new miners and then we can all promote the use of bitcoin, but as someone studying to get an MBA and a business owner, I wouldn't touch bitcoin with a ten foot pole right now as it is too vulnerable to scammers, botnets and speculating douchebags to consider accepting it as a legitimate currency.
Okay, sorry, rant over. I just know many new miners feel the same pain I do.
Maybe look at BAMT. I've been running linuxcoin without problems since June, but you may have better luck with BAMT. I'm still looking forward for the linux coin source |
|
|
|
Guys,
I would like to setup a Public P2Pool for anyone that doesn't have knowledge / time to setup its own P2Pool node...
How can I do it?! I mean, how people can use my P2Pool node and receive the payment on his own Bitcoin Address, not giving hashpower to me, of course...
Also, I would like to give people the possibility of merged mining too...
Thanks!
Thiago
honestly a better option might be to setup a p2pool vm service, where people pay .05 btc a month to mine, and you set them up with a p2pool ubuntu vm or something, all configured.. its not like p2pool requires any guts to run right? You read my mind. I can provide this service... But 0.05 BTC a month isn't enough... Maybe I can setup a little fee at P2Pool node that I manage. You think that there is a market for "P2Pool Private Hosting Service"?! Thanks! Thiago You are asking for things that are way too complicated. What you want already exists. Setup p2pool and add a "--fee 1" to take a 1% fee from anyone using your node. "$ ./run_p2pool.py --help" Others have already said that anyone can connect with their username being their payment address if you just open a port. I used to have my address (p2pool.stitthappens.com:8336) in my sig, but I just point to the wiki now. I also run p2pool2.stitthappens.com:8336 as my backup. You can even tell the fee by visiting http://<p2pool node>:<port>/fee Right now p2pool doesn't have much monitoring. It would be nice to have worker stats available in a few more formats. |
|
|
|
Are there better ways to stop p2pool?
I am pressing Ctrl+C to stop it right now.
I can turn two button into one for you, Click the X, There! one mouse click! (but seriously your question is rather vague, Do you wish to Pause p2pool? anyone can stop it easily) I think he was asking if there was some hotkey like "q" or something. Ctrl+C is what you want. |
|
|
|
|
I don't see the problem of maintaining a separate block chain. Not everyone who needs a wallet needs names and not everyone who needs names needs a wallet. We already have merged mining making multiple chains not too difficult.
|
|
|
|
Just a heads up for anyone using this app, the wallet.dat file in NOT encrypted in dropbox. It can be copied into another client to access your coins. This can be good, or bad. If you lose your phone, you can still access your coins. If someone else has access to your dropbox folder, they can copy your wallet.dat file into there own client and steal you coins.
That's really too bad. Especially since dropbox has messed up before... http://news.cnet.com/8301-31921_3-20072755-281/dropbox-confirms-security-glitch-no-password-required/ |
|
|
|
|
Just the display was floats, right? I hope they aren't being stored as floats in the backend
|
|
|
|
are you using the latest repos from http://gitorious.org/libbitcoin/ ? If so can you paste the error here (if different from above). It looks like you're using a libbitcoin from a few days ago but latest python bindings. Updating to the newest git head for libbitcoin seems to have fixed the last error. I don't know how I ended up with versions that didn't match considering I literally installed the system fresh last night and checked out the projects one after the other, but w/e. Weeee! (env)[user@silo onion-coin]$ python -i
Python 2.7.2+ (default, Oct 4 2011, 20:06:09)
[GCC 4.6.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import bitcoin
>>> dir(bitcoin)
['_1', '_2', '_3', '__builtins__', '__doc__', '__file__', '__name__', '__package__', '__path__', '_bitcoin', 'acceptor', 'address', 'address_to_short_hash', 'bdb_blockchain', 'bind', 'block', 'block_info', 'block_locator', 'block_locator_indices', 'block_reward', 'block_status', 'block_value', 'block_work', 'blockchain', 'bytes_from_pretty', 'channel', 'coin_price', 'coinbase_maturity', 'coinbase_script', 'data_chunk', 'decode_base58', 'elliptic_curve_key', 'encode_base58', 'error', 'error_code', 'exporter', 'generate_merkle_root', 'generate_ripemd_hash', 'generate_sha256_checksum', 'generate_sha256_hash', 'genesis_block', 'get_address', 'get_blocks', 'get_data', 'handshake', 'hash_block_header', 'hash_digest', 'hash_digest_from_pretty', 'hash_transaction', 'header', 'indices_list', 'input_point', 'inventory', 'inventory_list', 'inventory_type', 'inventory_vector', 'is_coinbase', 'magic_value', 'max_bits', 'max_money', 'max_target', 'network', 'network_address', 'network_address_list', 'null_hash', 'null_short_hash', 'opcode', 'opcode_to_string', 'operation', 'operation_stack', 'output_point', 'output_point_list', 'parse_script', 'payment_type', 'ping', 'previous_output_is_null', 'public_key_to_address', 'readjustment_interval', 'reward_interval', 'satoshi_exporter', 'save_script', 'script', 'setup_bdb_blockchain', 'short_hash', 'short_hash_from_pretty', 'short_hash_wrapper', 'sighash', 'string_to_opcode', 'target_spacing', 'target_timespan', 'total_output_value', 'transaction', 'transaction_input', 'transaction_input_list', 'transaction_list', 'transaction_output', 'transaction_output_list', 'verack', 'version']
So I'm trying to use your tutorials, but they aren't working for me. I'm not running bitcoind locally, so I think that might be why. Both tutorial.py and first500.py give this: $ python tutorial.py
s: version (112 bytes)
Bad header received.
For tutorial.py, I changed self.net.connect to my system running bitcoind and also I tried changing vers.address_you.ip. For first500.py, I changed hs.connect to my system, but it also failed. I am trying to build a lightweight tool for querying nodes to get their version. Right now, one of my systems has all of the tor hidden services added as nodes, but many of those services are offline and it takes forever trying to connect to all of them. I was hoping to use PyTorCtl and libbitcoin to map all of the addresses and then return versions for all of the nodes that are up. I could then drop this list of nodes that I know to be online and running current versions into my bitcoin.conf. From there it wouldn't be too much work to make it into a bot that updates the wiki page. It seems to connect, but the handshake is failing. |
|
|
|
My concern is... if someone hacks "deterministic key generation" algorithm... then every electra user is in danger, right?
The generation algorithm isn't what needs to be hacked. The seed private key would have to be hacked. This doesn't even really make sense if you know how public/private keys work. If private keys could be discovered in some way then all of bitcoin (and banks and more) are at risk, not just electrum users. |
|
|
|
I would stay away from the packages for the time being. Once I make a 1.0 release this month then I will update them. If anyone manages to get it to build, then build instructions would be much appreciated. I wrote these: https://bitcoinconsultancy.com/wiki/Build_libbitcoinI installed from the package first, and when that didn't work I used the guide at bitcoinconsultancy. While that works, I still can't get the python bindings built. I'm flying blind though since you don't have any docs for the python module. |
|
|
|
I will happily donate 5 BTC right off the bat to drggn or kjj or whomever updates this and gets it solid. includes the new and best driver sdk combos, maybe one version 5xxx series and one for 6xxx series?
also include p2pool, etc.
Take out all the browsing stuff as well, we only want to mine! just make it a miner only distro!
While having p2pool built in might seem nice, but most linuxcoin setups are running off USB drives. The blockchain is going to kill that poor thing. Assuming you have access to another system (or two) with a HD, it is way better to setup p2pool on there. If you just have the one machine or mine on your gaming rig or something, I guess that probably won't work for you though. |
|
|
|
Add these 2 lines to the end of your /etc/apt/sources.list deb http://ppa.launchpad.net/zgenjix/libbitcoin/ubuntu oneiric main
deb-src http://ppa.launchpad.net/zgenjix/libbitcoin/ubuntu oneiric main I think this should be " http://ppa.launchpad.net/genjix" without a "z" I also added it to "/etc/apt/sources.list.d/libbitcoin.list" instead of "/etc/apt/sources.list" Now lets see if I can get the python bindings built   [user@silo python-bitcoin]$ make
mkdir -p bitcoin
g++ -fPIC -Wall -ansi `pkg-config --cflags libbitcoin` -I/usr/include/python2.7 -c main.cpp -o main.o
In file included from /home/user/usr/include/bitcoin/exporter.hpp:7:0,
from /home/user/usr/include/bitcoin/network/channel.hpp:17,
from /home/user/usr/include/bitcoin/bitcoin.hpp:8,
from main.cpp:4:
/home/user/usr/include/bitcoin/constants.hpp:37:75: warning: missing braces around initializer for ‘std::array<unsigned char, 32ul>::value_type [32] {aka unsigned char [32]}’ [-Wmissing-braces]
/home/user/usr/include/bitcoin/constants.hpp:39:62: warning: missing braces around initializer for ‘std::array<unsigned char, 20ul>::value_type [20] {aka unsigned char [20]}’ [-Wmissing-braces]
main.cpp: In member function ‘void handshake_wrapper::start(boost::python::api::object)’:
main.cpp:288:61: error: no matching function for call to ‘libbitcoin::handshake::start(pyfunction<const std::error_code&>)’
main.cpp:288:61: note: candidate is:
/home/user/usr/include/bitcoin/network/handshake.hpp:31:10: note: void libbitcoin::handshake::start(libbitcoin::channel_ptr, libbitcoin::handshake::handshake_handler)
/home/user/usr/include/bitcoin/network/handshake.hpp:31:10: note: candidate expects 2 arguments, 1 provided
main.cpp: In member function ‘void handshake_wrapper::ready(channel_wrapper, boost::python::api::object)’:
main.cpp:299:14: error: ‘class libbitcoin::handshake’ has no member named ‘ready’
/home/user/usr/include/boost/system/error_code.hpp: At global scope:
/home/user/usr/include/boost/system/error_code.hpp:214:35: warning: ‘boost::system::posix_category’ defined but not used [-Wunused-variable]
/home/user/usr/include/boost/system/error_code.hpp:215:35: warning: ‘boost::system::errno_ecat’ defined but not used [-Wunused-variable]
/home/user/usr/include/boost/system/error_code.hpp:216:35: warning: ‘boost::system::native_ecat’ defined but not used [-Wunused-variable]
/home/user/usr/include/boost/asio/error.hpp:244:45: warning: ‘boost::asio::error::system_category’ defined but not used [-Wunused-variable]
/home/user/usr/include/boost/asio/error.hpp:246:45: warning: ‘boost::asio::error::netdb_category’ defined but not used [-Wunused-variable]
/home/user/usr/include/boost/asio/error.hpp:248:45: warning: ‘boost::asio::error::addrinfo_category’ defined but not used [-Wunused-variable]
/home/user/usr/include/boost/asio/error.hpp:250:45: warning: ‘boost::asio::error::misc_category’ defined but not used [-Wunused-variable]
make: *** [default] Error 1
|
|
|
|
Yeah I noticed your requirements have higher requirements for libboost and g++. I needed to upgrade my ubuntu server anyways, so I'm building it on there now. Installing boost is sure taking a while. |
|
|
|
So I'm running debian 6.0.4 (squeeze) and trying to get this installed for a small project. I'm just going to install it on an ubuntu system instead, but figured I would post my error log anyway. http://pastie.org/private/3jnuenhclxaf4f90wpbyfw |
|
|
|
That assumes the same salt and passphrase were used to produce all your paper wallets. If it were one salt per page, or one salt per address, that wouldn't be the case. If each address had its own salt, and you knew that you needed to redeem salt+passphrase, then you could do that (for example) directly on MtGox (which allows redemptions of arbitrary strings as private keys, which it converts via sha256 to a 256-bit value).
I think I was probably using the terminology wrongly, mixing "keys" with "wallets", etc. the paper wallet (with no private keys) could also have a single salt string printed on it, where the salt and the memorized key are required to regenerate the private keys
That's the part that made me think a single salt plus the passphrase would give up all the private keys in the wallet in one fell swoop. But if the salt was long enough to not be brute-forceable, and each address in the wallet had its own salt, that could work nicely. If you have to have a unique salt for every address, why even bother being deterministic... That's not deterministic anymore. I was picturing the paper wallet page having a text box at the top for a secret key. You put that it and it encrypts all of the private keys with the same key. This should be quite simple to do. I would probably print one unencrypted page for a physical safe, then enter a key to encrypt all of the private keys and print that page out to keep in my desk at home. If I use one of my paper keys on a compromised computer, I don't want to lose all of them. Non-deterministic wallets should guarantee this. |
|
|
|
... Lots of Images ...
So that looks really clean, but I'm curious as to why you even bothered with cases? Seems like they just trap heat and get in the way when you want to do any maintenance. |
|
|
|
Actually how do I use the "--address" option with merged mining?
Do I use a "," to separate them?
Thanks!
You can't specify an address for the merged chain (yet). The merged mining still needs some work. The address is currently fetched automatically via the RPC Ok, so I have put the same wallet(s) on all my mining machines, hence they all use the same addresse(s). Is that an ok workaround? Thank you! Why don't you just point all your miners to one p2pool merged mining instance? I have 3 miners but only run one p2pool, bitcoind, and namecoind. DING DING DING. If you are worried about fault tolerance make a second machine be the backup p2pool. Then setup cgminer w/ 3 pools p2pool - main p2pool - backup traditional pool If the machine w/ your p2pool goes down, cgminer will point all miners to the backup p2pool and if it also goes down it will point everything at a traditional pool. Or even better p2pool - main p2pool - backup traditional pool 1 traditional pool 2 traditional pool tor hidden service 1 traditional pool tor hidden service 2 |
|
|
|
Not sure if you have a feature request list, but I'd put this:
-- Graphs
-- ways to explore historical information? (like, how long has that card been throttling?)
-- configurable notifications, and way to test them?
I was working on integrating cgminer with Nagios and Cacti. This would give all the historical information. I've been busy working on another project though, so I haven't done much with it recently. |
|
|
|
What do you think? Encryption-protected paper wallets, excellent! +1 |
|
|
|
|
Show Posts
