Topic: The miner with IP 0.0.0.0 is close to 50% (Read 5247 times)

255.255.255.255 called, and said to bump this thread.

If, at this point, anyone still doesn't get 0.0.0.0 is NOTHING (null), there is nothing simpler than this explanation:

http://en.wikipedia.org/wiki/0.0.0.0

It also checks coinbase transaction.  This aids in detection of pools which put custom data in the coinbase.  For p2pool it is essential given p2pool has no fixed IP address.

There is no way to know the origination IP address only the first IP address you see.  A pool could obfuscate their blocks by not allowing connections to bitcoind from unknown sources and broadcasting blocks through relays.  For example if you knew the IP address of one of Mt.Gox bitcoind you could send block there where it would be broadcasted to the rest of network (including blockchain.info). 

That's the right answer to the wrong question.

When a Bitcoin block is found, the node that found it broadcasts it out to other nodes. blockchain.info is connected to hundreds of nodes, so by listening in on the new block announcements, it can quickly determine which Bitcoin node on which IP address found the block.

The chart uses known IPs of pools (that people report, or that are shown in pool docs for connecting your miner).

lolyup

OK.. 0.0.0.0 aside.. got a serious question... 

How do you come up with the IP address of the miner/pool?  Looking at raw blocks in block explorer I don't see an IP address anyplace ..

Sigg

No, the first two were fake. The third was true. Also this week: I caught the flu from one of my family members at the funeral, a sibling was involved in a domestic disturbance, I found out my only surviving grandparent has brain cancer, a tornado hit the town where my parents live, and apparently I donated 37 BTC the night I wrote this to victims of a Bitcoin scammer.

Let this be a lesson to you, kids, don't drink and bitcointalk.

Didn't you know? It's Zeta-Reticulans joined the party!

Please tell me you're trolling, 0.0.0.0 is the address for "broadcast to ALL the networks \o/".

Since it's 0.0.0.0, what this thread really needs is a...

umm, the relevant bit is right in your post:


what that means is that it is an ip that is only used on local networks, not the internet.  like 192.168.2.1 is usually a home routers ip address (not an internet ip address) and 127.0.0.1 is the localhost, which is basically a reference to the current computer.

This is all very odd.Maybe it's a US multinational or a university (as I was taught in computing that the low range IP addresses were reserved for US academic institutions/multinationals). I wouldn't rule out a multinational/university trying with BTC mining.As more people become aware of mining (BTC for profit),more and more entities will be getting in on the act.

I checked the IP with this :http://www.techzoom.net/tools/check-ip.en
I typed in 0.0.0.0 and this is what showed up:

"------------------------------------------------------------------
Time request .: 2012-02-26 19:03:42
Remote IP ....: 69.22.174.208
Whois-Server .: whois.arin.net
Request ......: 0.0.0.0
------------------------------------------------------------------
#
# Query terms are ambiguous.  The query is assumed to be:
#     "n 0.0.0.0"
#
# Use "?" to get help.
#

#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=0.0.0.0?showDetails=true&showARIN=false&ext=netref2
#

NetRange:       0.0.0.0 - 0.255.255.255
CIDR:           0.0.0.0/8
OriginAS:       
NetName:        SPECIAL-IPV4-LOCAL-ID-IANA-RESERVED
NetHandle:      NET-0-0-0-0-1
Parent:         
NetType:        IANA Special Use
Comment:        This block is assigned for use as local
Comment:        identification addresses. 0.0.0.0 refers to
Comment:        "this" host on "this" network. 0.0.0.0
Comment:        MUST NOT be sent, except as a source address 
Comment:        as part of an initialization procedure
Comment:        by which the host learns its own IP address.
Comment:        This block was assigned by the IETF in the
Comment:        Standard document, RFC 1122, and is
Comment:        further documented in the Best Current
Comment:        Practice document RFC 5735. These documents
Comment:        can be found at:
Comment:        http://www.rfc-editor.org/rfc/rfc1122.txt
Comment:        http://www.rfc-editor.org/rfc/rfc5735.txt
RegDate:       
Updated:        2010-04-14
Ref:            http://whois.arin.net/rest/net/NET-0-0-0-0-1

OrgName:        Internet Assigned Numbers Authority
OrgId:          IANA
Address:        4676 Admiralty Way, Suite 330
City:           Marina del Rey
StateProv:      CA
PostalCode:     90292-6695
Country:        US
RegDate:       
Updated:        2004-02-24
Ref:            http://whois.arin.net/rest/org/IANA

OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName:   Internet Corporation for Assigned Names and Number
OrgAbusePhone:  +1-310-301-5820
OrgAbuseEmail:  [email protected]
OrgAbuseRef:    http://whois.arin.net/rest/poc/IANA-IP-ARIN

OrgTechHandle: IANA-IP-ARIN
OrgTechName:   Internet Corporation for Assigned Names and Number
OrgTechPhone:  +1-310-301-5820
OrgTechEmail:  [email protected]
OrgTechRef:    http://whois.arin.net/rest/poc/IANA-IP-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#


------------------------------------------------------------------

'

Question is what business does ICANN have with mining bitcoins? Maybe they're trying to obtain them or a possible imposter using an IP mask to hide the fact that he's hogging the network.

Must... buy... tinfoil.... make... hat...

damn, if your for real, i'm genuinely sorry to hear it.  glad you've managed to keep your sense of humor.

This is just another post because I wanted to see my post count at 1234...

WTF?!?
I turned on Wireshark to confirm, and found ANOTHER IP trying to "ARP" my information from 192.168.1.1...WTF!

Looks like ::1 has access to all your bitcoins!

WHAT THE FUCK

lol, i must be as well because i screwed that sentence up good.  i'm just going to go 127.0.0.1