Bitcoin Forum
November 18, 2024, 10:45:42 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 3 »  All
  Print  
Author Topic: Upgrade problems from legacy version of Electrum. Coins stuck on WinXP PC wallet  (Read 703 times)
77Network (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 4


View Profile
December 28, 2020, 12:21:07 AM
Merited by o_e_l_e_o (2), ABCbits (1)
 #1

Dear Friends,

I am hoping someone can offer some assistance. I have a number of coins that are stuck in an old wallet on a PC running Win XP.
I also am looking for some help on the transaction signing process which has not been updated in the official documentation for the current release.  

History:
Back in 2017 I created an Offline Wallet using Electrum 2.9.0. The offline PC is an old Pentium running a fresh install of 32 bit Windows XP. The PC has never been connected to the internet and has nothing installed on it except the OS and Electrum. On my newer Win 10 laptop I have my Watching Only Wallet with the public master key.

My standard process for transactions in 2017 was to;
1. Create the transaction on my Win 10 laptop using my Watching Only Wallet.
2. Save the unsigned transaction to unsigned.txt.
3. Open unsigned.txt and decode the hex to json and visually verify the outputs of the transaction.
4. Copy unsigned.txt to a thumb drive.
5. Open unsigned.txt with my Offline Wallet, sign the transaction, and save it back to the thumb drive.
6. Visually verify raw signed transaction on my laptop.  
7. Open the transaction with the Watching Only Wallet and transmit it to the network.

I kind of forgot about things for 3 years, but now I would like to use Electrum again and I am having problems. I tried to follow the same process I outlined above.

The first issue I had is that when opening the Electrum 2.9.0 Watching Only Wallet with my laptop it is unable to connect to the sever nodes. I upgraded to Electrum 4.0.9. This solved that problem. I am now able to use my Watching Only Wallet using Electrum 4.0.9. Next, I created my unsigned transaction using Electrum 4.0.9 and saved it to disk. I then tried to open the unsigned transaction file to visually verify the outputs. This did not work because the file looks like it is encrypted. Reluctantly, I assumed the transaction was correct and saved it to my thumb drive. Also, I copied Electum 4.0.9 to my thumb drive to upgrade my Offline Wallet PC so that it can read these encrypted unsigned transactions. That is about as far as I got.

On my offline PC with Windows XP os, Electrum 4.0.9 does not work. On starting Electrum I keep getting a windows alert box with "the procedure entry point _wputenv_s could not be located in the dynamic link library mscrt.dll" I did some searching and the best information I could find was that I probably needed to install the "Microsoft Visual C++ redistributable package" from https://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=29. This did not work. The package appeared to install, but I still get the same alert box when trying to start Electrum. After more investigating I noticed that Electrum 4.0.9 says it is for Windows 7 and above. I tried to use some other releases of Electrum. It looks like the oldest Elecrum release that will connect to the server nodes is 3.0.1. That version also has the same mscrt.ddl library problem when running on Win XP.

So, That is where I am at now. My questions are;
1. Does anyone know if there are any library(s) that I can install on XP that will allow me to access an old Electrum wallet that is on a Win XP machine?
2. Is there anyway to still visually verify transactions before they get moved to a Offline Wallet PC? I am very uncomfortable with copying unsigned transaction files to the offline pc if I have no idea what is inside these files. I was hoping to be able to still follow a process like I outlined above.  
3. If there is no way to run Electrum on Win XP, how should I correct this situation? Is the best process to copy the Offline Wallet from my Win XP machine and put it on my newer laptop and try to open it there with Electrum 4.0.9? (I am reluctant to loose the security of the Offline Wallet)

Thank you.
James..


 
NotATether
Legendary
*
Offline Offline

Activity: 1792
Merit: 7389


Top Crypto Casino


View Profile WWW
December 28, 2020, 12:50:39 AM
 #2

Windows XP support is entirely dependent on the version of Python you are using. Python dropped support for Windows XP starting at version 3.5.

The Python bundle available on Electrum's download page needs Python 3.6.1 or higher. But that bundle is just made by installing all the python modules that Electrum uses and bundling them together.

You could try installing Python 3.4 and cloning https://github.com/spesmilo/electrum/tree/4.0.9, installing the dependencies using pip install -r contrib/requirements/requirements.txt. If you also need hardware wallet support, you also need to do  pip install -r contrib/requirements/requirements-hw.txt

Then you should have a working Electrum on Windows XP.

███████████████████████
████▐██▄█████████████████
████▐██████▄▄▄███████████
████▐████▄█████▄▄████████
████▐█████▀▀▀▀▀███▄██████
████▐███▀████████████████
████▐█████████▄█████▌████
████▐██▌█████▀██████▌████
████▐██████████▀████▌████
█████▀███▄█████▄███▀█████
███████▀█████████▀███████
██████████▀███▀██████████

███████████████████████
.
BC.GAME
▄▄▀▀▀▀▀▀▀▄▄
▄▀▀░▄██▀░▀██▄░▀▀▄
▄▀░▐▀▄░▀░░▀░░▀░▄▀▌░▀▄
▄▀▄█▐░▀▄▀▀▀▀▀▄▀░▌█▄▀▄
▄▀░▀░░█░▄███████▄░█░░▀░▀▄
█░█░▀░█████████████░▀░█░█
█░██░▀█▀▀█▄▄█▀▀█▀░██░█
█░█▀██░█▀▀██▀▀█░██▀█░█
▀▄▀██░░░▀▀▄▌▐▄▀▀░░░██▀▄▀
▀▄▀██░░▄░▀▄█▄▀░▄░░██▀▄▀
▀▄░▀█░▄▄▄░▀░▄▄▄░█▀░▄▀
▀▄▄▀▀███▄███▀▀▄▄▀
██████▄▄▄▄▄▄▄██████
.
..CASINO....SPORTS....RACING..


▄▄████▄▄
▄███▀▀███▄
██████████
▀███▄░▄██▀
▄▄████▄▄░▀█▀▄██▀▄▄████▄▄
▄███▀▀▀████▄▄██▀▄███▀▀███▄
███████▄▄▀▀████▄▄▀▀███████
▀███▄▄███▀░░░▀▀████▄▄▄███▀
▀▀████▀▀████████▀▀████▀▀
DireWolfM14
Copper Member
Legendary
*
Offline Offline

Activity: 2352
Merit: 4586


Join the world-leading crypto sportsbook NOW!


View Profile WWW
December 28, 2020, 02:18:12 AM
 #3

I think you're overcomplicating things.  If you have the seed phrase, just upgrade the OS to a newer version of Windows if possible, or the current LTS release of Ubuntu.  Then reinstall Electrum and restore the wallet.  Ensure you have the right seed phrase before you nuke the XP OS.

If you created the wallet with imported private keys, you should back those up, of course.

  ▄▄███████▄███████▄▄▄
 █████████████
▀▀▀▀▀▀████▄▄
███████████████
       ▀▀███▄
███████████████
          ▀███
 █████████████
             ███
███████████▀▀               ███
███                         ███
███                         ███
 ███                       ███
  ███▄                   ▄███
   ▀███▄▄             ▄▄███▀
     ▀▀████▄▄▄▄▄▄▄▄▄████▀▀
         ▀▀▀███████▀▀▀
░░░████▄▄▄▄
░▄▄░
▄▄███████▄▀█████▄▄
██▄████▌▐█▌█████▄██
████▀▄▄▄▌███░▄▄▄▀████
██████▄▄▄█▄▄▄██████
█░███████░▐█▌░███████░█
▀▀██▀░██░▐█▌░██░▀██▀▀
▄▄▄░█▀░█░██░▐█▌░██░█░▀█░▄▄▄
██▀░░░░▀██░▐█▌░██▀░░░░▀██
▀██
█████▄███▀▀██▀▀███▄███████▀
▀███████████████████████▀
▀▀▀▀███████████▀▀▀▀
█████████████LEADING CRYPTO SPORTSBOOK & CASINO█████████████
MULTI
CURRENCY
1500+
CASINO GAMES
CRYPTO EXCLUSIVE
CLUBHOUSE
FAST & SECURE
PAYMENTS
.
..PLAY NOW!..
77Network (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 4


View Profile
December 28, 2020, 02:29:46 AM
 #4

Thank you NotATether.

I am having a hard time understanding what you are telling me. Prior to release 3.0.0, Electrum was distributed using a version of python that did run on XP? Since Electrum 3.0.0 the version of python used no longer works on XP?

Are you suggesting that I download the last version of python which supports XP and then attempt to rebuild the Electrum executable using that version of python?

I think I could upgrade the OS. The PC is from 2000. The only reason I was keeping it around was for maintaining my offline wallet.

Regards,
James.

NotATether
Legendary
*
Offline Offline

Activity: 1792
Merit: 7389


Top Crypto Casino


View Profile WWW
December 28, 2020, 03:04:28 AM
 #5

Thank you NotATether.

I am having a hard time understanding what you are telling me. Prior to release 3.0.0, Electrum was distributed using a version of python that did run on XP? Since Electrum 3.0.0 the version of python used no longer works on XP?

It had to be because Python 3.5 was released at the end of 2015, while Electrum 3.0.0 was released at the end of 2017. It was too soon back then to drop 3.4.

Are you suggesting that I download the last version of python which supports XP and then attempt to rebuild the Electrum executable using that version of python?

Yes.

I think I could upgrade the OS. The PC is from 2000. The only reason I was keeping it around was for maintaining my offline wallet.

It should be able to run 32-bit Windows 7 provided that it has at least 1GB of memory. I have made it run with just 512MB but it struggles with speed. That'll be much easier for you then, since Python 3.6 is supported on Windows 7 so you can simply use the source distribution.

███████████████████████
████▐██▄█████████████████
████▐██████▄▄▄███████████
████▐████▄█████▄▄████████
████▐█████▀▀▀▀▀███▄██████
████▐███▀████████████████
████▐█████████▄█████▌████
████▐██▌█████▀██████▌████
████▐██████████▀████▌████
█████▀███▄█████▄███▀█████
███████▀█████████▀███████
██████████▀███▀██████████

███████████████████████
.
BC.GAME
▄▄▀▀▀▀▀▀▀▄▄
▄▀▀░▄██▀░▀██▄░▀▀▄
▄▀░▐▀▄░▀░░▀░░▀░▄▀▌░▀▄
▄▀▄█▐░▀▄▀▀▀▀▀▄▀░▌█▄▀▄
▄▀░▀░░█░▄███████▄░█░░▀░▀▄
█░█░▀░█████████████░▀░█░█
█░██░▀█▀▀█▄▄█▀▀█▀░██░█
█░█▀██░█▀▀██▀▀█░██▀█░█
▀▄▀██░░░▀▀▄▌▐▄▀▀░░░██▀▄▀
▀▄▀██░░▄░▀▄█▄▀░▄░░██▀▄▀
▀▄░▀█░▄▄▄░▀░▄▄▄░█▀░▄▀
▀▄▄▀▀███▄███▀▀▄▄▀
██████▄▄▄▄▄▄▄██████
.
..CASINO....SPORTS....RACING..


▄▄████▄▄
▄███▀▀███▄
██████████
▀███▄░▄██▀
▄▄████▄▄░▀█▀▄██▀▄▄████▄▄
▄███▀▀▀████▄▄██▀▄███▀▀███▄
███████▄▄▀▀████▄▄▀▀███████
▀███▄▄███▀░░░▀▀████▄▄▄███▀
▀▀████▀▀████████▀▀████▀▀
pooya87
Legendary
*
Offline Offline

Activity: 3640
Merit: 11040


Crypto Swap Exchange


View Profile
December 28, 2020, 05:06:58 AM
 #6

I suggest learning a bit about Linux and switching your offline storage to that instead. You can find light distributions such as Lubuntu that can run on older machines and are also much more secure than the ancient Windows XP and also can run newer application such as the new versions of Electrum.
https://lubuntu.net/

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
77Network (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 4


View Profile
December 28, 2020, 06:03:54 AM
 #7

I think you are right about using Linux. It looks like I might be able to run Win 7 on this hardware, but it is not abandon ware yet. I am not going to try to buy it or mess with hacked versions.

Can anyone tell me anything more about how the latest release handles saving unsigned transactions to a file? I like to manually verify all the outputs in the unsigned transaction file before I allow the file to be copied to a blank thumb drive. (And then loaded on the offline wallet to be signed.)  Is there anyway to validate the contents of this file using something external to Electrum before signing the transaction? I tried to open the file but it looks like encrypted contents now. The documentation does not appear to be updated since this was changed.

At some point in the past, the unsigned transaction was saved as hex which could be decoded to json with many different utilities.

Thanks,
James.
HCP
Legendary
*
Offline Offline

Activity: 2086
Merit: 4361

<insert witty quote here>


View Profile
December 28, 2020, 06:38:30 AM
 #8

Can anyone tell me anything more about how the latest release handles saving unsigned transactions to a file? I like to manually verify all the outputs in the unsigned transaction file before I allow the file to be copied to a blank thumb drive. (And then loaded on the offline wallet to be signed.)  Is there anyway to validate the contents of this file using something external to Electrum before signing the transaction? I tried to open the file but it looks like encrypted contents now. The documentation does not appear to be updated since this was changed.
It's Base64 encoded... and the data is in "Partially Signed Bitcoin Transaction" aka PSBT format... You can read about the PSBT format here: https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki


NOTE: Something like this tool will decrypt the Base64 to Hex: https://cryptii.com/pipes/base64-to-hex

█████████████████████████
████▐██▄█████████████████
████▐██████▄▄▄███████████
████▐████▄█████▄▄████████
████▐█████▀▀▀▀▀███▄██████
████▐███▀████████████████
████▐█████████▄█████▌████
████▐██▌█████▀██████▌████
████▐██████████▀████▌████
█████▀███▄█████▄███▀█████
███████▀█████████▀███████
██████████▀███▀██████████
█████████████████████████
.
BC.GAME
▄▄░░░▄▀▀▄████████
▄▄▄
██████████████
█████░░▄▄▄▄████████
▄▄▄▄▄▄▄▄▄██▄██████▄▄▄▄████
▄███▄█▄▄██████████▄████▄████
███████████████████████████▀███
▀████▄██▄██▄░░░░▄████████████
▀▀▀█████▄▄▄███████████▀██
███████████████████▀██
███████████████████▄██
▄███████████████████▄██
█████████████████████▀██
██████████████████████▄
.
..CASINO....SPORTS....RACING..
█░░░░░░█░░░░░░█
▀███▀░░▀███▀░░▀███▀
▀░▀░░░░▀░▀░░░░▀░▀
░░░░░░░░░░░░
▀██████████
░░░░░███░░░░
░░█░░░███▄█░░░
░░██▌░░███░▀░░██▌
░█░██░░███░░░█░██
░█▀▀▀█▌░███░░█▀▀▀█▌
▄█▄░░░██▄███▄█▄░░▄██▄
▄███▄
░░░░▀██▄▀


▄▄████▄▄
▄███▀▀███▄
██████████
▀███▄░▄██▀
▄▄████▄▄░▀█▀▄██▀▄▄████▄▄
▄███▀▀▀████▄▄██▀▄███▀▀███▄
███████▄▄▀▀████▄▄▀▀███████
▀███▄▄███▀░░░▀▀████▄▄▄███▀
▀▀████▀▀████████▀▀████▀▀
77Network (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 4


View Profile
December 28, 2020, 08:18:18 AM
 #9

I am sorry, but I am not understanding. If this is documented someplace, please let me know and I will research it.

I don't think Electrum is producing Base64 encoded psbt files. When I open the .psbt file I see this.

---
psbtÿ U   ä[J§éŽz ×U¶‚ÏÙ\¶iÁᬛÂrÑÑiå     ýÿÿÿ}    v©™\´¢tó÷t4¦!Êd,14ꈬ
   â   ÿãçæYÉqÇm÷Un]»:•4wÙ:.“b:©_TÍ    kH0E! è˜+‰P»AÁk~ ­xÍý¨©¼XÑo×0ù“hx{O 0ª¶É°O   DaYYKI¬’Òt[Ê–œx)(¼3;‰!HÁÞô×û²0„z4#qá)³   e~EöqØkð¤ö•/rþÿÿÿ}    v©Z   ìqï
,òê§ xn1u_ˆ¬@Ys    v©×dS8.Þ8WW̵FcÙ؈[Ûˆ¬É "ðÿez5ÅnÍ­,^
p'.4fýãÅÆ BqiÄ÷¬8ˆL ŽÐ       "Ê[Þ²Ûñ$À©¬õ¶É\_˜6¼H¶xü̶"æÛ÷ ŽР      
---

I think this is some kind of binary version of a psbt. I am wondering if there is anyway to reverse engineer this back to an actual transaction. I tried running it through that web based utility you mentioned in your post, but it says "Forbidden character at index 4."


nc50lc
Legendary
*
Offline Offline

Activity: 2604
Merit: 6424


Self-proclaimed Genius


View Profile
December 28, 2020, 01:55:19 PM
Merited by HCP (2), BitMaxz (1)
 #10

Can anyone tell me anything more about how the latest release handles saving unsigned transactions to a file? I like to manually verify all the outputs in the unsigned transaction file before I allow the file to be copied to a blank thumb drive. (And then loaded on the offline wallet to be signed.)  Is there anyway to validate the contents of this file using something external to Electrum before signing the transaction? I tried to open the file but it looks like encrypted contents now. The documentation does not appear to be updated since this was changed.
It's Base64 encoded... and the data is in "Partially Signed Bitcoin Transaction" aka PSBT format... You can read about the PSBT format here: https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki
If he use "Copy to clipboard", it will result with a Base64 string; IDK for the "Export to file" but it looks like a 'binary version' like he said.

@77Network Either (1) use the "copy to clipboard" and paste it on a text file then you can use Bitcoin Core (even offline) to decode it using the command: decodepsbt.
Or (2) Sign it first (then the exported file/text back to the online machine will be in HEX) and before you broadcast, you can decode it using your usual tools.

Of course, all of this are after the upgrade.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
igor72
Legendary
*
Offline Offline

Activity: 2016
Merit: 2081


Crypto Swap Exchange


View Profile
December 28, 2020, 06:04:18 PM
 #11

I have cold electrum 4.0.9 working fine on an old 2008 netbook (32-bit Intel Atom 1.6GHz N270, 2 GB) with Linux LXLE.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
77Network (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 4


View Profile
December 28, 2020, 06:04:28 PM
 #12

Thanks guys I appreciate the advice.

xenon, thank you for the instructions on how to circumvent the registration of Win 10. I think my hardware is probably not a good fit for Win 10, but the advice is most helpful.


I guess I am being too paranoid, but for me this is a signification amount of value I am trying to protect. My concern is a scenario where my Electrum gets compromised somehow. I had been manually verifying the transaction in the unsigned.txt file to make sure it matched what was being displayed in the Electrum GUI. I would do this before I signed the transaction and again after the transaction was signed. For the attack to be successful I know they would need to compromise both the on-line Electrum used to create the transaction and the off-line Electrum used to sign the transaction, which is unlikely.


I was unaware that the signed transaction will be exported in Base64. (I have not been able to get 4.0.9 to start yet for my offline wallet) So, at least I can still visually verify the signed transaction.


Just have 2 more questions,
1. Is there an easy way to decode the contents of the unsigned binary encoded .psbt file that does not involve using Electrum?
2. Can someone recommend an off-line utility which will decode the contents of the signed Base64 encoded .psbt file?

Thank you for helping me learn more about this.
James.  
HCP
Legendary
*
Offline Offline

Activity: 2086
Merit: 4361

<insert witty quote here>


View Profile
December 28, 2020, 09:31:04 PM
 #13

If he use "Copy to clipboard", it will result with a Base64 string; IDK for the "Export to file" but it looks like a 'binary version' like he said.
Ah yes... you are indeed correct. "Copy To Clipboard" option is a Base64 encoded string... the "Export to file" file is simply just the hex values written out to the file.



I was unaware that the signed transaction will be exported in Base64. (I have not been able to get 4.0.9 to start yet for my offline wallet) So, at least I can still visually verify the signed transaction.
Yeah, I got it wrong... I assumed the "copy to clipboard" and "export to file" options were exporting in the same format... they're not! Undecided as per nc50lc's comment, clipboard is in Base64 (which can be decoded directly using the Bitcoin Core RPC tool)... whereas the "export to file" is just the ASCII encoded hex values... ie. just a binary file.


Just have 2 more questions,
1. Is there an easy way to decode the contents of the unsigned binary encoded .psbt file that does not involve using Electrum?
2. Can someone recommend an off-line utility which will decode the contents of the signed Base64 encoded .psbt file?
So, you can simply open the .pbst file with a hex editor to retrieve the raw hex values... or you can use an ASCII to hex converter: https://www.rapidtables.com/convert/number/ascii-to-hex.html and copy paste the contents and it'll give the hex (set the output delimiter string to "None" if you use that converter).

The file format is defined in BIP174: https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki

There are a few tools floating around that will decode the PSBT... the easiest is the Bitcoin Core RPC online: https://bitcoincore.org/en/doc/0.20.0/rpc/rawtransactions/decodepsbt/ (or Bitcoin Core console itself if you have it installed, but that requires it to be in the Base64 encoding!)

Otherwise, there seem to be various Python and NodeJS/npm libraries floating around that seem to handle PSBT data.

Python:
https://github.com/btclib-org/btclib

NodeJS/npm:
https://www.npmjs.com/package/psbt

█████████████████████████
████▐██▄█████████████████
████▐██████▄▄▄███████████
████▐████▄█████▄▄████████
████▐█████▀▀▀▀▀███▄██████
████▐███▀████████████████
████▐█████████▄█████▌████
████▐██▌█████▀██████▌████
████▐██████████▀████▌████
█████▀███▄█████▄███▀█████
███████▀█████████▀███████
██████████▀███▀██████████
█████████████████████████
.
BC.GAME
▄▄░░░▄▀▀▄████████
▄▄▄
██████████████
█████░░▄▄▄▄████████
▄▄▄▄▄▄▄▄▄██▄██████▄▄▄▄████
▄███▄█▄▄██████████▄████▄████
███████████████████████████▀███
▀████▄██▄██▄░░░░▄████████████
▀▀▀█████▄▄▄███████████▀██
███████████████████▀██
███████████████████▄██
▄███████████████████▄██
█████████████████████▀██
██████████████████████▄
.
..CASINO....SPORTS....RACING..
█░░░░░░█░░░░░░█
▀███▀░░▀███▀░░▀███▀
▀░▀░░░░▀░▀░░░░▀░▀
░░░░░░░░░░░░
▀██████████
░░░░░███░░░░
░░█░░░███▄█░░░
░░██▌░░███░▀░░██▌
░█░██░░███░░░█░██
░█▀▀▀█▌░███░░█▀▀▀█▌
▄█▄░░░██▄███▄█▄░░▄██▄
▄███▄
░░░░▀██▄▀


▄▄████▄▄
▄███▀▀███▄
██████████
▀███▄░▄██▀
▄▄████▄▄░▀█▀▄██▀▄▄████▄▄
▄███▀▀▀████▄▄██▀▄███▀▀███▄
███████▄▄▀▀████▄▄▀▀███████
▀███▄▄███▀░░░▀▀████▄▄▄███▀
▀▀████▀▀████████▀▀████▀▀
BitMaxz
Legendary
*
Offline Offline

Activity: 3444
Merit: 3175


Playbet.io - Crypto Casino and Sportsbook


View Profile WWW
December 29, 2020, 12:18:35 AM
 #14

I think you don't need to upgrade anything OS or the Electrum installed in your offline PC/Laptop.
If you make the unsigned transaction from an online PC/laptop you must have the option to copy the hex/raw transaction just copy them and put them into notepad transfer it to your offline machine.

Now, open your Electrum 2.9.0 and check this



Now open the transferred notepad and copy hex/raw transaction paste it there and sign the transaction. The result must be your signed raw/hex transaction just copy them and save it again to a new notepad and transfer it back to the online machine. Now check it first before you broadcast if the transaction you made is correct you can use this tool https://coinb.in/#verify after that if all is correct you can now broadcast them here https://coinb.in/#broadcast just paste the hex/raw transaction then submit or you can use your latest Electrum installed in your online machine to broadcast the transaction.

███████████████
█████████████████████
██████▄▄███████████████
██████▐████▄▄████████████
██████▐██▀▀▀██▄▄█████████
████████▌█████▀██▄▄██████
██████████████████▌█████
█████████████▀▄██▀▀██████
██████▐██▄▄█▌███████████
██████▐████▀█████████████
██████▀▀███████████████
█████████████████████
███████████████

.... ..Playbet.io..Casino & Sportsbook.....Grab up to  BTC + 800 Free Spins........
████████████████████████████████████████
██████████████████████████████████████████████
██████▄▄████████████████████████████████████████
██████▐████▄▄█████████████████████████████████████
██████▐██▀▀▀██▄▄██████████████████████████████████
████████▌█████▀██▄▄█████▄███▄███▄███▄█████████████
██████████████████▌████▀░░██▌██▄▄▄██████████████
█████████████▀▄██▀▀█████▄░░██▌██▄░░▄▄████▄███████
██████▐██▄▄█▌██████████▀███▀███▀███▀███▀█████████
██████▐████▀██████████████████████████████████████
██████▀▀████████████████████████████████████████
██████████████████████████████████████████████
████████████████████████████████████████
coinmaster_47854
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
December 29, 2020, 12:25:38 AM
 #15

Why not just write down the seed on paper, install new version of Electrum and do it from there?

Using USB drives is dangerous because this way secrets may leak (in hypothetical scenario when there is a malware on the offline computer capable of writing on USB devices in a hidden way).

NotATether
Legendary
*
Offline Offline

Activity: 1792
Merit: 7389


Top Crypto Casino


View Profile WWW
December 29, 2020, 12:52:10 AM
Last edit: December 29, 2020, 04:31:50 AM by NotATether
 #16

I'll tell you what to do in your case.

1)Download the ISO file for Windows 10 from Microsoft's official website. 2) Write the image to USB drive (or DVD if ISO size matches it). 3) Install Win 10 on your offline computer (preferably 4 Gigas RAM , if less, it is better to add it, it is cheap).  4) Install the latest version of Electrum. 5) Always switch off offline computer  not via shut down, but via  hibernation. (By default this option is not visible in Win10, search the internet for how to make it visible.)  Microsoft allows you to work with a non-activated operating system for several days. If you turn computer off via  shutdown, you will not be able to boot after these days (even if the computer was not connected to the internet the whole time, the system has an internal counter). If you turn off via hibernation, the status of your computer will always be "spotlessly clean" after turning it on. 6) Just in case, after installing OS and Electrum, create an image of  system's partition and save it on an external hard drive or on the second HDD partition. This is necessary so that if you accidentally exit via shutdown and the system will not be able to boot after turning it on, you can restore everything to its original state.

This is how I made my cold computer about three years ago and everything is working fine. Right, I have Armory for my cold wallet, not Electrum, but that doesn't matter in this case.

Another legal way to extend the Windows 10 trial is run slmgr -rearm in Command Prompt when the 30-day trial is almost finished. This can be ran at most three times before it doesn't work anymore, so you get 120 days out of the trial.

But I honestly wouldn't bother in the case of Windows 10. The only impedance when running unactivated is that you can't change the personalizion settings and there's a not-so-obtrusive watermark on the bottom right. It doesn't shut down the computer at all which is bearable to me.



Thank you for the advice on how to extend the trial time for Windows 10. It is an interesting idea, but I think my hardware is too old to support 10.

slmgr works on all Windows operating systems from Vista to 10.

███████████████████████
████▐██▄█████████████████
████▐██████▄▄▄███████████
████▐████▄█████▄▄████████
████▐█████▀▀▀▀▀███▄██████
████▐███▀████████████████
████▐█████████▄█████▌████
████▐██▌█████▀██████▌████
████▐██████████▀████▌████
█████▀███▄█████▄███▀█████
███████▀█████████▀███████
██████████▀███▀██████████

███████████████████████
.
BC.GAME
▄▄▀▀▀▀▀▀▀▄▄
▄▀▀░▄██▀░▀██▄░▀▀▄
▄▀░▐▀▄░▀░░▀░░▀░▄▀▌░▀▄
▄▀▄█▐░▀▄▀▀▀▀▀▄▀░▌█▄▀▄
▄▀░▀░░█░▄███████▄░█░░▀░▀▄
█░█░▀░█████████████░▀░█░█
█░██░▀█▀▀█▄▄█▀▀█▀░██░█
█░█▀██░█▀▀██▀▀█░██▀█░█
▀▄▀██░░░▀▀▄▌▐▄▀▀░░░██▀▄▀
▀▄▀██░░▄░▀▄█▄▀░▄░░██▀▄▀
▀▄░▀█░▄▄▄░▀░▄▄▄░█▀░▄▀
▀▄▄▀▀███▄███▀▀▄▄▀
██████▄▄▄▄▄▄▄██████
.
..CASINO....SPORTS....RACING..


▄▄████▄▄
▄███▀▀███▄
██████████
▀███▄░▄██▀
▄▄████▄▄░▀█▀▄██▀▄▄████▄▄
▄███▀▀▀████▄▄██▀▄███▀▀███▄
███████▄▄▀▀████▄▄▀▀███████
▀███▄▄███▀░░░▀▀████▄▄▄███▀
▀▀████▀▀████████▀▀████▀▀
77Network (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 4


View Profile
December 29, 2020, 02:44:04 AM
 #17

Thank you for the advice on how to extend the trial time for Windows 10. It is an interesting idea, but I think my hardware is too old to support 10.

coinmaster, unable. Please read first post in thread.


BitMaxz, your idea is very intriguing. However, I tried what you suggested and am getting an unable to parse error in 2.9.0. I am not sure what format it is expecting. I tried with Base64. Is it hex, or json? I have never used this feature before.


Maybe we can back up the discussion a little bit and you guys could help me understand the different formats we are dealing with.
Using 4.0.9 I can choose to "export", and "copy to clipboard". This gives the transaction encoded in base64? And if I choose to "export to file" that is same base64 converted to ASCII?

Is there anyway to take either of these representations of the transaction and convert it to something that is in a human readable form? I thought I could take base64 string from the clipboard and convert it to hex using:  https://cryptii.com/pipes/base64-to-hex  Then, take the hex and use a tool like https://live.blockcypher.com/btc/decodetx/ to decode the hex to a json representation of the transaction. But this does not work. I think the hex is bad, but not sure.

I used to understand how this all worked on 2.9.0, but now I am very confused.

James.
nc50lc
Legendary
*
Offline Offline

Activity: 2604
Merit: 6424


Self-proclaimed Genius


View Profile
December 29, 2020, 03:15:14 AM
 #18

Maybe we can back up the discussion a little bit and you guys could help me understand the different formats we are dealing with.
Using 4.0.9 I can choose to "export", and "copy to clipboard". This gives the transaction encoded in base64? And if I choose to "export to file" that is same base64 converted to ASCII?
No for the second part; if you open the .psbt file using a text editor, it will just assume that the contents are any of the text character encodings and will display non-readable data.

I guess that it's a binary encoding: https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki#Encoding
But the encoded data is the same whatever option you've used to export the partial raw transaction.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
HCP
Legendary
*
Offline Offline

Activity: 2086
Merit: 4361

<insert witty quote here>


View Profile
December 29, 2020, 08:16:05 AM
Last edit: December 29, 2020, 08:30:18 AM by HCP
Merited by ranochigo (4), Heisenberg_Hunter (1)
 #19

Maybe we can back up the discussion a little bit and you guys could help me understand the different formats we are dealing with.
Using 4.0.9 I can choose to "export", and "copy to clipboard". This gives the transaction encoded in base64? And if I choose to "export to file" that is same base64 converted to ASCII?
Not quite correct... Electrum now uses the "Partially Signed Bitcoin Transaction" (aka PSBT) format when exporting "unsigned" transactions. As already noted, this psbt file format is defined here. The important thing to note is that it is a binary file format... there is unlikely to be any human readable text contained within it (aside from the "psbt" magic bytes at the the beginning of the file)

As far as the Electrum exports are concerned:

- When you use "copy to clipboard"... Electrum encodes that psbt binary data into Base64 text format (as copy/pasting "binary" data can be somewhat problematic).
- When you use "export to file"... Electrum simply writes the psbt binary data into the file directly.


Is there anyway to take either of these representations of the transaction and convert it to something that is in a human readable form? I thought I could take base64 string from the clipboard and convert it to hex using:  https://cryptii.com/pipes/base64-to-hex  Then, take the hex and use a tool like https://live.blockcypher.com/btc/decodetx/ to decode the hex to a json representation of the transaction. But this does not work. I think the hex is bad, but not sure.
Correct... using that base64-to-hex converter will indeed convert the "Copy to Clipboard" Base64 encoded psbt data from Electrum into the "hex" output...

The problem you have is that this hex is in psbt format... which is NOT the same format as a standard bitcoin transaction. This is why you get errors when trying to use a Bitcoin Transaction decoder. Having said that, the "raw unsigned transaction is actually contained in the psbt... and, the bonus is that it is included right at the beginning!

So... the basic format of the psbt file is:

4 bytes - Magic Bytes - 0x70736274 (Magic bytes which are ASCII for psbt)
1 byte - separator - 0xff

Then it should be the "global" key-value "map"... this is "variable" length, but the format is:

key length - int specifying number of bytes of the key
key data - the actual key data
value length - int specifying number of bytes of the value data
value data - the actual value data

It looks quite confusing... but hopefully an example will give you some hope... Wink

Here is a PBST from the "copy to clipboard"... so it's in Base64 format:
Code:
cHNidP8BAKACAAAAAo6AHdHDG49pUtMKtxy4zCwK7QY0CtCwfwiV6Lh2yCnLAAAAAAD9////3pHCZunJoabQc89f5IJTdjhVVp/AeJ4l5/H07F4GTPYAAAAAAP3///8CgoOYAAAAAAAZdqkUB/HU3mNuQvFvSZiMjcF+lEMG0mWIrICWmAAAAAAAGXapFFC6xnhio5hP5yg5rw8U4roI5nZkiKyJAh0AAAEA3wIAAAABvezCKQ3mY4LrjFOE8dnESCz7sAxPbbcdtCcQW3+jMI0AAAAAakcwRAIgCgsC9bw0YySu2sgEkK850tLWOeAd7jkfZim5/qnAiR4CIHVOTuA54s1qSDJppXLs8sq67sVda4035Iey5ZL2Yb9yASEDsO+Ka7A1s9cQ+qU9wDR56hP3JKNYs1IIsse9j4NRhvr9////AiKTmAAAAAAAGXapFK69AmfhNVMSEueR6yJVEL5m8Dz+iKwA4fUFAAAAABepFKdL1i+Rxwfqhr1wpPq5plBjnoo4h28xGwAiBgJjb4/vozNp1NLAfAewBDLt5aFVaIx7T8zaf+hF8RnnTAxrFj/5AQAAACIAAAAAAQDiAgAAAAGVl0bY5YaEfpcoXrwvXsL+nklaBPo5bdMcjmXwqcxDwAAAAABrSDBFAiEAh1wXXt69BhgVXQQawnI+zW/Jfk0pzh+N9UFMrR0pUBsCIAdFzlefu+XaKOg47EUzC/5TCR8wdNQK4DcYcMezKdL4ASEDKmFJM+504tv6gZbkwercqdWhPDd2D625GiNlGZ7tWOr9////AlaImAAAAAAAGXapFCkJ7Rj8JufGcxWlejQCZvSMHUVHiKyAlpgAAAAAABl2qRReMpJuA8PCbLIc5Eq8oc23PKd8T4isCQQYACIGAgKXNL1Qs696n22XEACcUvK3QLnuW/IlECDWEmobjYw4DGsWP/kBAAAAFQAAAAAiAgIG2/DJxpZGsYyAQF4QkRbENKVzebjk/AwnOm7OcHeVkwxrFj/5AQAAACsAAAAAIgIDO6NEp2YaMzKa4YHss0Fxy6Wg5W/8A69EChNBZr/7w1EMaxY/+QAAAAAAAAAAAA==


We run that through the "Base64 to hex" converter (set "Group By" = None), which gives us this:
Code:
70736274ff0100a002000000028e801dd1c31b8f6952d30ab71cb8cc2c0aed06340ad0b07f0895e8b876c829cb0000000000fdffffffde91c266e9c9a1a6d073cf5fe48253763855569fc0789e25e7f1f4ec5e064cf60000000000fdffffff0282839800000000001976a91407f1d4de636e42f16f49988c8dc17e944306d26588ac80969800000000001976a91450bac67862a3984fe72839af0f14e2ba08e6766488ac89021d00000100df0200000001bdecc2290de66382eb8c5384f1d9c4482cfbb00c4f6db71db427105b7fa3308d000000006a47304402200a0b02f5bc346324aedac80490af39d2d2d639e01dee391f6629b9fea9c0891e0220754e4ee039e2cd6a483269a572ecf2cabaeec55d6b8d37e487b2e592f661bf72012103b0ef8a6bb035b3d710faa53dc03479ea13f724a358b35208b2c7bd8f835186fafdffffff0222939800000000001976a914aebd0267e135531212e791eb225510be66f03cfe88ac00e1f5050000000017a914a74bd62f91c707ea86bd70a4fab9a650639e8a38876f311b00220602636f8fefa33369d4d2c07c07b00432ede5a155688c7b4fccda7fe845f119e74c0c6b163ff90100000022000000000100e20200000001959746d8e586847e97285ebc2f5ec2fe9e495a04fa396dd31c8e65f0a9cc43c0000000006b483045022100875c175edebd0618155d041ac2723ecd6fc97e4d29ce1f8df5414cad1d29501b02200745ce579fbbe5da28e838ec45330bfe53091f3074d40ae0371870c7b329d2f80121032a614933ee74e2dbfa8196e4c1eadca9d5a13c37760fadb91a2365199eed58eafdffffff0256889800000000001976a9142909ed18fc26e7c67315a57a340266f48c1d454788ac80969800000000001976a9145e32926e03c3c26cb21ce44abca1cdb73ca77c4f88ac09041800220602029734bd50b3af7a9f6d9710009c52f2b740b9ee5bf2251020d6126a1b8d8c380c6b163ff901000000150000000022020206dbf0c9c69646b18c80405e109116c434a57379b8e4fc0c273a6ece707795930c6b163ff9010000002b000000002202033ba344a7661a33329ae181ecb34171cba5a0e56ffc03af440a134166bffbc3510c6b163ff9000000000000000000


Now, looking at the beginning of the file...
Quote
70736274ff0100a002000000028e801dd1c31b8f6952d30ab71cb8cc2c0aed06340ad0b07f0895e8b876c829cb00000 00000fdffffffde91c266e9c9a1a6d073cf5fe48253763855569fc0789e25e7f1f4ec5e064cf600 00000000fdffffff0282839800000000001976a91407f1d4de636e42f16f49988c8dc17e944306d 26588ac80969800000000001976a91450bac67862a3984fe72839af0f14e2ba08e6766488ac8902 1d00000100df02000000....

We see:

70736274 == magic bytes
ff == separator

Then the "global key-value map" starts:
01 == length of key == 0x01 == 1 byte
00 == key value = 0x00 == "Unsigned Transaction PSBT_GLOBAL_UNSIGNED_TX" <--- This is the "key" we're after! Wink
a0 == length of data = 0xa0 == 160 bytes == 320 chars
02000000028e801dd1c31b8f6952d30ab71cb8cc2c0aed06340ad0b07f0895e8b876c829cb00000 00000fdffffffde91c266e9c9a1a6d073cf5fe48253763855569fc0789e25e7f1f4ec5e064cf600 00000000fdffffff0282839800000000001976a91407f1d4de636e42f16f49988c8dc17e944306d 26588ac80969800000000001976a91450bac67862a3984fe72839af0f14e2ba08e6766488ac8902 1d00 == actual data value == the unsigned transaction hex! SUCCESS! Wink

If we put that hex into the decodetx utility... we get:
Code:
{
    "addresses": [
        "1j1S6J5Azgju5PtpkwMLd5YMHBDD14BeP",
        "18Mroim7a2auG6C9X8QEDAUgUx5hDKMzZj"
    ],
    "block_height": -1,
    "block_index": -1,
    "confirmations": 0,
    "double_spend": false,
    "fees": 0,
    "hash": "0334ca8de093b635b490ec4480764b8e4a5a0c524ae2825135dd2aa4e2903822",
    "inputs": [
        {
            "age": 0,
            "output_index": 0,
            "prev_hash": "cb29c876b8e895087fb0d00a3406ed0a2cccb81cb70ad352698f1bc3d11d808e",
            "script_type": "empty",
            "sequence": 4294967293
        },
        {
            "age": 0,
            "output_index": 0,
            "prev_hash": "f64c065eecf4f1e7259e78c09f565538765382e45fcf73d0a6a1c9e966c291de",
            "script_type": "empty",
            "sequence": 4294967293
        }
    ],
    "lock_time": 1901193,
    "opt_in_rbf": true,
    "outputs": [
        {
            "addresses": [
                "1j1S6J5Azgju5PtpkwMLd5YMHBDD14BeP"
            ],
            "script": "76a91407f1d4de636e42f16f49988c8dc17e944306d26588ac",
            "script_type": "pay-to-pubkey-hash",
            "value": 9995138
        },
        {
            "addresses": [
                "18Mroim7a2auG6C9X8QEDAUgUx5hDKMzZj"
            ],
            "script": "76a91450bac67862a3984fe72839af0f14e2ba08e6766488ac",
            "script_type": "pay-to-pubkey-hash",
            "value": 10000000
        }
    ],
    "preference": "low",
    "received": "2020-12-29T08:05:12.865990958Z",
    "relayed_by": "3.86.86.99",
    "size": 160,
    "total": 19995138,
    "ver": 2,
    "vin_sz": 2,
    "vout_sz": 2
}

Obviously, it won't always be 160 bytes for every psbt that you create, so you'd need to find and calculate the "data length" value and then extract the appropriate number of following bytes...





Otherwise, another somewhat simpler (and less error-prone) option is to use NodeJS and the 'psbt' package with it's decodePsbt() method. We simply pass in the psbt "hex" and it outputs the fully decoded "psbt" with the raw transaction displayed at the end, like so:
Code:
> const psbt = require('psbt')
> psbt.decodePsbt({psbt:'70736274ff0100a002000000028e801dd1c31b8f6952d30ab71cb8cc2c0aed06340ad0b07f0895e8b876c829cb0000000000fdffffffde91c266e9c9a1a6d073cf5fe48253763855569fc0789e25e7f1f4ec5e064cf60000000000fdffffff0282839800000000001976a91407f1d4de636e42f16f49988c8dc17e944306d26588ac80969800000000001976a91450bac67862a3984fe72839af0f14e2ba08e6766488ac89021d00000100df0200000001bdecc2290de66382eb8c5384f1d9c4482cfbb00c4f6db71db427105b7fa3308d000000006a47304402200a0b02f5bc346324aedac80490af39d2d2d639e01dee391f6629b9fea9c0891e0220754e4ee039e2cd6a483269a572ecf2cabaeec55d6b8d37e487b2e592f661bf72012103b0ef8a6bb035b3d710faa53dc03479ea13f724a358b35208b2c7bd8f835186fafdffffff0222939800000000001976a914aebd0267e135531212e791eb225510be66f03cfe88ac00e1f5050000000017a914a74bd62f91c707ea86bd70a4fab9a650639e8a38876f311b00220602636f8fefa33369d4d2c07c07b00432ede5a155688c7b4fccda7fe845f119e74c0c6b163ff90100000022000000000100e20200000001959746d8e586847e97285ebc2f5ec2fe9e495a04fa396dd31c8e65f0a9cc43c0000000006b483045022100875c175edebd0618155d041ac2723ecd6fc97e4d29ce1f8df5414cad1d29501b02200745ce579fbbe5da28e838ec45330bfe53091f3074d40ae0371870c7b329d2f80121032a614933ee74e2dbfa8196e4c1eadca9d5a13c37760fadb91a2365199eed58eafdffffff0256889800000000001976a9142909ed18fc26e7c67315a57a340266f48c1d454788ac80969800000000001976a9145e32926e03c3c26cb21ce44abca1cdb73ca77c4f88ac09041800220602029734bd50b3af7a9f6d9710009c52f2b740b9ee5bf2251020d6126a1b8d8c380c6b163ff901000000150000000022020206dbf0c9c69646b18c80405e109116c434a57379b8e4fc0c273a6ece707795930c6b163ff9010000002b000000002202033ba344a7661a33329ae181ecb34171cba5a0e56ffc03af440a134166bffbc3510c6b163ff9000000000000000000'});
{
  inputs: [
    {
      non_witness_utxo: '0200000001bdecc2290de66382eb8c5384f1d9c4482cfbb00c4f6db71db427105b7fa3308d000000006a47304402200a0b02f5bc346324aedac80490af39d2d2d639e01dee391f6629b9fea9c0891e0220754e4ee039e2cd6a483269a572ecf2cabaeec55d6b8d37e487b2e592f661bf72012103b0ef8a6bb035b3d710faa53dc03479ea13f724a358b35208b2c7bd8f835186fafdffffff0222939800000000001976a914aebd0267e135531212e791eb225510be66f03cfe88ac00e1f5050000000017a914a74bd62f91c707ea86bd70a4fab9a650639e8a38876f311b00',
      bip32_derivations: [Array]
    },
    {
      non_witness_utxo: '0200000001959746d8e586847e97285ebc2f5ec2fe9e495a04fa396dd31c8e65f0a9cc43c0000000006b483045022100875c175edebd0618155d041ac2723ecd6fc97e4d29ce1f8df5414cad1d29501b02200745ce579fbbe5da28e838ec45330bfe53091f3074d40ae0371870c7b329d2f80121032a614933ee74e2dbfa8196e4c1eadca9d5a13c37760fadb91a2365199eed58eafdffffff0256889800000000001976a9142909ed18fc26e7c67315a57a340266f48c1d454788ac80969800000000001976a9145e32926e03c3c26cb21ce44abca1cdb73ca77c4f88ac09041800',
      bip32_derivations: [Array]
    }
  ],
  outputs: [ { bip32_derivation: [Object] }, { bip32_derivation: [Object] } ],
  pairs: [
    {
      type: '00',
      value: '02000000028e801dd1c31b8f6952d30ab71cb8cc2c0aed06340ad0b07f0895e8b876c829cb0000000000fdffffffde91c266e9c9a1a6d073cf5fe48253763855569fc0789e25e7f1f4ec5e064cf60000000000fdffffff0282839800000000001976a91407f1d4de636e42f16f49988c8dc17e944306d26588ac80969800000000001976a91450bac67862a3984fe72839af0f14e2ba08e6766488ac89021d00'
    },
    {
      type: '00',
      value: '0200000001bdecc2290de66382eb8c5384f1d9c4482cfbb00c4f6db71db427105b7fa3308d000000006a47304402200a0b02f5bc346324aedac80490af39d2d2d639e01dee391f6629b9fea9c0891e0220754e4ee039e2cd6a483269a572ecf2cabaeec55d6b8d37e487b2e592f661bf72012103b0ef8a6bb035b3d710faa53dc03479ea13f724a358b35208b2c7bd8f835186fafdffffff0222939800000000001976a914aebd0267e135531212e791eb225510be66f03cfe88ac00e1f5050000000017a914a74bd62f91c707ea86bd70a4fab9a650639e8a38876f311b00'
    },
    {
      type: '0602636f8fefa33369d4d2c07c07b00432ede5a155688c7b4fccda7fe845f119e74c',
      value: '6b163ff90100000022000000'
    },
    {
      type: '00',
      value: '0200000001959746d8e586847e97285ebc2f5ec2fe9e495a04fa396dd31c8e65f0a9cc43c0000000006b483045022100875c175edebd0618155d041ac2723ecd6fc97e4d29ce1f8df5414cad1d29501b02200745ce579fbbe5da28e838ec45330bfe53091f3074d40ae0371870c7b329d2f80121032a614933ee74e2dbfa8196e4c1eadca9d5a13c37760fadb91a2365199eed58eafdffffff0256889800000000001976a9142909ed18fc26e7c67315a57a340266f48c1d454788ac80969800000000001976a9145e32926e03c3c26cb21ce44abca1cdb73ca77c4f88ac09041800'
    },
    {
      type: '0602029734bd50b3af7a9f6d9710009c52f2b740b9ee5bf2251020d6126a1b8d8c38',
      value: '6b163ff90100000015000000'
    },
    {
      type: '020206dbf0c9c69646b18c80405e109116c434a57379b8e4fc0c273a6ece70779593',
      value: '6b163ff9010000002b000000'
    },
    {
      type: '02033ba344a7661a33329ae181ecb34171cba5a0e56ffc03af440a134166bffbc351',
      value: '6b163ff90000000000000000'
    }
  ],
  unsigned_transaction: '02000000028e801dd1c31b8f6952d30ab71cb8cc2c0aed06340ad0b07f0895e8b876c829cb0000000000fdffffffde91c266e9c9a1a6d073cf5fe48253763855569fc0789e25e7f1f4ec5e064cf60000000000fdffffff0282839800000000001976a91407f1d4de636e42f16f49988c8dc17e944306d26588ac80969800000000001976a91450bac67862a3984fe72839af0f14e2ba08e6766488ac89021d00'
}

█████████████████████████
████▐██▄█████████████████
████▐██████▄▄▄███████████
████▐████▄█████▄▄████████
████▐█████▀▀▀▀▀███▄██████
████▐███▀████████████████
████▐█████████▄█████▌████
████▐██▌█████▀██████▌████
████▐██████████▀████▌████
█████▀███▄█████▄███▀█████
███████▀█████████▀███████
██████████▀███▀██████████
█████████████████████████
.
BC.GAME
▄▄░░░▄▀▀▄████████
▄▄▄
██████████████
█████░░▄▄▄▄████████
▄▄▄▄▄▄▄▄▄██▄██████▄▄▄▄████
▄███▄█▄▄██████████▄████▄████
███████████████████████████▀███
▀████▄██▄██▄░░░░▄████████████
▀▀▀█████▄▄▄███████████▀██
███████████████████▀██
███████████████████▄██
▄███████████████████▄██
█████████████████████▀██
██████████████████████▄
.
..CASINO....SPORTS....RACING..
█░░░░░░█░░░░░░█
▀███▀░░▀███▀░░▀███▀
▀░▀░░░░▀░▀░░░░▀░▀
░░░░░░░░░░░░
▀██████████
░░░░░███░░░░
░░█░░░███▄█░░░
░░██▌░░███░▀░░██▌
░█░██░░███░░░█░██
░█▀▀▀█▌░███░░█▀▀▀█▌
▄█▄░░░██▄███▄█▄░░▄██▄
▄███▄
░░░░▀██▄▀


▄▄████▄▄
▄███▀▀███▄
██████████
▀███▄░▄██▀
▄▄████▄▄░▀█▀▄██▀▄▄████▄▄
▄███▀▀▀████▄▄██▀▄███▀▀███▄
███████▄▄▀▀████▄▄▀▀███████
▀███▄▄███▀░░░▀▀████▄▄▄███▀
▀▀████▀▀████████▀▀████▀▀
NotATether
Legendary
*
Offline Offline

Activity: 1792
Merit: 7389


Top Crypto Casino


View Profile WWW
December 29, 2020, 02:53:14 PM
 #20

The real cold computer  has not to go online even at the time of OS  registration. I have the legal WIN 10 license (in fact that is a volume license) but didn't  use it for  OS on my cold computer and found the way how to work around the limitation of trial period.  Couple of other notebooks that I have for online work  use that license.

slmgr doesn't connect to the internet, it's just a VBS script that resets the trial to the way it was when you installed Windows and you have to restart the computer for the changes to apply. There is no Internet connectivity involved at all.

But it's a pretty dumb solution for cold storage if you ask me since you still only get 120 days max, at least your method gives you an unlimited number of days.

███████████████████████
████▐██▄█████████████████
████▐██████▄▄▄███████████
████▐████▄█████▄▄████████
████▐█████▀▀▀▀▀███▄██████
████▐███▀████████████████
████▐█████████▄█████▌████
████▐██▌█████▀██████▌████
████▐██████████▀████▌████
█████▀███▄█████▄███▀█████
███████▀█████████▀███████
██████████▀███▀██████████

███████████████████████
.
BC.GAME
▄▄▀▀▀▀▀▀▀▄▄
▄▀▀░▄██▀░▀██▄░▀▀▄
▄▀░▐▀▄░▀░░▀░░▀░▄▀▌░▀▄
▄▀▄█▐░▀▄▀▀▀▀▀▄▀░▌█▄▀▄
▄▀░▀░░█░▄███████▄░█░░▀░▀▄
█░█░▀░█████████████░▀░█░█
█░██░▀█▀▀█▄▄█▀▀█▀░██░█
█░█▀██░█▀▀██▀▀█░██▀█░█
▀▄▀██░░░▀▀▄▌▐▄▀▀░░░██▀▄▀
▀▄▀██░░▄░▀▄█▄▀░▄░░██▀▄▀
▀▄░▀█░▄▄▄░▀░▄▄▄░█▀░▄▀
▀▄▄▀▀███▄███▀▀▄▄▀
██████▄▄▄▄▄▄▄██████
.
..CASINO....SPORTS....RACING..


▄▄████▄▄
▄███▀▀███▄
██████████
▀███▄░▄██▀
▄▄████▄▄░▀█▀▄██▀▄▄████▄▄
▄███▀▀▀████▄▄██▀▄███▀▀███▄
███████▄▄▀▀████▄▄▀▀███████
▀███▄▄███▀░░░▀▀████▄▄▄███▀
▀▀████▀▀████████▀▀████▀▀
Pages: [1] 2 3 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!