GE takes the price at the same level, but SWING falling day by day, if this trend continues quick price be comparable although the change was 1:10 
did you not read the devs last post? or ya just like to complain for no reason
Topic: ♘♕♔SWING♚ ♛♞ ▬▬▬▬●Programmatically Fluctuating Miners Cost!●▬▬▬▬ Now On Bittrex! - page 42. (Read 119581 times)
September 10, 2015, 01:14:39 PM
did you not read the devs last post? or ya just like to complain for no reason
September 10, 2015, 10:36:22 AM
less than 200k....this thing is way undervalued, going to buy some up 
September 10, 2015, 03:13:45 AM
GE takes the price at the same level, but SWING falling day by day, if this trend continues quick price be comparable although the change was 1:10
September 09, 2015, 05:14:24 PM
I'm having the same problem as HashStatz. I'm using 32bit Ubuntu and stuck on block 3004.
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
Trying to compile on a server as well?
Is it possible for you to try 64bit ubuntu 14.04?
Seems you both are trying to run on 32 bit. Might not make a difference but it's a connection between the two of you and the error.
Tomorrow I will try a fresh install on a fresh server(s) and see if I can replicate & fix the issue.
Unfortunately I am am stuck with 32bit.
Installed the wallet on a Ubuntu 64bit VPS with a different provider and everything seems to be working properly now (on block 8931). If everything is still working in a couple hours i will transfer my coins and start staking again.
Hey that's great! It sounds like it was either a 32 bit issue or a provider issue then.
Rewarding wise, very interesting.
Community wise? Further development?
Community wise? Further development?
Promotion and community growth is slotted for after:
A: We make a full cycle and miners go back down to 10% rewards.
B: The swap ends at the end of tomorrow
The first week+ has been about getting the seed coins out, seeing what issues arise when it goes live (fortunately very few), and making sure everything is operating as intended (so far so good).
Once we make a full cycle is when I start looking to grab more people's attention no worries.
September 09, 2015, 04:18:02 PM
I'm having the same problem as HashStatz. I'm using 32bit Ubuntu and stuck on block 3004.
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
Trying to compile on a server as well?
Is it possible for you to try 64bit ubuntu 14.04?
Seems you both are trying to run on 32 bit. Might not make a difference but it's a connection between the two of you and the error.
Tomorrow I will try a fresh install on a fresh server(s) and see if I can replicate & fix the issue.
Unfortunately I am am stuck with 32bit.
Installed the wallet on a Ubuntu 64bit VPS with a different provider and everything seems to be working properly now (on block 8931). If everything is still working in a couple hours i will transfer my coins and start staking again.
September 09, 2015, 04:05:20 PM
Rewarding wise, very interesting.
Community wise? Further development?
Community wise? Further development?
September 09, 2015, 12:02:42 PM
I'm having the same problem as HashStatz. I'm using 32bit Ubuntu and stuck on block 3004.
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
Trying to compile on a server as well?
Is it possible for you to try 64bit ubuntu 14.04?
Seems you both are trying to run on 32 bit. Might not make a difference but it's a connection between the two of you and the error.
Tomorrow I will try a fresh install on a fresh server(s) and see if I can replicate & fix the issue.
Unfortunately I am am stuck with 32bit.
September 09, 2015, 11:35:45 AM
What's everyone doing with their SWING? Staking? Trading? Only asking because I have but 90SWING 
Yes staking here too mate
Dont feel bad i have only 36.coin and my staking yesterday gave me9 coin and then 3 more so i got 12 coins staking yesterday just going to let stake and see where it take me wow it would b nice to make that daily i m just waiting to see how many i get today so if i stake for one year 4380but that figuring at 12 a day but as time goes on it would increase as it goes on staking so i could and up with 10000. or more well will just have to wait and see................... September 08, 2015, 10:51:32 PM
I'm having the same problem as HashStatz. I'm using 32bit Ubuntu and stuck on block 3004.
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
Trying to compile on a server as well?
Is it possible for you to try 64bit ubuntu 14.04?
Seems you both are trying to run on 32 bit. Might not make a difference but it's a connection between the two of you and the error.
Tomorrow I will try a fresh install on a fresh server(s) and see if I can replicate & fix the issue.
I was wondering the same thing about the 64bit connection between our problems.
I tried to compile the wallet tonight on the other VPS with a fresh copy Ubuntu 14.04 64bit. Unfortunately i ran into an issue with it only having 256MB of ram, and was unable to add a swap file like i have done in the past with other machines (looks like it has something to do with the provider has OpenVZ configured).
Time for bed now, i will look at spinning up another VPS tomorrow.
September 08, 2015, 09:59:02 PM
I'm having the same problem as HashStatz. I'm using 32bit Ubuntu and stuck on block 3004.
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
Trying to compile on a server as well?
Is it possible for you to try 64bit ubuntu 14.04?
Seems you both are trying to run on 32 bit. Might not make a difference but it's a connection between the two of you and the error.
Tomorrow I will try a fresh install on a fresh server(s) and see if I can replicate & fix the issue.
September 08, 2015, 07:55:46 PM
I'm having the same problem as HashStatz. I'm using 32bit Ubuntu and stuck on block 3004.
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 61001,
"walletversion" : 60000,
September 08, 2015, 05:29:57 PM
Also if it helps I'm running the seed node on a 14.04 x64 image from digitalocean.
September 08, 2015, 05:24:53 PM
Here's a peers.dat from 9/6/15 2:57PM EST with 14 connections. Just do the initial startup to get your base files, close the wallet (backup your wallet.dat if neccessary), replace peers.dat, and start the wallet back up. You should get more connections faster. If you wait too long from the time of upload it may not work as well but I can always get you a fresh copy.
https://mega.nz/#!fZBWkI7T!0FbVukLFRcxl6jc3ieiWvN0A98VSIK2cgfxLOV8brLY
https://mega.nz/#!fZBWkI7T!0FbVukLFRcxl6jc3ieiWvN0A98VSIK2cgfxLOV8brLY
I have a fresh wallet compiled and ready to fire up,
murderouskirk i should be popping online every hour or so all day so if your available to post an updated copy of your peers.dat i will try again (not really sure if thats the issue though as i have lots of connections).
Thanks for the help.
Sorry HashStatz I was away from my pc. Did you try it with the uploaded peers.dat?
On a similar note, if anyone wants to spin up Swing on a serer and share the IP we can put it as an addnode in the example config for better network connections.
Ya i tryed your peer file, but still got stuck at block 3004 with 36 connections. I am running this on a VPS and would be happy to setup as a node if i can get everything working correctly.
Try setting debug=1 in your conf file. You might be able to get some info out of it in the file it makes.
So i created a debug file like you suggested and after combing through it i found what seems to me where the error occurs starting at block 3005 and repeating every block after. Hopfuly this help give you an idea as to what my problem maybe caused by.
Code:
received: block (256 bytes)
received block 0000000000001a29c94c
ComputeNextStakeModifier: prev modifier=0xd05348b890b66422 time=2015-09-03 12:11:50 UTC
ERROR: ConnectBlock() : coinbase reward exceeded (actual=1200000 vs calculated=1199999)
InvalidChainFound: invalid block=0000000000001a29c94c height=3005 trust=14496107994403525608 blocktrust=1995525199418564 date=09/03/15 12:15:22
InvalidChainFound: current best=bf08d8b87f952089955b height=3004 trust=14494112469204107044 blocktrust=6179704 date=09/03/15 12:14:31
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
I've been trying to replicate this error without success. I tried downloading the chain both with and without a config file multiple times and was able to with my only connection being the seed node. I'm still looking into it some but:
What does your Swing.conf file look like?
Did you compile your own wallet?
When you try to download the chain, be sure you're doing the following:
1: Close the swing wallet
2: Go to C:\Users\Username\AppData\Roaming\Swing
3: Backup your wallet.dat if there are stored coins on your pc
4: Delete all the files in the swing folder
5: Start the swing wallet and let it get a connection & download.
If it fails, you might want to consider trying the wallet on a different PC or vm. You said you were running on a vm yes? It's possible that's causing some sort of conflict but that's just me going out on a limb to take additional guesses. You can also try downloading with and without your config file.
Yes i complied my own wallet, and am running the Swingd from the command line. All this is running on a Ubuntu 14.04 x86 OpenVZ container VPS.
I am going to trying installing this wallet on a different and fresh OpenVZ container on a VPS i am going to be retiring in a month or so. I will let you know how that goes later tonight.
Thanks for you help.
Ok cool. Please note that in a linux build you still have the same swing folder that needs deletion to redownload the chain.
(I'm guessing you know this since you enabled debug but just touching all bases I can think of)
You can probably find it at:
root/.Swing
or
cd ~
cd .Swing
It should be found in the same directory as the Swing folder and can be seen with 'ls -al'.
September 08, 2015, 04:29:41 PM
Here's a peers.dat from 9/6/15 2:57PM EST with 14 connections. Just do the initial startup to get your base files, close the wallet (backup your wallet.dat if neccessary), replace peers.dat, and start the wallet back up. You should get more connections faster. If you wait too long from the time of upload it may not work as well but I can always get you a fresh copy.
https://mega.nz/#!fZBWkI7T!0FbVukLFRcxl6jc3ieiWvN0A98VSIK2cgfxLOV8brLY
https://mega.nz/#!fZBWkI7T!0FbVukLFRcxl6jc3ieiWvN0A98VSIK2cgfxLOV8brLY
I have a fresh wallet compiled and ready to fire up,
murderouskirk i should be popping online every hour or so all day so if your available to post an updated copy of your peers.dat i will try again (not really sure if thats the issue though as i have lots of connections).
Thanks for the help.
Sorry HashStatz I was away from my pc. Did you try it with the uploaded peers.dat?
On a similar note, if anyone wants to spin up Swing on a serer and share the IP we can put it as an addnode in the example config for better network connections.
Ya i tryed your peer file, but still got stuck at block 3004 with 36 connections. I am running this on a VPS and would be happy to setup as a node if i can get everything working correctly.
Try setting debug=1 in your conf file. You might be able to get some info out of it in the file it makes.
So i created a debug file like you suggested and after combing through it i found what seems to me where the error occurs starting at block 3005 and repeating every block after. Hopfuly this help give you an idea as to what my problem maybe caused by.
Code:
received: block (256 bytes)
received block 0000000000001a29c94c
ComputeNextStakeModifier: prev modifier=0xd05348b890b66422 time=2015-09-03 12:11:50 UTC
ERROR: ConnectBlock() : coinbase reward exceeded (actual=1200000 vs calculated=1199999)
InvalidChainFound: invalid block=0000000000001a29c94c height=3005 trust=14496107994403525608 blocktrust=1995525199418564 date=09/03/15 12:15:22
InvalidChainFound: current best=bf08d8b87f952089955b height=3004 trust=14494112469204107044 blocktrust=6179704 date=09/03/15 12:14:31
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
I've been trying to replicate this error without success. I tried downloading the chain both with and without a config file multiple times and was able to with my only connection being the seed node. I'm still looking into it some but:
What does your Swing.conf file look like?
Did you compile your own wallet?
When you try to download the chain, be sure you're doing the following:
1: Close the swing wallet
2: Go to C:\Users\Username\AppData\Roaming\Swing
3: Backup your wallet.dat if there are stored coins on your pc
4: Delete all the files in the swing folder
5: Start the swing wallet and let it get a connection & download.
If it fails, you might want to consider trying the wallet on a different PC or vm. You said you were running on a vm yes? It's possible that's causing some sort of conflict but that's just me going out on a limb to take additional guesses. You can also try downloading with and without your config file.
Yes i complied my own wallet, and am running the Swingd from the command line. All this is running on a Ubuntu 14.04 x86 OpenVZ container VPS.
I am going to trying installing this wallet on a different and fresh OpenVZ container on a VPS i am going to be retiring in a month or so. I will let you know how that goes later tonight.
Thanks for you help.
September 08, 2015, 03:48:46 PM
On another note, miner rewards are about to go up to 80% so there are a larger amount of coins being created. Next comes 90%, then 100%.
After that miner rewards drop all the way back down to 10%, causing a decrease in new coin creation and an increase in miners cost.
Will be interesting to watch it play out for the first time.
Please remember that swaps will close at the end of the 10th (EST) as well. At that point GE price will no longer have any bearing on the price of Swing.
After that miner rewards drop all the way back down to 10%, causing a decrease in new coin creation and an increase in miners cost.
Will be interesting to watch it play out for the first time.
Please remember that swaps will close at the end of the 10th (EST) as well. At that point GE price will no longer have any bearing on the price of Swing.
September 08, 2015, 03:27:49 PM
Here's a peers.dat from 9/6/15 2:57PM EST with 14 connections. Just do the initial startup to get your base files, close the wallet (backup your wallet.dat if neccessary), replace peers.dat, and start the wallet back up. You should get more connections faster. If you wait too long from the time of upload it may not work as well but I can always get you a fresh copy.
https://mega.nz/#!fZBWkI7T!0FbVukLFRcxl6jc3ieiWvN0A98VSIK2cgfxLOV8brLY
https://mega.nz/#!fZBWkI7T!0FbVukLFRcxl6jc3ieiWvN0A98VSIK2cgfxLOV8brLY
I have a fresh wallet compiled and ready to fire up,
murderouskirk i should be popping online every hour or so all day so if your available to post an updated copy of your peers.dat i will try again (not really sure if thats the issue though as i have lots of connections).
Thanks for the help.
Sorry HashStatz I was away from my pc. Did you try it with the uploaded peers.dat?
On a similar note, if anyone wants to spin up Swing on a serer and share the IP we can put it as an addnode in the example config for better network connections.
Ya i tryed your peer file, but still got stuck at block 3004 with 36 connections. I am running this on a VPS and would be happy to setup as a node if i can get everything working correctly.
Try setting debug=1 in your conf file. You might be able to get some info out of it in the file it makes.
So i created a debug file like you suggested and after combing through it i found what seems to me where the error occurs starting at block 3005 and repeating every block after. Hopfuly this help give you an idea as to what my problem maybe caused by.
Code:
received: block (256 bytes)
received block 0000000000001a29c94c
ComputeNextStakeModifier: prev modifier=0xd05348b890b66422 time=2015-09-03 12:11:50 UTC
ERROR: ConnectBlock() : coinbase reward exceeded (actual=1200000 vs calculated=1199999)
InvalidChainFound: invalid block=0000000000001a29c94c height=3005 trust=14496107994403525608 blocktrust=1995525199418564 date=09/03/15 12:15:22
InvalidChainFound: current best=bf08d8b87f952089955b height=3004 trust=14494112469204107044 blocktrust=6179704 date=09/03/15 12:14:31
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
I've been trying to replicate this error without success. I tried downloading the chain both with and without a config file multiple times and was able to with my only connection being the seed node. I'm still looking into it some but:
What does your Swing.conf file look like?
Did you compile your own wallet?
When you try to download the chain, be sure you're doing the following:
1: Close the swing wallet
2: Go to C:\Users\Username\AppData\Roaming\Swing
3: Backup your wallet.dat if there are stored coins on your pc
4: Delete all the files in the swing folder
5: Start the swing wallet and let it get a connection & download.
If it fails, you might want to consider trying the wallet on a different PC or vm. You said you were running on a vm yes? It's possible that's causing some sort of conflict but that's just me going out on a limb to take additional guesses. You can also try downloading with and without your config file.
September 08, 2015, 10:30:36 AM
Here's a peers.dat from 9/6/15 2:57PM EST with 14 connections. Just do the initial startup to get your base files, close the wallet (backup your wallet.dat if neccessary), replace peers.dat, and start the wallet back up. You should get more connections faster. If you wait too long from the time of upload it may not work as well but I can always get you a fresh copy.
https://mega.nz/#!fZBWkI7T!0FbVukLFRcxl6jc3ieiWvN0A98VSIK2cgfxLOV8brLY
https://mega.nz/#!fZBWkI7T!0FbVukLFRcxl6jc3ieiWvN0A98VSIK2cgfxLOV8brLY
I have a fresh wallet compiled and ready to fire up,
murderouskirk i should be popping online every hour or so all day so if your available to post an updated copy of your peers.dat i will try again (not really sure if thats the issue though as i have lots of connections).
Thanks for the help.
Sorry HashStatz I was away from my pc. Did you try it with the uploaded peers.dat?
On a similar note, if anyone wants to spin up Swing on a serer and share the IP we can put it as an addnode in the example config for better network connections.
Ya i tryed your peer file, but still got stuck at block 3004 with 36 connections. I am running this on a VPS and would be happy to setup as a node if i can get everything working correctly.
Try setting debug=1 in your conf file. You might be able to get some info out of it in the file it makes.
So i created a debug file like you suggested and after combing through it i found what seems to me where the error occurs starting at block 3005 and repeating every block after. Hopfuly this help give you an idea as to what my problem maybe caused by.
Code:
received: block (256 bytes)
received block 0000000000001a29c94c
ComputeNextStakeModifier: prev modifier=0xd05348b890b66422 time=2015-09-03 12:11:50 UTC
ERROR: ConnectBlock() : coinbase reward exceeded (actual=1200000 vs calculated=1199999)
InvalidChainFound: invalid block=0000000000001a29c94c height=3005 trust=14496107994403525608 blocktrust=1995525199418564 date=09/03/15 12:15:22
InvalidChainFound: current best=bf08d8b87f952089955b height=3004 trust=14494112469204107044 blocktrust=6179704 date=09/03/15 12:14:31
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
September 08, 2015, 08:31:39 AM
What's everyone doing with their SWING? Staking? Trading? Only asking because I have but 90SWING
Yes staking here too mate
September 07, 2015, 05:51:21 PM
What's everyone doing with their SWING? Staking? Trading? Only asking because I have but 90SWING
Are the any incentives for node hosting? I've been trying to think of ways to acquire more coins...!
Of course staking
someone was lucky enough to get some cheap from low buy orders, lol I was too impatient and bought from the sell wall.
you might be lucky enough to find a block or 2 a day with 90 coins, but you might want to break it up into 10 coin chunks so when you find a block you don't have to wait for your whole stash to mature again
September 07, 2015, 05:45:51 PM
Here's a peers.dat from 9/6/15 2:57PM EST with 14 connections. Just do the initial startup to get your base files, close the wallet (backup your wallet.dat if neccessary), replace peers.dat, and start the wallet back up. You should get more connections faster. If you wait too long from the time of upload it may not work as well but I can always get you a fresh copy.
https://mega.nz/#!fZBWkI7T!0FbVukLFRcxl6jc3ieiWvN0A98VSIK2cgfxLOV8brLY
https://mega.nz/#!fZBWkI7T!0FbVukLFRcxl6jc3ieiWvN0A98VSIK2cgfxLOV8brLY
I have a fresh wallet compiled and ready to fire up,
murderouskirk i should be popping online every hour or so all day so if your available to post an updated copy of your peers.dat i will try again (not really sure if thats the issue though as i have lots of connections).
Thanks for the help.
Sorry HashStatz I was away from my pc. Did you try it with the uploaded peers.dat?
On a similar note, if anyone wants to spin up Swing on a serer and share the IP we can put it as an addnode in the example config for better network connections.
Ya i tryed your peer file, but still got stuck at block 3004 with 36 connections. I am running this on a VPS and would be happy to setup as a node if i can get everything working correctly.
Try setting debug=1 in your conf file. You might be able to get some info out of it in the file it makes.
Jump to: