Still, there's no way anons can prevail over the government agencies such as NSA. It is so clear I don't get how people fail to see it.
I fail to see it. Perhaps you can make the case for me. *edit* also notice that there are several different questions here that are sometimes treated as one. 1) can one create a crypto where if the nsa spends 10 million dollars trying to figure out the transaction history of 1 single person they still will not be able to uncover that information. 2) can one create a crypto where it is prohibitively expensive for the nsa to uncover the transaction history of large groups of people. 3) every point on the sliding scale between these two extremes When you send XMR from your wallet to someone, is that transaction sent in plain text? When you connect to a mining pool, or even solo mining, is that communication ALL encrypted? *sniff sniff* |
|
|
|
Yep, I am. I'll ignore the error for now, shouldn't be a problem.
I'm assigning each miner a worker ID, with payout set to poloniex. I can't see stats for each worker, this is the proper command to see all workers stats correct?
To view aggregated stats (and payments) enter: EXCHANGE_WALLET_ADDRESS.payment_id
I'm only seeing my total hashrate, no individual worker hashrates.
To view stats when mining with payment_id, enter: EXCHANGE_WALLET_ADDRESS.payment_id To view indivual stats (payments excluded) when mining with worker_id + payment_id, enter: EXCHANGE_WALLET_ADDRESS.payment_id.worker_id To view your payments enter: EXCHANGE_WALLET_ADDRESS.payment_id EXCHANGE_WALLET_ADDRESS.payment_id.worker_id Lets me see individual rigs properly EXCHANGE_WALLET_ADDRESS.payment_id Just shows me total hashrate for all rigs, without showing each rig's stats. Shouldn't it show details for all rigs listed individually? Or am I mistaken? That functionality (to display each and every rig details when no specific worker is chosen) is not present (yet) but that is a pretty decent suggestion.. |
|
|
|
Yep, I am. I'll ignore the error for now, shouldn't be a problem.
I'm assigning each miner a worker ID, with payout set to poloniex. I can't see stats for each worker, this is the proper command to see all workers stats correct?
To view aggregated stats (and payments) enter: EXCHANGE_WALLET_ADDRESS.payment_id
I'm only seeing my total hashrate, no individual worker hashrates.
To view stats when mining with payment_id, enter: EXCHANGE_WALLET_ADDRESS.payment_id To view indivual stats (payments excluded) when mining with worker_id + payment_id, enter: EXCHANGE_WALLET_ADDRESS.payment_id.worker_id To view your payments enter: EXCHANGE_WALLET_ADDRESS.payment_id |
|
|
|
They seem to happen every 30 minutes or so for some reason. I have never seen duplicate shares on the other XMR pools I've used before. Guess it's nothing to really worry about either way.
Just have to make sure you're connecting to the closest mirror available (you can verify that by pinging each ip) |
|
|
|
Ok, I switched 2 rigs over to test. Is this normal behavior? 09/14/14-11:26:30 - SHARE FOUND (target 15000) - (GPU 3)
09/14/14-11:26:31 - SHARE FOUND (target 15000) - (GPU 1)
DevFee: 09/14/14-11:26:41 - SHARE FOUND (target 7500) - (GPU 0)
Error in server response
: {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"Duplicateshare"}}
Stratum - connecting to 'usa.monero.rs' <198.27.78.226> port 4444
Stratum - Connected
DevFee: Pool Diff 7500
09/14/14-11:26:42 - SHARE FOUND (target 15000) - (GPU 1)
09/14/14-11:26:52 - SHARE FOUND (target 15000) - (GPU 2)
09/14/14-11:26:52 - SHARE FOUND (target 15000) - (GPU 2)
Duplicate shares (stale share) is quite rare but it happens with every just about every mining pool at some point or another. |
|
|
|
We need more hash to 'kill' the variance, lets push it above 500KH today!
Need more features to bring people across..  How about: * Show average hash rate per user (pool / people = avg) * Show your average hash rate (1h/6h/12h/24h any of those, the more the better) * Show your average hash rate per Worker |
|
|
|
|
Isn't what makes bit/altcoins so valuable is that there is a finite supply of them? Having an Infinite coin supply means that that miners will be the one who suffer if the coin ever had to be pick up in trend.. In the future, the only people that would be able to mine it would be those that have a large amount of mining resources or mine with a large pool.
|
|
|
|
jl777 seems to be a really smart theif. Stealing from his investor of all assets he hold.
I am glad I am on the "good" side. The only thing rpietila is pumping is Monero, nothing else from what I can tell by any of his post. He is not advocating any other altcoin, while this jl777 have 50 different pumps going on probably where he hold everything. It's like he built 50 castles of promises, while rpietila have 1 castle promoting financial privacy.
How easy it is to make money once you have a reputation. jl777 is going to take over the world (atleast he thinks) by having people buy all his crap assets. Compare BTCD, is it even working? Is the tech good? Are many people actively working on it? By my study, by going to check out the IRC channels I see nothing happening in #bitcoindark, around 21 people here, while there is 100+ in #monero-dev including core bitcoin developers.
The reason why Bitcoin Core developers is in #monero-dev and not #bitcoindark or #darkcoin? You should be able to read between my lines, but I will tell you right here, it is probably because the anonymity tech provided is really good.
I love the smell of Troll in the morning. |
|
|
|
The truth is out:
Troll harder. |
|
|
|
Tried pool for about 6 hours and it seemed I got less hash rate on your pool than minergate currently. I average about 23 - 24 KH/s on minergate and I'm getting about 21 KH/s on your pool. Using claymores miner on your pool, it says I'm connected to three pools and not two anymore like it does when I'm on other pools, so I how do I verify the actual 5% increase with your pool and claymore's miner, in hashrate increase or just an increase in overall coins.
Make sure you're using the pool that is closest to you. (You can ping the servers to see which has the best response time) |
|
|
|
Does this pool work with GPU mining?
Yea it does |
|
|
|
I must say, its working like a charm. On minergate using a few of my servers I was doing around 12 000 h/s.. using Monero.rs I'm doing around 16 000 h/s.. That is a considerable jump!
That's because Minergate is a scam. Feel free to provide proof. |
|
|
|
|
Please could you guys release a statically built version of the minergate-cli binary or even the source so I can build it myself?
There are a number of CentOS (and other Linux distro) machines I would like to run it on.
|
|
|
|
How transparent will MEW be to non-members? Will meeting minutes/logs and such be published for public viewing?
I think/hope MEW aims for maximum impact and usefulness. So if there is anything that could be useful for the general public, it will be published. The meetings are not the primary idea though. The focus is on doing things. MEW needs its own dedicated site. A cat logo is needed.. |
|
|
|
When i mine DSH, diff is 70.000.000, so very hard to mine DSH. And now, diff is too slow and with this DSH's price I wasted my energy.
Have you tried a different pool? Extreme sho diff as 13816535. I know it is 2% but sometimes in life it is worth paying a little extra!  http://dsh.extremepool.org/Diff is changing in real time and it is the same for every pool. Remember to test what your hash rate is like on every pool as there will be differences. |
|
|
|
|
I must say, its working like a charm. On minergate using a few of my servers I was doing around 12 000 h/s.. using Monero.rs I'm doing around 16 000 h/s.. That is a considerable jump!
|
|
|
|
We could have a site that queries all in the list for your address on the api port. Edit: I've set up a SRV record as an example. _bb._tcp.us.cncoin.farm that has all the pools listed on the first page that have dns names for connecting. That is one issue with this approach. All pools would have to have a name and not an IP for a SRV record to work. You can see what it returns with dig SRV _bb._tcp.us.cncoin.farm in linux, or nslookup -type=all _bb._tcp.us.cncoin.farm in windows. example output: ;; ANSWER SECTION:
_bb._tcp.us.cncoin.farm. 7199 IN SRV 10 0 11007 bbr.poolto.be.
_bb._tcp.us.cncoin.farm. 7199 IN SRV 0 0 7777 bbr.cncoin.farm.
_bb._tcp.us.cncoin.farm. 7199 IN SRV 0 0 1111 mine.bbr.unipool.pro.
_bb._tcp.us.cncoin.farm. 7199 IN SRV 0 0 7777 boolberry.extremepool.org. Notice it gives a port. It has a priority that I have set the non-us pool to a higher number to give it less priority. Could do the opposite with a _bb._tcp.non-us or _bb._tcp.eu or whatever, even separate lists for cpu/gpu ports. Obviously, it should be managed by core boolberry team or at least not a pool operator, and then miner would have to use something like libsrv (first google hit I saw) to query this record. We could even have a complimentary SRV record to determine API port of these servers I guess. What do you think? Reference I used for SRV records here: http://www.zytrax.com/books/dns/ch8/srv.htmlQuite an elegant solution actually. No other coin offers this type of integration either. Allowing a core boolberry team member to operate it means complaints about scams, faulty pooling payouts etc can easily be addressed and failure to fix a problem or comply will mean the majority of every day people will not be served automagically from the boolberry master pool. |
|
|
|
so is this dead now?
Ye its dead.. |
|
|
|
Nice, looks good. Sounds like I should change some diffs, then, too .  Network Hash Rate: 7.29 GH/sec Block Found: 2 minutes ago Our Pool Hash Rate: 3.51 GH/sec Block Found: 2 minutes ago Right now BBR is getting itself into a bad situation for multiple reasons.. Besides the 51% attack, a DDOS attack @ http://cncoin.farm/ and mining BBR becomes *extremely* profitable for an attacker. I was wondering what I can do about that. Probably need miners to fail-over at least. If pools had standard ports, I was wondering if a round-robin dns with all of them listed would work out ok. Otherwise I guess I can set a really high fee to get people to switch when it's so high, but I'd sure look greedy doing that with so much of the network. Some type of round robin would actually work out really well. Then all pool owners can apply to be apart of the pool. There are a lot of reasons this is a good way of doing it. The down side to doing it would be how would a miner see his hashrate? |
|
|
|
Coming soon - trollbox. No other pool lets miners interact and share mining tips and tricks in real time!
$ minerd-xmr -a cryptonight -p 86676108fe902b8c76a0d9663369d0703f0c0e3ec21d1c83a669dccab60f7811 -u 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB [2014-09-11 13:57:11] Using JSON-RPC 2.0 [2014-09-11 13:57:11] Starting Logrotation [2014-09-11 13:57:11] 7 miner threads started, using 'cryptonight' algorithm. [2014-09-11 13:57:12] Pool set diff to 10000 [2014-09-11 13:57:12] Stratum detected new block Works fine.. But: $ minerd-xmr -a cryptonight -o stratum+tcp://eu.monero.rs:4444 -p 86676108fe902b8c76a0d9663369d0703f0c0e3ec21d1c83a669dccab60f7811 -u 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB Segmentation fault (core dumped) You might want to fix that first.. You cant specify -o stratum+tcp://eu.monero.rs:4444 on our private miner, ips are hardcoded. Do not use 7 threads, you should get better results with 4 or 5 on a 8core server. Do you have pre-compiled binaries that use port 4444? |
|
|
|
|
Show Posts
