tomahawkeer
Member
 Offline
Activity: 109
Merit: 10
|
 |
September 27, 2016, 06:51:25 PM |
|
One thing I have noticed with 2.1.2.3 is the recent transactions on the overview tab, at least for me, is not the most recent transactions. They are from almost a week ago. My wallet is still staking, and showing as such if you go to look at all transactions, but the recent transactions on the overview page is not correct for me.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The trust scores you see are subjective; they will change depending on who you have in your trust list. |
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
4x13 (OP)
Legendary
Offline
Activity: 1078
Merit: 1011
|
|
September 27, 2016, 06:56:58 PM |
|
One thing I have noticed with 2.1.2.3 is the recent transactions on the overview tab, at least for me, is not the most recent transactions. They are from almost a week ago. My wallet is still staking, and showing as such if you go to look at all transactions, but the recent transactions on the overview page is not correct for me.
Sounds like you are seeing orphans, which always move to the top. you need to zap your wallet from the Wallet Repair menu |
|
|
|
|
|
Daffadile
|
|
September 27, 2016, 07:02:35 PM |
|
I think it should be even longer than 4 hours like 6 or 12 maybe. 4 seems too little and far to frequently if people want the exact value they will surely be following it in the markets anyway. But every 6 to 12 hours lets people know what is going on without looking at the exchange all the time and I think 24 hours might be too long.
|
|
|
|
tomahawkeer
Member
Offline
Activity: 109
Merit: 10
|
|
September 27, 2016, 07:33:03 PM |
|
One thing I have noticed with 2.1.2.3 is the recent transactions on the overview tab, at least for me, is not the most recent transactions. They are from almost a week ago. My wallet is still staking, and showing as such if you go to look at all transactions, but the recent transactions on the overview page is not correct for me.
Sounds like you are seeing orphans, which always move to the top. you need to zap your wallet from the Wallet Repair menu Yeah that took care of it. Thanks! |
|
|
|
|
|
borris123
|
|
September 27, 2016, 08:15:28 PM |
|
When does update need to be done by?
|
|
|
|
|
4x13 (OP)
Legendary
Offline
Activity: 1078
Merit: 1011
|
|
September 27, 2016, 08:17:22 PM |
|
When does update need to be done by?
When 85% of the masternodes are updated, the Enforcement is turned back on. Usually takes a few days at least, sometimes longer |
|
|
|
|
4x13 (OP)
Legendary
Offline
Activity: 1078
Merit: 1011
|
|
September 27, 2016, 08:17:51 PM |
|
All binairies have been uploaded and the links on the OP have been updated as well
|
|
|
|
|
4x13 (OP)
Legendary
Offline
Activity: 1078
Merit: 1011
|
|
September 27, 2016, 09:39:48 PM |
|
EXCHANGES that have responded as being updated to v2.1.3.0
NovaExchange
|
|
|
|
|
|
borris123
|
|
September 27, 2016, 10:21:52 PM |
|
still not fixed the wallet crashing when starting nodes. and i am doing the walletpassphrase command.
|
|
|
|
|
4x13 (OP)
Legendary
Offline
Activity: 1078
Merit: 1011
|
|
September 27, 2016, 10:31:18 PM |
|
still not fixed the wallet crashing when starting nodes. and i am doing the walletpassphrase command.
continue to do; walletpassphrase masternode start-alias walletpassphrase masternode start-alias |
|
|
|
|
|
borris123
|
|
September 27, 2016, 10:33:02 PM |
|
still not fixed the wallet crashing when starting nodes. and i am doing the walletpassphrase command.
continue to do; walletpassphrase masternode start-alias walletpassphrase masternode start-alias thats what i was doing. doesnt usual crash but it did a few times. |
|
|
|
|
jakiman
Legendary
Offline
Activity: 1638
Merit: 1011
jakiman is back!
|
|
September 27, 2016, 10:41:38 PM |
|
still not fixed the wallet crashing when starting nodes. and i am doing the walletpassphrase command.
That issue was never mentioned as fixed. So I assume it can still happen. But in saying that, I haven't had that hang issue for the last 100+ start-alias commands. I just make sure I run start-alias at least 5 seconds after running the walletpassphrase. |
|
|
|
|
StakeBox
|
|
September 27, 2016, 11:23:30 PM |
|
still not fixed the wallet crashing when starting nodes. and i am doing the walletpassphrase command.
That issue was never mentioned as fixed. So I assume it can still happen. But in saying that, I haven't had that hang issue for the last 100+ start-alias commands. I just make sure I run start-alias at least 5 seconds after running the walletpassphrase. I also find that patience is a virtue. Wait an half hour or more after starting your controller wallet before running start commands. It seems to really help a lot. |
|
|
|
tomahawkeer
Member
Offline
Activity: 109
Merit: 10
|
|
September 28, 2016, 12:06:10 AM |
|
Linux users:
About how much ram is each wallet instance using for you?
IPv6 users:
Have you had any difficulties configuring / running master nodes ?
I am asking because I am considering buying some VPS and running some masternodes.
|
|
|
|
|
|
StakeBox
|
|
September 28, 2016, 01:00:44 AM |
|
OK folks, we have a working testnet finally, That will allow us to more thoroughly test updates ahead of time, but we will need the help of the community. If you are able to fire up a wallet on testnet get addresses to us and we will throw some coins your way. We need stakers, masternodes, people mixing, etc. to fully test things.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
|
|
|
|
|
NotMyFarm
|
|
September 28, 2016, 01:46:52 AM |
|
OK folks, we have a working testnet finally, That will allow us to more thoroughly test updates ahead of time, but we will need the help of the community. If you are able to fire up a wallet on testnet get addresses to us and we will throw some coins your way. We need stakers, masternodes, people mixing, etc. to fully test things.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
if you have an (idiot proved) mac guide for this i consider  |
|
|
|
jakiman
Legendary
Offline
Activity: 1638
Merit: 1011
jakiman is back!
|
|
September 28, 2016, 02:33:59 AM |
|
Linux users:
About how much ram is each wallet instance using for you?
On mine, approx. 200-220MB per masternode instance on average with v2.1.2.3. |
|
|
|
|
StakeBox
|
|
September 28, 2016, 02:59:47 AM |
|
OK folks, we have a working testnet finally, That will allow us to more thoroughly test updates ahead of time, but we will need the help of the community. If you are able to fire up a wallet on testnet get addresses to us and we will throw some coins your way. We need stakers, masternodes, people mixing, etc. to fully test things.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
if you have an (idiot proved) mac guide for this i consider You just start the wallet with the --testnet flag. So, for the qt, ./darknet-qt --testnet Edit: There may be a slightly different syntax for starting programs on Mac than Linux, let me yell to s3v3n, he is the Mac guy. |
|
|
|
|
NotMyFarm
|
|
September 28, 2016, 03:06:09 AM |
|
OK folks, we have a working testnet finally, That will allow us to more thoroughly test updates ahead of time, but we will need the help of the community. If you are able to fire up a wallet on testnet get addresses to us and we will throw some coins your way. We need stakers, masternodes, people mixing, etc. to fully test things.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
if you have an (idiot proved) mac guide for this i consider You just start the wallet with the --testnet flag. So, for the qt, ./darknet-qt --testnet Edit: There may be a slightly different syntax for starting programs on Mac than Linux, let me yell to s3v3n, he is the Mac guy. tx for the "yell" at s3v3n as well how do i run 2nd wallet on 1 computer (1 testnet - 1 real) |
|
|
|
4x13 (OP)
Legendary
Offline
Activity: 1078
Merit: 1011
|
|
September 28, 2016, 03:09:48 AM
Last edit: September 28, 2016, 03:31:28 AM by s3v3nh4cks |
|
Add testnet=1 in your darknet.conf file, the change the addnodes.
you can also cd from a terminal to the binary location of the wallet, and run './darknet-qt -testnet' Which will start the wallet in testnet mode.
Personally, I run mine in VM's so each wallet has it's own environment. All will work just fine
|
|
|
|
|
|
Poll
