Bitcoin Forum>Alternate cryptocurrencies>Announcements (Altcoins)
Pages:
Author

Topic: . - page 22. (Read 491778 times)

GoldenEye
hero member
Activity: 601
Merit: 500
Re: .
January 25, 2016, 04:04:34 PM
#2667
Quote from: markm on January 25, 2016, 05:20:48 AM
On the admin.html page where you generate your hallmark, the date format is not specified, the example date is ambiguous, it is not clear that international standard dates that collate normally in ASCII are intended, because the example date shown would also work if it was some kind of bastardised non-collating wierd U.S. format where they screwed up the month and day to break easy collation (listing in sequence) of dates (such as if you happen to use a date as a filename or whatever).

So presumably either the U.S. idiots or the whole rest of the world might well be entering the date incorrectly, would that screw up their distribution of coins for running a node?

This seems like an important problem, who the heck decided to put such an ambiguous date in there as example date instead of something like 2013-12-31 that makes it plain the normal easy-to-collate international date style is intended? (Or vice versa, 2013-31-12 if stupid american crap is intended) ?

TL;DR what the fuck order are we supposed to put the year month and day in that stupid/idiotic form?

-MarkM-


https://en.wikipedia.org/wiki/ISO_8601

Would the stupid american really write 2013-31-12 ? Never seen it before.
JPred
sr. member
Activity: 392
Merit: 250
my magic is growing strong[er]
Re: .
January 25, 2016, 02:47:34 PM
#2666
^ awesomely fascinating altsheets.  Smiley Being visually inclined helped me make sense of your network analysis.
altsheets
legendary
Activity: 902
Merit: 1001
Free trial of #AltFolio = save time, react faster
Re: .
January 25, 2016, 01:27:25 PM
#2665
altsheets
legendary
Activity: 902
Merit: 1001
Free trial of #AltFolio = save time, react faster
Re: .
January 25, 2016, 10:47:45 AM
#2664
Quote from: MaWo on January 25, 2016, 05:28:31 AM
Quote from: markm on January 25, 2016, 05:20:48 AM
This seems like an important problem, who the heck decided to put such an ambiguous date in there as example date instead of something like 2013-12-31 that makes it plain the normal easy-to-collate international date style is intended? (Or vice versa, 2013-31-12 if stupid american crap is intended) ?
...
-MarkM-

I guess Jean Luc:
https://bitbucket.org/JeanLucPicard/nxt/annotate/108075295db840cf588dc30a9b77a262ccf92802/webapps/root/admin.html?at=0.4.8&fileviewer=file-view-default#admin.html-50


Does this help? --> Hallmark.parseDate(dateValue) --> class Hallmark


*g*
MaWo
hero member
Activity: 575
Merit: 502
Re: .
January 25, 2016, 05:28:31 AM
#2663
Quote from: markm on January 25, 2016, 05:20:48 AM

...

This seems like an important problem, who the heck decided to put such an ambiguous date in there as example date instead of something like 2013-12-31 that makes it plain the normal easy-to-collate international date style is intended? (Or vice versa, 2013-31-12 if stupid american crap is intended) ?

...
-MarkM-


I guess Jean Luc:
https://bitbucket.org/JeanLucPicard/nxt/annotate/108075295db840cf588dc30a9b77a262ccf92802/webapps/root/admin.html?at=0.4.8&fileviewer=file-view-default#admin.html-50
markm
legendary
Activity: 2940
Merit: 1090
Re: .
January 25, 2016, 05:20:48 AM
#2662
On the admin.html page where you generate your hallmark, the date format is not specified, the example date is ambiguous, it is not clear that international standard dates that collate normally in ASCII are intended, because the example date shown would also work if it was some kind of bastardised non-collating wierd U.S. format where they screwed up the month and day to break easy collation (listing in sequence) of dates (such as if you happen to use a date as a filename or whatever).

So presumably either the U.S. idiots or the whole rest of the world might well be entering the date incorrectly, would that screw up their distribution of coins for running a node?

This seems like an important problem, who the heck decided to put such an ambiguous date in there as example date instead of something like 2013-12-31 that makes it plain the normal easy-to-collate international date style is intended? (Or vice versa, 2013-31-12 if stupid american crap is intended) ?

TL;DR what the fuck order are we supposed to put the year month and day in that stupid/idiotic form?

-MarkM-
Nxtblg
legendary
Activity: 924
Merit: 1000
Re: .
January 24, 2016, 05:34:44 PM
#2661
Try this one: https://159.203.20.204/wallet/index.html  Smiley

