V12 Testing Thread

crowning

Well-known Member
May 29, 2014
1,415
1,997
183
Alpha Centauri Bc
crowning I hope the watch-only column is not going to be part of the release?
It's part and feature of Bitcoin, they have it there as well.


The Overview screen should be kept as clean as possible. If the user wished more info, they should be able to find it elsewhere.

I suggested in Jira that even the Darksend progress in the overview screen is too much. I think that we should eventually create a new "Darksend tab", which would house this information, moving it from the Overview screen.

The other cool thing I suggested was to have the functionality to use the Darksend tab to send Darksend transactions, and keep the Send tab just for normal transactions. InstantX could be a checkbox in both tabs.
Already on my ToDo-list (but with low priority):
  • move the whole Darksend shebang to own tab (this will be some REALLY tedious work).
  • Send-screen gets dedicated buttons for "Send" and "Darksend". Both have their available balance shown somewhere. The only checkbox will be for InstantX .

Maybe eduffield will even approve it :)
 

TaoOfSatoshi

Grizzled Member
Jul 15, 2014
2,797
2,614
1,183
Dash Nation
www.dashnation.com
It's part and feature of Bitcoin, they have it there as well.




Already on my ToDo-list (but with low priority):
  • move the whole Darksend shebang to own tab (this will be some REALLY tedious work).
  • Send-screen gets dedicated buttons for "Send" and "Darksend". Both have their available balance shown somewhere. The only checkbox will be for InstantX .

Maybe eduffield will even approve it :)
That's why we should have the Darksend tab so the user can view the progress, and then Darksend his transaction "in tab" not having to go to the Send tab.

Darksend Tab - Mixing progress and Darksend transactions.

Send tab - Normal "Bitcoin-like transactions.

InstantX - checkbox in both tabs.

Cleans everything right up, and makes it easy for users such as businesses to pick one tab or the other. If you don't need Darksend functionality, just use the Send tab. If you're always using Darksend, the Darksend tab is for you.
 

bertlebbert

Active Member
Jul 17, 2014
670
289
133
Is there anywhere posted an explanation of the result obtained from "masternode status" command? ... the numbers listed for "status" in particular?
 

bertlebbert

Active Member
Jul 17, 2014
670
289
133
Afaik, none. I'm puzzled about that command too.
Glad I'm not the only one... for status I've seen results from time to time of 0, 1, and 4... suggesting there is probably also a 3.

If someone would post an explanation here, we could that as official documentation for others' future reference.
 

bertlebbert

Active Member
Jul 17, 2014
670
289
133
Anyway, I have a local hot wallet running a MN all day - it was "successfully started" and has had current "status" = 4 ever since. it shows as "ENABLED" using masternodelist full command, but has received no payments at all.
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Anyway, I have a local hot wallet running a MN all day - it was "successfully started" and has had current "status" = 4 ever since. it shows as "ENABLED" using masternodelist full command, but has received no payments at all.
Wallet still has freezing issue, and maybe some other issue, idk. But Evan is on it.
 

moocowmoo

Bovine Bit-flipper
Foundation Member
Jun 15, 2014
483
603
263
masternode.me
Dash Address
XmoocowYfrPKUR6p6M5aJZdVntQe71irCX
Is there anywhere posted an explanation of the result obtained from "masternode status" command? ... the numbers listed for "status" in particular?
Here's the codes from masternode.h

Code:
16 #define MASTERNODE_INITIAL                     0 // initial state
17 #define MASTERNODE_SYNC_IN_PROCESS             1
18 #define MASTERNODE_INPUT_TOO_NEW               2
19 #define MASTERNODE_NOT_CAPABLE                 3
20 #define MASTERNODE_STARTED                     4
 
  • Like
Reactions: bertlebbert

bertlebbert

Active Member
Jul 17, 2014
670
289
133
Here's the codes from masternode.h

Code:
16 #define MASTERNODE_INITIAL                     0 // initial state
17 #define MASTERNODE_SYNC_IN_PROCESS             1
18 #define MASTERNODE_INPUT_TOO_NEW               2
19 #define MASTERNODE_NOT_CAPABLE                 3
20 #define MASTERNODE_STARTED                     4
Than you very much!
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Just waiting for 15 confirms to start 12 with scratchy's cloud:

View attachment 1660
ahahahaha... i was about to ask if you're running MNs on his service... Now when you're ready, please test "masternode start-many", then shut down, wait for 5 min, restart the wallet and do "masternode start-many" again. If the wallet hangs when shutting down or freezes when you start the mns, please report. Thanks :)
 

bertlebbert

Active Member
Jul 17, 2014
670
289
133
ahahahaha... i was about to ask if you're running MNs on his service... Now when you're ready, please test "masternode start-many", then shut down, wait for 5 min, restart the wallet and do "masternode start-many" again. If the wallet hangs when shutting down or freezes when you start the mns, please report. Thanks :)
Being cold local wallet, I should be able to close it and the the remote MNs keep running, no need to restart, in fact should not restart, no?
 

bertlebbert

Active Member
Jul 17, 2014
670
289
133
I was going to leave local wallet running a bit (to see if it might receive any fees), close it for a while, open it again and hopefully see it had continued to get paid.

I dunno tho, I have 1 hot wallet been open for a while now, with MN successfully started (and status 4) and it's not getting paid
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Being cold local wallet, I should be able to close it and the the remote MNs keep running, no need to restart, in fact should not restart, no?
We're testing the wallet. Evan put in a port checking when masternodes were started.. so if you noticed the last few versions the mn start was a bit slower.. It also froze the wallet after a few times.. and didn't come back to life, had to be manually closed, at least what i saw. With this latest version he "Removed port check due to lockups", so we're testing for those..
 

bertlebbert

Active Member
Jul 17, 2014
670
289
133
We're testing the wallet. Evan put in a port checking when masternodes are started.. so if you noticed the last version the mn start was a bit slower.. It also froze the wallet after a few times.. and didn't come back to life, had to be manually closed, at least what i saw. With this latest version he "Removed port check due to lockups", so we're testing for those..
K, no worries, whatever you need :)
 

bertlebbert

Active Member
Jul 17, 2014
670
289
133
So I just closed and re-opened my wallet, 3 tx have 16 confirm, 4 have only 14, and 5 have only 12 confirm; I was expecting 3 to start, butcapture_004_29072015_204431.jpg :
 

bertlebbert

Active Member
Jul 17, 2014
670
289
133
I left the wallet closed for at least 5 minutes (now up to 16 confirms minimum), issued start-many command... sorry, same result:

capture_005_29072015_210409.jpg

Could it be: maybe issue not with wallet, but rather blonkel's cloud?
Are you also trying this, any luck?
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183

bertlebbert

Active Member
Jul 17, 2014
670
289
133
I also closed my hot wallet for 5 minutes and re-opened... it is now receiving "Mined" fees.

I keep closing my start-many wallet (5 mins), re-open and trying star-many again, but successfully started 0 each time;
however no hanging on close - in fact, it seems to close quite quickly.