♘♕♔SWING♚ ♛♞ ▬▬▬▬●Programmatically Fluctuating Miners Cost!●▬▬▬▬ Now On Bittrex!

[nikkers]

*** SWING NEEDS YOUR VOTE ***
https://www.cryptopia.co.nz/Home/Voting

Voted, i really like this coin, one of the few with a good communicative dev behind it, who is visibly putting in a lot of effort.

keep it up mate 

[1714326971]

1714326971

[murderouskirk]

Quick status report.

I've been taking some time to research into the best ways to go about this upcoming core upgrade. I've spoken with a few other devs about the issues we are looking to upgrade and gotten some valuable input and suggestions on alternate solutions. I'm meeting in person this week with an intelligent coder friend of mine who is familiar with the issues we're facing. We plan to take a deeper look at the code itself and potentially come up with the proposed patch. Along with this I'm factoring in some minor core upgrades to be packaged into the update (checkpoints, seed node update, protocol versioning, etc.. etc..).

In addition I've been looking into getting more devs on the swing team. The other coin devs I've spoken with have expressed an interest in helping but had to keep focus on their own projects. One of them has expressed an interest in some cross marketing down the road. The dev I'm meeting with is busy chasing his phd, but has expressed a willingness to work on the code with me and get involved to an extent.

Trying to make sure this is done right rather than rushing a quick patch.

Will keep you all updated.

I'm quoting this just so it's visible on the new page.

Thanks for voting guys, keep it up!

[murderouskirk]

Quick status report.

I've been taking some time to research into the best ways to go about this upcoming core upgrade. I've spoken with a few other devs about the issues we are looking to upgrade and gotten some valuable input and suggestions on alternate solutions. I'm meeting in person this week with an intelligent coder friend of mine who is familiar with the issues we're facing. We plan to take a deeper look at the code itself and potentially come up with the proposed patch. Along with this I'm factoring in some minor core upgrades to be packaged into the update (checkpoints, seed node update, protocol versioning, etc.. etc..).

In addition I've been looking into getting more devs on the swing team. The other coin devs I've spoken with have expressed an interest in helping but had to keep focus on their own projects. One of them has expressed an interest in some cross marketing down the road. The dev I'm meeting with is busy chasing his phd, but has expressed a willingness to work on the code with me and get involved to an extent.

Trying to make sure this is done right rather than rushing a quick patch.

Will keep you all updated.

I'm quoting this just so it's visible on the new page.

Thanks for voting guys, keep it up!

Alright so we've dug into the code to take a look for potential connectivity upgrades and have made progress.

I'd like to try to force some connectivity problems in a test environment, that way I have something I can use to test potential upgrades against.

In order to do that I need to get a better feel for the environments any forking occurs in.

Put simply, if you think you have experienced forking, i NEED to know what operating system it happened in.

I'll check back to see if anyone responds. If not I'll start prodding people from earlier in the thread.

Thanks.

[sparksi]

Quick status report.

I've been taking some time to research into the best ways to go about this upcoming core upgrade. I've spoken with a few other devs about the issues we are looking to upgrade and gotten some valuable input and suggestions on alternate solutions. I'm meeting in person this week with an intelligent coder friend of mine who is familiar with the issues we're facing. We plan to take a deeper look at the code itself and potentially come up with the proposed patch. Along with this I'm factoring in some minor core upgrades to be packaged into the update (checkpoints, seed node update, protocol versioning, etc.. etc..).

In addition I've been looking into getting more devs on the swing team. The other coin devs I've spoken with have expressed an interest in helping but had to keep focus on their own projects. One of them has expressed an interest in some cross marketing down the road. The dev I'm meeting with is busy chasing his phd, but has expressed a willingness to work on the code with me and get involved to an extent.

Trying to make sure this is done right rather than rushing a quick patch.

Will keep you all updated.

I'm quoting this just so it's visible on the new page.

Thanks for voting guys, keep it up!

Alright so we've dug into the code to take a look for potential connectivity upgrades and have made progress.

I'd like to try to force some connectivity problems in a test environment, that way I have something I can use to test potential upgrades against.

In order to do that I need to get a better feel for the environments any forking occurs in.