Thanks, MaWo  Wink
altsheets
legendary
Activity: 902
Merit: 1001
Free trial of #AltFolio = save time, react faster
Re: .
January 24, 2016, 08:57:23 AM
#2660
Quote from: MaWo on January 24, 2016, 06:03:50 AM
Quote from: altsheets on January 24, 2016, 05:53:16 AM

--> Where can I find documentation how to communicate on port 7774? Command list? Thx!

And the approximate number of nodes you are finding is ... ?
Am I in the right ballpark?

Thanks.

I used the following documentation for the peer server Wink
https://github.com/NeXTHorizon/hz-source/tree/master/src/java/nxt/peer

Haha :-) Alright then, thx for the hint ... I found this now there:
https://github.com/NeXTHorizon/hz-source/blob/master/src/java/nxt/peer/PeerServlet.java#L61-L71

Thanks.


Quote from: MaWo on January 24, 2016, 06:03:50 AM
Quote from: altsheets on January 24, 2016, 05:53:16 AM
And the approximate number of nodes you are finding is ... ?
Am I in the right ballpark?
Thanks.

results from last night:
... 179 ...
Good to know, thanks. So with my 124 nodes, I wasn't too far off at least.
Perhaps those missing ones are the nodes which work on different ports than 7776 and 7774 ?

I'd like to find out ...


.

EDIT: Solved it!

At first I could not get around this obstacle: https://github.com/altsheets/chaincountdown/blob/master/tools/test7774.py#L9-L15

But now I found the reason, with this testing script:

Code:
rm test7774.py -f
wget https://raw.githubusercontent.com/altsheets/chaincountdown/master/tools/test7774.py
python test7774.py

The breakthrough was possible when I realized that I can compare curl to python.requests.post at www.requestb.in

--> Solution:

Code:
headers = {'content-type': 'application/x-www-form-urlencoded'}

Now it works. *sigh*. Yiehah.
MaWo
hero member
Activity: 575
Merit: 502
Re: .
January 24, 2016, 06:03:50 AM
#2659
Quote from: altsheets on January 24, 2016, 05:53:16 AM
Very interesting, thank you very much.
That is helpful.

From a quick browse through your script, I am gathering, that you are using only port 7774 for all communication?
So you are querying also the "getPeers" call on 7774 ? Network-wise, I was thinking the same - that I should be able to get all peers of a node, even if the API (7776) is not open.

And that command "getCumulativeDifficulty" doesn't exist on 7776 ( http://api.nhzcrypto.org:7776/test )

--> Where can I find documentation how to communicate on port 7774? Command list? Thx!
...

And the approximate number of nodes you are finding is ... ?
Am I in the right ballpark?

Thanks.

I used the following documentation for the peer server Wink
https://github.com/NeXTHorizon/hz-source/tree/master/src/java/nxt/peer

