Topic: [ANN] VGC - VegasCoin - page 2. (Read 74457 times)
whether is until now Vegascoin is still alive or have dead because I did not find where this coin was traded on the market. this project has long since passed and does Vegacoin have no future? there are still people who are interested in getting Vegacoin while there is no trading in this coin on the market.
Do inbound connections require a certain config setting? Or is this problem hardware related or service related?
This week microsoft sent multiple auto updates causing multiple restarts. It's a major security risk. Does anyone have instructions for a solid Linux install that will properly support the network. I tried on a Linux MINT machine and the dependencies didn't take well. I'll try on Ubuntu as github instructions suggest. But I did manage to get the windows wallet to run on MINT using WINE (and PlayOnLinux as the frontend), it's seems to be fine (stayed running through the windows updates while my other machines restarted), but I don't know if this is any worse than a regular Linux install. Any thoughts?
This week microsoft sent multiple auto updates causing multiple restarts. It's a major security risk. Does anyone have instructions for a solid Linux install that will properly support the network. I tried on a Linux MINT machine and the dependencies didn't take well. I'll try on Ubuntu as github instructions suggest. But I did manage to get the windows wallet to run on MINT using WINE (and PlayOnLinux as the frontend), it's seems to be fine (stayed running through the windows updates while my other machines restarted), but I don't know if this is any worse than a regular Linux install. Any thoughts?
if people want a robust network they need to open up their firewall (and router) port 52400 to their daemon/wallets.
Definitely.
There's been more than a few occasions where my server (which allows inbound connections) was the only thing propping up the network of a quiet altcoin, because none of the other peers permitted inbound connections. My server ended up being the middle of a star - a single point of failure for the entire network - rather than being just another peer in a properly distributed mesh.
It looks like the network is completely dead. I will make a better VEGAS and anyone with old coins can swap them.
how do you define 'completely dead' ?
my fulltime wallet currently has 9 connections
Code:
"addr" : "24.234.35.51:48842", (wsip-24-234-35-51.lv.lv.cox.net)
"addr" : "217.175.119.125:57233", (net-217-175-119.ip125.koping.net)
"addr" : "213.32.6.132:47626", (wallets2.mining-dutch.nl)
"addr" : "78.109.23.2:10389", (2-23-109-78.hosting.ua)
"addr" : "105.226.165.208:59937", (165-226-105-208.north.dsl.telkomsa.net)
"addr" : "80.31.126.250:62969",
"addr" : "71.38.192.169:60175", (71-38-192-169.lsv2.qwest.net)
"addr" : "203.20.114.252:52400",
"addr" : "83.40.149.60:63253", (60.red-83-40-149.dynamicip.rima-tde.net)
"addr" : "217.175.119.125:57233", (net-217-175-119.ip125.koping.net)
"addr" : "213.32.6.132:47626", (wallets2.mining-dutch.nl)
"addr" : "78.109.23.2:10389", (2-23-109-78.hosting.ua)
"addr" : "105.226.165.208:59937", (165-226-105-208.north.dsl.telkomsa.net)
"addr" : "80.31.126.250:62969",
"addr" : "71.38.192.169:60175", (71-38-192-169.lsv2.qwest.net)
"addr" : "203.20.114.252:52400",
"addr" : "83.40.149.60:63253", (60.red-83-40-149.dynamicip.rima-tde.net)
eight of them are 'inbound' connections, implying they are probably leaches who dont allow
inbound connections to themselves.
if people want a robust network they need to open up their firewall (and router) port 52400 to their daemon/wallets.
...and how do you swap coins if the network is completely dead? you need to move coins to swap them
i think they were trying to manipulate peoples connections (to try to make us think it was dead), my connections dropped a couple days ago, but i got them back... i will check my router's port forwarding too... i did it a long time ago but when i got a new router, i never changed any of the default settings. simple stuff like that can optimize performance.
It looks like the network is completely dead. I will make a better VEGAS and anyone with old coins can swap them.
how do you define 'completely dead' ?
my fulltime wallet currently has 9 connections
Code:
"addr" : "24.234.35.51:48842", (wsip-24-234-35-51.lv.lv.cox.net)
"addr" : "217.175.119.125:57233", (net-217-175-119.ip125.koping.net)
"addr" : "213.32.6.132:47626", (wallets2.mining-dutch.nl)
"addr" : "78.109.23.2:10389", (2-23-109-78.hosting.ua)
"addr" : "105.226.165.208:59937", (165-226-105-208.north.dsl.telkomsa.net)
"addr" : "80.31.126.250:62969",
"addr" : "71.38.192.169:60175", (71-38-192-169.lsv2.qwest.net)
"addr" : "203.20.114.252:52400",
"addr" : "83.40.149.60:63253", (60.red-83-40-149.dynamicip.rima-tde.net)
eight of them are 'inbound' connections, implying they are probably leaches who dont allow
inbound connections to themselves.
if people want a robust network they need to open up their firewall (and router) port 52400 to their daemon/wallets.
...and how do you swap coins if the network is completely dead? you need to move coins to swap them
my connections are back and mining is working. (same nodes).
It looks like the network is completely dead. I will make a better VEGAS and anyone with old coins can swap them.
Instead of creating a new Vegas. why don't you work o the main network and fix the network issues and make it active again? spending a lot of time on another network is pointless.
BTW are you the official dev?
either resolve the problem in the current network or just vanish this. there is already bunch of shitcoins available.
It looks like the network is completely dead. I will make a better VEGAS and anyone with old coins can swap them.
more vegas projects from developers and you arent doing any work on this one.... why?
i am not a developer right now, i have limited coding ability, but I am a good learner and a few years of computer science already so I should be able to contribute with development in major ways at some point. I know that doesnt do anyone any good at this moment but I was going to setup vegascointalk so we could really build this idea together, and expand the community... miners are getting cheaper and better, there are more projects out there we can adapt to use with our coin.
i found a tutorial video for liquidus block explorer setup (very easy)... i am going to try my hand at the linux install and see what i can do (still never heard back from cryptochat about block explorers)... everyone should have a look at it and see what other projects out there you can adapt for vegascoin. the hardest part is making sure your linux has all the needed dependencies. the tutorial really helps get a look at exactly how to do it.
It looks like the network is completely dead. I will make a better VEGAS and anyone with old coins can swap them.
I only heard the name may also know this project is being developed in the country? A good project for the development of business tourism as well as for businesses. Wish for development projects around the world, not just on the territorial scope of a country.
Where is this development??
I only heard the name may also know this project is being developed in the country? A good project for the development of business tourism as well as for businesses. Wish for development projects around the world, not just on the territorial scope of a country.
-Markets 
This plan includes a number of the best things: a great team, a great product, a great idea, a great start! I'm sure that the company will take the leading place in this worl
i had a 24 hour internet outage and just left the miner and everything running until internet was restored... since then my connection count has been sitting at 1 (it was fluctuating between 7 and 11 before the outage). is it wiser in this situation to keep it running as is or should i restart the wallet and the miner (i am solo mining). this is a theoretical problem, but even though i only have one connection right now, i still think it may be better just to let it keep running as it is (and it should catch up with the network, and start seeing more connections)... this is the first time this has happened to me.
never mine without at least two valid nodes connected to your wallet. you are pretty much guaranteed to fork if you do.
ok. thats a good call... i just figured the ISP would connect me back up to the same nodes... which it probly did... i restarted anyway. im up to 3 connections so doing better already, im sure ill be reconnected to more soon.
NOTE: i notice that my laptop using WIFI only gets 2 connections and my desktop which is wired gets more... this may be my laptop/router/ISP... (i moved the laptop wallet to the desktop and saw the connections jump. and i started a new laptop wallet and still only get 2... so other factors can affect your connection count.
i had a 24 hour internet outage and just left the miner and everything running until internet was restored... since then my connection count has been sitting at 1 (it was fluctuating between 7 and 11 before the outage). is it wiser in this situation to keep it running as is or should i restart the wallet and the miner (i am solo mining). this is a theoretical problem, but even though i only have one connection right now, i still think it may be better just to let it keep running as it is (and it should catch up with the network, and start seeing more connections)... this is the first time this has happened to me.
never mine without at least two valid nodes connected to your wallet. you are pretty much guaranteed to fork if you do.
i did that and it hasnt synced anyway
sometimes a wallet gets connected to one or more 'bad' nodes and it interferes with downloading
the correct chain.
one possible thing to try in your config file is to remove all the addnode= lines and add:
connect=address
rather than addnode=address
connect will cause your wallet/daemon to ONLY connect to the specified address(es) and not connect
to any others. you just need to find nodes you 'trust' and that they will allow incoming connections.
i suppose my node is fairly trustworthy
connect=23.233.2.252
you can add other connects too.
once you are synched, edit those connects back to addnode because if those connect nodes become unavailable in the future you wont have any nodes at all.
whenever you edit your config file, you must stop and restart your wallet/daemon.
forgetting this step can waste you a lot of time. (what i really wanted to suggest in the first place, i added the above to seem less glib
)i had a 24 hour internet outage and just left the miner and everything running until internet was restored... since then my connection count has been sitting at 1 (it was fluctuating between 7 and 11 before the outage). is it wiser in this situation to keep it running as is or should i restart the wallet and the miner (i am solo mining). this is a theoretical problem, but even though i only have one connection right now, i still think it may be better just to let it keep running as it is (and it should catch up with the network, and start seeing more connections)... this is the first time this has happened to me.
Mining without a connection to the network may cause your wallet to fork and that may prevent it from connecting to other nodes. Try restarting the wallet 1st, then verify if block heights are correct. If not, then you may need to resync wallet. Only start mining when you are sure wallet is synced correctly.
i did that and it hasnt synced anyway
sometimes a wallet gets connected to one or more 'bad' nodes and it interferes with downloading
the correct chain.
one possible thing to try in your config file is to remove all the addnode= lines and add:
connect=address
rather than addnode=address
connect will cause your wallet/daemon to ONLY connect to the specified address(es) and not connect
to any others. you just need to find nodes you 'trust' and that they will allow incoming connections.
i suppose my node is fairly trustworthy
connect=23.233.2.252
you can add other connects too.
once you are synched, edit those connects back to addnode because if those connect nodes become unavailable in the future you wont have any nodes at all.
whenever you edit your config file, you must stop and restart your wallet/daemon.
forgetting this step can waste you a lot of time. (what i really wanted to suggest in the first place, i added the above to seem less glib
)i had a 24 hour internet outage and just left the miner and everything running until internet was restored... since then my connection count has been sitting at 1 (it was fluctuating between 7 and 11 before the outage). is it wiser in this situation to keep it running as is or should i restart the wallet and the miner (i am solo mining). this is a theoretical problem, but even though i only have one connection right now, i still think it may be better just to let it keep running as it is (and it should catch up with the network, and start seeing more connections)... this is the first time this has happened to me.
is anyone developing this coin?
The website looks very outdated...
The website looks very outdated...
No development for a few years now. Also, no more exchanges.
is anyone developing this coin?
The website looks very outdated...
The website looks very outdated...
i did that and it hasnt synced anyway
sometimes a wallet gets connected to one or more 'bad' nodes and it interferes with downloading
the correct chain.
one possible thing to try in your config file is to remove all the addnode= lines and add:
connect=address
rather than addnode=address
connect will cause your wallet/daemon to ONLY connect to the specified address(es) and not connect
to any others. you just need to find nodes you 'trust' and that they will allow incoming connections.
i suppose my node is fairly trustworthy
connect=23.233.2.252
you can add other connects too.
once you are synched, edit those connects back to addnode because if those connect nodes become unavailable in the future you wont have any nodes at all.
whenever you edit your config file, you must stop and restart your wallet/daemon.
forgetting this step can waste you a lot of time. (what i really wanted to suggest in the first place, i added the above to seem less glib
)Jump to: