According to the OP, on which the bounty is detailed, the bounty hunter was to do a base58 decode and encode:
Base58Encode[x_Integer] (returns Mathematica string)
Base58Decode[x_String] (returns Mathematica integer)
There is no mention in the OP as to the number or nature of leading '1s' to include.
However, according to the document,
https://en.bitcoin.it/wiki/Base58Check_encoding, which is the one you encouraged me to read, it defines what is meant by a normalized base-58 encoding in point 4:
Treating the results of step 3 - a series of bytes - as a single big-endian bignumber, convert to base-58 using normal mathematical steps (bignumber division) and the base-58 alphabet described below. The result should be normalized to not have any leading base-58 zeroes (character '1').
I refer your attention to the last sentence, that the result should have no leading base-58 zeroes (character '1').
This is precisely the functionality provided to you on May 20 at 4:22pm when you use the default function without specifying n, the base-58 encoding with no leading '1s'.
What you have been asking for since is the next step, which is the Base58Check, and beyond the scope of the bounty as described.
I am open to discuss this further if you wish; however --- respectfully --- I submit that the bounty is already completed and that no more work is required on my part.
Please send 0.075BTC the bounty to: 19t2j4ZHfaNf1hX7YEDLZpdURcwvGywBhc