Put simply, if you think you have experienced forking, i NEED to know what operating system it happened in.

I'll check back to see if anyone responds. If not I'll start prodding people from earlier in the thread.

Thanks.

Late 23rd of November (EET) and operating system is Win7 Ultimate. BTW: https://bitcointalk.org/index.php?topic=678849.msg13142326#msg13142326

[murderouskirk]

Quick status report.

I've been taking some time to research into the best ways to go about this upcoming core upgrade. I've spoken with a few other devs about the issues we are looking to upgrade and gotten some valuable input and suggestions on alternate solutions. I'm meeting in person this week with an intelligent coder friend of mine who is familiar with the issues we're facing. We plan to take a deeper look at the code itself and potentially come up with the proposed patch. Along with this I'm factoring in some minor core upgrades to be packaged into the update (checkpoints, seed node update, protocol versioning, etc.. etc..).

In addition I've been looking into getting more devs on the swing team. The other coin devs I've spoken with have expressed an interest in helping but had to keep focus on their own projects. One of them has expressed an interest in some cross marketing down the road. The dev I'm meeting with is busy chasing his phd, but has expressed a willingness to work on the code with me and get involved to an extent.

Trying to make sure this is done right rather than rushing a quick patch.

Will keep you all updated.

I'm quoting this just so it's visible on the new page.

Thanks for voting guys, keep it up!

Alright so we've dug into the code to take a look for potential connectivity upgrades and have made progress.

I'd like to try to force some connectivity problems in a test environment, that way I have something I can use to test potential upgrades against.

In order to do that I need to get a better feel for the environments any forking occurs in.

Put simply, if you think you have experienced forking, i NEED to know what operating system it happened in.

I'll check back to see if anyone responds. If not I'll start prodding people from earlier in the thread.

Thanks.

Late 23rd of November (EET) and operating system is Win7 Ultimate. BTW: https://bitcointalk.org/index.php?topic=678849.msg13142326#msg13142326

x64 or x32?

[crackfoo]

Wallet is disabled on Bittrex, any idea whats up? Just routine?

[VentureC]

Wallet is disabled on Bittrex, any idea whats up? Just routine?

No. Swing was delisted from Bittrex unfortunately because of lack of trading volume. So you'll have to trade Swing elsewhere now (Yobit).

Vote it up at Cryptopia to get it listed there:
https://www.cryptopia.co.nz/Home/Voting

[sparksi]

Quick status report.

I've been taking some time to research into the best ways to go about this upcoming core upgrade. I've spoken with a few other devs about the issues we are looking to upgrade and gotten some valuable input and suggestions on alternate solutions. I'm meeting in person this week with an intelligent coder friend of mine who is familiar with the issues we're facing. We plan to take a deeper look at the code itself and potentially come up with the proposed patch. Along with this I'm factoring in some minor core upgrades to be packaged into the update (checkpoints, seed node update, protocol versioning, etc.. etc..).

In addition I've been looking into getting more devs on the swing team. The other coin devs I've spoken with have expressed an interest in helping but had to keep focus on their own projects. One of them has expressed an interest in some cross marketing down the road. The dev I'm meeting with is busy chasing his phd, but has expressed a willingness to work on the code with me and get involved to an extent.

Trying to make sure this is done right rather than rushing a quick patch.

Will keep you all updated.

I'm quoting this just so it's visible on the new page.

Thanks for voting guys, keep it up!

Alright so we've dug into the code to take a look for potential connectivity upgrades and have made progress.

I'd like to try to force some connectivity problems in a test environment, that way I have something I can use to test potential upgrades against.

In order to do that I need to get a better feel for the environments any forking occurs in.

Put simply, if you think you have experienced forking, i NEED to know what operating system it happened in.

I'll check back to see if anyone responds. If not I'll start prodding people from earlier in the thread.

Thanks.

Late 23rd of November (EET) and operating system is Win7 Ultimate. BTW: https://bitcointalk.org/index.php?topic=678849.msg13142326#msg13142326

x64 or x32?

64

[zazarb]

Swing still listing in bittrex,  
The SWING market is back online after some maintenance.
but swing rate totally disappointing

