Topic: ♘♕♔SWING♚ ♛♞ ▬▬▬▬●Programmatically Fluctuating Miners Cost!●▬▬▬▬ Now On Bittrex! - page 28. (Read 119520 times)

Just guesswork and theory here, but I would assume that it's not advantageous to allow staking inputs to get too small.

I've been doing some testing with wallets that have around 600-700 each. They still will combine the inputs even the the nStakeCombineThreshold is 1000. Does anyone know why that is?

Frigging rights SWING is a goldmine for anyone who has gotten into this coin early on I'm honestly surprised that we haven't had clone after clone after clone of this coin yet!! That just blows my mind because the entire concept is just awesome!!

Don't get the word out too much yet, hehe.  Swing is a goldmine for those who are in it right now. 

Just kidding, it's just my greedy self speaking. Yes, it would be great to get some more exposure for Swing and introduce the coin to a greater audience.

Hey everybody, let's get the volume up and start trading with each other. It's more fun when there are more active traders!

Glad to hear you like it. It's recording data as it does, it's not setup to crawl backwards at this point in time. So 1 day is about right.

the chart looks good! I can't wait until the new features are available. currently I can only see today and that's it.

Alright guys, chart released and website cleaned up a little to go with it.

Check it out!

Swing Expected Rewards vs Price vs Total Supply

TrySwing.com

or

TrySwing.com/chart




So we went with the one looking for 1btc that I've worked with in the past. He was kind enough to work towards getting our chart live before the 1 BTC was raised.

Any help pulling together the btc is extremely helpful in this situation. 0.1 here and .05 there adds up fast. If you appreciate his work on our new chart, consider showing him some support.

1E6soVzn7Z5NGguwD9sZfXkVmn8a51Cg71

Some additional cool info:

The dev has stated that he is willing to entertain the idea of upgrading the chart with more data/features once it's been paid off just for the sake of making it better.

Once we pull together his 1btc and get him paid we can likely get some more stats added to the chart such as:

Trade volume
Order depth
Net Hashrate
Net Difficulties
Number of connected parties
Number of Coins being moved
On-Click events opening Chainz BE details for specific blocks
etc.. etc.. (Your ideas welcome here!)

I'm sure you guys can think up more possibilities and the thought of getting more data excites me, hopefully you guys too.

Anyway, happy to hear constructive feedback at this point. I'm already using the chart like crazy with 1 day of data recorded, hopefully you guys find it as useful as I do.

Very excited about this! Thanks!

Thanks! We need to get more people involved and build the network and community. Just trying to help out!

Awesome! Thanks for doing this. I managed to catch the last few messages where you were chatting with people about getting the wallet downloaded and staking. Good work! 

Status report: Chart's done. I'm just letting it go through at least 1k blocks to get some data on it. Finishing up the website update to compliment it. Expect it to launch sometime around/after block 52k. (Currently 51,700)

Hey everybody, I'll be raining SWING in the Yobit trollbox to try and generate interest and get some new people involved.

having issues mining?

Stratum port: 3388
stratum1.suchpool.pw:3388
stratum2.suchpool.pw:3388
Not normal mining     

Yes, if you have thousands of coins in the wallet, then they will split and then recombine depending on the number of inputs your wallet has. If you have a high number of inputs, then the wallet will recombine them in chunks of 1000 coins, and then proceed to split into two inputs from there.

Here are some examples:

https://chainz.cryptoid.info/swing/tx.dws?82948.htm
https://chainz.cryptoid.info/swing/block.dws?50666.htm
https://chainz.cryptoid.info/swing/block.dws?50657.htm

If you were inclined to change the nStakeCombineThreshold in a future wallet release, it could be found at the top of the wallet.cpp file.

I think the problem with such a low amount of coins to combine can be disadvantageous to those with more than one thousand coins in their wallet because the transactions that combine your inputs destroys over 1000 stake weight and te new weight climbs more slowly. On the other hand, it gives an advantage to those with lower amounts of coins because they can achieve a closer to full stake weight with their smaller inputs, and they wan also create as many inputs as the'd like.

Although, the probability that you will hit a staked block increases with input size, so that may be the reason for the slower accumulation of weight in relation to input size.

I think if the nStakeCombineThreshold were increased to somewhere between 2500-5000 in a future release, then it would be more fair to those with medium size wallets, considering the low supply of coins. Once the supply of Swing is in the multimillions, it may make sense to adjust it down. jmho

Side note. I believe our fancy new price vs expected pow/pos rewards vs supply chart is about ready (it looks great). I'm hoping to get it live for you guys sometime this weekend.

This is actually some really interesting questioning and insight thank you for posting and digging into it a little. This is exactly the kind of discussion we need to work towards improving the core. To be honest I have not dug into that portion of the code very deeply. However, I have been under the impression that coins split into two inputs when they stake not combine. Are you under the impression that they recombine when you have more than 1k? Or am I completely mistaken here?

Thanks for the discussion!  

Yeah you need to redownload the blockchain sorry for the inconveniance. I think I've identified a connectivity upgrade but it involves a fork. I personally feel it's best to wait till we can bundle In some more upgrades (security, latest bips.. etc...) before we try to push that update. It also allows community members to discuss possible amendments like in the comment above (which I will reply to in a minute). If it helps I think you only have a chance of falling out of sync after disconnecting from the network for a while. Far as I've noticed at least.