Saturday, January 20, 2018

coin control youtube links




What is Coin Control ?

 http://pos-monkey.com/what-is-coin-control/


Alright Staking fellas, in this tutorial i am going to explain the “Coin Control” feature and the benefits of it to you.
As you learned in the How to Start tutorial Proof of Stake coins and their rewards are in almost every case related to the size of your coins.
Let me give you an easy example here with my favourite 808coin:
You bought 440.000 808coin, transfered them to your wallet, let them mature and stake after lets say 8 to 11 days. You received a reward something like 90.000 coins. Afterwards your “new” stake is automaticaly splited into 2 stakes containing 50% of the new total value you gained. So now you start staking 2 blocks of roundabout 266.000 coins. Almost all PoS Coins act like this. So after you receive a stake your total amount of coins is splitted. Then you got two “smaller” stakes, which will then of course take longer to hit the block when its time to earn the rewards.
Please see this example screenshots from my wallet for easier understanding:

As you can see here I transfered 122.000 coins and 440.000 coins to my wallet. Both hit rewards several times so far. To be exact:
The 122.000 hit a 28.000 reward and were then splitted into two parts of 50% each -> about 75.000. Those two hit a new stake of 16.000 ( 3 days faster ) and 21.000 splitting my 75.000 blocks into 4 blocks of each about 45.000. They are actualy staking as you can see on the next screenshot. Also my 440.000 coins hit a reward of 93.000 coins. And guess what, they are now splitted into 2 Blocks of each 266.000 coins (see next screenshot).

As you can see here I started with 2 transfers (122.000 & 440.00 coins) bringing me now 6 minting blocks taking already way longer then the expected 8 days. The reason for this is pretty easy.
The larger the blocks the faster they hit a stake!
That is the most important rule for PoS coins!
So what shall we do against it? Blocks keep splitting up every week and at some day you will have to stake with 500 coins and wait for weeks.
Now our nice feature “Coin Control” is coming into the game!
You have to enable the “Coin Control” feature at “Settings”. After you enabled the coin control please navigate to your “Send Coins” Tab. There shall now appear a button called “Input”, please open this.

Here you can now see an overview about the coins you have and the several blocks they contain of. 808 is pretty cool, because u basicaly have the coin control feature enabled at minting. Minting always shows you the several blocks that stake. But coins like EMBER, WOMEN, IFLT, KOI and many more wont show you a minting tab. Whenever you receive stakes open the coincontrol feature to doublecheck if your coins are splitted into tiny blocks. If your blocks were splitte several times you have to rearrange them to 1 big block, because as we know already, one big block stakes way faster ( we talk about days til weeks here… ).
When you want to combine a block you have to follow these steps:
Select list mode and there you will have all your coins and now if you want to combine them all into 1 block you just check all the boxes and then click ok. Once done you’ll see Amount fee etc… copy the amount and paste it into the amount box under Label then put in your coin address and click send. Don’t forget about the fee though and you should then have all your coins combined in 1 block. After you resend the coins they have to mature again, but its still better then wasting time on waiting weeks for a rewards.

I really hope this tutorial helped some of you guys to improove their staking results,
cheers !

Using the Coin Control Feature of Your GUI Qt Walle

 http://cryptomining-blog.com/7778-using-the-coin-control-feature-of-your-gui-qt-wallet/

Using the Coin Control Feature of Your GUI Qt Wallet 23 Apr

2016
coin-control-feature
Taking advantage of the Coin Control feature is something considered a bit more advanced, especially if you don’t have built-in support in the specific crypto currency’s GUI Qt wallet and have to use the console. But Bitcoin and many of the more recent altcoins or ones with updated wallets do have built-in support making things easy to use the coin control feature right from the GUI. By default the feature is not enabled, so you will have to go to Settings / Options / Display and enable the coin control feature to be displayed. After that when you go to the Send coins panel of your coin wallet you will see a button to call the Coin Control feature, but what is this feature and why do you need to use it in the first place?
coin-control-feature2
The coin control feature allows you to control how you spend the coins in your wallet when sending a transaction. You can choose what addresses will be the ones sending the coins and which of the coins you have received will be used. With this feature you can do things like combine multiple transactions and the coins from them that you have received in a single large sum of coins available to one of you wallet addresses. To do that you can just select which coins and the address you want them sent to and use on of your own wallet addresses, so you will actually be sending yourself the coins. Sending yourself coins would require you to pay a network transaction fee, but by consolidating multiple small amounts of coins into single ones you can actually reduce on further transaction costs.
coin-control-feature3
The coin control feature however is more important for PoS (Proof of Stake) coins and altcoins that do have some other forms of awarding users with extra coins for holding some amount in their wallets. Consolidating the coins in your wallet will mean that they will available for stating altogether giving you bigger weight on the staking, so you should be able to save on time when staking coins. If a coin is rewarding you for keeping your coins in the wallet for some time, but there is a maximum time they need to stay in the wallet without moving you can use the coin control feature to see when you need to resend some of the coins back to your own wallet in order to keep getting rewards. So depending on the specific coin taking advantage of the coin control feature might help you maximize your PoS earnings, get more rewards or execute transactions with the coins you want from the address you want them to be sent. If you still haven’t used that feature you might want to give it a try and see how easy it is to use it especially if it is already available in your GUI qt wallet and you just need to enable it and not having to run console commands.

Friday, December 28, 2012

If the hardware is still in the old system with the pool imported, from a SSH session as root paste the output of:
zpool status -v

Once the hardware is in the new system, from a SSH session as root paste the output of:

zpool import

camcontrol devlist


gpart show


glabel status


FYI, I may not be around all that much the next few days.

FreeNas - Possible bad drive - ada4



[root@tank] ~# smartctl -a /dev/ada4
smartctl 5.42 2011-10-20 r3458 [FreeBSD 8.2-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F4 EG (AFT)
Device Model:     SAMSUNG HD204UI
Serial Number:    S2H7J1NB402983
LU WWN Device Id: 5 0024e9 004d8251a
Firmware Version: 1AQ10001
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Fri Dec 28 05:05:18 2012 MST

==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Buggy and fixed firmware report same version number!
See the following web pages for details:
http://www.samsung.com/global/business/hdd/faqView.do?b2b_bbs_msg_id=386
http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks

SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (20160) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 255) minutes.
SCT capabilities:              (0x003f) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   068   068   025    Pre-fail  Always       -       9958
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       868
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       2085
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       21
181 Program_Fail_Cnt_Total  0x0022   100   100   000    Old_age   Always       -       9638164
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       7
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   064   064   000    Old_age   Always       -       20 (Min/Max 15/34)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       0
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       874

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      2085         -
# 2  Short offline       Completed without error       00%      2084         -
# 3  Short offline       Completed without error       00%      2078         -

Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed [00% left] (0-65535)
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.