Topic: 【ANN】◢◣ Swipp ◢◣ Modern cryptocurrency ● X11 ● POW/POS ● Masternodes - page 17. (Read 19080 times)
December 03, 2017, 11:57:13 PM
any update ?
December 01, 2017, 11:36:38 AM
Try this pool, its stable and works best
http://s1.altcoinix.com/swipp/public/index.php?page=dashboard
http://s1.altcoinix.com/swipp/public/index.php?page=dashboard
December 01, 2017, 11:27:18 AM
December 01, 2017, 08:06:38 AM
there is a guide to setup masternode vps linux?
December 01, 2017, 06:04:44 AM
Anybody can provided linux vps for MN setup ?
Thanks in advanced
Thanks in advanced
you can get it from vultr or digitalocean
December 01, 2017, 03:30:10 AM
Anybody can provided linux vps for MN setup ?
Thanks in advanced
Thanks in advanced
December 01, 2017, 01:59:33 AM
windows version 2.0.2 shows that i need 20.000 for a masternode. did i miss something???
you need 30000 that's just a typo it will be fixed in the next release, I saw that too when I just fired up my masternode today.Yeah, I was bummed by that, but now I have 30K, so its a little better.
I am not sure I really like this decreasing rewards for new MNs... but am willing to hang in there.
November 30, 2017, 11:02:34 PM
Hi erverybody. New wallet release is approaching. We will be setting a break to the next version at block 125 000. Watch this thread closely in the next few days. Masternode payments will be significantly higher with this release. As before, anybody that has not updated once we reach 125 000, will be on a obsolete chain.
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
i set up masternode when 20k/node. i receive 60swp/day
then i set up masternode when 30k/node. i receive 48swp/day
the roi is very small
hope something new
Hi.
Indeed. The staking rewards in Swipp are lower now (they decreased from 5 to 3 Swipp at block 93 000. The next decrease in staking rewards is at block 200 000 - it will then go to 2 Swipp per block.
With those figures, your ROI is 58.4% which isn't all that bad. Currencies with 500%+ or several thousand percent in ROI have no future. Our focus is to build something long-term.
Nevertheless, the situation will improve with the next wallet release, as masternodes will receive PoW blocks also. The ROI will jump to roughly 350-450% after this change. This will make Swipp one of the more profitable masternode coins... However, more masternodes will then likely open, so returns will probably go down slightly as they do. We are preparing the next wallet release, so keep an eye on this thread.
Yours, team swipp
Actually, we only have 17 master nodes alive and 07 MN dead at this moment
17 mn = 450%... what about 300mn
You still alive
November 30, 2017, 08:17:44 PM
windows version 2.0.2 shows that i need 20.000 for a masternode. did i miss something???
you need 30000 that's just a typo it will be fixed in the next release, I saw that too when I just fired up my masternode today. November 30, 2017, 06:22:32 PM
windows version 2.0.2 shows that i need 20.000 for a masternode. did i miss something???
November 30, 2017, 01:57:38 PM
Hi erverybody. New wallet release is approaching. We will be setting a break to the next version at block 125 000. Watch this thread closely in the next few days. Masternode payments will be significantly higher with this release. As before, anybody that has not updated once we reach 125 000, will be on a obsolete chain.
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
i set up masternode when 20k/node. i receive 60swp/day
then i set up masternode when 30k/node. i receive 48swp/day
the roi is very small
hope something new
Hi.
Indeed. The staking rewards in Swipp are lower now (they decreased from 5 to 3 Swipp at block 93 000. The next decrease in staking rewards is at block 200 000 - it will then go to 2 Swipp per block.
With those figures, your ROI is 58.4% which isn't all that bad. Currencies with 500%+ or several thousand percent in ROI have no future. Our focus is to build something long-term.
Nevertheless, the situation will improve with the next wallet release, as masternodes will receive PoW blocks also. The ROI will jump to roughly 350-450% after this change. This will make Swipp one of the more profitable masternode coins... However, more masternodes will then likely open, so returns will probably go down slightly as they do. We are preparing the next wallet release, so keep an eye on this thread.
Yours, team swipp
Actually, we only have 17 master nodes alive and 07 MN dead at this moment
17 mn = 450%... what about 300mn
November 30, 2017, 01:14:17 PM
Hi erverybody. New wallet release is approaching. We will be setting a break to the next version at block 125 000. Watch this thread closely in the next few days. Masternode payments will be significantly higher with this release. As before, anybody that has not updated once we reach 125 000, will be on a obsolete chain.
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
i set up masternode when 20k/node. i receive 60swp/day
then i set up masternode when 30k/node. i receive 48swp/day
the roi is very small
hope something new
Hi.
Indeed. The staking rewards in Swipp are lower now (they decreased from 5 to 3 Swipp at block 93 000. The next decrease in staking rewards is at block 200 000 - it will then go to 2 Swipp per block.
With those figures, your ROI is 58.4% which isn't all that bad. Currencies with 500%+ or several thousand percent in ROI have no future. Our focus is to build something long-term.
Nevertheless, the situation will improve with the next wallet release, as masternodes will receive PoW blocks also. The ROI will jump to roughly 350-450% after this change. This will make Swipp one of the more profitable masternode coins... However, more masternodes will then likely open, so returns will probably go down slightly as they do. We are preparing the next wallet release, so keep an eye on this thread.
Yours, team swipp
Actually, we only have 17 master nodes alive and 07 MN dead at this moment
November 30, 2017, 12:36:51 PM
Hi erverybody. New wallet release is approaching. We will be setting a break to the next version at block 125 000. Watch this thread closely in the next few days. Masternode payments will be significantly higher with this release. As before, anybody that has not updated once we reach 125 000, will be on a obsolete chain.
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
i set up masternode when 20k/node. i receive 60swp/day
then i set up masternode when 30k/node. i receive 48swp/day
the roi is very small
hope something new
Hi.
Indeed. The staking rewards in Swipp are lower now (they decreased from 5 to 3 Swipp at block 93 000. The next decrease in staking rewards is at block 200 000 - it will then go to 2 Swipp per block.
With those figures, your ROI is 58.4% which isn't all that bad. Currencies with 500%+ or several thousand percent in ROI have no future. Our focus is to build something long-term.
Nevertheless, the situation will improve with the next wallet release, as masternodes will receive PoW blocks also. The ROI will jump to roughly 350-450% after this change. This will make Swipp one of the more profitable masternode coins... However, more masternodes will then likely open, so returns will probably go down slightly as they do. We are preparing the next wallet release, so keep an eye on this thread.
Yours, team swipp
November 30, 2017, 11:31:09 AM
Hi erverybody. New wallet release is approaching. We will be setting a break to the next version at block 125 000. Watch this thread closely in the next few days. Masternode payments will be significantly higher with this release. As before, anybody that has not updated once we reach 125 000, will be on a obsolete chain.
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
i set up masternode when 20k/node. i receive 60swp/day
then i set up masternode when 30k/node. i receive 48swp/day
the roi is very small
hope something new
Hi.
Indeed. The staking rewards in Swipp are lower now (they decreased from 5 to 3 Swipp at block 93 000. The next decrease in staking rewards is at block 200 000 - it will then go to 2 Swipp per block.
With those figures, your ROI is 58.4% which isn't all that bad. Currencies with 500%+ or several thousand percent in ROI have no future. Our focus is to build something long-term.
Nevertheless, the situation will improve with the next wallet release, as masternodes will receive PoW blocks also. The ROI will jump to roughly 350-450% after this change. This will make Swipp one of the more profitable masternode coins... However, more masternodes will then likely open, so returns will probably go down slightly as they do. We are preparing the next wallet release, so keep an eye on this thread.
Yours, team swipp
November 30, 2017, 10:50:37 AM
Hi erverybody. New wallet release is approaching. We will be setting a break to the next version at block 125 000. Watch this thread closely in the next few days. Masternode payments will be significantly higher with this release. As before, anybody that has not updated once we reach 125 000, will be on a obsolete chain.
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
i set up masternode when 20k/node. i receive 60swp/day
then i set up masternode when 30k/node. i receive 48swp/day
the roi is very small
hope something new
November 30, 2017, 07:16:54 AM
With the new swipp wallet, don't forget to update for this issue:
https://github.com/bitcoin/bitcoin/issues/7086
I'll be happy to test build it on Raspberry Pi (which easily exercises the issue) as a beta tester if you'd like.
Fusion
https://github.com/bitcoin/bitcoin/issues/7086
I'll be happy to test build it on Raspberry Pi (which easily exercises the issue) as a beta tester if you'd like.
Fusion
Thank you for all the feedback @Fusion.
To clear up some of your questions;
Masternode distance/proximity between masternodes will be determined using a combination of geoip localization and simple tracerouting. At some point, this feature was discussed and planned in DASH but never got implemented.
We are aware of the issue discussed in https://github.com/bitcoin/bitcoin/issues/7086. This is caused by an API change between OpenSSL1.1/OpenSSL2. We plan to update the code base to SSL2 at a later point. For now (while there are some more pressing things to handle), SSL1.1 works just fine. That being said, pull requests are always welcome if anybody would like a crack at it.
When it comes to the bounty system - DASH (and a few other currencies) have a voting system where masternodes can vote on different proposals. It's still very centralized and requires the core development team to handle all the funds. We want to take it one step further and completely decentralize the process.
Comcerning test building, the whole development team currently consists of Linux nerds, so what we really need is a Windows and/or OS X maintainer.
Yours, team swipp
November 30, 2017, 03:09:11 AM
With the new swipp wallet, don't forget to update for this issue:
https://github.com/bitcoin/bitcoin/issues/7086
I'll be happy to test build it on Raspberry Pi (which easily exercises the issue) as a beta tester if you'd like.
Fusion
https://github.com/bitcoin/bitcoin/issues/7086
I'll be happy to test build it on Raspberry Pi (which easily exercises the issue) as a beta tester if you'd like.
Fusion
November 30, 2017, 02:37:15 AM
Hi erverybody. New wallet release is approaching. We will be setting a break to the next version at block 125 000. Watch this thread closely in the next few days. Masternode payments will be significantly higher with this release. As before, anybody that has not updated once we reach 125 000, will be on a obsolete chain.
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
While making masternodes meaningful is valuable, how will distance/proximity be determined? I can buy an MN in my basement and create 40 ms between it and the rest of the world and be rewarded because I appear to be far away from all of the other MNs.
Separately, forcing MNs to not share physical hosts is not a bad idea. It will penalize hosters like Vultr -- who, while they may be on different IPs, aren't necessarily going to be far from each other.
The logical resolution of this distance issue is that instead of using hosters, people will host MNs on their residential internet connections and universities ... which improves diversity at the sacrifice of resilience.
Fusion
November 30, 2017, 02:33:15 AM
Hello everybody.
To be honest, the idea of a dev-fee with funds going to an address controlled by us, personally makes me very nervous. So I am personally agreeing with @fusionfoto on this one.
That being said, instead of a "dev-fee", we have talked about a bounty system governed by the masternodes. Basically, we are thinking that we allocate maybe 5% of all newly generated coins to this bounty fund - the masternodes can then issue new bounties and allocate rewards..... A bounty is only enabled once a certain number of masternodes all agree upon it. The same goes for payment of the bounty - a certain amount of masternodes need to reach consensus before it is paid out. Anybody will be able to apply for the bounties (the current core dev team included).
To be honest, the idea of a dev-fee with funds going to an address controlled by us, personally makes me very nervous. So I am personally agreeing with @fusionfoto on this one.
That being said, instead of a "dev-fee", we have talked about a bounty system governed by the masternodes. Basically, we are thinking that we allocate maybe 5% of all newly generated coins to this bounty fund - the masternodes can then issue new bounties and allocate rewards..... A bounty is only enabled once a certain number of masternodes all agree upon it. The same goes for payment of the bounty - a certain amount of masternodes need to reach consensus before it is paid out. Anybody will be able to apply for the bounties (the current core dev team included).
The vision of this kind of governance is real. If you want the coin to last more than a few years and support the concept of larger scale adoption, some sort of stake-based governance is real. I think Dash has something similar. I think representing bounties in the blockchain is still up in the air a bit, but I think that with all of the ways to use the blockchain to send messaging, etc, there is a real way to build and manage consensus.
Fusion
November 30, 2017, 12:16:56 AM
Hi erverybody. New wallet release is approaching. We will be setting a break to the next version at block 125 000. Watch this thread closely in the next few days. Masternode payments will be significantly higher with this release. As before, anybody that has not updated once we reach 125 000, will be on a obsolete chain.
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
Great.
Hope this update will make successful for Swipp
Jump to: