BitShares Forum
Other => Graveyard => Marketplace => Topic started by: bytemaster on December 28, 2013, 08:37:40 am
-
Provide a working solution that allows someone to download a PTS wallet and get connected to the network in less than 5 minutes.
This bounty is still in the pending state until the full specification for this bounty can be defined. If you would like to tackle this bounty help us define the SPEC and requirements first.
This bounty will be won when I have a downloadable Windows Binary produced by a trusted (by me) source (FreeTrade or other), a pull request for the required changes, and I can verify that downloading on clean machine results in rapid connections.
A secondary bounty for $10 per month (Paid in PTS) will be given to people who host seed nodes on unique services. Limit 4 total.
This bounty is now ACTIVE.
-
But it's already possible to do this?
... I could make a video showing how easy it is? lol
my server has never had more than 400 connections at once. i always get connected within a second or two. provided it doesn't get DDoSed, this should continue
-
I'll be done in an hour, hope i get there first. It's rough but it will work. I'll have to figure it for windows users though.
-
sudo apt-get update && sudo apt-get install git make g++ build-essential libminiupnpc-dev libboost-all-dev libdb++-dev libgmp-dev libssl-dev dos2unix cmake qt4-qmake libgmp3-dev autotools-dev nautilus-open-terminal xsensors autoconf curl dos2unix libtool libcurl4-openssl-dev mesa-utils libncurses5-dev python3-pycurl python-simplejson python3-urllib3 python-beautifulsoup python-numpy-dev python3-numpy-dev libdb48-dev libopenssl-dev libdb++-dev qt-sdk openssh-server cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 libelfg0 dh-modaliases ia32-libs ia32-libs-multiarch lib32gcc1 libc6 pkg-config automake
wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz
tar -xzvf db-4.8.30.NC.tar.gz
cd db-4.8.30.NC/build_unix
../dist/configure --enable-cxx
sudo make
sudo make install
cd
git clone https://github.com/InvictusInnovations/ProtoShares
git clone https://github.com/Nameshar/PTSBoost.git
mv PTSBoost .protoshares
cd Protoshares
qmake-qt4
make
./Protoshares-qt --reindex
need to get home and test it, but i think the files should already be on github, if anyone is interested, you can try it in the mean time. I'll be at my desk soon.
The whole idea is to use direct download to get the Block chain in seconds/ 2 minutes depending on your bandwidth , copy files that are at worst a day old and have your Client running hopefully in less than 5 minutes. The above script is my system-remake.sh that i use to change a newly installed linux to a miner, i have removed things like all the cpuminers, cgminer and my coins of interest to make it specific to this cause. The full system-remake includes most of the required stuff for development.
An advantage of this is that it even includes a peers file that enable quick connection to others.
-
Taking long to upload files
-
The issue people have is finding nodes to connect to not downloading the chain.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
The issue people have is finding nodes to connect to not downloading the chain.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
modify this
static const char *strMainNetDNSSeed[][2] = {
{"162.243.45.158", "162.243.45.158"},
{"192.241.150.158", "192.241.150.158"},
{"162.243.67.4", "162.243.67.4"},
{"162.243.54.126", "162.243.54.126"},
{"37.139.29.236", "37.139.29.236"},
{"64.90.183.137", "64.90.183.137"},
{"111.93.163.251","111.93.163.251"},
{"54.219.164.96","54.219.164.96"},
{"198.211.112.13","198.211.112.13"},
{"50.112.199.32","50.112.199.32"},
{"106.187.41.67","106.187.41.67"},
{"54.218.232.206","54.218.232.206"},
{"54.212.175.33","54.212.175.33"},
{NULL, NULL}
};
in protoshares/src/net.cpp
to
static const char *strMainNetDNSSeed[][2] = {
{"49.89.6.185", "49.89.6.185"},
{"222.174.212.250", "222.174.212.250"},
{"183.8.183.73", "183.8.183.73"},
{"173.208.148", "173.208.148"},
{"169.237.74.213", "169.237.74.213"},
{"175.42.27.186","175.42.27.186"},
{NULL, NULL}
};
Add more, as you see fit. also maybe get a server online that has high bandwidth, run the client there and add it to this list.
mine connects in seconds with the above.
-
Or do you want a pull request?
-
Or do you want a pull request?
I would like a pull request as well as some background on the nodes in the list. How do we know they will stay up?
-
Or do you want a pull request?
I would like a pull request as well as some background on the nodes in the list. How do we know they will stay up?
I would also like a windows EXE built by someone I trust and who's identity I know.
-
The seed nodes are just addnodes that were thrown around.
If you want nodes you can control, you need only fire up a few VPS and then use them as the seednodes.
As for windows compilation, i am unable to do that part for the time being. Pull request is being refused, please follow link for modified file.
https://drive.google.com/file/d/0BxCtiOzdwvPyYkpGdXJBZkZsX0k/edit?usp=sharing (https://drive.google.com/file/d/0BxCtiOzdwvPyYkpGdXJBZkZsX0k/edit?usp=sharing)
-
Here is barwizi's change as a pull request:
https://github.com/InvictusInnovations/ProtoShares/pull/5
If you guys can guarantee reimbursement I'd be glad to make a DO account and spin up some dedicated nodes.
-
Here is barwizi's change as a pull request:
https://github.com/InvictusInnovations/ProtoShares/pull/5
If you guys can guarantee reimbursement I'd be glad to make a DO account and spin up some dedicated nodes.
We will fund this reimbursement in PTS from the Angel fund. As this effort is collaborative each of you must agree as to how to divide the 50 PTS among yourselves to deliver the complete solution. The solution will be complete when I can post an updated download link and people have a positive experience.
-
The issue people have is finding nodes to connect to not downloading the chain.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
I added a 'churn' option to MemoryCoin to help with this. It allows a seed node to be started so that it maintains outbound connections, but churns (disconnects) inbound connections after 10 minutes, hopefully allowing new users to connect, get a list of good nodes, and disconnect. Small addition to the source to do it.
-
Ok, I'm setting up a DO droplet. I'll report when it's built and blockchain is downloaded. Once we confirm it works, I'll write a setup script and spin up 5-10 instances, then update the pull request with the new IP addresses.
-
Built from source with the new change and got some connections right away!
{
"version" : 80600,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 8639,
"timeoffset" : -1,
"connections" : 5,
"proxy" : "",
"difficulty" : 0.00001526,
"testnet" : false,
"keypoololdest" : 1388266820,
"keypoolsize" : 101,
"paytxfee" : 0.01000000,
"errors" : ""
}
Current droplet at: 162.243.197.231
I used addnode with this IP with the old client and it found some connections right away. So far I've built and tested the daemon on ubuntu. We need someone to build and test the QT client on windows (I don't have a windows machine), and then we're good!
-
Actually, we should decide how many nodes we want / who we want to own them (should be distributed among a few people IMO) and then update the pull request.
Any volunteers for hosting seed nodes? Hosting costs will be reimbursed and I can provide a setup script pretty soon.
-
sudo apt-get update && sudo apt-get install git make g++ build-essential libminiupnpc-dev libboost-all-dev libdb++-dev libgmp-dev libssl-dev dos2unix
git clone https://github.com/InvictusInnovations/ProtoShares
cd Protoshares/src
make -f makefile.unix
echo "rpcuser=[youruser]" >> /root/.protoshares/protoshares.conf
echo "rpcpassword=[yourpass]" >> /root/.protoshares/protoshares.conf
./bitcoind -daemon
./bitcoind setgenerate true 3
since it's a vps, you may as well mine with it.
-
I love the team work!
Free trades fix needs to be part of the solution because my seed node fills up and stops accepting connections. I have to kill it every 15 minutes to keep things working.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
I love the team work!
Free trades fix needs to be part of the solution because my seed node fills up and stops accepting connections. I have to kill it every 15 minutes to keep things working.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Quick-n-dirty solution would be to just set a cron job to kill and restart the node, if that indeed does work.
Someone check this (goes in crontab)?
* * 15 * * ps -eo pid,args | grep bitcoind | awk '{print $1}' | xargs -I {} kill -9 {} && ~/ProtoShares/src/bitcoind -daemon
-
Modified files here https://drive.google.com/folderview?id=0BxCtiOzdwvPyTUZ2UjhaQXFDOHM&usp=sharing (https://drive.google.com/folderview?id=0BxCtiOzdwvPyTUZ2UjhaQXFDOHM&usp=sharing)
net.cpp and init.cpp
I added the churn function
just replace and build or push
My upload streams are both unreliable, cant seem to push to github
-
Added your changes and my new seed node, they're in the same pull request
https://github.com/InvictusInnovations/ProtoShares/pull/5
for some reason the diffs on github aren't working properly, can you copy/paste the parts you changed here so we can see?
-
Mission acomplished, now....who gets what %?
-
Let's make sure it builds and runs on all platforms first, and maybe see what I3 guys say about how many dedicated seeds they want?
I'm fine with 20 for me and 30 for you, assuming we'll get paid for hosting separately.
I did:
Set up new working seed and github stuff. Also was working on setup script but you got to it first. Gonna set up more seeds if bytemaster wants them.
you did:
Setup script, churn code (how hard was this? was very fast, I assume you used freetrade's code for this), found the list of working seed IPs
still to do: build working pts-qt for windows
-
Mission acomplished, now....who gets what %?
No idea - but if it pans out and if I'm due something here's my PTS - PnARJi1wbdCUGMzdck16xe5RKpf3eYBmQP
-
I think 3 plus my current seed node for a total of 4 will be fine. Not all at DO though 4 different providers.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
I think 3 plus my current seed node for a total of 4 will be fine. Not all at DO though 4 different providers.
Wait so are you saying your current node is DO? Can I use the one I just set up plus two more (say, linode and rackspace)?
-
This is now complicated.
-
Yeah I agree, I think the bounty should be bumped a bit?
Having new nodes or requires setting up nodes with different providers wasn't part of the original spec.
I'm AFK for a while, someone else want to set up nodes on non-DO servers?
-
Yeah I agree, I think the bounty should be bumped a bit?
Having new nodes or requires setting up nodes with different providers wasn't part of the original spec.
I'm AFK for a while, someone else want to set up nodes on non-DO servers?
I provided fix for the initial bounty and his request to add Freetrades mod. You pushed the fixes and created a node. So maybe he'll compansate for the extra work if we are lucky.
-
PiNEJGUv4AZVZkLuF6hV4xwbYTRp5etWWJ
-
Yo, it doesn't build anymore after the churn fix
init.cpp: In function ‘bool AppInit2(boost::thread_group&)’:
init.cpp:498:22: error: ‘setChurnMode’ was not declared in this scope
make: *** [obj/init.o] Error 1
edit: derp, wasn't in the header
-
Did you try building and testing your change? There were compile errors
net.cpp: In function ‘void setChurnMode()’:
net.cpp:77:29: error: assignment of read-only variable ‘MAX_OUTBOUND_CONNECTIONS’
net.cpp: In function ‘void ThreadOpenConnections()’:
Fixed by making MAX_OUTBOUND_CONNECTIONS not a static const
Is my churn usage understanding correct? I'm changing your script to use the new flag:
sudo apt-get update && sudo apt-get install git make g++ build-essential libminiupnpc-dev libboost-all-dev libdb++-dev libgmp-dev libssl-dev dos2unix
git clone https://github.com/InvictusInnovations/ProtoShares
cd Protoshares/src
make -f makefile.unix
echo "rpcuser=[youruser]" >> /root/.protoshares/protoshares.conf
echo "rpcpassword=[yourpass]" >> /root/.protoshares/protoshares.conf
./bitcoind -daemon -churn
./bitcoind setgenerate true 3
-
Ok, I'm setting up a DO droplet. I'll report when it's built and blockchain is downloaded. Once we confirm it works, I'll write a setup script and spin up 5-10 instances, then update the pull request with the new IP addresses.
I don't want to pay for more instances than necessary, so can we justify the monthly cost of 5-10 instances vs just 5?
-
it did compile on mine, strange. oh, i know why it gave you that error, net.h was missing from the files i uploaded. follow the link again, it should be there.
-
oh, you already got around it, cool. churn, is Freetrade's item, he'd know best.
-
Would like bytemaster to comment:
Can we make hosting nodes a separate bounty? Maybe like, 2 PTS plus the cost of hosting, for the first 4 people who use a new provider (I did the first one with DO). That way the seed nodes aren't all controlled by one person, and people who already have accounts on other hosting services can set it up. We already have the setup script and everything. We could hard-code the IPs later once they are set up, there is already enough to have new nodes connect successfully.
If we do that, I think 50 PTS is still fair, even though we did more than was strictly necessary to satisfy the initial requirements. I say a token 2 PTS to freetrade for his suggestion, then 20 to me and 28 to barwizi.
-
Would like bytemaster to comment:
Can we make hosting nodes a separate bounty? Maybe like, 2 PTS plus the cost of hosting, for the first 4 people who use a new provider (I did the first one with DO). That way the seed nodes aren't all controlled by one person, and people who already have accounts on other hosting services can set it up. We already have the setup script and everything. We could hard-code the IPs later once they are set up, there is already enough to have new nodes connect successfully.
If we do that, I think 50 PTS is still fair, even though we did more than was strictly necessary to satisfy the initial requirements. I say a token 2 PTS to freetrade for his suggestion, then 20 to me and 28 to barwizi.
Agreed. I will start a new bounty for that, with a maximum hosting cost of $10 per month because many people are probably already running servers that are not at full capacity and adding an extra service is not costing them anything extra.
-
So what else do we have to do to claim this? The pull request is ready and has been tested on ubuntu.
There are build errors on OSX, but they are totally unrelated to our changes. Is this expected? Error below.
I don't have a way to test on windows.
/Users/nikolai/ProtoShares/src/serialize.h:911:10: error: class member cannot be redeclared
void insert(iterator it, std::vector<char>::const_iterator first, std::vector<char>::const_iterator last)
^
/Users/nikolai/ProtoShares/src/serialize.h:898:10: note: previous declaration is here
void insert(iterator it, const_iterator first, const_iterator last)
^
/Users/nikolai/ProtoShares/src/serialize.h:911:10: error: redefinition of 'insert'
void insert(iterator it, std::vector<char>::const_iterator first, std::vector<char>::const_iterator last)
^
/Users/nikolai/ProtoShares/src/serialize.h:898:10: note: previous definition is here
void insert(iterator it, const_iterator first, const_iterator last)
^
-
Is my churn usage understanding correct? I'm changing your script to use the new flag:
sudo apt-get update && sudo apt-get install git make g++ build-essential libminiupnpc-dev libboost-all-dev libdb++-dev libgmp-dev libssl-dev dos2unix
git clone https://github.com/InvictusInnovations/ProtoShares
cd Protoshares/src
make -f makefile.unix
echo "rpcuser=[youruser]" >> /root/.protoshares/protoshares.conf
echo "rpcpassword=[yourpass]" >> /root/.protoshares/protoshares.conf
./bitcoind -daemon -churn
./bitcoind setgenerate true 3
I think so - check your log to ensure that you're getting notices of disconnections due to churn.
Also you might want to play around with the default numbers. For the MC network, I chose the default number of outgoing connections to be 4 - you might want to stick with 8. I think I set the number of outgoing connections for a churn node to be 50, but you might want more if you have a bigger network.
-
this is ridiculous, there never was an issue to begin with
while you're bust distributing money to people that have done absolutely nothing, i've been running a dedicated node for a month
"version" : 80600,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 36221,
"timeoffset" : -1,
"connections" : 375,
"proxy" : "",
"difficulty" : 0.01203577,
"testnet" : false,
"keypoololdest" : 1384922232,
"keypoolsize" : 6,
"paytxfee" : 0.01000000,
"errors" : ""
the solution was obvious, fix the seed node list
i have noticed i've been getting more connections lately. i'd hate to be a source of free money for someone that's done two things: jack and shit. so if i find that it's on a new seed node list, i'll take it down
-
this is ridiculous, there never was an issue to begin with
while you're bust distributing money to people that have done absolutely nothing, i've been running a dedicated node for a month
"version" : 80600,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 36221,
"timeoffset" : -1,
"connections" : 375,
"proxy" : "",
"difficulty" : 0.01203577,
"testnet" : false,
"keypoololdest" : 1384922232,
"keypoolsize" : 6,
"paytxfee" : 0.01000000,
"errors" : ""
the solution was obvious, fix the seed node list
i have noticed i've been getting more connections lately. i'd hate to be a source of free money for someone that's done two things: jack and shit. so if i find that it's on a new seed node list, i'll take it down
First of all there is an issue that I have observed. The fix requires providing a new binary with free trades churn arg. As I do not have time nor a windows machine to produce the binaries and our other devs are busy it is easily worth $1000 to save our time.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
ZVS, do you have a windows machine?
If you build the new source on a windows machine you can get in on this bounty. Yes, the original issue was just that their seed nodes list was bad but since then we've made a few other improvements too. Also, in this thread we've had bytemaster confirm that he'll reimburse up to $10 a month for people who run seed nodes, up to 4 total nodes on distinct providers.
https://github.com/nmushegian/ProtoShares/tree/psforkinit
-
this is ridiculous, there never was an issue to begin with
while you're bust distributing money to people that have done absolutely nothing, i've been running a dedicated node for a month
"version" : 80600,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 36221,
"timeoffset" : -1,
"connections" : 375,
"proxy" : "",
"difficulty" : 0.01203577,
"testnet" : false,
"keypoololdest" : 1384922232,
"keypoolsize" : 6,
"paytxfee" : 0.01000000,
"errors" : ""
the solution was obvious, fix the seed node list
i have noticed i've been getting more connections lately. i'd hate to be a source of free money for someone that's done two things: jack and shit. so if i find that it's on a new seed node list, i'll take it down
First of all there is an issue that I have observed. The fix requires providing a new binary with free trades churn arg. As I do not have time nor a windows machine to produce the binaries and our other devs are busy it is easily worth $1000 to save our time.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
I'd like to point out that I feel this is not in the spirit of the bounty, the bounty is for a fix for synchronization time. That i completed on my second try. FreeTrade then mentioned that he has a util "churn" and you asked that it be added, which i did, but that was already past the "fix". You did not mention the need for windows or osx in the OP. All further work such as providing binaries and other patches is separate and was done on request, it is up to you whether you wish to pay for it but i feel the terms of this bounty have been met.
In response to ZVS, the difference between you having a permanent seed node, and my Hard-coding them into the client is that my fix affects everyone, it meets the requirement. Instead of having to either browse through threads for addnodes or waiting for the client to discover on it's own, it will just start by connecting to an always on node, which greatly shortens the time required to sync.
As for windows build, it is not part of the bounty but i will try to get the dependencies nw that i have a windows machine and try my hand at it. Which version of boost is necessary by the way?
As part of the fix, i think i may as well include a checkpoint since I don't think we need daily builds. Osx is another thing altogether, toast, can you try it out?
-
...
First of all there is an issue that I have observed. The fix requires providing a new binary with free trades churn arg. As I do not have time nor a windows machine to produce the binaries and our other devs are busy it is easily worth $1000 to save our time.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
I'd like to point out that I feel this is not in the spirit of the bounty, the bounty is for a fix for synchronization time. That i completed on my second try. FreeTrade then mentioned that he has a util "churn" and you asked that it be added, which i did, but that was already past the "fix" as you did not mention the need for windows or osx in the OP. All further work such as providing binaries and other patches is separate and was done on request, it is up to you whether you wish to pay for it but i feel the terms of this bounty have been met.
Totally agree, most of the work we did was for stuff tacked on as the thread evolved.
As for windows build, it is not part of the bounty but i will try to get the dependencies nw that i have a windows machine and try my hand at it. Which version of boost is necessary by the way?
Check out doc/build-msw.md
-
This bounty is still in the pending state until the full specification for this bounty can be defined. If you would like to tackle this bounty help us define the SPEC and requirements first.
We are working to clarify the bounty process, but experience has taught me that there must be two-way communication before there can be a full meeting of the minds. I started the process, but I do not consider this bounty won until someone can download a Windows-Qt binary and have it connect from a fresh PC within a couple of minutes.
We discussed the requirements in the thread. I know as a fact that simply having a seed node without churn will not solve this problem, I already have a seed node with a hack to implement churn. Recognizing that having additional/redundant seed nodes is also part of the process I spawned of separate bounties for that which means that simply updating the nodes listed is not enough. I need a working binary built by a trusted source combined with the commit.
-
Provide a working solution that allows someone to download a PTS wallet and get connected to the network in less than 5 minutes.
Show me where I can download a PTS wallet and get connected that quickly? I see the code, but the job is only half done.
-
Provide a working solution that allows someone to download a PTS wallet and get connected to the network in less than 5 minutes.
Show me where I can download a PTS wallet and get connected that quickly? I see the code, but the job is only half done.
That's not really applicable here, you are the dev, as a result it falls to you to provide for your windows users. Keep in mind the risks involved with just anyone building it. Do it yourself, risking malware, wallet stealers and other risks involved is not worth it.
BTW, i tried to build it, but the dependencies listed in the build-msw.md are incorrect and incomplete for building on windows.
-
this is ridiculous, there never was an issue to begin with
while you're bust distributing money to people that have done absolutely nothing, i've been running a dedicated node for a month
"version" : 80600,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 36221,
"timeoffset" : -1,
"connections" : 375,
"proxy" : "",
"difficulty" : 0.01203577,
"testnet" : false,
"keypoololdest" : 1384922232,
"keypoolsize" : 6,
"paytxfee" : 0.01000000,
"errors" : ""
the solution was obvious, fix the seed node list
i have noticed i've been getting more connections lately. i'd hate to be a source of free money for someone that's done two things: jack and shit. so if i find that it's on a new seed node list, i'll take it down
First of all there is an issue that I have observed. The fix requires providing a new binary with free trades churn arg. As I do not have time nor a windows machine to produce the binaries and our other devs are busy it is easily worth $1000 to save our time.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
I'd like to point out that I feel this is not in the spirit of the bounty, the bounty is for a fix for synchronization time. That i completed on my second try. FreeTrade then mentioned that he has a util "churn" and you asked that it be added, which i did, but that was already past the "fix". You did not mention the need for windows or osx in the OP. All further work such as providing binaries and other patches is separate and was done on request, it is up to you whether you wish to pay for it but i feel the terms of this bounty have been met.
In response to ZVS, the difference between you having a permanent seed node, and my Hard-coding them into the client is that my fix affects everyone, it meets the requirement. Instead of having to either browse through threads for addnodes or waiting for the client to discover on it's own, it will just start by connecting to an always on node, which greatly shortens the time required to sync.
As for windows build, it is not part of the bounty but i will try to get the dependencies nw that i have a windows machine and try my hand at it. Which version of boost is necessary by the way?
As part of the fix, i think i may as well include a checkpoint since I don't think we need daily builds. Osx is another thing altogether, toast, can you try it out?
It probably wouldn't be hard to copy it out of bitcoin's code, right? lol.
bitcoin-seeder updated regularly & peer receiving this information via DNS request, http://luke.dashjr.org/programs/bitcoin/files/charts/seeds.txt
the current seed nodes provided are either down or full. that is why people have problems.
besides that, a tip: in main.cpp, the timeout delays in "Inactivity Checking" are way too long
-
this is ridiculous, there never was an issue to begin with
while you're bust distributing money to people that have done absolutely nothing, i've been running a dedicated node for a month
"version" : 80600,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 36221,
"timeoffset" : -1,
"connections" : 375,
"proxy" : "",
"difficulty" : 0.01203577,
"testnet" : false,
"keypoololdest" : 1384922232,
"keypoolsize" : 6,
"paytxfee" : 0.01000000,
"errors" : ""
the solution was obvious, fix the seed node list
i have noticed i've been getting more connections lately. i'd hate to be a source of free money for someone that's done two things: jack and shit. so if i find that it's on a new seed node list, i'll take it down
First of all there is an issue that I have observed. The fix requires providing a new binary with free trades churn arg. As I do not have time nor a windows machine to produce the binaries and our other devs are busy it is easily worth $1000 to save our time.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
I'd like to point out that I feel this is not in the spirit of the bounty, the bounty is for a fix for synchronization time. That i completed on my second try. FreeTrade then mentioned that he has a util "churn" and you asked that it be added, which i did, but that was already past the "fix". You did not mention the need for windows or osx in the OP. All further work such as providing binaries and other patches is separate and was done on request, it is up to you whether you wish to pay for it but i feel the terms of this bounty have been met.
In response to ZVS, the difference between you having a permanent seed node, and my Hard-coding them into the client is that my fix affects everyone, it meets the requirement. Instead of having to either browse through threads for addnodes or waiting for the client to discover on it's own, it will just start by connecting to an always on node, which greatly shortens the time required to sync.
As for windows build, it is not part of the bounty but i will try to get the dependencies nw that i have a windows machine and try my hand at it. Which version of boost is necessary by the way?
As part of the fix, i think i may as well include a checkpoint since I don't think we need daily builds. Osx is another thing altogether, toast, can you try it out?
It probably wouldn't be hard to copy it out of bitcoin's code, right? lol.
bitcoin-seeder updated regularly & peer receiving this information via DNS request, http://luke.dashjr.org/programs/bitcoin/files/charts/seeds.txt
the current seed nodes provided are either down or full. that is why people have problems.
besides that, a tip: in main.cpp, the timeout delays in "Inactivity Checking" are way too long
lol, last i heard PTS was based on bitcoin. and for some it's not so easy. i was just lucky that it was something i had read somewhere and knew how to find it. As for the bitcoin seeder....i see no relevance to the PTS chain.
the whole vps always on seednode thing + churn sweetens the pot.
-
C:\ProtoShares-psforkinit\ProtoShares-psforkinit\src>make -f Makefile.Release
Makefile.Release:194: *** missing separator. Stop.
this is where i am stuck making the windows build now.
-
bytemaster, who built the previous versions of the windows client?
-
Freetrade
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
I am aware of the risks regarding who builds the client.
If you want me to pull our windows devs from keyhotee to build it then I will ask them to estimate a rate. Otherwise I think freetrade will do it for a reasonable share.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Let's try freetrade first, gonna pm him now
-
Let's try freetrade first, gonna pm him now
Yes, I'll do this later today when I get a few moments.
-
So I compiled, but the new version isn't finding any nodes after 10 minutes.
I think you need to remove all the old/dead/full nodes from net.cpp and only include ones that are running with -churn
-
As a sanity check, is this your seed nodes list?
static const char *strMainNetDNSSeed[][2] = {
{"49.89.6.185", "49.89.6.185"},
{"222.174.212.250", "222.174.212.250"},
{"183.8.183.73", "183.8.183.73"},
{"173.208.148", "173.208.148"},
{"169.237.74.213", "169.237.74.213"},
{"175.42.27.186","175.42.27.186"},
{"162.243.197.231", "162.243.197.231"},
{NULL, NULL}
};
We're not working on master, but on psforkinit
-
on 162.243.197.231
root 2232 0.5 16.3 819396 167068 ? SLsl Dec28 7:18 ./bitcoind -daemon -churnroot@seedpts1:~# ProtoShares/src/bitcoind getinfo
{
"version" : 80600,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 36478,
"timeoffset" : 0,
"connections" : 38,
"proxy" : "",
"difficulty" : 0.00994143,
"testnet" : false,
"keypoololdest" : 1388266820,
"keypoolsize" : 101,
"paytxfee" : 0.01000000,
"errors" : ""
}
-
Hmm, looks like github hasn't been updated with anything in 3 weeks - let me know it's updated and I'll try to compile again. I don't want to get drawn into source control or editing as I'm busy with MemoryCoin.
-
As a sanity check, is this your seed nodes list?
static const char *strMainNetDNSSeed[][2] = {
{"49.89.6.185", "49.89.6.185"},
{"222.174.212.250", "222.174.212.250"},
{"183.8.183.73", "183.8.183.73"},
{"173.208.148", "173.208.148"},
{"169.237.74.213", "169.237.74.213"},
{"175.42.27.186","175.42.27.186"},
{"162.243.197.231", "162.243.197.231"},
{NULL, NULL}
};
We're not working on master, but on psforkinit
https://github.com/nmushegian/ProtoShares/tree/psforkinit
No idea why it's this way, I just went with what the invictus repo is doing
-
...
First of all there is an issue that I have observed. The fix requires providing a new binary with free trades churn arg. As I do not have time nor a windows machine to produce the binaries and our other devs are busy it is easily worth $1000 to save our time.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
I'd like to point out that I feel this is not in the spirit of the bounty, the bounty is for a fix for synchronization time. That i completed on my second try. FreeTrade then mentioned that he has a util "churn" and you asked that it be added, which i did, but that was already past the "fix" as you did not mention the need for windows or osx in the OP. All further work such as providing binaries and other patches is separate and was done on request, it is up to you whether you wish to pay for it but i feel the terms of this bounty have been met.
Totally agree, most of the work we did was for stuff tacked on as the thread evolved.
As for windows build, it is not part of the bounty but i will try to get the dependencies nw that i have a windows machine and try my hand at it. Which version of boost is necessary by the way?
Check out doc/build-msw.md
I worked on formatting those Bitcoin docs at some point. I can tell you most of that content is probably incorrect or out of date.
-
Seems Freetrade has it under control. But now we have branch issues, bytemaster i think that is your que.
-
Seems Freetrade has it under control. But now we have branch issues, bytemaster i think that is your que.
FreeTrade has permissions on the repository. As my head is not in the code it would probably be better for him to merge it.
Make sure we increment the version number for this build. We overlooked that and people complained last time.
-
The git needs attention, else we cant do this. while master branch uses autotools, psforkinit uses .pro. we need sanity checks, merges and revision notes. Maybe open up a request for someone to manage the git.
-
As far as I can tell psforkinit is the main branch, and nobody has been working on master for a while now. This does seem wrong, though.
The version on nmushegian/psforkinit is what we want, right?
-
As far as I can tell psforkinit is the main branch, and nobody has been working on master for a while now. This does seem wrong, though.
The version on nmushegian/psforkinit is what we want, right?
I agree the code should be migrated back to the master. We ended up this way in the mad rush to solve the crashing Linux server after our first fork.
-
So then...what now? This bounty will be on hold until someone sorts this out?
-
Sorting the branch out is not part of this bounty.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Use the fork branch and I will create a new bounty to merge them in a sane way
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Okay, nice - I compiled nmushegian/psforkinit and new client finds a connection within a few seconds - will upload and send BM a link by PM.
-
Okay, nice - I compiled nmushegian/psforkinit and new client finds a connection within a few seconds - will upload and send BM a link by PM.
http://the-iland.net/static/downloads/ProtoShares-0.4.0.zip
Can someone verify FreeTrade's latest submission (I don't have windows here) and make sure that the version number has been bumped from the prior clients and verify that it connects rapidly. If everything checks out, please give me the address of one person to pay who will be responsible for dividing up the payment.
-
I say FreeTrade splits it up since he has the most rep around here. Put all three of us (barwizi/toast/freetrade) on the google doc though.
Even 3-way split sound good? Also ok with giving barwizi a bit more than 1/3rd, maybe 20/15/15
edit: sp
-
I say FreeTrade splits it up since he has the most rep around here. Put all three of us (barwizi/toast/freetrade) on the google doc though.
Even 3-way split sound good? Also ok with giving barwizi a bit more than 1/3rd, maybe 20/15/15
edit: sp
If the google doc is updated 3 way, I might as well send 3 different transactions. I just want to avoid having to be responsible for recording 3x as many transactions. If this is about credit then I will do three entries and send 3 payments.
I think FreeTrade was good with what ever reward. So if barwizi is good with 20 PTS then that is the only confirmation I need.
-
Fine by me, about time i roamed about for other bounties
PiNEJGUv4AZVZkLuF6hV4xwbYTRp5etWWJ
-
funds to signature
-
I just need a PTS address from FreeTrade
-
Mission acomplished, now....who gets what %?
No idea - but if it pans out and if I'm due something here's my PTS - PnARJi1wbdCUGMzdck16xe5RKpf3eYBmQP
Thanks
-
Mission acomplished, now....who gets what %?
No idea - but if it pans out and if I'm due something here's my PTS - PnARJi1wbdCUGMzdck16xe5RKpf3eYBmQP
Thanks
care to share how you got around the error i was encountering?
-
estimate on time of payment? :P
-
estimate on time of payment? :P
I didn't want to take funds out of the Angel fund until after the first day has closed because people using block explorers to estimate the balance might get confused. On the other hand maybe it will be ok to send payments now. Thoughts?
-
:-\ seems all the same. my personal preference is now so i close books for the year, there is only 6 hours left of 2013 for me.
-
In any case you'll have to instruct whoever writes the angelshare explorer to use the "total received" instead of "final balance" for computing contributions. It's probably a good idea to wait to see that they've done this correctly. You could send some of I3's own PTS and then pay yourself back from the fund later, not too hard to just make a note of what happened.
-
In any case you'll have to instruct whoever writes the angelshare explorer to use the "total received" instead of "final balance" for computing contributions. It's probably a good idea to wait to see that they've done this correctly. You could send some of I3's own PTS and then pay yourself back from the fund later, not too hard to just make a note of what happened.
Not really a problem, we can calculate the proper AGS allocation at any time in the future. All that matters is funds received, not funds sent or balance. The purpose of the address is to allow us to raise funds to spend.
-
Can you open the seed node bounty? I'd like to prepay for a year on my DO node. I think it should be (1 PTS + ($10 x months)) ~= 7 PTS for a year.
-
Can you open the seed node bounty? I'd like to prepay for a year on my DO node. I think it should be (1 PTS + ($10 x months)) ~= 7 PTS for a year.
We will pay this month-to-month as I expect PTS to rise dramatically over that time ;)
-
Good point. Also then you can't have people take down their node and run off with the shares.
-
If my stake in PTS grows larger than 1000 i will run a high speed/ bandwidth node at work.
-
Can someone find or post a single run bash script to compile and run Protoshares from source? Should auto-generate a random rpc user and pass, and increase max connections.
Once that is done I can host it on Protoshares.com and automatically launch at least 3 permanent seednodes at my expense.
To make DAC launches easier I can probably launch temporarily ~50 seed nodes, but I need a script that takes out all the manual work first.
-
Host away super3 no need for more than 3
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Host away super3 no need for more than 3
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
I think in the future I can use Digital Ocean's API to launch as many seed nodes as we want for the first few days. This should make DAC launches as smooth as possible and not have everyone scrambling for seeds at launch or slow block downloads.
-
Can someone find or post a single run bash script to compile and run Protoshares from source? Should auto-generate a random rpc user and pass, and increase max connections.
Once that is done I can host it on Protoshares.com and automatically launch at least 3 permanent seednodes at my expense.
To make DAC launches easier I can probably launch temporarily ~50 seed nodes, but I need a script that takes out all the manual work first.
From earlier in the thread:
sudo apt-get update && sudo apt-get install git make g++ build-essential libminiupnpc-dev libboost-all-dev libdb++-dev libgmp-dev libssl-dev dos2unix
git clone https://github.com/InvictusInnovations/ProtoShares
cd Protoshares/src
make -f makefile.unix
echo "rpcuser=[youruser]" >> /root/.protoshares/protoshares.conf
echo "rpcpassword=[yourpass]" >> /root/.protoshares/protoshares.conf
./bitcoind -daemon -churn
./bitcoind setgenerate true 3
Once you get some seed nodes up you should post them in this thread so we can get them baked into the client
-
here's what happens when I take my node down for 30 minutes, guess what my block total is?
2014-01-08 18:46:34 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=219.142.145.176:55045
2014-01-08 18:46:35 receive version message: version 70001, blocks=40615, us=5.9.24.81:29977, them=46.4.63.71:3888, peer=46.4.63.71:3888
2014-01-08 18:46:35 receive version message: version 70001, blocks=40615, us=5.9.24.81:14332, them=23.92.25.118:3888, peer=23.92.25.118:3888
2014-01-08 18:46:44 receive version message: version 70001, blocks=40615, us=5.9.24.81:14936, them=79.223.151.58:3888, peer=79.223.151.58:3888
2014-01-08 18:46:46 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=121.27.104.83:1622
2014-01-08 18:46:48 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=59.108.29.48:11270
2014-01-08 18:46:50 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=183.14.85.84:49537
2014-01-08 18:46:50 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=171.223.131.28:7200
2014-01-08 18:46:50 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=58.243.104.22:12675
2014-01-08 18:46:50 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=99.227.219.44:56856
2014-01-08 18:46:51 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=27.158.179.242:64193
2014-01-08 18:46:55 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=113.68.10.137:59149
2014-01-08 18:46:55 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=218.242.174.226:55255
2014-01-08 18:46:57 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=125.69.28.89:59297
2014-01-08 18:46:59 receive version message: version 70001, blocks=40615, us=5.9.24.81:16389, them=192.241.228.126:3888, peer=192.241.228.126:3888
2014-01-08 18:47:02 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=112.192.69.244:3943
(i missed 25 seconds here, since i reset the log)
2014-01-08 18:47:29 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=111.201.22.38:50351
2014-01-08 18:47:29 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=59.175.59.64:3820
2014-01-08 18:47:38 receive version message: version 70001, blocks=40615, us=5.9.24.81:27708, them=46.238.28.249:3888, peer=46.238.28.249:3888
2014-01-08 18:47:39 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=60.191.254.118:36897
2014-01-08 18:47:43 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=36.251.214.82:27798
2014-01-08 18:47:50 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=122.226.253.39:48743
2014-01-08 18:47:51 receive version message: version 70001, blocks=40615, us=5.9.24.81:52250, them=91.218.212.181:3888, peer=91.218.212.181:3888
2014-01-08 18:48:04 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=174.140.166.70:44019
2014-01-08 18:48:04 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=120.42.46.6:14093
2014-01-08 18:48:05 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=220.173.129.103:40248
2014-01-08 18:48:05 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=59.172.101.129:3901
2014-01-08 18:48:09 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=222.179.116.154:64516
2014-01-08 18:48:12 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=183.16.190.66:64700
2014-01-08 18:48:17 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=58.22.83.71:55873
2014-01-08 18:48:17 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=122.136.176.34:64164
2014-01-08 18:48:17 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=183.2.80.158:26435
2014-01-08 18:48:21 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=182.151.214.182:2941
2014-01-08 18:48:22 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=151.50.109.120:3888, peer=151.50.109.120:51747
2014-01-08 18:48:28 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=113.17.59.152:57093
2014-01-08 18:48:29 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=60.191.254.117:51421
2014-01-08 18:48:29 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=116.27.69.251:35091
2014-01-08 18:48:32 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=218.65.5.210:1495
2014-01-08 18:48:42 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=183.44.79.168:26272
2014-01-08 18:49:27 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=60.168.238.74:1745
2014-01-08 18:49:38 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=77.247.181.164:11546
2014-01-08 18:49:50 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=124.237.77.48:63330
2014-01-08 18:50:09 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=113.245.87.60:54843
2014-01-08 18:50:13 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=220.173.134.223:17644
2014-01-08 18:50:22 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=171.34.70.232:27141
2014-01-08 18:50:23 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=14.108.44.172:2341
2014-01-08 18:50:29 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=116.27.69.251:35249
gg
-
here's what happens when I take my node down for 30 minutes, guess what my block total is?
2014-01-08 18:46:34 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=219.142.145.176:55045
2014-01-08 18:46:35 receive version message: version 70001, blocks=40615, us=5.9.24.81:29977, them=46.4.63.71:3888, peer=46.4.63.71:3888
2014-01-08 18:46:35 receive version message: version 70001, blocks=40615, us=5.9.24.81:14332, them=23.92.25.118:3888, peer=23.92.25.118:3888
2014-01-08 18:46:44 receive version message: version 70001, blocks=40615, us=5.9.24.81:14936, them=79.223.151.58:3888, peer=79.223.151.58:3888
2014-01-08 18:46:46 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=121.27.104.83:1622
2014-01-08 18:46:48 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=59.108.29.48:11270
2014-01-08 18:46:50 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=183.14.85.84:49537
2014-01-08 18:46:50 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=171.223.131.28:7200
2014-01-08 18:46:50 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=58.243.104.22:12675
2014-01-08 18:46:50 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=99.227.219.44:56856
2014-01-08 18:46:51 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=27.158.179.242:64193
2014-01-08 18:46:55 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=113.68.10.137:59149
2014-01-08 18:46:55 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=218.242.174.226:55255
2014-01-08 18:46:57 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=125.69.28.89:59297
2014-01-08 18:46:59 receive version message: version 70001, blocks=40615, us=5.9.24.81:16389, them=192.241.228.126:3888, peer=192.241.228.126:3888
2014-01-08 18:47:02 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=112.192.69.244:3943
(i missed 25 seconds here, since i reset the log)
2014-01-08 18:47:29 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=111.201.22.38:50351
2014-01-08 18:47:29 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=59.175.59.64:3820
2014-01-08 18:47:38 receive version message: version 70001, blocks=40615, us=5.9.24.81:27708, them=46.238.28.249:3888, peer=46.238.28.249:3888
2014-01-08 18:47:39 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=60.191.254.118:36897
2014-01-08 18:47:43 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=36.251.214.82:27798
2014-01-08 18:47:50 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=122.226.253.39:48743
2014-01-08 18:47:51 receive version message: version 70001, blocks=40615, us=5.9.24.81:52250, them=91.218.212.181:3888, peer=91.218.212.181:3888
2014-01-08 18:48:04 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=174.140.166.70:44019
2014-01-08 18:48:04 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=120.42.46.6:14093
2014-01-08 18:48:05 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=220.173.129.103:40248
2014-01-08 18:48:05 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=59.172.101.129:3901
2014-01-08 18:48:09 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=222.179.116.154:64516
2014-01-08 18:48:12 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=183.16.190.66:64700
2014-01-08 18:48:17 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=58.22.83.71:55873
2014-01-08 18:48:17 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=122.136.176.34:64164
2014-01-08 18:48:17 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=183.2.80.158:26435
2014-01-08 18:48:21 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=182.151.214.182:2941
2014-01-08 18:48:22 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=151.50.109.120:3888, peer=151.50.109.120:51747
2014-01-08 18:48:28 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=113.17.59.152:57093
2014-01-08 18:48:29 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=60.191.254.117:51421
2014-01-08 18:48:29 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=116.27.69.251:35091
2014-01-08 18:48:32 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=218.65.5.210:1495
2014-01-08 18:48:42 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=183.44.79.168:26272
2014-01-08 18:49:27 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=60.168.238.74:1745
2014-01-08 18:49:38 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=77.247.181.164:11546
2014-01-08 18:49:50 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=124.237.77.48:63330
2014-01-08 18:50:09 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=113.245.87.60:54843
2014-01-08 18:50:13 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=220.173.134.223:17644
2014-01-08 18:50:22 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=171.34.70.232:27141
2014-01-08 18:50:23 receive version message: version 70001, blocks=40615, us=5.9.24.81:3888, them=0.0.0.0:0, peer=14.108.44.172:2341
2014-01-08 18:50:29 receive version message: version 70001, blocks=40599, us=5.9.24.81:3888, them=0.0.0.0:0, peer=116.27.69.251:35249
gg
Probably not everyone has updated their client which has new seed nodes