Add additional unlock_time details to Moneropedia

[SamsungGalaxyPlayer]

Requires a review by a knowledgeable individual, such as @TheCharlatan or @Mitchellpkt.

[netlify]

Deploy preview for barolo-time-757cf9 ready!

Built without sensitive environment variables with commit 8a6d6f9

https://deploy-preview-1343--barolo-time-757cf9.netlify.app

[TheCharlatan]

Thanks for adding this. I just have a suggestion for additional content.

[Mitchellpkt]

Good updates, thanks for writing this up sgp.

Hmm, I'm not sure if this is in scope of the doc, but I'll mention it just in case - there is a mismatch between CLI & RPC behavior around transaction generation. If I recall correctly, the wallet only accepts height-like values (up to millions), but the RPC accepts any uint64 value (up to 18,446,744,073,709,551,615). Thus transactions with very high lock values were either submitted by RPC or custom software. (Also, I'm not sure, does the GUI set unlock_time=0 for all transactions it creates, or is there a way to customize it?)

[Mitchellpkt]

Oh, and also potential wording tweak, clarify
"The integer should be an absolute block height value or Unix epoch timestamp, not a relative value"
to
"The integer value will be interpreted by the protocol as an absolute block height value or Unix epoch timestamp, not a relative value"

[SamsungGalaxyPlayer]

@Mitchellpkt @TheCharlatan please review when you have a chance

[erciccione]

Let's wait a bit before merging this. #1270 must be kept in consideration.

[plowsof]

closed by #2076