the total amount of coins will be 1 billion? Is it confirmed somewhere? Sorry i am asking, I wasn't able to find this on the first page. I think distribution of this coin is confusing.
The total number of coins is a little confusing, but I think the distribution is quite clear (and more important, fair!) if you read the main post. Other than total number of coins, what specifically is confusing about the distribution? With specifics, maybe someone can clear any confusion up for you. -x Before the shareholders changed distro rules : Only 1.5 distro rounds on western media, everything else including auctions on Chinese media only... |
|
|
|
Signed up ! Any chance of a pic of this beautyful girl ? |
|
|
|
You probably want to use -addnode and not -connect, because connect implies a set exclusive peer list (i.e. you won't connect to any other peers). Or you can just remove them from the .conf after you load it, as the valid ones will now be in peers.dat
maybe that is what he intended to do... only connect to exclusive peer (that he believes on the main/correct chain) I actually tried removing .conf after that and started the client again, and it still re-connects to certain clients on wrong fork again I think because it always ask for more new peers from the connected peers to propagate the network How can I tell? because when I removed .conf my upload bandwidth went crazy again... all connected peers are all different than those exclusive list I connected earlier and I noticed 1 of the connected peer height is way below (is at 173217) and stay like that for days as I remember also a few connected nodes are at "startingheight" : -1 I doubt that means he just started. What exactly height -1 means here? in .conf file, is there a way to block certain peer? something like perma-banned until we removed it in the future You are spot on. Its indeed intended to force your wallet to connect only to certain/trusted peers. When using connect= , Listen=1 will be ignored, which means no incomming connects accepted. What clam needs would be so-called seed peers or nodes. 1 is enough, but for back up reasons of course its better to have at least 2 or more. How to block certain peers ? You can make use of an ip filter like peerblock. There are others out there. Also LMHOST file inside your windows directory can be used to do that, effectively redirecting unwanted ip to blackhole, and have a nice day ! But any decent firewall, indeed NOT windows firewall, can be use to block. Depending on what apps I have running I use firewall and at times make use of peerblock on top of it. Peerblock comes with block lists so you can block ip ranges of anti p2p, secret service or other crap. Also have a look at TCPView, it shows you what is connected to your box. It has helped me findig unwanted connects of various app including Windows. NETstat will do the same btw. As usual, a quick search on the net should get you further information. Do a search of bitcoin.conf to locate the wiki, detailed info about options and how to use them. Further questions ? Just post and I will try to help if time permits it. Anyway time to stop I start to make stupid typos. |
|
|
|
connect=84.194.247.232:31174
connect=23.92.210.2:31174
connect=54.75.227.85:38343
connect=104.131.59.43:53103
[...]
Just a quick note: if the IP doesn't have the default port then it's probably an outbound connection, and any attempt to connect to that IP (inbound) on that port is likely to fail. Best to omit the port when specifying addnode/connect parameters. I understand this was probably a copy and paste of your getpeerinfo output, just pointing out that potential problem, for future reference.  Damn there goes my reputation ! But yes, it was indeed a quick copy and paste action and a quick clean up with notepad. With incorrect or no port forwarding, incomming connects are useless. If correct, incomming are also usefull. Normally port nr, can or should be deleted, since ppl might change these on the fly. And the wallet has no problems sorting out which port to connect to since that info is updated whenever there is peer exchange info. Or more simply put whenever peer.dat gets updated. The best way of course to find out if an ip is in or outbound is by getpeerinfo, typical output would be : { "addr" : "xx.xxx.xxx.xx:18775", "services" : "00000000", "lastsend" : 1415481527, "lastrecv" : 1415481538, "conntime" : 1415481527, "bytessent" : 126, "bytesrecv" : 1467, "blocksrequested" : 0, "version" : 0, "subver" : "", "inbound" : false, <===== BINGO ! "releasetime" : 0, "startingheight" : -1, "banscore" : 0 } I almost forgot. connect= also tells wallet not to accept incoming connects, listen=1 will be ignored as such.  |
|
|
|
I think I can reproduce a bug.
wallet running unter w7 64 bit
I have send to that wallet coins with message.
since then the wallet crashes
after delete the wallet the walletsoftware doesn't crash
provide me a test VPN adress and I send some coins in de way I did before and see what happend.
Send to my signature and I will return the same amount. Debit: -100.00 VPN Transaction fee: -0.0001 VPN Net amount: -100.0001 VPN Transaction ID: 1bdd55105ef5a4eda65fec0ba8acce347a4fcbd47c5d54edbb535e1ce3430456 Transaction Message: @FROM=VvgF9LPkgAJNqqdppGkRxTuwGGu7nD4uRJ@SUBJ=Vpn Fee@MSG=This message will crash your wallet I have received your message and no crash. Closed wallet and retarted wallet again no crash. Using 1119-4 and WinXP sp3. I will return exact message and amount. Is this your address ? VvgF9LPkgAJNqqdppGkRxTuwGGu7nD4uRJ The crash was by windows 7 pro 64bit But thx for the test. Someone else want to test with windows 7 pro 64bit? Ok, sorry for the confusion. Did you sent me that message or was it someone else ? |
|
|
|
I think I can reproduce a bug.
wallet running unter w7 64 bit
I have send to that wallet coins with message.
since then the wallet crashes
after delete the wallet the walletsoftware doesn't crash
provide me a test VPN adress and I send some coins in de way I did before and see what happend.
Send to my signature and I will return the same amount. Debit: -100.00 VPN Transaction fee: -0.0001 VPN Net amount: -100.0001 VPN Transaction ID: 1bdd55105ef5a4eda65fec0ba8acce347a4fcbd47c5d54edbb535e1ce3430456 Transaction Message: @FROM=VvgF9LPkgAJNqqdppGkRxTuwGGu7nD4uRJ@SUBJ=Vpn Fee@MSG=This message will crash your wallet I have received your message and no crash. Closed wallet and retarted wallet again no crash. Using 1119-4 and WinXP sp3. I will return exact message and amount. Is this your address ? VvgF9LPkgAJNqqdppGkRxTuwGGu7nD4uRJ |
|
|
|
many people interested with bitvpn
because the features and functions of this coin
This could go into all circles
only need improvisations to make easier in use
Do you mean improvements to the wallet like UI or documentation/manual ? Or both ? |
|
|
|
I think I can reproduce a bug.
wallet running unter w7 64 bit
I have send to that wallet coins with message.
since then the wallet crashes
after delete the wallet the walletsoftware doesn't crash
provide me a test VPN adress and I send some coins in de way I did before and see what happend.
Send to my signature and I will return the same amount. |
|
|
|
still waiting for a reply regarding my LAN proxy settings being automatically changed every time I launch VPN wallet. Original post here https://bitcointalk.org/index.php?topic=789961.msg9438324#msg9438324Cmon dev...Wallet issues are typically where things get ugly. I'm asking for an explanation. Why would I continue to run my wallet when it is changing LAN settings without my authorization? If there is a fix, perfect let me know about it. Silence speaks volumes and it never turns out good. I'm having this problem too. I'm from California if location matters Same problem here. I had posted this issue a long time ago. Its not a bug but supposed to be like that because of default settings. BitNetCoin or BNC, make changes to your windows connection. ANY program that make use of windows connection might experience connection problems. Sollution 1 : Preventing BNC to make changes to windows connection settings : Go to BitNet tab > settings Disable p2p Domain name system. Not prefered option since it turns BitNet into a plain wallet. Sollution 2 : Preventing browser to use windows connection settings : In your browser, locate network/proxy settings. Select "direct connection". If you need proxy other then BiNet, select manual proxy settings. Most Browsers, except iexplorer and Chrome, allows you to make those changes. Firfox and clones : options > advanced > connection settings : Select "no proxy" or "manual proxy config" Chrome and clones : settings > advanged settings > network : "Chrome is using your computer's system proxy settings to connect to the network" Bad luck ! Webkit browsers : options > proxy > disable "Auto-proxy" if present. If "Auto-proxy" is not present you should be ok. As always : READ your manual of your browser if you have problems locating these settings. Still having problems ? Post and I will try to help you, but be patient since I am not active everyday, have to work to pay my rent.  Finally someone steps up to help out. Odd that it wasn't answered by the dev...actually, complete horseshit that it wasn't answered by dev but at least someone from the community is reading the thread.  Thanks for the explanation ButtCrack No problemo. Fun part is that I have posted this before a couple of times I think, just making changes cleaning up text. I forgot to add some stuff I wrote earlier about port forwarding, which as you probably know is important for making sure others can reach you and helps you getting firmly connected with the swarm. Just do a search in this thread using "port forwarding" or my nick. And when found don't be shy to quote and re-post. Right now I am a bit too lazy to do this myself. As always feedback appreciated, especially when text needs some improvement or is not clear. (Of course I don't mind a tip if you liked it, wink wink, nudge budge ) |
|
|
|
1119-2, 1119-4 crashes after several minutes  If you have windows 8 in the .conf autorelaynode=0 can be changed to autorelaynode=1 Del peers.dat and restart wallet. Just to add, autorelaynode=1 in conf file also works in WinXp and very likely any verion upwards. |
|
|
|
still waiting for a reply regarding my LAN proxy settings being automatically changed every time I launch VPN wallet. Original post here https://bitcointalk.org/index.php?topic=789961.msg9438324#msg9438324Cmon dev...Wallet issues are typically where things get ugly. I'm asking for an explanation. Why would I continue to run my wallet when it is changing LAN settings without my authorization? If there is a fix, perfect let me know about it. Silence speaks volumes and it never turns out good. I'm having this problem too. I'm from California if location matters Same problem here. I had posted this issue a long time ago. Its not a bug but supposed to be like that because of default settings. BitNetCoin or BNC, make changes to your windows connection. ANY program that make use of windows connection might experience connection problems. Sollution 1 : Preventing BNC to make changes to windows connection settings : Go to BitNet tab > settings Disable p2p Domain name system. Not prefered option since it turns BitNet into a plain wallet. Sollution 2 : Preventing browser to use windows connection settings : In your browser, locate network/proxy settings. Select "direct connection". If you need proxy other then BiNet, select manual proxy settings. Most Browsers, except iexplorer and Chrome, allows you to make those changes. Firfox and clones : options > advanced > connection settings : Select "no proxy" or "manual proxy config" Chrome and clones : settings > advanged settings > network : "Chrome is using your computer's system proxy settings to connect to the network" Bad luck ! Webkit browsers : options > proxy > disable "Auto-proxy" if present. If "Auto-proxy" is not present you should be ok. As always : READ your manual of your browser if you have problems locating these settings. Still having problems ? Post and I will try to help you, but be patient since I am not active everyday, have to work to pay my rent. |
|
|
|
any new wallet update? my wallet still not synching...  I assume you have connections and run windows ? Try this : Locate directory of wallet.dat. Delete everything except wallet.dat. Copy wallet.dat to a safe place. Create text file with name "Clam.conf" in that directory. Open text file with notepad and insert follwing lines : connect=84.194.247.232:31174 connect=23.92.210.2:31174 connect=54.75.227.85:38343 connect=104.131.59.43:53103 connect=77.247.181.165:65190 connect=162.218.65.19:45406 connect=96.246.211.120:19476 connect=83.86.189.163:58108 connect=93.103.131.59:53324 connect=71.188.55.212:31174 connect=76.94.201.185:36079 connect=109.195.211.62:50318 connect=86.58.104.183:49860 connect=203.20.114.252:31174 connect=108.195.138.58:60527 connect=193.166.139.206:55786 connect=78.134.3.254:63941 connect=198.245.60.38:53497 connect=24.96.235.190:61000 connect=108.237.13.94:34724 connect=71.241.130.246:31174 connect=198.245.60.38:55364 connect=203.174.191.230:50533 connect=69.131.59.58:4719 connect=24.67.30.88:51620 connect=89.88.199.104:51398 connect=37.209.45.163:49312 connect=108.227.82.11:50317 connect=108.91.73.3:63989 connect=73.55.207.245:64773 connect=80.195.253.183:31174 connect=95.91.224.82:11614 These nodes are on the right chain, and should get your wallet synced. Open help > debug window so you can check block count going up. If it does not, wait for 30 min - 1 hour. Still not going up ? Close wallet and restart. Repeat if syncing stalls. Let me know if it worked. |
|
|
|
|
Forum problems solved !
Just use normal internet, NOT bitnet.
Also old users have to register again, old profiles have been deleted.
|
|
|
|
better if the member moving to bitnettalk
too many FUDDER in BTT
do you mean that bitnet will take place of btt? did you read my post?... moving to Bitnettalk,not to take place of btt.. more pleasant in own forum too many fudder in btt So far VPN thread has been very clean, have not seen any postings of trolls spreading FUD. Maybe its because VPN team deletes those post, I do not know. maybe not yet,..fudder always had a way I have noticed that if people just ignore fudders they quickly leave the room. Fudders love attention, so just ignore and have a laugh. |
|
|
|
Forum has too many problems : -translation does not work, I like English but still many functions show Chinese text. -logging in does not work either. -often fails to load. |
|
|
|
Please read !For new users or anyone that has some problems with the wallet. Replay : NEVER allow others to use your ip if you can into trouble with the law !! To prevent others to use your ip make make sure you have following settings disabled : -start vpn service -start p2p proxy Here is a quick user guide : 502 error is just that what it says, site off line or the node that host the site is not connected to your client. In BitNet settings, tab "all nodes" you can check if you are connected with the right node, check for nickname "BitNetTalk.com". Also have a look for "dice.com", " www.game.com", and check if you can load these sites. If you can, then BitNetTalk.com is off line. In BitNet settings, tab "settings" you can enable all you see in "normal" settings. However in "service" settings ONLY enable : -open p2p Domain Name System -start http service -start https service Make sure you have following settings disabled : -start vpn service -start p2p proxy If not present, add the following in the text box just above "start p2p proxy" and "work threads" : localhost;127.0.0.1 Hit "SAVE" when done ! Following ports should be forwarded : 920 - TCP 922 - TCP/UDP 923 - TCP/UDP Read your manual how to configure your modem/router ! autosyncnode=0
autorelaynode=0
addnode=42.96.197.68
addnode=101.55.120.249
addnode=101.55.120.133
addnode=192.110.160.49
addnode=223.27.35.130
addnode=223.27.35.130:4603
addnode=23.96.2.215:1040
addnode=37.215.181.12:8207
addnode=27.251.160.137:51569
addnode=108.231.88.101:62064
addnode=89.239.152.116:54370
addnode=193.95.228.55:60937
addnode=211.100.56.237:41494
addnode=219.146.196.34:2788
addnode=114.255.94.54:32351
addnode=221.194.45.36:50876
addnode=182.73.68.30:64082
addnode=220.235.229.28:51453
addnode=112.113.96.138:54068
addnode=171.106.45.103:920
addnode=59.52.226.117:47710
addnode=60.169.74.232:1268
addnode=213.184.227.118:60854
addnode=92.255.167.153:24277
addnode=123.51.208.55:2363
addnode=91.216.173.52:4420
addnode=98.226.35.5:54019
addnode=212.98.190.209:21712
addnode=91.64.8.155:56335
addnode=37.233.8.185:55503
addnode=192.110.160.49:4900
addnode=136.169.60.25:53538
addnode=178.89.190.22:4439
addnode=192.200.114.122:1914
addnode=188.162.41.120:6210
addnode=213.233.250.235:51974
addnode=202.120.121.78:55788
addnode=116.52.102.106:4902
addnode=116.23.3.29:57250
addnode=27.202.149.89:58324
addnode=118.81.1.146:9185
addnode=124.16.152.96:58389
addnode=116.237.89.30:61025
addnode=114.228.85.11:50744
addnode=182.72.199.226:62455
addnode=113.111.227.23:63854
addnode=183.92.244.55:9066
addnode=91.122.75.176:1452
addnode=95.24.71.163:50231
addnode=171.217.146.3:2143
addnode=157.7.211.106:1912
addnode=222.132.198.253:5821
addnode=76.188.72.8:50981
addnode=77.106.70.104:53744
addnode=222.162.97.74:55506
addnode=188.105.106.115:57513
addnode=119.60.173.246:53776
addnode=124.237.166.242:19596
addnode=115.192.187.221:20881
addnode=58.198.102.74:56627
addnode=118.232.53.195:60703
addnode=212.15.158.202:51625
addnode=37.213.51.70:24284
addnode=103.18.120.126:54323
addnode=119.85.130.87:3733
addnode=184.164.78.62:62103
addnode=221.194.45.39:58878
addnode=113.251.44.38:52715
addnode=42.96.197.68:3546
addnode=223.27.35.130:63049
addnode=37.110.210.245:60938
addnode=125.45.74.0:1718
addnode=125.45.74.0:1719
addnode=109.169.55.110:2595
addnode=113.16.215.179:63856
addnode=109.207.87.27:52032
addnode=38.72.115.49:1652
addnode=101.55.120.249:63638
addnode=77.239.228.198:62015
addnode=193.110.112.126:54759
addnode=77.38.4.128:59237
addnode=171.8.228.229:53647
addnode=185.36.60.70:51253
addnode=95.65.110.170:1225
addnode=62.4.5.121:42270
addnode=178.40.129.3:63890
addnode=101.55.120.249:63639
addnode=95.31.232.9:65485
addnode=109.207.87.27:52068
addnode=37.110.210.245:60983
addnode=95.71.8.190:50810
addnode=221.194.45.39:59623
addnode=223.27.35.130:63082
addnode=77.88.208.12:58658
addnode=194.186.254.178:3992
-Locate directory of your wallet.dat file. -Create a text file, name "vpncoin.conf", and simply copy and paste the lines of text from Somare : autosyncnode=0 autorelaynode=0 addnode=42.96.197.68 addnode=101.55.120.249 addnode=101.55.120.133 addnode=192.110.160.49 Note : You can add ALL addnodes from the quote if you like, they can help you jump start getting connected. I only copied a few to make this posting not too long. Some additions : autorelaynode=0 can be changed to autorelaynode=1. Have tested this and it works just fine. Also as posted by others, in case you have problems syncing or getting connected, delete peers.dat ! NOTE : Feedback welcome ! Might do a re-write/cleaning up text if needed or requested.
|
|
|
|
better if the member moving to bitnettalk
too many FUDDER in BTT
do you mean that bitnet will take place of btt? did you read my post?... moving to Bitnettalk,not to take place of btt.. more pleasant in own forum too many fudder in btt So far VPN thread has been very clean, have not seen any postings of trolls spreading FUD. Maybe its because VPN team deletes those post, I do not know. |
|
|
|
1st payment received. Thanks ! |
|
|
|
sorry to bother you guys again, I have another small question (problem) I just noticed that since I got back on the main chain, my upload data transfer is MUCH higher than usual I don't understand why this happening, because the outbound port on my side is blocked by firewall I got multiple occurrences of these, getblocks 170613 to 00000000000000000000 limit 500
getblocks stopping at limit 171112 b31ce7156dffe7912335
getblocks 169613 to 00000000000000000000 limit 500
getblocks stopping at limit 170112 cab452d5b579a4001875
getblocks 169113 to 831d2270c55e9d017514 limit 500
getblocks stopping at limit 169612 09777d16b5cf14ad79ee is this my client requesting blocks or other node requesting blocks from me? is this the same problem as almightyruler said couple days ago? if it is how could it be, coz my firewall blocks incoming requests Try to add "listen=0" in config, it means "do not accept incoming connections". I do not think it will work but worth to give it a try. Problem is that "outgoing connections only" still alows uploading. When you upload a lot it means the swarm likes you and have many clients updating using your connection. Once swarn has updated most clients and are in sync it should normalise. |
|
|
|
autosyncnode=0
autorelaynode=0
addnode=42.96.197.68
addnode=101.55.120.249
addnode=101.55.120.133
addnode=192.110.160.49
addnode=223.27.35.130
addnode=223.27.35.130:4603
addnode=23.96.2.215:1040
addnode=37.215.181.12:8207
addnode=27.251.160.137:51569
addnode=108.231.88.101:62064
addnode=89.239.152.116:54370
addnode=193.95.228.55:60937
addnode=211.100.56.237:41494
addnode=219.146.196.34:2788
addnode=114.255.94.54:32351
addnode=221.194.45.36:50876
addnode=182.73.68.30:64082
addnode=220.235.229.28:51453
addnode=112.113.96.138:54068
addnode=171.106.45.103:920
addnode=59.52.226.117:47710
addnode=60.169.74.232:1268
addnode=213.184.227.118:60854
addnode=92.255.167.153:24277
addnode=123.51.208.55:2363
addnode=91.216.173.52:4420
addnode=98.226.35.5:54019
addnode=212.98.190.209:21712
addnode=91.64.8.155:56335
addnode=37.233.8.185:55503
addnode=192.110.160.49:4900
addnode=136.169.60.25:53538
addnode=178.89.190.22:4439
addnode=192.200.114.122:1914
addnode=188.162.41.120:6210
addnode=213.233.250.235:51974
addnode=202.120.121.78:55788
addnode=116.52.102.106:4902
addnode=116.23.3.29:57250
addnode=27.202.149.89:58324
addnode=118.81.1.146:9185
addnode=124.16.152.96:58389
addnode=116.237.89.30:61025
addnode=114.228.85.11:50744
addnode=182.72.199.226:62455
addnode=113.111.227.23:63854
addnode=183.92.244.55:9066
addnode=91.122.75.176:1452
addnode=95.24.71.163:50231
addnode=171.217.146.3:2143
addnode=157.7.211.106:1912
addnode=222.132.198.253:5821
addnode=76.188.72.8:50981
addnode=77.106.70.104:53744
addnode=222.162.97.74:55506
addnode=188.105.106.115:57513
addnode=119.60.173.246:53776
addnode=124.237.166.242:19596
addnode=115.192.187.221:20881
addnode=58.198.102.74:56627
addnode=118.232.53.195:60703
addnode=212.15.158.202:51625
addnode=37.213.51.70:24284
addnode=103.18.120.126:54323
addnode=119.85.130.87:3733
addnode=184.164.78.62:62103
addnode=221.194.45.39:58878
addnode=113.251.44.38:52715
addnode=42.96.197.68:3546
addnode=223.27.35.130:63049
addnode=37.110.210.245:60938
addnode=125.45.74.0:1718
addnode=125.45.74.0:1719
addnode=109.169.55.110:2595
addnode=113.16.215.179:63856
addnode=109.207.87.27:52032
addnode=38.72.115.49:1652
addnode=101.55.120.249:63638
addnode=77.239.228.198:62015
addnode=193.110.112.126:54759
addnode=77.38.4.128:59237
addnode=171.8.228.229:53647
addnode=185.36.60.70:51253
addnode=95.65.110.170:1225
addnode=62.4.5.121:42270
addnode=178.40.129.3:63890
addnode=101.55.120.249:63639
addnode=95.31.232.9:65485
addnode=109.207.87.27:52068
addnode=37.110.210.245:60983
addnode=95.71.8.190:50810
addnode=221.194.45.39:59623
addnode=223.27.35.130:63082
addnode=77.88.208.12:58658
addnode=194.186.254.178:3992
autosyncnode=0 autorelaynode=0 YES !! Just what I was looking for ! Stalling of block chain has stopped, it syncs just like other qt wallets, and there is no "storm" of connections anymore. At times I had some 900+ connections and it took maybe some 30 min before it got to normal. For anyone who has no clue what to do with these lines of text from the quote : -Locate directory of your wallet.dat file. -Create a text file, name "vpncoin.conf", and simply copy and paste the lines of text from Somare : autosyncnode=0 autorelaynode=0 addnode=42.96.197.68 addnode=101.55.120.249 addnode=101.55.120.133 addnode=192.110.160.49 Note : You can add ALL addnodes from the quote if you like, they can help you jump start getting connected. I only copied a few to make this posting not too long. |
|
|
|
|
Show Posts