[gregofdoom]

SWING is still on Bittrex it would be unhappy to lose this exchange.

[murderouskirk]

Hey guys, just wanted to touch base.

I'm at the point where I have a good feel for exactly where and how the Swing core can be improved. I'm on a buisness trip this weekend but when I get back I'm going to work on pulling together/finalizing and posting the proposed upgrade.

I plan to explain the issues currently occurring in the code with example debug logs, along with the difference the upgrade would make. That way everyone can easily understand the issues and see what it is were talking about changing.

Thanks guys. More info to come later.

[BluRPie]

Nice, good to hear!

[TheInfidel]

Hey guys, just wanted to touch base.

I'm at the point where I have a good feel for exactly where and how the Swing core can be improved. I'm on a buisness trip this weekend but when I get back I'm going to work on pulling together/finalizing and posting the proposed upgrade.

I plan to explain the issues currently occurring in the code with example debug logs, along with the difference the upgrade would make. That way everyone can easily understand the issues and see what it is were talking about changing.

Thanks guys. More info to come later.

Looking forward to hearing more about that. Incidentally I have had not wallet or staking issues that I'm aware of, running two wallets, one on WIN 10 and one on WIN 8.1 both 64 bit systems.

[BluRPie]

Hey guys, just wanted to touch base.

I'm at the point where I have a good feel for exactly where and how the Swing core can be improved. I'm on a buisness trip this weekend but when I get back I'm going to work on pulling together/finalizing and posting the proposed upgrade.

I plan to explain the issues currently occurring in the code with example debug logs, along with the difference the upgrade would make. That way everyone can easily understand the issues and see what it is were talking about changing.

Thanks guys. More info to come later.

Looking forward to hearing more about that. Incidentally I have had not wallet or staking issues that I'm aware of, running two wallets, one on WIN 10 and one on WIN 8.1 both 64 bit systems.

I dont have any issues here either, i had in the beginning but not the past 3 months or so. WIN10 64 here

[VentureC]

Bittrex is showing this warning for the SWING/BTC trading pair:

"This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on Friday, December 18th 2015 unless the average daily trade volume for the last 7 days exceeds 0.2 BTC. If you are the developer of the coin and would like to keep it listed, please contact us at support@bittrex.com."

Dev, I hope you'll have time to contact them. Bittrex is an important exchange for SWING. Thanks.

[gregofdoom]

Bittrex is showing this warning for the SWING/BTC trading pair:

"This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on Friday, December 18th 2015 unless the average daily trade volume for the last 7 days exceeds 0.2 BTC. If you are the developer of the coin and would like to keep it listed, please contact us at support@bittrex.com."

Dev, I hope you'll have time to contact them. Bittrex is an important exchange for SWING. Thanks.

Instead of waiting on dev, we do try to do a little volume on bitrex.
I've already done and ask for help

[murderouskirk]

Bittrex is showing this warning for the SWING/BTC trading pair:

"This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on Friday, December 18th 2015 unless the average daily trade volume for the last 7 days exceeds 0.2 BTC. If you are the developer of the coin and would like to keep it listed, please contact us at support@bittrex.com."

Dev, I hope you'll have time to contact them. Bittrex is an important exchange for SWING. Thanks.

Instead of waiting on dev, we do try to do a little volume on bitrex.
I've already done and ask for help

Me contacting them doesn't resolve this. We just need to make trades or encourage new traders to automatically resolve this. More volume = warning vanishes.

