Search results

Yup totally understandable why it's off. Just looking forward to it's return as I'm sure I've made it clear.

HAHA No I host mine off my neighbors WiFi so it's free and again, i never said I personally was "loosing money" i said hosting fees may not make it worth it until there is some know expectancy. It seems entirely possible to go a whole moth without out a MN reward in this randomization style...

I wasn't "bitching" but i suppose any post where someone complains they are "loosing money" is consider to be bitching Yep agreed, I am merely trying to say that if there is no enforcement "investors" and people who may invest or think about investing more into these systems will not when...

I would not quite call it "round robin" with 20% non mn paid blocks plus the randomization my Masternode has dried up for over 3000 blocks now no payments while others report rewards everyday or multiple times in one day. I must say hosting fees may not make it worth running a mn if there is no...

There seems to be 3-5 public keys eachassigned to a single IP 37.157.250.20:9999Open (38m34s)0.11.0.13XcrkmzZLWN9YzjaaUrfCHdVCQiGVa96eM5[1][2]1,006.8538s58m10s Active (100%) 37.157.250.20:9999Open (38m34s)0.11.0.13XxLVtj1bpaZoma94WHCwdZshh5Zst76xjk[1][2]1,007.7018s58m10s Active (100%)...

Curious about the unique IP requirement for Masternodes. There seems to be a rise in non unique IP addresses today. DRK.MN reports 1964 actives + 0 inactives 1705 unique IPs how does this affect the network and is it supported to point multiple masternodes at the same IP address?

Catch is Enforcement is not active

Why not disable it at the interface not at the application? Are you running IPv6 for other things on the same system?

Mine some MazaCoin with it since it's going to the moon! Maza.CryptoADHD.com

Nice work with all the quick changes you guys are the best dev team. Hopefully we will make this the quickest update the network has seen. And when that does happen when does enforcement return?

what if the v11 MN owners were running some scripts on the MN that killed connections from the old protocol MNs? not sure if it's been helping but I've been killing any out of date peers from being connected to my updated MN and only allowing 70054 to connect to my node. I guess as cam was...

There are many factors to these questions here is my best shot at answering them. 1. There are guides it is not difficult. I run a masternode on test net off a notebook. 2. There is always a chance of something like this. The internet is like the wild wild west. However if you use strong...

what about MN using a single static IP and multiple pubkeys does this have a similar effect?

such as the example of 127.0.0.4 on test net, but its mysteriously gone today...no node could ever access it and whenever it was elected current MN it crashed the party so to speak.

Static or not it needs to make that first check to verify the pubkey and ports are open. It seems after that you can trick it to think just about anything, on testnet we still have 127.0.0.4 I thought there was some bugs fixed to prevent gaming the MN system. Maybe it wasn't related to this...

i'm down to one connection every time I kill it a new 0.10 MN connects. I'm still trying to find someone on 70052 for my last connection. Not sure it was the best way but I increased my terminal history and then copied it all to my text editor and found the 70051 and used tcpkill host <IP>...

Ok but ins't there a chance they eventually re-peer until the old ones are updated? Also how can you get a list of IP still on 70051 using peerinfo? its a long list of peers...

Did you update to 11.0.7?

The MANDATORY updates should disallow rewards to Older version masternodes! That would get the owners of MN to pay attention and upgrade their systems faster.....

With one lower end card you might get about 2.5 -3 MHS and on a big pool with luck you might get about .01DRK per day. Your power will cost more. There isn't much "profit" in mining DRK right now for us average joes, I mostly keep the miners i built running at a loss now to help "secure" the...