results from last night:
Code:
cat peer-results-2016-01-24-00-53-40.txt
counter peers   new     total   host    version height
1       146     146     147     eu6.woll-e.net  NHZ V5.4        554958
2       5       1       148     107.161.81.142  NHZ V5.4        554958
3       32      2       150     185.32.157.22   NHZ V5.4        554958
4       22      3       153     193.198.102.32  NHZ V5.4        554958
5       21      0       153     194.135.89.18   NHZ V5.4        554958
6       22      1       154     194.135.88.110  NHZ V5.4        554958
7       30      1       155     52.32.104.97    NHZ V5.4        554958
8       22      0       155     85.214.65.220   NHZ V5.4        554958
9       37      1       156     185.32.157.23   NHZ V5.4        554958
10      0       0       156     185.32.157.143  NHZ V5.4        0
11      33      1       157     185.32.157.95   NHZ V5.4        554958
12      34      0       157     185.32.157.20   NHZ V5.4        554958
13      24      0       157     192.99.77.148   NHZ V5.4        554958
14      37      0       157     185.32.157.94   NHZ V5.4        554958
15      41      0       157     185.32.157.21   NHZ V5.4        554958
16      28      0       157     50.173.35.180   NHZ V5.4        554958
17      4       0       157     107.161.81.146  NHZ V5.4        554958
18      43      0       157     185.32.157.26   NHZ V5.4        554958
19      24      0       157     52.26.118.234   NHZ V5.4        554953
20      32      0       157     185.32.157.27   NHZ V5.4        554958
21      22      0       157     194.135.85.170  NHZ V5.4        554958
22      25      0       157     192.227.175.158 NHZ V5.4        554958
23      29      0       157     52.24.16.77     NHZ V5.4        554958
24      45      0       157     185.32.157.24   NHZ V5.4        554958
25      38      0       157     185.32.157.147  NHZ V5.4        554958
26      33      0       157     185.32.157.25   NHZ V5.4        554958
27      24      0       157     161.53.40.94    NHZ V5.4        554958
28      34      1       158     185.32.157.105  NHZ V5.4        554958
29      38      0       158     185.32.157.149  NHZ V5.4        554958
30      26      0       158     185.32.156.47   NHZ V5.4        554958
31      43      0       158     185.32.157.104  NHZ V5.4        554958
32      45      0       158     185.32.157.148  NHZ V5.4        554958
33      21      0       158     193.198.102.245 NHZ V5.4        554958
34      23      0       158     185.32.156.46   NHZ V5.4        554958
35      27      0       158     unna.zapto.org  NHZ V5.4        554958
36      35      0       158     185.32.157.28   NHZ V5.4        554958
37      21      0       158     193.198.102.246 NHZ V5.4        554958
38      23      0       158     185.32.156.45   NHZ V5.4        554958
39      21      0       158     198.154.60.61   NHZ V5.4        554958
40      44      0       158     185.32.157.29   NHZ V5.4        554958
41      26      0       158     185.32.156.44   NHZ V5.4        554958
42      24      0       158     52.24.142.13    NHZ V5.4        554957
43      21      2       160     158.69.202.70   NHZ V5.3        554958
44      37      0       160     185.32.157.101  NHZ V5.4        554958
45      22      0       160     185.32.156.43   NHZ V5.4        554958
46      25      1       161     54.174.241.182  NHZ V5.4        554958
47      21      0       161     178.33.14.208   NHZ V5.4        554958
48      30      0       161     185.32.157.100  NHZ V5.4        554958
49      31      0       161     52.24.187.95    NHZ V5.4        554957
50      27      0       161     185.32.156.42   NHZ V5.4        554958
51      34      0       161     185.32.157.99   NHZ V5.4        554958
52      31      0       161     185.32.157.77   NHZ V5.4        554958
53      40      0       161     185.32.157.103  NHZ V5.4        554958
54      28      0       161     185.32.156.41   NHZ V5.4        554958
55      39      0       161     185.32.157.98   NHZ V5.4        554959
56      39      0       161     185.32.157.76   NHZ V5.4        554959
57      0       0       161     185.32.157.102  NHZ V5.4        0
58      38      0       161     185.32.156.40   NHZ V5.4        554959
59      28      0       161     98.207.117.83   NHZ V5.4        554959
60      32      0       161     143.177.26.246  NHZ V5.4        554959
61      24      0       161     193.198.102.54  NHZ V5.4        554959
62      24      0       161     130.211.142.219 NHZ V5.4        554959
63      23      0       161     52.16.128.175   NHZ V5.4        554959
64      5       0       161     192.227.239.69  NHZ V5.4        554959
65      29      0       161     79.241.209.184  NHZ V5.4        554959
66      23      0       161     70.118.207.119  NHZ V5.4        554959
67      24      0       161     92.222.65.40    NHZ V5.4        554959
68      22      0       161     193.198.102.51  NHZ V5.4        554959
69      42      0       161     185.32.157.81   NHZ V5.4        554959
70      21      0       161     198.46.192.106  NHZ V5.4        554959
71      21      15      176     45.55.79.49     NHZ V4.0e       565925
72      21      0       176     159.203.125.129 NHZ V4.0e       565925
73      22      0       176     104.131.0.36    NHZ V4.0e       565925
74      21      0       176     40.115.9.55     NHZ V4.0e       565923
75      21      0       176     159.203.76.78   NHZ V4.0e       565925
76      21      0       176     176.126.245.17  NHZ V4.0e       565925
77      21      0       176     159.203.119.139 NHZ V4.0e       565925
78      20      0       176     193.198.102.53  NHZ V5.4        554959
79      34      0       176     185.32.157.60   NHZ V5.4        554959
80      26      0       176     23.95.44.142    NHZ V5.4        554959
81      21      0       176     159.203.65.55   NHZ V4.0e       565925
82      22      0       176     193.198.102.52  NHZ V5.4        554959
83      23      0       176     85.214.37.185   NHZ V5.4        554959
84      37      2       178     107.155.89.207  NHZ V3.8        347214
85      0       0       178     204.44.118.124  NHZ V3.2        276108
86      21      0       178     104.236.121.190 NHZ V4.0e       565925
87      20      0       178     85.214.243.229  NHZ V5.4        554959
88      25      0       178     194.135.88.140  NHZ V5.4        554959
89      23      0       178     52.28.46.180    NHZ V5.4        554959
90      41      0       178     85.214.43.71    NHZ V5.4        554959
91      23      0       178     77.88.208.12    NHZ V5.4        554959
92      22      0       178     194.135.89.218  NHZ V5.4        554959
93      24      0       178     188.226.179.119 NHZ V5.4        554959
94      22      0       178     193.107.35.234  NHZ V5.4        554959
95      28      0       178     52.24.85.12     NHZ V5.4        554956
96      25      0       178     37.120.160.148  NHZ V5.2        554959
97      20      0       178     backslash.dyndns.info   NHZ V4.0e       565925
98      0       0       178     204.44.115.27   NHZ V3.2        236131
99      32      0       178     185.32.157.52   NHZ V5.4        554959
100     1       1       179     192.227.163.233 NHZ V5.4        554959
101     1       0       179     null
102     36      0       179     185.32.157.51   NHZ V5.4        554960
103     25      0       179     31.24.29.221    NHZ V5.4        554960
104     67      0       179     110.143.228.78  NHZ V5.4        554960
105     21      0       179     178.62.194.195  NHZ V5.4        554960
106     21      0       179     69.28.82.75     NHZ V5.4        554960
107     23      0       179     194.135.88.81   NHZ V5.4        554960
108     33      0       179     185.32.157.57   NHZ V5.4        554960
109     21      0       179     104.236.83.233  NHZ V5.4        554960
110     35      0       179     185.32.157.56   NHZ V5.4        554960
111     22      0       179     192.3.156.15    NHZ V5.4        554958
112     23      0       179     194.135.92.93   NHZ V5.4        554960
113     36      0       179     185.32.157.19   NHZ V5.4        554960
114     30      0       179     37.120.173.114  NHZ V5.2        554960
115     4       0       179     138.128.169.91  NHZ V5.4        554960
116     40      0       179     185.32.157.18   NHZ V5.4        554960
117     21      0       179     81.169.133.57:80        NHZ V5.4        554960
118     22      0       179     192.3.156.18    NHZ V5.4        554958
119     37      0       179     107.155.90.83   NHZ V3.8        347289
120     32      0       179     52.32.66.50     NHZ V5.4        554960
121     22      0       179     93.75.9.10      NHZ V5.4        554960
122     10      0       179     185.38.44.173   NHZ V5.4        554960
123     22      0       179     198.154.60.183  NHZ V5.4        554961
124     36      0       179     185.32.157.59   NHZ V5.4        554961
125     44      0       179     185.32.157.154  NHZ V5.4        554961
126     26      0       179     104.219.53.3    NHZ V5.4        554961
127     146     0       179     5.9.149.197     NHZ V5.4        554961
128     65      0       179     eu4.woll-e.net  NHZ V5.4        554961
129     32      0       179     185.32.157.58   NHZ V5.4        554961
130     32      0       179     54.201.121.58   NHZ V5.4        554961
131     24      0       179     161.53.40.242   NHZ V5.4        554961
132     130     0       179     nhz.noip.me     NHZ V5.4        554961
133     27      0       179     185.32.157.152  NHZ V5.4        554961
134     5       0       179     185.38.44.174   NHZ V5.4        554961
135     31      0       179     52.24.108.223   NHZ V5.4        554956
136     38      0       179     185.32.157.153  NHZ V5.4        554961
137     42      0       179     107.155.89.235  NHZ V3.8        565926
138     41      0       179     185.32.157.150  NHZ V5.4        554961
139     20      0       179     162.213.153.7   NHZ V5.4        554961
140     28      0       179     52.27.145.90    NHZ V5.4        554961
141     25      0       179     194.135.91.6    NHZ V5.4        554961
142     25      0       179     130.211.178.56  NHZ V5.4        554961
143     21      0       179     194.135.88.186  NHZ V5.4        554961
144     27      0       179     185.32.156.36   NHZ V5.4        554961
145     32      0       179     52.26.95.4      NHZ V3.9.1      565882
146     37      0       179     185.32.156.37   NHZ V5.4        554961
147     24      0       179     89.72.57.246    NHZ V5.4        554961
148     23      0       179     167.206.61.3    NHZ V5.4        554961
149     25      0       179     185.32.156.35   NHZ V5.4        554961
150     36      0       179     52.25.130.226   NHZ V3.9.1      565926
151     26      0       179     173.232.15.176  NHZ V5.4        554961
152     22      0       179     99.192.94.44    NHZ V5.4        554961
153     41      0       179     185.32.157.30   NHZ V5.4        554961
154     22      0       179     194.135.88.20   NHZ V5.4        554961
155     22      0       179     84.198.88.87    NHZ V5.4        554961
156     26      0       179     5.196.143.14    NHZ V5.4        554961
157     23      0       179     85.214.18.69    NHZ V5.4        554961
158     21      0       179     40.115.9.5      NHZ V4.0e       565925
159     4       0       179     138.128.169.44  NHZ V5.4        554961
160     31      0       179     192.3.148.171   NHZ V5.4        554961
161     24      0       179     178.130.36.81   NHZ V5.2        554961
162     22      0       179     nsports.de      NHZ V5.3        554961
163     21      0       179     23.245.7.15     NHZ V5.4        554961
164     24      0       179     54.164.36.118   NHZ V5.4        554959
165     22      0       179     138.128.169.220 NHZ V5.4        554961
166     33      0       179     79.132.111.195  NHZ V5.4        554961
167     5       0       179     138.128.169.227 NHZ V5.4        554961
168     28      0       179     113.243.8.137   NHZ V5.4        554961
169     30      0       179     52.88.94.131    NHZ V5.4        554959
170     23      0       179     45.55.157.54    NHZ V5.2        554961
171     53      0       179     nhz.woll-e.net  NHZ V5.4        554961
172     22      0       179     45.55.81.226    NHZ V4.0e       565927
173     39      0       179     142.68.155.233  NHZ V5.4        554961
174     26      0       179     194.135.88.1    NHZ V5.4        554961
175     25      0       179     107.178.217.48  NHZ V5.4        554961
176     25      0       179     150.107.225.218 NHZ V5.4        554961
177     29      0       179     185.32.156.38   NHZ V5.4        554959
178     22      0       179     5.45.111.215    NHZ V5.2        554961
179     34      0       179     185.32.156.39   NHZ V5.4        554961
altsheets
legendary
Activity: 902
Merit: 1001
Free trial of #AltFolio = save time, react faster
Re: .
January 24, 2016, 05:53:16 AM
#2658
Very interesting, thank you very much.
That is helpful.

From a quick browse through your script, I am gathering, that you are using only port 7774 for all communication?
So you are querying also the "getPeers" call on 7774 ? Network-wise, I was thinking the same - that I should be able to get all peers of a node, even if the API (7776) is not open.

And that command "getCumulativeDifficulty" doesn't exist on 7776 ( http://api.nhzcrypto.org:7776/test )

--> Where can I find documentation how to communicate on port 7774? Command list? Thx!

Quote from: MaWo on January 23, 2016, 07:00:08 PM
Quote from: altsheets on January 23, 2016, 06:23:41 PM
...
BUT that way, I could NOT find 85.214.65.220 which is api.nhzcrypto.org.
So ... something in my strategy is not perfect yet. I might not be finding all nodes!
Happy about any suggestion.

My bash script finds peer 85.214.65.220:7774/api.nhzcrypto.org:7774

Code:
#!/bin/bash
...
PEER_SERVER_PORT="7774"
...
"requestType":"getInfo"
...
"requestType":"getCumulativeDifficulty"
...
"requestType":"getPeers"


And the approximate number of nodes you are finding is ... ?
Am I in the right ballpark?

Thanks.
MaWo
hero member
Activity: 575
Merit: 502
Re: .
January 23, 2016, 07:00:08 PM
#2657
Quote from: altsheets on January 23, 2016, 06:23:41 PM
...
BUT that way, I could NOT find 85.214.65.220 which is api.nhzcrypto.org.
So ... something in my strategy is not perfect yet. I might not be finding all nodes!
Happy about any suggestion.

My bash script finds peer 85.214.65.220:7774/api.nhzcrypto.org:7774

Code:
#!/bin/bash

SDATE=`date '+%Y-%m-%d-%H-%M-%S'`
RESULTS="peer-results-${SDATE}.txt"
PEER_SERVER_PORT="7774"
PEER_URI_SUFFIX="nhz"
FIRST_PEER="eu6.woll-e.net"

declare -A assoPeers

exists(){
  if [ "$2" != in ]; then
    echo "Wrong syntax!"
    echo "Syntax: exists {key} in {array}"
    return
  fi   
  eval '[ ${'$3'[$1]+test} ]' 
}

typeset -i addCounter=0

function getPeerInfo() {
    peer="$1"
    addCounter=0
    ROW="$peer  "

    # test whether announced address includes a port
    if [ `echo $peer| grep ':'|wc -l` -gt 0 ]; then
        URI="http://${peer}/${PEER_URI_SUFFIX}"
    else
        URI="http://${peer}:${PEER_SERVER_PORT}/${PEER_URI_SUFFIX}"
    fi

    ROW2=`curl --silent -4 -m5 --data '{"platform":"TEST","protocol":1,"application":"TEST Bot","requestType":"getInfo","version":"v0.1"}' "${URI}" | tr '\r\|\n' ' '`
    if [ $? -gt 0 ]; then
        assoPeers["${peer}"]="error getInfo"
        return 1
    fi
    sleep 0.1

    peerVersion=`echo "$ROW2" | jshon -C -Q -e version | sed -e 's/"//g'`

    ROW3=`curl --silent -4 -m5 --data '{"platform":"TEST","protocol":1,"application":"TEST Bot","requestType":"getCumulativeDifficulty","version":"v0.1"}' "${URI}" | tr '\r\|\n' ' '`
    ROW2+="     ${ROW3}"
    if [ $? -gt 0 ]; then
        assoPeers["${peer}"]="error getCumulativeDifficulty"
        return 1
    fi
    sleep 0.1
    peerHeight=`echo "$ROW3" | jshon -C -Q -e blockchainHeight | sed -e 's/"//g'`

    PEERS=`curl --silent -4 -m5 --data '{"platform":"TEST","protocol":1,"application":"TEST Bot","requestType":"getPeers","version":"v0.1"}' "${URI}"| jshon -C -Q -e peers | grep -v '\]\|\['| sed -e 's/[" ,]//g'`
    if [ $? -gt 0 ]; then
        assoPeers["${peer}"]="error getPeers"
        return 1
    fi

    ROW2+="     "`echo $PEERS|tr '\r\|\n' ' '`

    # read peers into an array
    IFS=$'\n ' read -r -d '' -a peersarray < <(printf '%s\0' "$PEERS")

    #add only elements from peersarray into the associative array which doesn't exist
    if [ "${#peersarray[@]}" -gt 0 ]; then
        for a in "${peersarray[@]}"; do
            if ! exists "$a" in assoPeers; then
                assoPeers["$a"]="0";
                addCounter=addCounter+1
            fi
        done
    fi
    ROW+="      ${#peersarray[@]}       $addCounter     ${#assoPeers[@]}"
    assoPeers["${peer}"]="$ROW  $ROW2"

    printf "${peerCounter}\t${#peersarray[@]}\t$addCounter\t${#assoPeers[@]}\t${peer}\t${peerVersion}\t${peerHeight}\n" | tee -a $RESULTS
}

function isNextPeer() {
    nextPeer=""
    for key in ${!assoPeers[@]}; do
        if [ "${assoPeers[${key}]}" == "0" ]; then
            assoPeers["${key}"]="started"
            nextPeer="${key}"
            return 0
        fi
    done
    return 1
}

### MAIN  ###

typeset -i peerCounter=1
printf "counter\tpeers\tnew\ttotal\thost\tversion\theight\n"| tee -a $RESULTS
getPeerInfo "${FIRST_PEER}"

while isNextPeer; do
    peerCounter=peerCounter+1
    getPeerInfo "$nextPeer"
done

altsheets
legendary
Activity: 902
Merit: 1001
Free trial of #AltFolio = save time, react faster
Re: .
January 23, 2016, 06:23:41 PM
#2656
EDITED heavily, to avoid repetition below. See this post for the continuation of this.

chaincountdown v18
Motivation, why all this --> A user had complained that my image server 'ChainCountDown' was broken ... but it actually was jxnt.org which was down - which is the server I had been using for API queries (of 'getBlockchainStatus' --> blockNumber). New solution: Whenever an API lookup is failing, the next server is asked. Only if all nodes are failing, my server is in trouble. But now server names are hardcoded in config.py - so I wanted to select servers which may last a while. Choosing by looking at their domain names.

-->

 PeerExplorer for HZ - updated!
Domain lookup for HZ nodes and NXT nodes

Code:
mkdir -p testing; cd testing; rm peerMagic.py* -f
apt-get -y install wget python
wget https://raw.githubusercontent.com/altsheets/chaincountdown/master/tools/peerMagic.py
python peerMagic.py
Or on Windows: install Python 2.7, then download & doubleclick peerMagic.py

You can
* study the source code
* look at the NXT results
* and the -really interesting- HZ results,
* and see the network analysis results below.

---

For NXT

... I could use www.peerexplorer.com results, so the main work was a multi-threaded DNS lookup.

Plus meaningful sorting mechanisms:
* The domain names are sorted back to front, with TLD as the most significant split part.
* The IP addresses are in increasing order, with most significant the left-most byte.

For 30 of the 46 IPs with open nxt API ... I got domain names.

---

For Horizon HZ

... I could not query any peerexplorer.com server, so I developed my own crawler:

(1) ask 'woll-e.net' for 'getPeers' ... answer is 659 APs (address+port, or IP)
(2) enqueue them all, and start 150 worker threads
(3) in each thread ... dequeue one AP, add it to 'apDone'.
(4) if an IP answers to a 'getTime' query on 7776, save it to 'openAPI'.
(5) if AP is answering on peer node port (usually 7774) to 'getInfo', then query 'getPeers' - then enqueue all its (yet-unvisited) peers.
(6) store all results in lists, do cool infoline printing ...
(7) keep on working through the queue ... until it is finally empty:

Ready. After checking 669 APs, on two ports each (and in ~20 seconds only!) ...:

Found
187 HZ nodes, and
63 with open API (answering on port 7776).

---

Of 63 nodes with open API, 44 had a domain name.

To see all details, scroll down in this output file peerMagic_HZ.txt.


Punchline: All HZ nodes with open API that I could find are these ...

Code:
 107.161.81.146:                               serv1.care-market.biz
 107.161.81.142:                           mail2.turboxafiliados.biz
 138.128.169.44:                    mail10.flex04.flexmailing.com.br
138.128.169.220:                  spcr-5.interspireservidores.com.br
138.128.169.227:                  spcr-6.interspireservidores.com.br
 107.155.89.207:                107-155-89-207-customer-at-wable.com
 107.155.89.235:                107-155-89-235-customer-at-wable.com
  107.155.90.83:                 107-155-90-83-customer-at-wable.com
  52.24.108.223:   ec2-52-24-108-223.us-west-2.compute.amazonaws.com
   52.24.142.13:    ec2-52-24-142-13.us-west-2.compute.amazonaws.com
   52.24.187.95:    ec2-52-24-187-95.us-west-2.compute.amazonaws.com
    52.24.85.12:     ec2-52-24-85-12.us-west-2.compute.amazonaws.com
  52.25.130.226:   ec2-52-25-130-226.us-west-2.compute.amazonaws.com
  52.26.118.234:   ec2-52-26-118-234.us-west-2.compute.amazonaws.com
     52.26.95.4:      ec2-52-26-95-4.us-west-2.compute.amazonaws.com
   52.27.145.90:    ec2-52-27-145-90.us-west-2.compute.amazonaws.com
    52.32.66.50:     ec2-52-32-66-50.us-west-2.compute.amazonaws.com
   52.88.94.131:    ec2-52-88-94-131.us-west-2.compute.amazonaws.com
  54.201.121.58:   ec2-54-201-121-58.us-west-2.compute.amazonaws.com
 192.227.239.69:                192-227-239-69-host.colocrossing.com
 173.232.15.176:                173-232-15.static.rdns.serverhub.com
  85.214.37.185:                                      mail.cochet.de
     78.46.32.4:            static.4.32.46.78.clients.your-server.de
   194.135.88.1:                                  7146.s.time4vps.eu
 194.135.89.218:                                  7169.s.time4vps.eu
   194.135.91.6:                                  7170.s.time4vps.eu
  194.135.89.18:                                  7171.s.time4vps.eu
  194.135.88.81:                                  7172.s.time4vps.eu
 194.135.88.110:                                  7173.s.time4vps.eu
  194.135.88.20:                                  7174.s.time4vps.eu
 194.135.88.186:                                  7175.s.time4vps.eu
 194.135.88.140:                                  7176.s.time4vps.eu
  194.135.92.93:                                  9205.s.time4vps.eu
  161.53.40.242:                                     castor.riteh.hr
   161.53.40.94:                                 penguinium.riteh.hr
  85.214.65.220:                           h1746043.stratoserver.net
 178.150.207.53:                          53.207.150.178.triolan.net
 178.150.207.53:                          53.207.150.178.triolan.net
 81.169.157.223:                                          woll-e.net
 81.169.157.223:                                          woll-e.net
 85.214.243.229:                                      eu2.woll-e.net
  81.169.133.57:                                      eu3.woll-e.net
  81.169.133.57:                                      eu3.woll-e.net
   85.214.18.69:                                      eu5.woll-e.net
    23.245.7.15
     40.115.9.5
    40.115.9.55
    45.55.79.49
   45.55.81.226
   45.55.157.54
   104.131.0.36
104.236.121.190
 138.128.169.91
150.107.225.218
  159.203.65.55
159.203.119.139
159.203.125.129
 176.126.245.17
  178.33.14.208
  185.38.44.173
  185.38.44.174
192.227.163.233
 193.198.102.32

These are all IPs with open API!

I still did not really know how to speak to peernodeservers. Is the port 7774 communication really not documented other than so? During my first attempt,  I covered only ~2/3 of the network:

Quote
BUT that way, I could NOT find 85.214.65.220 which is api.nhzcrypto.org.
So ... something in my strategy is not perfect yet. I might not be finding all nodes!
Happy about any suggestion.

MaWo's script helped ... and after a lot of fiddling, I found the way. See below.


