When I am moving coins to a wallet for staking, is there any benefit staking-wise to sending them in smaller transactions, or in one large transaction or does it make no difference at all as far as staking goes...?

For fun, I am attempting to generate bitcoin WIF PrivKeys from random binary strings. I have everything figured out except the final step of converting to WIF using base58check encoding.

Here is where I am at:
Step 1) Generated random binary string

Code:

0100 0100 1101 0000 0000 1111 0110 1110 1011 0010 1110 0101 0100 1001 0001 1100
1101 0111 1010 1011 0111 1110 0111 0001 1000 0101 1101 1000 0001 1011 0110 0111
1010 0010 0011 1100 0100 1001 1000 0000 1111 0110 0010 1011 0010 1110 1101 0000
1001 0001 0100 1101 0011 0010 1011 0111 1110 1011 0001 1100 0101 0101 1000 0001

Step 2) Converted binary string to hex string

Code:

44D00F6EB2E5491CD7AB7E7185D81B67A23C4980F62B2ED0914D32B7EB1C5581

Step 3) Added 0x80 byte to beginning of hexstring

Code:

8044D00F6EB2E5491CD7AB7E7185D81B67A23C4980F62B2ED0914D32B7EB1C5581

Step 4) Hashed new hex string to SHA256 encoded string, took result and hashed to a new SHA256 string

Code:

2897b55427f86f73136d55c1729cb4ce56d72e40e33baf8ca10e9e02cb963434

Step 5) Took first 4 bytes (checksum) and added them to end of hex string from Step 2

Code:

8044D00F6EB2E5491CD7AB7E7185D81B67A23C4980F62B2ED0914D32B7EB1C55812897b554

And this is where I am lost... No matter what information I look up online I can not seem to figure out how to turn the last string into a base58check encoded string to complete the process of turning it into a WIF PrivKey.

Thanks to "TP's Go Bitcoin Tests", I know that the end result should be

Code:

5JLbJxi9koHHvyFEAERHLYwG7VxYATnf8YdA9fiC6kXMghkYXpk

But I have no idea nor can I seem to find a clear, coherent explanation of the base58check process that changed my modified hex string to a WIF PrivKey...

To be clear, I want to actually learn how the process works, so please do not just point me at a tool online and say "Just do it here, it is much easier".

Thank you in advance to anyone who can help explain this to me!

[Bitcoin/Altcoin Tools for Newbies - Version 1.0.1]

Bitcoin/Altcoin Tools for Newbies - Version 1.0.1

**Apr 04, 2016 - UPDATE: Version 1.0.2 Released**


INTRO
BATforN is for the Windows operating system. It has only been tested on Windows 8.1 but as far as I know should work on all Windows
platforms. If you encounter any bugs, have any requests, questions, comments or concerns, please let me know.

Many coin clients don't have simple, easy-to-use buttons for all of their features. This set of scripts simply makes those
features easier to use.

Someone using a coin client that doesn't have simple, easy-to-use buttons for signing messages, verifying messages,
encrypting their wallet, exporting/importing private keys, generating new keypairs, repairing corrupted wallets, checking
wallet integrity, validating coin addresses, validating public keys, etc... can find great use from this simple set of scripts.

The best part is that the scripts can be used with pretty much ANY coin client.

BATforN started as a way to make my own Bitcoin/Altcoin tasks faster and easier to accomplish. As I progressed, I decided I
would release my files for public use and so I have also added scripts that I thought might be useful for people who are
either new to Bitcoin or just less tech-savvy in general. If you're not comfortable with using the debug console, you find
the debug console confusing to use, etc... then this tool will likely be helpful for you. I will continue to improve and add
features.

All elements of BATforN are entirely open-source with the exception of "coind". If you do not trust my daemon then you can
replace it by going to http://bitcoin.org, download either the 32 or 64 bit ZIP package of the Bitcoin wallet, extract the
downloaded folder, open the "bin" folder inside, rename "bitcoin-cli" to "coind" then copy to "BATforN\Scripts" and
overwrite the old file. Once done, you can delete the rest of the downloaded Bitcoin files.

To view the source code for any of the scripts, simply right-click the script and select "Edit". Do NOT make/save any changes
or you can/will break the script.



CURRENT FUNCTIONS
Backup Wallet to Location
Check Wallet for Integrity
Dump Private Keys
Encrypt Wallet
Get Balance
Get Client Info
Get Mining Info
Get Peer info
Get Raw Transaction by TXID
Get Staking Info
Get Subsidy
Get Transaction by TXID
Help Information Returned by Coin Client
Import Private Keys
List Accounts in Your Wallet
Make a Public/Private Keypair
Repair Corrupted Wallet
Resend Stuck (0 Confirmation) Transactions
Sign Message With Address
Stop/Exit Coin Client
Validate Coin Address
Validate Public Keys
Verify Signed Messages


USAGE
Step 1: Configure BATforN for your coin of choice by running the "Run_First" file.
If you have more than one coin, you MUST run the "Run_First" file before working with each new coin.
Follow the prompts & enter requested information.

Step 2: Open the "Scripts" folder and run the appropriate script for the task you wish to accomplish.
Follow the prompts and enter information if requested.



VirusTotal
https://www.virustotal.com/en/file/7247a8bded0ae9a8e27bf2c04eca470f7a003665319d09ac1ec7a64f7798b5e3/analysis/1458821115/


DOWNLOAD
http://github.com/ExabyteMiner/BATforN



CHANGELOG
Apr 04, 2016 - Fixed an issue preventing scripts from working with encrypted wallets, improved user experience

Mar 25, 2016 - Made script output more descriptive, Made code cleaner/less redundant

Mar 24, 2016 - Fixed "SignMessage" and "VerifyMessage" scripts which functioned improperly with whitespaces, added
functionality to resend stuck transactions

Mar 23, 2016 - Initial Release