vertcoind is running fine, and I was going to try running p2pool on VTC to try out your mod, but am getting an error:
exceptions.ImportError: No module named vtc_scrypt
Any suggestions one what dependencies on Ubuntu 13 are needed for p2pool? I am using the donSchoe / p2pool-vtc fork from github.
:-)
Check the README file for instructions on installing the vertcoin_scrypt module.  |
|
|
|
Ok by installing everything form source I've got it built. Whew. Wish they provided packages for haskell for 12.04 LTS since it's still got a few years of support left in it. Once built though, how do you actually run it? This is all I've come up with. ubuntu@ip-10-143-203-223:~/code/proxypool$ ./dist/build/server/server
[2014-02-27 23:37:10][main][INFO] Starting server with config: proxypool.json
[2014-02-27 23:37:10][client][INFO] Listening on localhost:9555
[2014-02-27 23:37:10][db][INFO] Connecting to localhost
[2014-02-27 23:37:10][db][WARNING] IOException in DB: connect: does not exist (Connection refused)
[2014-02-27 23:37:10][db][WARNING] Sleeping for 5 seconds before reconnection
server: getAddrInfo: does not exist (Name or service not known)
README has all the build/config info but not what to do once actually built.  What are the redis* settings for? What sort of database do I need to configure? |
|
|
|
You could change networks.py to try and have a lower share difficulty but it'll go back up once more hash power joins the network. The way p2pool is designed, there is always going to be some level of hash power that is so small the variance is too high for people to stomach. For them it's probably better to use a proxypool like doge.st is designing. |
|
|
|
But if small mining rigs run their own node, it still seems impossible to get rewarded (my p2pool environment shows enough hashrate to at least find a block several times a day). If I understand it correctly you are forcing the node (not the pool) to give you a small share difficulty, but if you run your own node it will be using standard difficulties anyway?
roy7 you have my deepest respect for your efforts to make p2pool useable for small miners. However I still cannot follow how this can be achieved, I'm talking cpu-mining for scrypt coins. My current try is to setup a node on each cpu-machine and connect to their localhost using your hack /0.0001. Is this overkill?
The issue is that bigger miners are given higher share targets so they don't use up too much of the share chain themselves. p2pool is designed around the idea that each miner is running their own node. So a node = a miner. Thus, a node scales the difficulty for the workers connected to that node (all of your mining gear) to a higher level if you have a high combined speed. This causes an issue for a public node with lots of small miners that the target share difficulty is being set to the combined total speed, not each miner's speed. So 100 people at 5GH will each be given a target share difficulty for a 500 GH miner. The same difficulty a 500 GH miner would have on his own private node. If these miners ran their own private node with just 5GH of speed, they'd have lower targets. So that is what my patch did, lower the target share difficulty for an address based only on the addresses' speed, not the node's total combined speed. This is also why the patch does nothing for a miner running his own private node, you already have a target based on your personal speed. My patch changes the vardiff algorithm as above. If you set a target yourself with /DIFF, then the vardiff isn't used and my patch does nothing. /DIFF also overrides the dust prevention so you'll get the smallest shares you can no matter how little they pay. This can result in tx fees that cost more to spend the shares than they are worth. I don't think people should do that if they are mining long-term, but it's the easiest way to try and make "Why am I not getting paid" complaints go away. No matter what vardiff does or what /DIFF you set, you will never get a share difficulty target below the minimum share difficulty for the network. |
|
|
|
|
It has been a fun year but given the ever increasing difficulty of TRC, and the pool continuing to remain small, I'm thinking about switching the port to be a public p2pool node. That would drastically reduce the variance for anyone who does mine on it. Right now even when one or two of the 200GH miners join the pool, it can take a very long time to find blocks. Unfortunately I think the vast amount of TRC hash power still just mines with Coinotron.
Thoughts if any of the regular miners who mine when TRC is more profitable than BTC happen to follow this thread?
|
|
|
|
Just get 13.10, I think Haskell platform missed the Ubuntu 12 release and it causes major pain.
apt-get install haskell-platform
cabal update
cabal install cabal-install # gets 1.18v
Add this line to the bottom of .profile
PATH="$HOME/.cabal/bin:$PATH"
Check cabal --version
Done.
Can I install the 13.10 package onto 12.04? Or do you mean upgrading from Ubuntu 12.04 LTS to 13.10? I've thought about that. Just makes me nervous. I let the build run all night but there's an error in the html file it can't get past. I change the build file to not build the docs, and have restarted the compile. Sadly it's back on stage 0 but I'm letting it run all day while I'm at work. I did try updating cabal before but didn't use "cabal install cabal-install". Maybe that will upgrade me. I wasn't able to directly upgrade base to 4.6.0.1 from within cabal that I could tell, and my base version was to old for your dependencies it seemed. Edit: Perhaps I'm not meant to be a part of this project, lol. [73 of 73] Compiling Main ( Main.hs, dist/build/cabal/cabal-tmp/Main.o )
Linking dist/build/cabal/cabal ...
Installing executable(s) in /home/ubuntu/.cabal/bin
ubuntu@ip-10-143-203-223:~/code/proxypool$ cabal --version
cabal-install version 0.14.0
using version 1.14.0 of the Cabal library
But wait! ~/.cabal/bin you say? ubuntu@ip-10-143-203-223:~/code/proxypool$ ~/.cabal/bin/cabal --version
cabal-install version 1.18.0.2
using version 1.18.1.2 of the Cabal library
But alas, even with cabal 1.18 I'm still stuck with base-4.5.0.0 which fails the base ==4.6.* check. |
|
|
|
My patch has no effect on running your own node. It's purpose is to let each miner on a public node get the share difficulty target they would get as if they were running their own node. To control your miner's difficulty target put /DIFF after your username you are using to connect to your node with. If you use a tiny one it'll make sure you always find the smaller shares possible (whatever the pool's minimum share difficulty is for that time). |
|
|
|
if I run my own p2pool node how do I change to ADDR/0.001? is there a switch in run_p2pool to achieve this? when i do run_p2pool -a <addr>/0.0001 it gives me a parse error Is it the username your miner uses to connect to a node. Instead of username = payment address, use ADDR+DIFF to control the pseudo share difficulty (for graphing or support really old asics) or use ADDR/DIFF to control your share target. You can also use both. For instance I mine Uno (a sha256 coin) with ADDR/64000+64 on my Antminer S1 (180GH). |
|
|
|
Won't they still need to find a payable share to get into the share chain?
Yes indeed. It just makes miner's share targets lower if they are on a public node. Still compiling haskell. At least stage 0 is done and into stage 1. About 3.5 hours so far. |
|
|
|
There doesn't seem to be a ubuntu package for the version of haskeel this needs but I'm trying. (base-4.6 was required but the normal packages install an older base). Edit: Ah ha. Ubuntu 12 is the problem, doesn't have packages for newer haskell. Time to compile from source, which takes a lifetime. |
|
|
|
I'm thinking of setting a P2Pool node up for around 2MH/s on Vertcoin. Can you still auto donate 1% to the dev's?
I don't think Forrest has a Vertcoin address but you can ask him. The address hard coded into the repo wouldn't work anyway. Maybe best to just do a manual donation now and then to his BTC address. |
|
|
|
The issue with this would be dust. If you have a 1% fee on your node then your node hash rate would have to be such that 1% of that wouldn't create dust on every block.
One thing to keep in mind though is that you'd be getting 1% of every share your node found. So if there are lots of shares in the share chain, you'd add up 1% of each of them and the pool receives that one single payment like any other miner in the payouts list. If the fee to the node operator is so small it's just useless dust he can't spend anyway, then he should either get more miners to use his node or drop the fee to 0. |
|
|
|
i am not normally one to speak positively of regulation, but this is one of several reasons that money transmitters and MSBs require licenses in the US: too many unscrupulous people have started up such businesses, then there is a "theft" of funds and all the customers are missing money.
I'm not either and because of the regulations I would never set up my own exchange of any sort. However, I do benefit from it by only using coinbase for my transactions since they do follow the US regulations and are a US company. I feel much more comfortable doing bank transfers to coinbase for BTC purchases that I would with other random exchanges (be it BTC-E, Cryptsy, Coinex, or someone else). Also getting cash back from them by selling BTC is easy and direct to my bank account. |
|
|
|
I just immediately reconnect when that happens. Have not had to use + anything but then again I have 5 Mh/s so it may be adjusting higher faster for me so when I reconnect the pseudo diff is already primed to be higher.
The danger is like the guy who replied here https://github.com/forrestv/p2pool/issues/183You probably recognize him from irc. If he falls over to a backup pool then much later back to his own node, it might do nothing but HWs all day until he can manually fix it because of the 0 diff issue. |
|
|
|
Anyone else stuck at the landing page? It forces you to a FAQ but when you agree to proceed it says page not found. Way to go Josh.... Lock a bunch of bitcoiners out from their money who have just been traumatized by being locked out from their money. Stay classy.
Did you email and let him know? I reported a database problem yesterday and he fixed it very quickly. |
|
|
|
Also this statement: any BTC I own personally were on MtGox...notice the way he sayd "were" on Mt. Gox. Meaning...Gox is no longer there, and the coins are no longer in his control?
Yes. He's saying his coins are in the same boat as everyone else's. [12:02] <JonWickedFire> How much did you lose yourself? [12:04] <MagicalTux> Well, technically speaking it's not "lost" just yet, just temporarily unavailable Of course, for any verified users that used the malleability issue to steal coins, the authorities should be able to go after them for theft. Unfortunately MtGox didn't used to require ID verification for purely BTC withdrawals. |
|
|
|
And who brings a cat to his office, he thinks he's Blofeld?  He was at home, not at an office, btw. |
|
|
|
|
Show Posts