(I'll give it a shot though.)

Hello,

I am the swing dev.

 This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on Friday, December 18th 2015 unless the average daily trade volume for the last 7 days exceeds 0.2 BTC. If you are the developer of the coin and would like to keep it listed, please contact us at support@bittrex.com.

Our coin is still active, just a bit of low volume at the moment. Aside from encouraging holders to make volume and trying to get new traders, what can we do to keep listed during times of low volume?

Thanks!

[murderouskirk]

Hey guys, just wanted to touch base.

I'm at the point where I have a good feel for exactly where and how the Swing core can be improved. I'm on a buisness trip this weekend but when I get back I'm going to work on pulling together/finalizing and posting the proposed upgrade.

I plan to explain the issues currently occurring in the code with example debug logs, along with the difference the upgrade would make. That way everyone can easily understand the issues and see what it is were talking about changing.

Thanks guys. More info to come later.

Looking forward to hearing more about that. Incidentally I have had not wallet or staking issues that I'm aware of, running two wallets, one on WIN 10 and one on WIN 8.1 both 64 bit systems.

I dont have any issues here either, i had in the beginning but not the past 3 months or so. WIN10 64 here

Just for clarity sake I haven't had any issues myself either. I went out of sync once weeks ago when i was offline for a while but aside from that no problems.

I'm just going off what people have reported as opportunities to strengthen the core code.

Let me give some insight.

I've recently been digging into what happens with the rewards when they are calculated, and exactly what's going on when getting calculated.

With the current setup, that process looks something like this:

Code:

Block Count: 975 Last Three: 975 Decimal: 9.75 Final:975000000

Count: 976 Three: 976 Decimal: 9.76 Final:976000000

Count: 977 Three: 977 Decimal: 9.77 Final:977000000

Count: 978 Three: 978 Decimal: 9.78 Final:977999999.99999988079071044921875

Count: 979 Three: 979 Decimal: 9.790000000000001 Final:979000000.00000011920928955078125

Count: 980 Three: 980 Decimal: 9.8 Final:980000000.00000011920928955078125

Count: 981 Three: 981 Decimal: 9.81 Final:981000000

Count: 982 Three: 982 Decimal: 9.82 Final:982000000

Count: 983 Three: 983 Decimal: 9.83 Final:983000000

Count: 984 Three: 984 Decimal: 9.84 Final:984000000

Count: 985 Three: 985 Decimal: 9.85 Final:985000000

Count: 986 Three: 986 Decimal: 9.86 Final:986000000

Count: 987 Three: 987 Decimal: 9.870000000000001 Final:987000000.00000011920928955078125

Count: 988 Three: 988 Decimal: 9.88 Final:988000000.00000011920928955078125

HERE is the section of code that spits this out. I just used block 1 - 999 as sample output. For the sake of clarity i re-coded the process in java for faster debugging. (im just better at java is all, but java may produce slightly different results is the point)

So what I discovered is that somewhere else in the code the decimal is inserted into a full number with 9+ digits.
The end result in this section of code that gets passed out looks something like '9.87 * COIN' (=987000000).

Me attempting to put in the decimal during the reward calculation instead of letting it do it after results in some unnecessary math. Math that doesn't always turn out clean, and leaves room to lose accuracy when clipping/rounding the final result to a full number.

I'm working on re-coding this section so a result like this:

Count: 987 Three: 987 Decimal: 9.870000000000001 Final:987000000.00000011920928955078125

Acts like this:

Count: 987 Last Three: 987 Final:987000000

Now, this is an example of POS. POW gets a little more challenging since rewards need to be multiplied by 10%.. 20%.. 30%.. etc.. But I'm working on doing that cleanly too.

But that's essentially where we have room for core upgrades and cleaning up the internal math for increased accuracy.

So that should give you guys a little better idea at what I've been looking at.

Will post more later as I make progress.

[murderouskirk]

I should also mention that I want to redo the website at some point. It's built on a platform that was fast and easy to get up in time for launch, but is now charging me money that doesn't need to be spent. I'll rebuild the website into a cleaner/ more professional looking 'scroller' website on wordpress when I get the chance. I want to wrap up the proposed core upgrade before I work on that though so you guys have a chance to go over it while I do the site.

Basically when I get happy with the core upgrade proposal I'll post it. You guys can look it over, see the exact changes it would make, and decide if you want to go through with an upgrade or make further changes to the proposal. We don't HAVE to upgrade if people are largely content, but I want the option to be there for when / if we come to the agreement to rework the reward code. We could just put the upgrade on standby and focus on things like marketing and increasing our userbase. If / when we do decide the proposal is good and largely agreed upon, we will then go over what the upgrade process would look like and proceed from there.

I think explaining the room for improvement and putting out proposals like this is a good way to get people thinking about the core code and potentially stepping up as a volunteer dev willing to keep improving Swing as a community.

[murderouskirk]