 Show Posts
|
|
Pages: « 1 2 3 4 [5] 6 »
|
Maybe Mintpal hired Mark Karpelès to help handle "early withdrawal" requests.
Probably hired his cat... |
|
|
|
I'd vote for Cam's left nut as well... but either Newbie acounts can't vote or i'm too stupid to find the place your vote checkbox. |
|
|
|
Okay - somebody hold my fucking hand.....
Looking for a P2P to hook-up to
What's the best one around?
I asked this last night but I'm not seeing any answers....... anybody?
http://p2pools.org/drkpick the one with the lowest latency to you. |
|
|
|
Well, my wallet is mining on my desktop again to support the network, LOL. How many cores does it default to? 'cause I just started it with setgenerate true  All of them. Please be careful and monitor the temperature of your PC. I don't recommend mining with your ordinary work pc. You could damage it if it doesn't have proper ventilation. (better run only 1 core at all times) I just tested on my work pc (4 core AMD (Vishera) with 3.6 GH) it shows a hashrate of about 40 kh/s and needs about 95 Watt if I am not mistaken. So, we have to find out the total net hashrate of the darkcoin network, to calculate how much help those 40 kh/s would be. Or if I only used 1 core, the 10 kh/s. What is the total net hashrate at the moment? Network Hashrate: 91.98 GH/s |
|
|
|
Here you go Tante... 4 simple rules.
Treat every weapon as if it were loaded
Never point your weapon at anything you don't intend to shoot
keep your finger straight and off the trigger until you are ready to fire
keep your weapon on safe until you intend to fire
Thank you, I married a Texan, nuff said, LOL. All my kids, myself and my mother have been trained LOL. Good girl |
|
|
|
Can I bring my guns?
As long as you let me shoot one!  Please, gun safety lessons FIRST! non-gun owners get really weird with guns..... LOL So how many days has Mintpal been down? 3? I trade so little, so I went where the fees were smallest, and had some ready to sell, but then suddenly MP went down. I saw no warning, but I'm not always around 24 hours are really stretching long.... Here you go Tante... 4 simple rules. Treat every weapon as if it were loaded Never point your weapon at anything you don't intend to shoot keep your finger straight and off the trigger until you are ready to fire keep your weapon on safe until you intend to fire |
|
|
|
Am I being to worrysome to think that if and when instant tx happen and drk becomes massively adopted being its annoymous would their be any backlash from govts claiming it could be used to fund terrorism? That scares me a bit because once that stigma gets attached I'm afraid it will be impossible to ever shake.
I think the Govts should be more concerned with people figuring out that they are more likely to get hit by a bus crossing the street than beheaded by a terrorist... then where will the justification for their budget be? |
|
|
|
Make it happen down at the protocol level, or use multisig addresses that require users to countersign any movement of funds? Got to be a solution... [/quote] I'd love it if I could securely "buy in" on shares of a Masternode but i think that should be a separate endeavor rather than trying to tie it directly to mining. My initial gut reaction is you will open up an attack vector if you try to combine the two functions. That isn't to say you can't get a solution for both things but don't tie unrelated stuff together at the hip or you will end up with unintended consequences. |
|
|
|
Nodes can deduct a fee though - that 'fee' could be pointed to a MN share address and proceed from there? The software already tracks submitted user work, so you could keep track of who'e owed what percentage of MN payouts. Having said that, why not just have the MN network as one big old regular (but distributed) pool? Need to think some more about it. after thinking another two minutes it would be easy to make sure that >51% didn't get at any one node... just have the masternodes track their load and if any one node started receiving too much hash it could start randomly dropping packets to reduce the hashrate being thrown at it... Think WRED as it realates to QoS.
Yeah, it had already occurred to me that as and when MNs have the ability to really enforce MN payments, they will almost by default also have the ability to also enforce hash distribution, in that they could monitor pool hash and orphan blocks from any pool approaching or at 50%. [/quote] With this you are opening the door to bad actors... the node fee gets paid to the node operator... now we are back to trusting whoever owns the node to actually pay out what is owed. Which is why I moved off the regular pools and set up my own p2pool node. Its like solo mining without the huge variance and I don't have to trust some unknown person to not shut the pool down without actually paying out and then claiming that they got hacked. |
|
|
|
|
after thinking another two minutes it would be easy to make sure that >51% didn't get at any one node... just have the masternodes track their load and if any one node started receiving too much hash it could start randomly dropping packets to reduce the hashrate being thrown at it... Think WRED as it realates to QoS.
|
|
|
|
I'm not sure wtf crawled up Crouton's posterior though... he was about 2 posts away from getting put next to Sh*tJaywhatevertheFhisnameis as the second person on my ignore list for being a damn troll. You "Sir" need to check yourself.
**edit** in addition you might want to look up how P2Pool actually pays out so you don't sound like a complete idiot when talking about using the Masternodes as P2Pool nodes that somehow hold the coins you mine for some kind of stake in the Masternode. I actually happen to run my own node because i got bored one afternoon... 68-112-53-84.static.hlrg.nc.charter.com
Don't worry, I check myself whenever there's a reflective surface nearby. Current status: magnificent.  Not sure what your other comment was about though. Are you a python coder? I ask because I've looked at dstorm's p2pool code and as far as I can see, modifying it to send selected payouts to a node address (and keep a record of that for pro-rata MN reward payouts) that could be used as a feeder for a 1000DRK MN vin wouldn't need that much of a rewrite. And you'd need a bit of new front end stuff to allow users to specify how much they'd like to leave on the node etc. It's not my day job though, maybe there's some shopstopper I'm not seeing. Seriously, does the prospect of a simple and automatic way of allowing miners who want to to have a stake in the Masternode system seem like such a terrible idea? Seems like plenty of people have been asking for just such a thing... The way it currently works is you mine to your wallet address. The node never receives the coins when a block is found. You are paid straight from the blockchain. By introducing a third party (ie the masternode) as a middle man in the payout scheme you are no longer a peer to peer network by definition. By doing it the way you suggest you are just moving the current structure of regular pools on top of the masternodes which kind of defeats the purpose in my mind. Now that being said, I personally think that making masternodes double as true P2Pool nodes would be a brilliant way of securing the blockchain from 51% attacks as long as you can somehow block the regular pools from connecting to a single node. **edit** nope not a programer... but I've been in Networking for over 20 years so I have some background knowledge. |
|
|
|
As usual Camosoul pretty much nails everything right on the head.
If it were important enough, and it's not, I think it would be interesting to see a poll of how many people agree with you... It's dangerous to be right when the majority of nationalist free stuff voters are wrong... when you're surrounded by hammers... don't be a nail |
|
|
|
I read this thread constantly but rarely post and I've always liked how friendly the amotsphere is with fellow DRK supporters, but what the hell is going on in here today. I have never seen such dick measuring ego spewing garbage besides the ocassional troll. We need masternodes, we need POW miners that's what's has made drk great not one or the other. So the price is not where everyone wants it right now but I'm certain that it will go back up and beyond what we've seen. I think what's goin on in this thread right now is going to cause unintended harm to the coin because if the core supporters are in fighting it's going to scare away potential new supporters and isn't that what this is about? Getting greater outside adoption? I believe dark is the greatest crypto out there n part of that was the because of the community it had.
I'm with Cryptosis on this one... Part of my daily ritual since I bought in to this damn coin at .0225 is keeping up to date on this thread even though I don't usually have much to post. As usual Camosoul pretty much nails everything right on the head. I'm not sure wtf crawled up Crouton's posterior though... he was about 2 posts away from getting put next to Sh*tJaywhatevertheFhisnameis as the second person on my ignore list for being a damn troll. You "Sir" need to check yourself. **edit** in addition you might want to look up how P2Pool actually pays out so you don't sound like a complete idiot when talking about using the Masternodes as P2Pool nodes that somehow hold the coins you mine for some kind of stake in the Masternode. I actually happen to run my own node because i got bored one afternoon... 68-112-53-84.static.hlrg.nc.charter.com |
|
|
|
|
I'd be a lot less afraid of it if I just knew what it was called. Let's call it Steve. Steve? That's a pretty name...
You all sound like a bunch of 2nd Lieutenants sitting around mentally masturbating over what to call something... although I agree with Camo.
My 2 duffs
|
|
|
|
|
DRKTor... When I saw the first masternode diagram that showed how they mixed coins I thought to myself this is just like Tor. Didn't take a large jump to reach the conclusion that this was coming like 3 weeks ago. Nice to see it spelled out though. BZ devs.
|
|
|
|
|
Don't let the trolls get to you canuck... in Norway they are considered good luck.
|
|
|
|
I see his problem... its windows! sorry Camo... couldn't resist If that looks like windows to you, then you might be a windows user... ;-) Linux64 hehe... actually both... windows 8.1 host... vmware workstation with a couple ubuntu hosts... one for the wallet I use and one for the p2pool node / darkcoind. Got to have windows for the occasional blow stuff up in arma III fix or i'd lose it completely |
|
|
|
I see his problem... its windows! sorry Camo... couldn't resist |
|
|
|
Hi guys, Trying to setup a darkcoin p2pool node following the instructions here: https://bitbucket.org/dstorm/p2pool-drkWhen I execute the command "python setup.py install" from within the /xcoin-hash folder I get "error: [Errno 13] Permission denied: '/usr/local/lib/python2.7/dist-packages/xcoin_hash.so'" - tried running the command with sudo but get the same result. I run a few p2pool nodes for various coins, so I know it's not a dependency issue..... Any ideas what the problem is? Peace  I'm sure you'll get better help in IRC #Darkcoin... dunno, anyone around here to lend a hand? Yeah, I just posted there too, thanks for the suggestion. If anyone here could give a suggestion I'd be grateful....... There's still 4 page for me to read and maybe this has been answered but.... My understanding would be....... When ever a permission is denied, use: sudo Didn't see an answer to your question after wading through all the FUD in the thread so... I set up my p2pool node last weekend using http://blog.crahl.ca/p2pool-setup/ as a guide. worked like a champ for me on ubuntu 14.04. |
|
|
|
What's causing some coins to get stuck as unconfirmed during the anonymisation process? I currently have 20 unconfirmed, and they have been like that from a day. And if I go to transactions there are 2 transactions that don't seem to have reached the network. Will this sort itself out or is there something I should do?
The TXes not on the blockchain should be deleted. They may be what's holding it up. It's due to a timing issue that has been fixed in latest release. Essentially, Evan made DS+ run so fast that it was moving faster than the users. I had over 7000DRK "stuck" due tot he same problem. It's no big deal. But, if it exists in your wallet already, you have to remove them. The updated wallet will respect them, it just won't make the mistake of creating more. It's up to you to determine what needs removed. Evan's way of making sure it didn't "automagically" remove something it shouldn't, then you'd REALLY be pissed... How do I remove transactions? smh... The last posting from your IP was less than 360 seconds ago. Please try again later. go to the debug console and type in "erasetransaction <txid>" I believe you only want to do that on transactions that haven't hit the block chain yet 0/6 confirmations yada yada |
|
|
|
|