Now ChainCountDown is more resilient, because instead of 1 server per coin, I hardcoded 6 and 7 addresses with open API. That should do the trick.

:-)


If you like this, show it:
  NHZ-Q675-SGBG-LQ43-D38L6   or   NXT-CMKU-ZQYK-V6CD-9UHF4
  or hard cash BTC 13whfNFT2dse7eiuNXVkuJivjxqSXHrW4j
 
EDIT: retweet

EDITED heavily, to avoid repetition below. See this post for the continuation of this.
Pizpie
legendary
Activity: 971
Merit: 1000
Re: .
January 19, 2016, 02:27:47 AM
#2655
Quote from: nwfella on January 18, 2016, 12:32:38 AM
Interested in setting up a hallmark node but the youtube video in OP is no longer available.  Anybody have a link handy available for quick DIY guide?

I made some new ones and will get them up this week!
nwfella
legendary
Activity: 1610
Merit: 1000
Well hello there!
Re: .
January 18, 2016, 12:32:38 AM
#2654
Interested in setting up a hallmark node but the youtube video in OP is no longer available.  Anybody have a link handy available for quick DIY guide?
altsheets
legendary
Activity: 902
Merit: 1001
Free trial of #AltFolio = save time, react faster
Re: .
January 16, 2016, 09:24:08 AM
#2653
7d
https://explorer.horizonplatform.io/?page=graphs&graph=distribution&offset=7d
30d
https://explorer.horizonplatform.io/?page=graphs&graph=distribution&offset=30d
60d
https://explorer.horizonplatform.io/?page=graphs&graph=distribution&offset=60d
90d
https://explorer.horizonplatform.io/?page=graphs&graph=distribution&offset=90d


max time ?
https://explorer.horizonplatform.io/?page=graphs&graph=distribution&offset=any


would be nice to also implement these:
https://explorer.horizonplatform.io/?page=graphs&graph=distribution&offset=180d
https://explorer.horizonplatform.io/?page=graphs&graph=distribution&offset=1y
https://explorer.horizonplatform.io/?page=graphs&graph=distribution&offset=500d


The code lines are these?
https://github.com/pharesim/hz-blockexplorer/blob/master/classes/model.php#L582-L604


;-)
Pizpie
legendary
Activity: 971
Merit: 1000
Re: .
January 16, 2016, 03:43:41 AM
#2652
Quote from: Emerger on January 11, 2016, 11:45:41 PM
Also very grateful for the tireless efforts taken to ensure Horizon's stakeholder bounty was honored. Congratulations! I hope that the fair distribution model will serve as a major advantage sometime in HZ's future. Thanks for all your work Smiley

Is there anywhere I can see stats on total % or coins that was distributed this way, preferably graphed over time?

These charts were available on the old site. I will see if I can dig them up.
Emerger
full member
Activity: 199
Merit: 102
Re: .
January 11, 2016, 11:45:41 PM
#2651
Also very grateful for the tireless efforts taken to ensure Horizon's stakeholder bounty was honored. Congratulations! I hope that the fair distribution model will serve as a major advantage sometime in HZ's future. Thanks for all your work Smiley

Is there anywhere I can see stats on total % or coins that was distributed this way, preferably graphed over time?
JPred
sr. member
Activity: 392
Merit: 250
my magic is growing strong[er]
Re: .
January 11, 2016, 11:26:36 PM
#2650

Herewith please accept my heartfelt gratitude for receiving those tireless stakeholder bounties day after day for many many days. It was indeed a pleasure to have held balance of my HZ in account - it beat (%wise) what any fiat bank would have been able (willing) to provide by far.
Pizpie
legendary
Activity: 971
Merit: 1000
Re: .
January 11, 2016, 11:18:47 PM
#2649
Quote from: nwfella on January 11, 2016, 10:59:42 PM
Quote from: quasimodo on January 08, 2016, 12:30:49 AM
My second day without stakeholderbounty. Is there a problem with the script? The post above says, end of distribution is in 14 days (+/-).
No stakeholderbounty received since the 6th here :/

As mentioned in the previous page - The stakeholder bounty has completed after 1.5 years of running!
nwfella
legendary
Activity: 1610
Merit: 1000
Well hello there!
Re: .
January 11, 2016, 10:59:42 PM
#2648
Quote from: quasimodo on January 08, 2016, 12:30:49 AM
My second day without stakeholderbounty. Is there a problem with the script? The post above says, end of distribution is in 14 days (+/-).
No stakeholderbounty received since the 6th here :/
Pages:
Bitcoin Forum>Alternate cryptocurrencies>Announcements (Altcoins)
Jump to: