Bitcoin Forum
August 09, 2024, 11:41:53 PM *
News: Latest Bitcoin Core release: 27.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 [96] 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 ... 177 »
  Print  
Author Topic: [ANN][OC] Orangecoin ★★ POS ★★ Anon Transactions ★★ Masternodes  (Read 209507 times)
Specialkey
Hero Member
*****
Offline Offline

Activity: 504
Merit: 500


View Profile
June 09, 2014, 03:53:55 PM
 #1901

Anything with about 80 Mio in 10 years arround would be even ok for me.
Only 84 Mio I am not a fan from this number as mentioned above. Grin
Halofire
Hero Member
*****
Offline Offline

Activity: 938
Merit: 1000


@halofirebtc


View Profile
June 09, 2014, 03:54:06 PM
 #1902

From Ramblers model: end at year 40 and we are good to go.
From OC's model: Increase schedule to 200 million, not 84.

Only reason I suggested adding the 20-30 million to cap was because we proved slashing everything in half would give same result except giving the holders a 100% increase in value.

Fellow oranges, reducing the cap does more damage than good or is pointless as I pointed out. Our coin would be minted too fast or we'd get too much value too quick - both instances resulting in a 'price catch up' against BTC for the next 20-30 years. It would increase the worth of our coins by too much, but if we must, I think I've found the middle ground....

Reduce cap by 1/3 to 133.33333333 million over '40' years. Gives everyone holding now 33% increase in value to compensate future PoS loss, cut PoS in half allows 83% ROI for the stakers which includes the 33% increase from cap reduction, apply 10-20% for MN 13.3 or 26.6 million which will be worth more since cap reduced. Cap = 133.3333333+13.33333333= 146.66666666 million for (10% MN) coin cap or 133.3333333+26.66666666= 160 million for (20% MN) coin cap. 'price catch up' would be less damaging, but we'd still be behind BTC price curve until BTC is finished mining.

My opinion which I haven't stated yet as to not influence others:
End PoS early to pay for Mnodes and leave cap at 200 million and leave all other specs the same. This hurts only those people now who would be holding coins for those last remaining years of PoS if they intended on holding the coins for the full 46 years. Price will remain the same, value of what's in circulation remains the same, oc:btc price curve will be on target. This way also benefits no one, versus the select holders if we reduced the cap

OC Development - oZwWbQwz6LAkDLa2pHsEH8WSD2Y3LsTgFt
SMC Development - SgpYdoVz946nLBF2hF3PYCVQYnuYDeQTGu
Friendly reminder: Back up your wallet.dat files!!
Specialkey
Hero Member
*****
Offline Offline

Activity: 504
Merit: 500


View Profile
June 09, 2014, 04:16:26 PM
 #1903

From Ramblers model: end at year 40 and we are good to go.
From OC's model: Increase schedule to 200 million, not 84.

Only reason I suggested adding the 20-30 million to cap was because we proved slashing everything in half would give same result except giving the holders a 100% increase in value.

Fellow oranges, reducing the cap does more damage than good or is pointless as I pointed out. Our coin would be minted too fast or we'd get too much value too quick - both instances resulting in a 'price catch up' against BTC for the next 20-30 years. It would increase the worth of our coins by too much, but if we must, I think I've found the middle ground....

Reduce cap by 1/3 to 133.33333333 million over '40' years. Gives everyone holding now 33% increase in value to compensate future PoS loss, cut PoS in half allows 83% ROI for the stakers which includes the 33% increase from cap reduction, apply 10-20% for MN 13.3 or 26.6 million which will be worth more since cap reduced. Cap = 133.3333333+13.33333333= 146.66666666 million for (10% MN) coin cap or 133.3333333+26.66666666= 160 million for (20% MN) coin cap. 'price catch up' would be less damaging, but we'd still be behind BTC price curve until BTC is finished mining.

My opinion which I haven't stated yet as to not influence others:
End PoS early to pay for Mnodes and leave cap at 200 million and leave all other specs the same. This hurts only those people now who would be holding coins for those last remaining years of PoS if they intended on holding the coins for the full 46 years. Price will remain the same, value of what's in circulation remains the same, oc:btc price curve will be on target. This way also benefits no one, versus the select holders if we reduced the cap


Understood and I agree. Wink

I like your model and even the mn should get 20%. They are important and should be well rewarded all time. Smiley

Jim_Rambler
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
June 09, 2014, 04:18:59 PM
 #1904

on what % of trans will ppl will actually need/desire anon?
If this is a fraction, less than 10% why are we paying an arm and leg for 100% anon
when optional would take a fraction of the Mnodes/cost and please as many people?

i mean who cares if the nsa finds out i buy my shorts at overstock

It takes a certain amount of maternodes to make the feature secure. Need a good amount of nodes to be avalible to make it secure, and decentralized. To do this there is a balance, which is what we are all working on to create


Halofire: great point, on my moblie now but will run these numbers soon, Cheers
Dancingk
Member
**
Offline Offline

Activity: 84
Merit: 10


View Profile
June 09, 2014, 04:19:18 PM
 #1905

should i buy some OC now Cool

bep42
Hero Member
*****
Offline Offline

Activity: 910
Merit: 500


View Profile
June 09, 2014, 04:20:21 PM
 #1906

should i buy some OC now Cool

you'll find some on Kingcoiny my friend! > https://www.kingcoiny.com/index.php?page=trade&market=18
Specialkey
Hero Member
*****
Offline Offline

Activity: 504
Merit: 500


View Profile
June 09, 2014, 04:22:53 PM
 #1907


and sell volume climbs  Grin
bep42
Hero Member
*****
Offline Offline

Activity: 910
Merit: 500


View Profile
June 09, 2014, 04:33:58 PM
 #1908


sure! This community is awesome!
Halofire
Hero Member
*****
Offline Offline

Activity: 938
Merit: 1000


@halofirebtc


View Profile
June 09, 2014, 04:43:20 PM
 #1909


Can't believe OC still trading over 500 satoshi at your place! Way to be!  Grin

OC Development - oZwWbQwz6LAkDLa2pHsEH8WSD2Y3LsTgFt
SMC Development - SgpYdoVz946nLBF2hF3PYCVQYnuYDeQTGu
Friendly reminder: Back up your wallet.dat files!!
cryptoba
Sr. Member
****
Offline Offline

Activity: 435
Merit: 250


View Profile
June 09, 2014, 04:44:25 PM
 #1910

Oangecoin, Halofire, Jim Rambler,

I think you should take a decision. You should discuss all those interesting thoughts and come out with a great structure  Grin
We reduce the coin cap, keep a nice Pos system and have a great Masternodes system. I think we shouldn't compare too much with other coins. As, what is being decided is being talked about, and is not hidden. All those changes are justified and thought about.
The most important is to come out with an attractive and clear structure.

And everybody will find it great Cheesy
btcMagnet
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
June 09, 2014, 05:01:28 PM
 #1911

End PoS early to pay for Mnodes and leave cap at 200 million and leave all other specs the same. This hurts only those people now who would be holding coins for those last remaining years of PoS if they intended on holding the coins for the full 46 years. Price will remain the same, value of what's in circulation remains the same, oc:btc price curve will be on target. This way also benefits no one, versus the select holders if we reduced the cap
This is a good paragraph.  46 years would take the sting out.
Halofire
Hero Member
*****
Offline Offline

Activity: 938
Merit: 1000


@halofirebtc


View Profile
June 09, 2014, 05:36:04 PM
 #1912

End PoS early to pay for Mnodes and leave cap at 200 million and leave all other specs the same. This hurts only those people now who would be holding coins for those last remaining years of PoS if they intended on holding the coins for the full 46 years. Price will remain the same, value of what's in circulation remains the same, oc:btc price curve will be on target. This way also benefits no one, versus the select holders if we reduced the cap
This is a good paragraph.  46 years would take the sting out.

It wouldn't be 46 years, that's what it is now. We'd shorten POS to 39-40 years, if this option is chosen.

OC Development - oZwWbQwz6LAkDLa2pHsEH8WSD2Y3LsTgFt
SMC Development - SgpYdoVz946nLBF2hF3PYCVQYnuYDeQTGu
Friendly reminder: Back up your wallet.dat files!!
Halofire
Hero Member
*****
Offline Offline

Activity: 938
Merit: 1000


@halofirebtc


View Profile
June 09, 2014, 05:41:28 PM
 #1913

get voting on mintpal, we are 10 votes away from taking the next spot from pinkcoin............  Wink

OC Development - oZwWbQwz6LAkDLa2pHsEH8WSD2Y3LsTgFt
SMC Development - SgpYdoVz946nLBF2hF3PYCVQYnuYDeQTGu
Friendly reminder: Back up your wallet.dat files!!
btcMagnet
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
June 09, 2014, 05:47:39 PM
 #1914

End PoS early to pay for Mnodes and leave cap at 200 million and leave all other specs the same. This hurts only those people now who would be holding coins for those last remaining years of PoS if they intended on holding the coins for the full 46 years. Price will remain the same, value of what's in circulation remains the same, oc:btc price curve will be on target. This way also benefits no one, versus the select holders if we reduced the cap
This is a good paragraph.  46 years would take the sting out.

It wouldn't be 46 years, that's what it is now. We'd shorten POS to 39-40 years, if this option is chosen.
I see this but it still appears to defer the effect long enough to make it irrelevant.

Yet there is still a price for current investors, remember... all new coins created for rewards will reduce holder equity (now not in 46 years), while coins minted do not reduce equity, provided the holder is minting.

hmmm we have 3 kinds of oranges here

ppl trying to make the sweetest deal they can for their planned Mnodes
ppl trying to preserve the equity that was promised when they bought into the coin
and the devs caught in the middle

I'm more worried about overpaying the Mnodes than under.  OC pointed out yesterday that the price of orange is going up, 10x and more. so maybe we should have some way to adjust the Mnodes rewards, keep them fat and happy but not obscene.
Halofire
Hero Member
*****
Offline Offline

Activity: 938
Merit: 1000


@halofirebtc


View Profile
June 09, 2014, 06:00:37 PM
 #1915

End PoS early to pay for Mnodes and leave cap at 200 million and leave all other specs the same. This hurts only those people now who would be holding coins for those last remaining years of PoS if they intended on holding the coins for the full 46 years. Price will remain the same, value of what's in circulation remains the same, oc:btc price curve will be on target. This way also benefits no one, versus the select holders if we reduced the cap
This is a good paragraph.  46 years would take the sting out.

It wouldn't be 46 years, that's what it is now. We'd shorten POS to 39-40 years, if this option is chosen.
I see this but it still appears to defer the effect long enough to make it irrelevant.

Yet there is still a price for current investors, remember... all new coins created for rewards will reduce holder equity (now not in 46 years), while coins minted do not reduce equity, provided the holder is minting.

hmmm we have 3 kinds of oranges here

ppl trying to make the sweetest deal they can for their planned Mnodes
ppl trying to preserve the equity that was promised when they bought into the coin
and the devs caught in the middle

I'm more worried about overpaying the Mnodes than under.  OC pointed out yesterday that the price of orange is going up, 10x and more. so maybe we should have some way to adjust the Mnodes rewards, keep them fat and happy but not obscene.

What I highlighted in orange is exactly what I was getting at, but you said it much better.

Edit: Your next thought, The 'price paid by investors'  would be 20% divided by 39-40 years, going back to the orange highlight comment.

OC Development - oZwWbQwz6LAkDLa2pHsEH8WSD2Y3LsTgFt
SMC Development - SgpYdoVz946nLBF2hF3PYCVQYnuYDeQTGu
Friendly reminder: Back up your wallet.dat files!!
Jim_Rambler
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
June 09, 2014, 06:05:44 PM
 #1916

hmmm we have 3 kinds of oranges here

