Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 157. (Read 782370 times)

Quote from: iloveBTCtomuch on April 25, 2017, 10:14:35 PM
Quote
Very interesting:
https://www.dashforcenews.com/5-reasons-why-dash-evolution-will-blow-competitors-away/

https://youtu.be/7J4m04Tkfb4

Dash: 2 million coins pre-mined or 72,000,000 (sorry my mistake x 2 staggering amount of 144,000,000 dollars!)  USD escaped open market trade to hands of a few or downright fraud has been committed  

hence.. not very interesting, at least not to many

Nope not true, it was not a pre-mine it was an instamine, and their is lots and lots of info on that. On the other hand:
PIVX a 100% fastmine

To sum it up:
-DASH is only a 10% instamine of the totall coin supply  vs 100% fastmine with masternodes earning straight from the start with PIVX
- PIVX had only a mining periode of 181 day's, 70% minined out in less than 100 days
- PIVx two anonymous creators did burn their pre-mine of 6 masternodes, but kept the rewards (anyways it worked out well from a markting perspective, my compliments )
- PIVX masternodes earned straight from the start, the rewards where so large that early holders, never had to sell their mn
- PIVX hash-rate has been very low during the POW mining fase, aka few people where mining it
- PIVX its coin distribution especially during and just after the POW fase was very concentrated, still close to 250 addresses held during this quick rise in marketcap (the smart owners either sold off allot or at the very least divided their holdings of multiple addresses
http://www.presstab.pw/phpexplorer/PIVX/richlist.php?count=250

Very little info to clear up the 100% fastmine of PIVX but plenty of good information on DASH it's 10% instamine:

Evan Duffield has no more than 256,000 Dash and will give away 80% of that to fund DAOs within DASH https://www.reddit.com/r/dashpay/comments/62jc3b/evan_duffield_has_no_more_than_256000_dash_and/
Dash Instamine Issue Clarification https://dashpay.atlassian.net/wiki/display/OC/Dash+Instamine+Issue+Clarification
Instamine FAQ https://dashpay.atlassian.net/wiki/display/DOC/Legacy+FAQ#LegacyFAQ-WasDashInstamined
Was The Instamine A Positive Thing For Dash? https://dashdot.io/alpha/?page_id=118
My View: Dash’s Instamine Is Not A Problem http://fintekneeks.com/my-view-dashs-pre-mine-is-not-a-problem/
Deep technical analysis of the early mining and distribution https://bitcointalksearch.org/topic/m.15619552
Confessions of a Instaminer Hashman https://bitcointalksearch.org/topic/m.18041424


who is this joker?? where have you been the last 3 years that it has been proven in black and white dash is a scam?

Just take your total balance and divide it up between whichever addys you want to use and do it in successive transactions.

Much higher in my experience.  But after I kill my MNs, how do I rebalance my wallet addresses?

No one has answered yet.  Yes, I know I can just "send" to an address, but how do I know which address it's being sent from... or how much is in that address in the first place so I can balance my staking addresses.

And on that last note, how do I check the balances of my addresses so I can do that better?

Staking is easier to do, and could result in higher payouts depending on your luck.

Just send the coins to the address you want them to be in, same as if you were sending to any other address. The wallet will label it as a transfer to yourself. If it's for a MN and you're adding up to 10K with a bunch of smaller inputs, you'd have to accumulate 10K+ in a single address and then transfer exactly 10K in a single transaction from there to your desired MN address.

Also, re: MN payout frequency...

The 3+ day thing is just at the start, after you've enabled your MN. After that, the payout will, on average, follow the expected rate given the current block reward and number of MNs on the network. Having run MNs for well more than a year now, I've never had a deviation from the expected payout schedule of more than a few hours either way, and the overall payout rate has always matched the expected rate.

Given the current number of MNs, staking is very nearly as attractive as running a MN. So if you don't want the hassle of managing a MN, staking may well be the better option for you. Personally, I prefer MNs because you don't need to keep the controller wallet online, which feels more secure, and you're better positioned to take advantage of the uptick in payout amount/rate that comes if/when there's a selloff or network hiccup.

Also, is there a user friendly way to move coins within internal addresses on the controller wallet?

Ex:  I've generated 6 total addresses now, how can I neatly organize my PIVX into 2 addresses within my wallet?

It could be less, for example, if some other masternodes are shut down or have a misconfigured firewall perhaps.

I'm not sure about the consensus algorithm for how the winning masternodes are chosen. I have had a masternode get no payments for a bit longer period and then have rewards come in more quickly. But it should average out.

At the moment I count 380 masternodes that haven't received payments. I may try to collect some more data and see how the situation changes.

EDIT: For me, masternode payments have started coming in after 90 hours.

So it's a consistent 1.4 day rotation through the 2070 MNs for 1 block reward?

Once the masternode gets the first block, the next ones come in turn according to the number of masternodes.

The transactions for the masternode(s) are "locked" when you start your wallet. (pivxd reads the transaction list from the masternode.conf file).

If you comment or remove those lines from the masternode.conf and restart the wallet, transactions that were reserved for the masternode will be able to stake. After those transactions stake, they will not be able to be used for a masternode so you would need to go through the process of setting up the masternode again.

I think the the block rewards would be about the same or maybe a tad more than the equivalent time staking. The three+ day wait is a bit painful considering that the block reward is scheduled to halve when we reach "PoS Phase X: [blocks 648000-Infinite] 05 PIV (90% SEESAW ~ 10% BUDGET)". Certain upgrades need a restart and then all who run masternodes need to wait some time. This is longer than before but there are more masternodes now than when I was running this before.

Myself, I had been staking for the last while since running masternodes needs a bit more effort and attention. I put some pivx back into masternodes for this upgrade a bit over 3 days ago, thinking I would get a bit more in this last month with the higher reward. It's hard to say what the best decision would be there's another 21+ days to go until the block reward halving.
 
With 2037 masternodes, a masternode payout should about about every 1.4 days.

According to one of my masternodes about an hour ago, here's a list of the largest uptimes  for unpaid masternodes in seconds....

  325883
  325933
  325984
  326057
  326120
  326139
  331264
  340139
  345954
  408003

The last one seems to be an outlier, it's possible that it is misconfigured.  (Yesterday when I looked the oldest ones were in the 360000 seconds range.

At the moment, the oldest unpaid masternode was started 113 hours (4.7 days) ago and the next one 96 hours (4 days).

I would say be patient and don't mess with anything if you started less than 4 days ago.
Can't say for sure how long it would take if a masternode was restarted today.

If you would like to check that the masternode is running ok can try running the following on the masternode.

"$ pivx-cli masternode debug
Masternode successfully started"

If it is more than four days, you might want to have a check that how many peers are connected and that other peers are able to connect to it.

Maybe someone with more technical knowledge here can could provide some more detail for things to check.

I suppose... it is ok for a masternode to not have any inbound peers as long as masternodes are able to make connections to the masternode's port 51472 at its advertised IP address or TOR address.

you need to wait ~3 days
if the node is listed as enbaled on controller wallet and you see  "status" : "Masternode successfully started" on vps just wait
after updating to 2.2.0 you need to to start the node on vps too