[ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 492.

kokokoin

hero member

Activity: 638

Merit: 500

Quote from: bathrobehero on March 09, 2016, 07:53:15 AM

What about masternode payouts?

Not changing, like in the firs post of ANN:

Quote

PoW Rewards Breakdown: [0000002-0043200] 20% MNODE / 80% MINER
PoW Rewards Breakdown: [0043201-0259201] 20% MNODE / 70% MINER / 10% PROPOSALS

bathrobehero

legendary

Activity: 2002

Merit: 1051

ICO? Not even once.

Quote from: Zeraful on March 09, 2016, 07:47:23 AM

Why are there unqualified masternodes, mine apparently is also unqualified? There should seriously be more in-depth guide for masternodes and other related items, it is going to be a must in the future. The setup guide is okay but it is seriously lacking troubleshooting completely which is necessary for this to grow. Imo.

There are pelnty of masternode guides for other coins which you can find in google.

Quote from: kokokoin on March 09, 2016, 07:51:51 AM

I want to remind you about this proposal. Even if you don't like it, please vote 'no' to show number of atcive masternode owners. But i think DNET POW should be decreased to keep the coin attractive to new investors.

Quote from: kokokoin on March 07, 2016, 05:37:12 AM

I am a miner and masternodes owner. I think constant supply during POW phase is bad for cryptocurrency. It leads to constant inflation and therefore fading of interest of investors.

My proposal for supply reduction during POW phase. It will decrease inflation, leaving enough coins for fair distribution. We will have total of 45 360 000 coins at the end of the POW phase instead of 64 800 000 coins (-19 440 000 coins).

Blocks 1 - 86 400 (56 days)
POW reward: 250 DNET
Total supply: 21 600 000

Blocks 86 401 - 172 800 (56 days)
POW reward: 175 DNET
Total supply: 36 720 000

Blocks 172 801 - 259 200 (56 days)
POW reward: 100 DNET
Total supply: 45 360 000

Blocks 259 200 +
POS

To vote in favor = "mnbudget vote eb800b00add41c506738592d8cc7de53c17bbfec4ca572b77c778632c57e2c3c yes"
To vote against = "mnbudget vote eb800b00add41c506738592d8cc7de53c17bbfec4ca572b77c778632c57e2c3c no"
(use 'vote-many' instead of 'vote' to vote using all your MN at once via controller wallet).

What about masternode payouts?

kokokoin

hero member

Activity: 638

Merit: 500

I want to remind you about this proposal. Even if you don't like it, please vote 'no' to show number of atcive masternode owners. But i think DNET POW should be decreased to keep the coin attractive to new investors.

Quote from: kokokoin on March 07, 2016, 05:37:12 AM

I am a miner and masternodes owner. I think constant supply during POW phase is bad for cryptocurrency. It leads to constant inflation and therefore fading of interest of investors.

My proposal for supply reduction during POW phase. It will decrease inflation, leaving enough coins for fair distribution. We will have total of 45 360 000 coins at the end of the POW phase instead of 64 800 000 coins (-19 440 000 coins).

Blocks 1 - 86 400 (56 days)
POW reward: 250 DNET
Total supply: 21 600 000

Blocks 86 401 - 172 800 (56 days)
POW reward: 175 DNET
Total supply: 36 720 000

Blocks 172 801 - 259 200 (56 days)
POW reward: 100 DNET
Total supply: 45 360 000

Blocks 259 200 +
POS

To vote in favor = "mnbudget vote eb800b00add41c506738592d8cc7de53c17bbfec4ca572b77c778632c57e2c3c yes"
To vote against = "mnbudget vote eb800b00add41c506738592d8cc7de53c17bbfec4ca572b77c778632c57e2c3c no"
(use 'vote-many' instead of 'vote' to vote using all your MN at once via controller wallet).

Zeraful

full member

Activity: 214

Merit: 100

Why are there unqualified masternodes, mine apparently is also unqualified? There should seriously be more in-depth guide for masternodes and other related items, it is going to be a must in the future. The setup guide is okay but it is seriously lacking troubleshooting completely which is necessary for this to grow. Imo.

q327K091

legendary

Activity: 1792

Merit: 1010

Quote from: borris123 on March 09, 2016, 03:12:28 AM

Quote from: q327K091 on March 09, 2016, 12:07:17 AM

update: 9th MN has been started successfully, might as well keep on going with VPS or local virtualization, we shall see...

If you do local virtualization how do u need to get more IPS off isp?

very true, thanks Boris I aint getting more IP's so we are just will be going after VPS , goal is no less then 50 MN's and we stop at that point

let me see 50 x 500 (~ approx) DNET = 25,000 DNET a day , and nice part about it for y ll I aint selling and will be creating base demand

at the same time dev(s) here are thinking deep and hard on cryptology problems it all is moving the right direction

why 50 ? life is too short don't waste it

borris123

hero member

Activity: 728

Merit: 500

If u have already used masternode start-many don't use it again everyone as I found out yesterday it resets the time and takes hours again to get a transaction

borris123

hero member

Activity: 728

Merit: 500

Quote from: danonthehill on March 09, 2016, 04:35:11 AM

Quote from: StakeBox on March 08, 2016, 10:18:37 PM

Quote from: danonthehill on March 08, 2016, 09:48:54 PM

Quote from: StakeBox on March 08, 2016, 09:32:01 PM

Quote from: danonthehill on March 08, 2016, 08:17:59 PM

I'm getting error: could not allocate vin when starting remote masternodes.

Sorry you are having issues. Is this a local Masternode, or a remote Masternode? Are you following the instructions in the OP? If it is a remote Masternode which wallet are you using to start it, and what is the command you are using? Are you sure that you have a confirmed transaction of exactly 10000 DNET in your wallet, if it is a remote Masternode, the coins are in your local wallet, right? More information is needed to troubleshoot your problem. There are quite a few places things could go wrong in the setup procedure, and without all of the relevant info it won't be possible to remotely solve.

Followed, cut & pasted this https://bitcointalksearch.org/topic/m.14138827 for remote .conf and OP for local .confs.

Using local wallet to start 6 remote MNs. Transactions sent 6 x 10000. Command: masternode start-many.

Get the error message for 1st 5 MNs, 6th says successful.

Thanks

I am going to look a bit deeper into this, but the first thing that comes to mind is, did you use coin control when sending the 6 transactions? It is possible that you sent 10k to the first address, and then when you sent 10k to the second address, since the initial 10k transaction wouldn't have been locked, it was combined with another input and used to send the second one, and so on down the line, until you sent the last one, which would be the only remaining full 10k input in your wallet. That would explain why only the last one started successfully. If you haven't already go to settings->options->wallet in your local wallet and enable coin control. Then, go to the sending page of the wallet and click on inputs. The screen that opens should show 6 10k inputs, if not, then that is what happened. I will try to figure out some other way you could be getting that error in the meantime, but I bet that is what happened.

Coin control wasn't enabled. Inputs shows 6x locked 10k transactions. Thanks a lot.

You tried masternode start-missing ? Check the vps which has masternode priv key on setup is correct. If it is showing a lock on it that from my understanding means it's working and won't allow you to send them as I had 10000 in a MN address but until I enabled vps it didn't lock the coins

danonthehill

hero member

Activity: 710

Merit: 500

Quote from: StakeBox on March 08, 2016, 10:18:37 PM

Quote from: danonthehill on March 08, 2016, 09:48:54 PM

Quote from: StakeBox on March 08, 2016, 09:32:01 PM

Quote from: danonthehill on March 08, 2016, 08:17:59 PM

I'm getting error: could not allocate vin when starting remote masternodes.

Sorry you are having issues. Is this a local Masternode, or a remote Masternode? Are you following the instructions in the OP? If it is a remote Masternode which wallet are you using to start it, and what is the command you are using? Are you sure that you have a confirmed transaction of exactly 10000 DNET in your wallet, if it is a remote Masternode, the coins are in your local wallet, right? More information is needed to troubleshoot your problem. There are quite a few places things could go wrong in the setup procedure, and without all of the relevant info it won't be possible to remotely solve.

Followed, cut & pasted this https://bitcointalksearch.org/topic/m.14138827 for remote .conf and OP for local .confs.

Using local wallet to start 6 remote MNs. Transactions sent 6 x 10000. Command: masternode start-many.

Get the error message for 1st 5 MNs, 6th says successful.

Thanks

I am going to look a bit deeper into this, but the first thing that comes to mind is, did you use coin control when sending the 6 transactions? It is possible that you sent 10k to the first address, and then when you sent 10k to the second address, since the initial 10k transaction wouldn't have been locked, it was combined with another input and used to send the second one, and so on down the line, until you sent the last one, which would be the only remaining full 10k input in your wallet. That would explain why only the last one started successfully. If you haven't already go to settings->options->wallet in your local wallet and enable coin control. Then, go to the sending page of the wallet and click on inputs. The screen that opens should show 6 10k inputs, if not, then that is what happened. I will try to figure out some other way you could be getting that error in the meantime, but I bet that is what happened.

Coin control wasn't enabled. Inputs shows 6x locked 10k transactions. Thanks a lot.

borris123

hero member

Activity: 728

Merit: 500

Quote from: q327K091 on March 09, 2016, 12:07:17 AM

update: 9th MN has been started successfully, might as well keep on going with VPS or local virtualization, we shall see...

If you do local virtualization how do u need to get more IPS off isp?

q327K091

legendary

Activity: 1792

Merit: 1010

update: 9th MN has been started successfully, might as well keep on going with VPS or local virtualization, we shall see...

StakeBox

full member

Activity: 226

Merit: 100

Quote from: danonthehill on March 08, 2016, 09:48:54 PM

Quote from: StakeBox on March 08, 2016, 09:32:01 PM

Quote from: danonthehill on March 08, 2016, 08:17:59 PM

I'm getting error: could not allocate vin when starting remote masternodes.

Sorry you are having issues. Is this a local Masternode, or a remote Masternode? Are you following the instructions in the OP? If it is a remote Masternode which wallet are you using to start it, and what is the command you are using? Are you sure that you have a confirmed transaction of exactly 10000 DNET in your wallet, if it is a remote Masternode, the coins are in your local wallet, right? More information is needed to troubleshoot your problem. There are quite a few places things could go wrong in the setup procedure, and without all of the relevant info it won't be possible to remotely solve.

Followed, cut & pasted this https://bitcointalksearch.org/topic/m.14138827 for remote .conf and OP for local .confs.

Using local wallet to start 6 remote MNs. Transactions sent 6 x 10000. Command: masternode start-many.

Get the error message for 1st 5 MNs, 6th says successful.

Thanks

I am going to look a bit deeper into this, but the first thing that comes to mind is, did you use coin control when sending the 6 transactions? It is possible that you sent 10k to the first address, and then when you sent 10k to the second address, since the initial 10k transaction wouldn't have been locked, it was combined with another input and used to send the second one, and so on down the line, until you sent the last one, which would be the only remaining full 10k input in your wallet. That would explain why only the last one started successfully. If you haven't already go to settings->options->wallet in your local wallet and enable coin control. Then, go to the sending page of the wallet and click on inputs. The screen that opens should show 6 10k inputs, if not, then that is what happened. I will try to figure out some other way you could be getting that error in the meantime, but I bet that is what happened.

danonthehill

hero member

Activity: 710

Merit: 500

Quote from: StakeBox on March 08, 2016, 09:32:01 PM

Quote from: danonthehill on March 08, 2016, 08:17:59 PM

I'm getting error: could not allocate vin when starting remote masternodes.

Sorry you are having issues. Is this a local Masternode, or a remote Masternode? Are you following the instructions in the OP? If it is a remote Masternode which wallet are you using to start it, and what is the command you are using? Are you sure that you have a confirmed transaction of exactly 10000 DNET in your wallet, if it is a remote Masternode, the coins are in your local wallet, right? More information is needed to troubleshoot your problem. There are quite a few places things could go wrong in the setup procedure, and without all of the relevant info it won't be possible to remotely solve.

Followed, cut & pasted this https://bitcointalksearch.org/topic/m.14138827 for remote .conf and OP for local .confs.

Using local wallet to start 6 remote MNs. Transactions sent 6 x 10000. Command: masternode start-many.

Get the error message for 1st 5 MNs, 6th says successful.

Thanks

StakeBox

full member

Activity: 226

Merit: 100

Quote from: danonthehill on March 08, 2016, 08:17:59 PM

I'm getting error: could not allocate vin when starting remote masternodes.

Sorry you are having issues. Is this a local Masternode, or a remote Masternode? Are you following the instructions in the OP? If it is a remote Masternode which wallet are you using to start it, and what is the command you are using? Are you sure that you have a confirmed transaction of exactly 10000 DNET in your wallet, if it is a remote Masternode, the coins are in your local wallet, right? More information is needed to troubleshoot your problem. There are quite a few places things could go wrong in the setup procedure, and without all of the relevant info it won't be possible to remotely solve.

danonthehill

hero member

Activity: 710

Merit: 500

Yes.

4x13

legendary

Activity: 1078

Merit: 1011

Quote from: danonthehill on March 08, 2016, 08:17:59 PM

I'm getting error: could not allocate vin when starting remote masternodes.

Is this a new Masternode??

danonthehill

hero member

Activity: 710

Merit: 500

I'm getting error: could not allocate vin when starting remote masternodes.

4x13

legendary

Activity: 1078

Merit: 1011

The lock allows you to toggle the locked inputs, but be careful, if you choose to mess with the 10k that is alotted to a masternode, you will have to redo your setup to get it working again.

avitas

sr. member

Activity: 302

Merit: 250

Quote from: bathrobehero on March 08, 2016, 05:52:42 AM

What I did was that I have my masternodes working separately but I have all the masternode wallets (private keys) imported to a local non-masternode wallet, with the main 10k fees locked so I can "milk" the masternodes easily anytime.

I did see a lock/unlock option in the coin control area, but don't know what it does. So by locking the 10k inputs? you can just spend as usual and don't worry about picking input any more?

this wallet already have some pretty nice features. the darknet red theme is a bit bright tho...maybe a darker red would look nicer.

4x13

legendary

Activity: 1078

Merit: 1011

Quote from: borris123 on March 08, 2016, 06:36:07 PM

Quote from: StakeBox on March 08, 2016, 06:34:17 PM

Quote from: kbhutto on March 08, 2016, 09:18:29 AM

@s3v3nh4cks miners are still getting 166.6 instead of 175 DNETs. No plan to fix this bug?

We have found and fixed the problem, we are cleaning up a few more things, expect a new release in the next week or so. In the meantime, if anyone notices anything else that should be checked, let us know. It will be a mandatory update, and the fix for the rewards will take effect at block 86400, all wallets will need to be updated three days before that. We will get you a more exact time the update must be completed by when we release the new wallet.

Anything else planned for release in this update? The road map is a little basic.

Would you prefer I fluff and embellish?? We are on a Road to steady updates and a reliable dev team. We are not going to purposely put stuff out that we knowing can not accomplish. Please feel free to make suggestions on features you would like us to consider, or create a proposal to have something added to the Roadmap. This is a community coin, get involved, let us hear your ideas..

borris123

hero member

Activity: 728

Merit: 500

Quote from: StakeBox on March 08, 2016, 06:34:17 PM

Quote from: kbhutto on March 08, 2016, 09:18:29 AM

@s3v3nh4cks miners are still getting 166.6 instead of 175 DNETs. No plan to fix this bug?

We have found and fixed the problem, we are cleaning up a few more things, expect a new release in the next week or so. In the meantime, if anyone notices anything else that should be checked, let us know. It will be a mandatory update, and the fix for the rewards will take effect at block 86400, all wallets will need to be updated three days before that. We will get you a more exact time the update must be completed by when we release the new wallet.

Anything else planned for release in this update? The road map is a little basic.

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