ppl trying to make the sweetest deal they can for their planned Mnodes
ppl trying to preserve the equity that was promised when they bought into the coin
and the devs caught in the middle

I'm more worried about overpaying the Mnodes than under.  OC pointed out yesterday that the price of orange is going up, 10x and more. so maybe we should have some way to adjust the Mnodes rewards, keep them fat and happy but not obscene.

Ok how about this?


   Coins produced            PoS          PoS rewards      Masternodes    MN rewadrs
1   50,000,000             20%          10000000                      2%            1000000
2   61,000,000             10%             6100000                      1%             610000
3   67,710,000             5%             3385500                   0.5%              338550
4   71,434,050            2.5%           1785851.25             0.25%         178585.125
5   73,398,486.375      2.5%           1834962.159           0.25%          183496.21593
6   75,416,944.7503    2.5%            1885423.618           0.25%        188542.36187
7   77,490,910.7309    2.5%            1937272.76827       0.25%        193727.27682
8   79,621,910.7760    2.5%           1990547.76940        0.25%        199054.77694
9   81,811,513.3223    2.5%           2045287.83305       0.25%        204528.78330
10   84,061,329.9387    2.5%         2101533.24846       0.25%        210153.32484


See how the last column goes up exponentially, what if we deduce the % in a reverse exponential function and shift that extra to more PoS or longer. Meaning do it so that even then though the amount of coins raise each year, the Mnodes still receive the same constant amount.  
bep42
Hero Member
*****
Offline Offline

Activity: 910
Merit: 500


View Profile
June 09, 2014, 06:09:48 PM
 #1917

Just a simple comparaison :

Bittrex last price : 0.00000436 BTC
Kingcoiny last price : 0.00000533 BTC

Bittrex best buys orders : 0.00000435 BTC
Kingociny best buys orders : 0.00000520 BTC

Make the good choice, choose Kingcoiny > https://www.kingcoiny.com/index.php?page=trade&market=OC

the best,
Ben
btcMagnet
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
June 09, 2014, 06:33:03 PM
 #1918

hmmm we have 3 kinds of oranges here

ppl trying to make the sweetest deal they can for their planned Mnodes
ppl trying to preserve the equity that was promised when they bought into the coin
and the devs caught in the middle

I'm more worried about overpaying the Mnodes than under.  OC pointed out yesterday that the price of orange is going up, 10x and more. so maybe we should have some way to adjust the Mnodes rewards, keep them fat and happy but not obscene.

Ok how about this?


   Coins produced            PoS          PoS rewards      Masternodes    MN rewadrs
1   50,000,000             20%          10000000                      2%            1000000
2   61,000,000             10%             6100000                      1%             610000
3   67,710,000             5%             3385500                   0.5%              338550
4   71,434,050            2.5%           1785851.25             0.25%         178585.125
5   73,398,486.375      2.5%           1834962.159           0.25%          183496.21593
6   75,416,944.7503    2.5%            1885423.618           0.25%        188542.36187
7   77,490,910.7309    2.5%            1937272.76827       0.25%        193727.27682
8   79,621,910.7760    2.5%           1990547.76940        0.25%        199054.77694
9   81,811,513.3223    2.5%           2045287.83305       0.25%        204528.78330
10   84,061,329.9387    2.5%         2101533.24846       0.25%        210153.32484


See how the last column goes up exponentially, what if we deduce the % in a reverse exponential function and shift that extra to more PoS or longer. Meaning do it so that even then though the amount of coins raise each year, the Mnodes still receive the same constant amount.  
I think a price like this can only be realistically and efficiently set by the free and constantly changing market, so it would be optimal (if possible) to have something like bidding every year, with the devs deciding who gets nodes based on performance expectations and price (lower bids).  We just don't want to end up with some pay plan set in stone that pays nodes way beyond reasonable.
Jim_Rambler
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
June 09, 2014, 06:42:14 PM
 #1919

hmmm we have 3 kinds of oranges here

ppl trying to make the sweetest deal they can for their planned Mnodes
ppl trying to preserve the equity that was promised when they bought into the coin
and the devs caught in the middle

I'm more worried about overpaying the Mnodes than under.  OC pointed out yesterday that the price of orange is going up, 10x and more. so maybe we should have some way to adjust the Mnodes rewards, keep them fat and happy but not obscene.

Ok how about this?


   Coins produced            PoS          PoS rewards      Masternodes    MN rewadrs
1   50,000,000             20%          10000000                      2%            1000000
2   61,000,000             10%             6100000                      1%             610000
3   67,710,000             5%             3385500                   0.5%              338550
4   71,434,050            2.5%           1785851.25             0.25%         178585.125
5   73,398,486.375      2.5%           1834962.159           0.25%          183496.21593
6   75,416,944.7503    2.5%            1885423.618           0.25%        188542.36187
7   77,490,910.7309    2.5%            1937272.76827       0.25%        193727.27682
8   79,621,910.7760    2.5%           1990547.76940        0.25%        199054.77694
9   81,811,513.3223    2.5%           2045287.83305       0.25%        204528.78330
10   84,061,329.9387    2.5%         2101533.24846       0.25%        210153.32484


See how the last column goes up exponentially, what if we deduce the % in a reverse exponential function and shift that extra to more PoS or longer. Meaning do it so that even then though the amount of coins raise each year, the Mnodes still receive the same constant amount.  
I think a price like this can only be realistically and efficiently set by the free and constantly changing market, so it would be optimal (if possible) to have something like bidding every year, with the devs deciding who gets nodes based on performance expectations and price (lower bids).  We just don't want to end up with some pay plan set in stone that pays nodes way beyond reasonable.


Lets not for get the masternodes buying the req. amount of OC to start one will also raise the over all price. They should raise together in ROI, this helps offset the cost to buy the OC at start up. Lets not for get that if OC raises to $2 per coin it will cost $4,000 to start one, and that ROI needs to be equal to coins price.
Halofire
Hero Member
*****
Offline Offline

Activity: 938
Merit: 1000


@halofirebtc


View Profile
June 09, 2014, 06:43:31 PM
 #1920

hmmm we have 3 kinds of oranges here

ppl trying to make the sweetest deal they can for their planned Mnodes
ppl trying to preserve the equity that was promised when they bought into the coin
and the devs caught in the middle

I'm more worried about overpaying the Mnodes than under.  OC pointed out yesterday that the price of orange is going up, 10x and more. so maybe we should have some way to adjust the Mnodes rewards, keep them fat and happy but not obscene.

Ok how about this?


   Coins produced            PoS          PoS rewards      Masternodes    MN rewadrs
1   50,000,000             20%          10000000                      2%            1000000
2   61,000,000             10%             6100000                      1%             610000
3   67,710,000             5%             3385500                   0.5%              338550
4   71,434,050            2.5%           1785851.25             0.25%         178585.125
5   73,398,486.375      2.5%           1834962.159           0.25%          183496.21593
6   75,416,944.7503    2.5%            1885423.618           0.25%        188542.36187
7   77,490,910.7309    2.5%            1937272.76827       0.25%        193727.27682
8   79,621,910.7760    2.5%           1990547.76940        0.25%        199054.77694
9   81,811,513.3223    2.5%           2045287.83305       0.25%        204528.78330
10   84,061,329.9387    2.5%         2101533.24846       0.25%        210153.32484


See how the last column goes up exponentially, what if we deduce the % in a reverse exponential function and shift that extra to more PoS or longer. Meaning do it so that even then though the amount of coins raise each year, the Mnodes still receive the same constant amount.  

just keep halving the mn payout % every few years until the MN 'fund' runs out of coin. it will produce a longer but consistent payout schedule for the Mnodes to collect well past when PoS ends.

OC Development - oZwWbQwz6LAkDLa2pHsEH8WSD2Y3LsTgFt
SMC Development - SgpYdoVz946nLBF2hF3PYCVQYnuYDeQTGu
Friendly reminder: Back up your wallet.dat files!!
Pages: « 1 ... 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 [96] 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 ... 177 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!