Author Topic: Features for a new version (round 2)  (Read 5911 times)

minerpage

  • Admin
  • *****
  • Posts: 112
    • View Profile
Re: Features for a new version
« Reply #15 on: January 28, 2015, 06:07:00 pm »
I really like the MasterNodes and how it's working out... looks like excellent programming to me and I can see the solid foundation being built for a long term coin...

Let's continue the testing cycle so we can bring this phase to a conclusion and launch for real sometime soon...

Once the MasterNodes launched and operational, we will be able to showcase a solid coin and rebuff all critics, attract more users and create substantial value...

georgem

  • Tech Admin
  • ******
  • Posts: 880
    • View Profile
Re: Features for a new version
« Reply #16 on: January 28, 2015, 06:10:38 pm »
I really like the MasterNodes and how it's working out... looks like excellent programming to me and I can see the solid foundation being built for a long term coin...

Let's continue the testing cycle so we can bring this phase to a conclusion and launch for real sometime soon...

Once the MasterNodes launched and operational, we will be able to showcase a solid coin and rebuff all critics, attract more users and create substantial value...

Indeed, I believe this coin could easily become a showrunner in the crypto world.

MyFarm

  • Sr. Member
  • ****
  • Posts: 259
    • View Profile
Re: Features for a new version
« Reply #17 on: January 28, 2015, 06:21:56 pm »
Looks like a good list of new features.  One small suggestion.  On the masternode tab, change the column labeled, "Control" to "Start | Stop"

I think that makes more sense from a usability perspective.

MyFarm

  • Sr. Member
  • ****
  • Posts: 259
    • View Profile
Re: Features for a new version
« Reply #18 on: January 28, 2015, 07:48:21 pm »
Looks like a good list of new features.  One small suggestion.  On the masternode tab, change the column labeled, "Control" to "Start | Stop"

I think that makes more sense from a usability perspective.
Along this same line, if it's easy, I'd change the checkbox to a "Start" and "Stop" button like the mining button.

girino

  • Newbie
  • *
  • Posts: 40
    • View Profile
Re: Features for a new version
« Reply #19 on: January 28, 2015, 08:03:30 pm »
Just thought or something. Sorry for the wiring. I'm on my cell phone.

We need features to mitigate forks on the main net when master node are in place. I'd suggest two features:

- a "voting" system that would only switch the mn features if most of the network is updated
- automatic backup of the wallet just before the switch
- an easy "rollback" button so if a fork is detected we do not need to download a new wallet just switch it back to the old behavior.

Strumpet!

  • Full Member
  • ***
  • Posts: 158
    • View Profile
Re: Features for a new version
« Reply #20 on: January 29, 2015, 02:09:01 am »
As CLI user, i'd love to see the following features:

- An easy way to list my transactions that are eligible for becoming a master node. Example:

Code: [Select]
./spreadcoind listeligiblemn
{[{"txoutput": "ed3fc8a83ece9d4fa40055883825c62aa6902942b0a6a93fc579044fc66d7e15:1" , "value" : "150.0"}
   {"txoutput": "737f21d0ccc2426e9d30152b56a2aecd0d7a08ab17dd85a9acbc7a2992159eff:0", "value" : "150.0"}]}

- an easy way to list my masternodes
Code: [Select]
./spreadcoind listlocalmn
{[{"address" : "mxUGx8xfTmDJrEw4Ndmx9vUYiSiGPrvR8R", "amount": "111.00", "elected" : "no", "score" : "500", "votes" : "0", "txoutput":  "ed3fc8a83ece9d4fa40055883825c62aa6902942b0a6a93fc579044fc66d7e15:1"},
   {"address" : "mxUGx8xfTmDJrEw4Ndmx9vUYiSiGPrvR8R", "amount": "350.00", "elected" : "yes", "score" : "0.001", "votes" : "0.03333", "txoutput":  "737f21d0ccc2426e9d30152b56a2aecd0d7a08ab17dd85a9acbc7a2992159eff:0"}]}


and on the GUI, i'd love to see a separate list with my "eligible" masternodes, and the ones present on the network, so i can control my MNs without browsing the huge list. (maybe this can be solved by making the column "Control" sortable, so myne appear first?)

now, this is more of a question than a feature request: Is it possible to run a Master Node on a locked wallet? Does the PK generated by the "mnsecret" command enables access to the funds in the masternode? In that case, does locking the wallet prevent a hacker from stealing those coins?

Yep some improved CLI calls please. Being able to list just your own wallet MNs and their status would be great.

girino

  • Newbie
  • *
  • Posts: 40
    • View Profile
Re: Features for a new version
« Reply #21 on: January 29, 2015, 02:28:24 am »
Thought of another simple request:

On GUI and on "getinfo", do not count the coins held by master nodes as part of the balance. On the GUI, add another field for the coins held on Master nodes. (on the getinfo, it would also be useful, but not necessary as it can break something and adding another RPC command would make the RPC API too bloated)

njs811

  • Jr. Member
  • **
  • Posts: 88
    • View Profile
Re: Features for a new version
« Reply #22 on: January 29, 2015, 02:33:35 am »
I have complete faith that this coin is the future.

elbandi

  • Jr. Member
  • **
  • Posts: 57
    • View Profile
Re: Features for a new version
« Reply #23 on: January 29, 2015, 10:53:53 am »
Is encrypted (=passworded) wallet works with masternode? or you have to unlock the whole wallet for MN?

Mr. Spread

  • Core Developer
  • ******
  • Posts: 105
    • View Profile
Re: Features for a new version
« Reply #24 on: January 29, 2015, 05:36:02 pm »
Is encrypted (=passworded) wallet works with masternode? or you have to unlock the whole wallet for MN?
If you will start masternode from GUI you will need to enter password, your wallet will be unlocked for one moment and then locked again and your masternode then will run with locked wallet. Unlocking wallet is also required to execute mnsecret command but not required for mnstart.
Please test.

Mr. Spread

  • Core Developer
  • ******
  • Posts: 105
    • View Profile
Re: Features for a new version
« Reply #25 on: January 29, 2015, 05:42:21 pm »
Thought of another simple request:

On GUI and on "getinfo", do not count the coins held by master nodes as part of the balance. On the GUI, add another field for the coins held on Master nodes. (on the getinfo, it would also be useful, but not necessary as it can break something and adding another RPC command would make the RPC API too bloated)
For GUI it is already mentioned in OP.

georgem

  • Tech Admin
  • ******
  • Posts: 880
    • View Profile
Re: Features for a new version
« Reply #26 on: January 29, 2015, 05:53:23 pm »
As I posted here: http://spreadcointalk.org/index.php?topic=37.msg790#msg790

Something tells me it could be a good idea to set the max amount of MN to 1440.

This way we would reach a rather persistent payment cycle where every (stable, still in the race) MN recieves a payment once a day.


georgem

  • Tech Admin
  • ******
  • Posts: 880
    • View Profile
Re: Features for a new version
« Reply #27 on: January 29, 2015, 06:09:54 pm »
I think another important feature could be:

All "hypothetical" Masternode that show up in my mnlist, which I could check and start, should not be listed in the mn list,
but in a separate list, maybe below the mn list.

The problem with those "hypothetical" masternodes is that they mess up the ranking by being in the main list.

e1ghtSpace

  • Full Member
  • ***
  • Posts: 113
  • Part of the 2 year club
    • View Profile
Re: Features for a new version
« Reply #28 on: January 30, 2015, 06:27:57 am »
Quote from: Mr. Spread
Mr. Spread,

Can you please implement a Vanity Address Generator into the wallet?
It would be a great feature. Don't you think?
We just have to wait.

gjhiggins

  • Guest
Re: Features for a new version (round 2)
« Reply #29 on: March 18, 2015, 02:11:56 pm »
Here is a list of features that I plan to implement in the next version:

Checking target vs actual ...

Service nodes:
Reduce number of service nodes required to start payments (currently it is 300) - unchanged at 300 since last commit.
Reduce total number of service nodes (currently it is 1000) - new commit - increased to 1440

User interface:
Sort service nodes by column - new commit
Display number of elected service nodes - new commit
On overview page display your amount locked in service nodes separately instead of including it in balance - new commit

RPC/Console
Command to get list of service nodes with info for each node - new commit

Internals
Move votes from header to block body - new commit

Elevated these to the github issue ticketing system.

Cheers

Graham

Edit: annotated as done