|
|
|
|
|
|
|
|
|
|
|
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
WarrEagle
|
 |
September 11, 2014, 02:45:56 AM |
|
Figures I get an offline wallet and cannot get it to sync with the network. Debug logs show connection timeouts when attempting to connect to peers. I can ping the IP's but cant connect with the wallet. Any suggestions? I have 400K coins sent to my wallet ID, then noticed it would not sync. ARRRGHHH.
|
DELETED
|
|
|
|
WarrEagle
|
|
September 11, 2014, 04:01:46 AM |
|
Baffled....this is a first when trying to use a wallet.
Done loading
ThreadOpenConnections started
refreshWallet
ThreadStakeMiner started
ThreadMessageHandler started
Flushed 2 addresses to peers.dat 59ms
keypool added key 118, size=101
4 addresses found from DNS seeds
ThreadDNSAddressSeed exited
trying connection 198.144.184.175:22223 lastseen=91.5hrs
ipcThread started
UPnP: ExternalIPAddress = 75.76.64.183
AddLocal(75.76.64.183:22223,3)
UPnP Port Mapping successful.
Flushing wallet.dat
Flushed wallet.dat 278ms
GetMyExternalIP() received [75.76.64.183] 75.76.64.183:0
GetMyExternalIP() returned 75.76.64.183
AddLocal(75.76.64.183:22223,5)
connection timeout
trying connection 192.227.247.33:22223 lastseen=81.0hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=81.0hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=91.5hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=81.0hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=91.5hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=91.5hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=81.0hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=81.0hrs
I can ping these addresses just fine. So strange and it leaves me with just under 400K coins in limbo.
|
DELETED
|
|
|
|
sonysasankan (OP)
|
|
September 11, 2014, 04:12:30 AM |
|
Figures I get an offline wallet and cannot get it to sync with the network. Debug logs show connection timeouts when attempting to connect to peers. I can ping the IP's but cant connect with the wallet. Any suggestions? I have 400K coins sent to my wallet ID, then noticed it would not sync. ARRRGHHH.
Was it the latest wallet downloaded from the ANN page / website? Do you have an extremely slow connection? I noticed I get frequently disconnected from my ISP and sometimes notice my wallet would be stuck at the last synced block before I got disconnected. Usually restarting the wallet fixes the issue, and I am currently synced. So nothing wrong with the network I'm assuming. Is anyone else having issues syncing? Also are you using a .conf file in the folder? You dont need one. So if there is one, you could try deleting/renaming it and see if the wallet starts to sync without the conf file. |
|
|
|
|
WarrEagle
|
|
September 11, 2014, 04:43:36 AM |
|
Figures I get an offline wallet and cannot get it to sync with the network. Debug logs show connection timeouts when attempting to connect to peers. I can ping the IP's but cant connect with the wallet. Any suggestions? I have 400K coins sent to my wallet ID, then noticed it would not sync. ARRRGHHH.
Was it the latest wallet downloaded from the ANN page / website? Do you have an extremely slow connection? I noticed I get frequently disconnected from my ISP and sometimes notice my wallet would be stuck at the last synced block before I got disconnected. Usually restarting the wallet fixes the issue, and I am currently synced. So nothing wrong with the network I'm assuming. Is anyone else having issues syncing? Also are you using a .conf file in the folder? You dont need one. So if there is one, you could try deleting/renaming it and see if the wallet starts to sync without the conf file. No, I have solid internet and all of my other wallets are fine. Just Pink acting up. No sure if I have the right wallet...I have Beta 2.0 and a light wallet from crypto.pink/wallet I even tried installing the wallet on a server I run 2200 miles away. Same issue. |
DELETED
|
|
|
|
fayoling
|
|
September 11, 2014, 05:25:05 AM |
|
Figures I get an offline wallet and cannot get it to sync with the network. Debug logs show connection timeouts when attempting to connect to peers. I can ping the IP's but cant connect with the wallet. Any suggestions? I have 400K coins sent to my wallet ID, then noticed it would not sync. ARRRGHHH.
Was it the latest wallet downloaded from the ANN page / website? Do you have an extremely slow connection? I noticed I get frequently disconnected from my ISP and sometimes notice my wallet would be stuck at the last synced block before I got disconnected. Usually restarting the wallet fixes the issue, and I am currently synced. So nothing wrong with the network I'm assuming. Is anyone else having issues syncing? Also are you using a .conf file in the folder? You dont need one. So if there is one, you could try deleting/renaming it and see if the wallet starts to sync without the conf file. No, I have solid internet and all of my other wallets are fine. Just Pink acting up. No sure if I have the right wallet...I have Beta 2.0 and a light wallet from crypto.pink/wallet I even tried installing the wallet on a server I run 2200 miles away. Same issue. The thread windows 2.0.0.0 is not the latest, we will update that. Try 2.0.0.1 on http://crypto.pink/wallet/ |
|
|
|
|
hdclover
|
|
September 11, 2014, 06:02:35 AM |
|
why the sudden rise on price ? 132 sat now  |
Blah blah
|
|
|
|
fayoling
|
|
September 11, 2014, 06:05:39 AM |
|
why the sudden rise on price ? 132 sat now |
|
|
|
|
|
|
WarrEagle
|
|
September 11, 2014, 11:43:29 AM |
|
Figures I get an offline wallet and cannot get it to sync with the network. Debug logs show connection timeouts when attempting to connect to peers. I can ping the IP's but cant connect with the wallet. Any suggestions? I have 400K coins sent to my wallet ID, then noticed it would not sync. ARRRGHHH.
Was it the latest wallet downloaded from the ANN page / website? Do you have an extremely slow connection? I noticed I get frequently disconnected from my ISP and sometimes notice my wallet would be stuck at the last synced block before I got disconnected. Usually restarting the wallet fixes the issue, and I am currently synced. So nothing wrong with the network I'm assuming. Is anyone else having issues syncing? Also are you using a .conf file in the folder? You dont need one. So if there is one, you could try deleting/renaming it and see if the wallet starts to sync without the conf file. No, I have solid internet and all of my other wallets are fine. Just Pink acting up. No sure if I have the right wallet...I have Beta 2.0 and a light wallet from crypto.pink/wallet I even tried installing the wallet on a server I run 2200 miles away. Same issue. The thread windows 2.0.0.0 is not the latest, we will update that. Try 2.0.0.1 on http://crypto.pink/wallet/ Just updated to 2.0.0.1 and it is still not syncing |
DELETED
|
|
|
|
WarrEagle
|
|
September 11, 2014, 12:43:05 PM |
|
Flushed 2 addresses to peers.dat 43ms
trying connection 192.227.247.33:22223 lastseen=89.9hrs
UPnP Port Mapping successful.
connection timeout
trying connection 198.144.184.175:22223 lastseen=100.4hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=89.9hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=100.4hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=100.4hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=89.9hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=100.4hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=89.9hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=100.4hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=89.9hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=100.4hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=100.4hrs
connection timeout
|
DELETED
|
|
|
|
exoton
|
|
September 11, 2014, 01:10:21 PM |
|
is poker already implemented `?
|
|
|
|
|
GanjaFarmer23
Newbie
 Offline
Activity: 29
Merit: 0
|
|
September 11, 2014, 01:15:50 PM |
|
Could someone please explain the calculus behind buying 2 mill pink at these price and get something worth 500$? If I buy 2 mill coins now i pay roughly 3 btc.
and what the hell do you mean with value per pink = 0.000375
If it was 200,000 and 1,000,000 it would make sense..
|
|
|
|
|
Burninj
Legendary
Offline
Activity: 1148
Merit: 1000
|
|
September 11, 2014, 01:30:24 PM |
|
anyone having a working node list?
|
|
|
|
|
|
WarrEagle
|
|
September 11, 2014, 01:35:42 PM |
|
anyone having a working node list?
That would be nice. |
DELETED
|
|
|
|
kashking
|
|
September 11, 2014, 01:50:38 PM |
|
Baffled....this is a first when trying to use a wallet.
Done loading
ThreadOpenConnections started
refreshWallet
ThreadStakeMiner started
ThreadMessageHandler started
Flushed 2 addresses to peers.dat 59ms
keypool added key 118, size=101
4 addresses found from DNS seeds
ThreadDNSAddressSeed exited
trying connection 198.144.184.175:22223 lastseen=91.5hrs
ipcThread started
UPnP: ExternalIPAddress = 75.76.64.183
AddLocal(75.76.64.183:22223,3)
UPnP Port Mapping successful.
Flushing wallet.dat
Flushed wallet.dat 278ms
GetMyExternalIP() received [75.76.64.183] 75.76.64.183:0
GetMyExternalIP() returned 75.76.64.183
AddLocal(75.76.64.183:22223,5)
connection timeout
trying connection 192.227.247.33:22223 lastseen=81.0hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=81.0hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=91.5hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=81.0hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=91.5hrs
connection timeout
trying connection 198.144.184.175:22223 lastseen=91.5hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=81.0hrs
connection timeout
trying connection 192.227.247.33:22223 lastseen=81.0hrs
I can ping these addresses just fine. So strange and it leaves me with just under 400K coins in limbo.
Getting the same thing here....Can't get it to sync at all. |
|
|
|
GanjaFarmer23
Newbie
Offline
Activity: 29
Merit: 0
|
|
September 11, 2014, 01:59:12 PM
Last edit: September 11, 2014, 02:29:36 PM by GanjaFarmer23 |
|
Could someone please explain the calculus behind buying 2 mill pink at these price and get something worth 500$? If I buy 2 mill coins now i pay roughly 3 btc.
and what the hell do you mean with value per pink = 0.000375
If it was 200,000 and 1,000,000 it would make sense..
Why do you expect them to give you an equal amount of money back when you would still have the coin on top it? Compared to what i get for buying one Sync now, it doesn't make any sense. |
|
|
|
|
|
sumgye
|
|
September 11, 2014, 05:00:54 PM |
|
No, no fork. I just fell asleep at the keyboard and my nodes got pummelled to death. It'll sync now, and I'll keep an eye on it. Gonna talk to the guys about getting some new nodes up. In the meantime, if you do have trouble connecting (quite possible with the sudden surge of people all trying to sync up at once) you can add the following addnodes to your pinkcoin.conf: addnode=86.121.18.190
addnode=189.149.149.215
addnode=209.95.36.152
addnode=69.168.186.177
addnode=92.222.38.197
addnode=178.32.88.50
addnode=71.84.193.132
The file needs to be in your %appdata%/pinkcoin folder in windows, or $HOME/Library/Application Support/Pinkcoin/ on Mac OS X. If you don't already have one (there isn't one by default) just create one using any basic text editor, like Notepad or TextEditor. This isn't absolutely necessary, but will help you get more connections initially, and thus sync faster.And for what it's worth, you only really need the main nodes to get your initial connection to the decentralized network. Once you've made half a dozen connections to the network you're unlikely to ever see this sort of problem again. |
|
|
|
|
|
WarrEagle
|
|
September 11, 2014, 05:39:45 PM |
|
I have a dedicated dual core box on a 1 GBPS port not being used. Can I make a node?
|
DELETED
|
|
|
|
hdclover
|
|
September 11, 2014, 06:51:46 PM |
|
awesome news... should have invest more in pink
|
Blah blah
|
|
|
|
