[ANN] (QTUM) - A Scalable Smart Contract Platform w/ Proof of Stake - page 8.

Qtum

sr. member

Activity: 722

Merit: 259

Hard Fork Special: Linux and Raspberry Pi

https://blog.qtum.org/hard-fork-special-linux-raspberry-pi-40e60341923d

In this blog, we look at the Qtum mainnet hard fork at block 680,000 on August 28, 2020. This hard fork added protocol and consensus changes to activate offline staking and was a mandatory update for the Qtum Core wallets Qtum-Qt (the GUI desktop wallet) and qtumd (the command-line server wallet). There were no updates required for other types of wallets (mobile wallets, hardware wallets, etc.) and no new coins were created.

The hard fork for Qtum version 0.19.1 added offline staking capability, allowing address delegation and super stakers. The Qtum Core wallet can now be operated as a super staker to receive address delegations from others and stake their UTXOs. The hard fork happened at block 680,000) on August 28, 2020, at 7:11 pm GMT and only applied to the Qtum Core wallets Qtum-Qt and qtumd, no other wallets. While updated wallets made the hard fork automatically, users that don’t update in time saw their wallets disconnected from the main network, are not be able to make transactions, and (for staking wallets) may see their coins staked on a split chain, where they are difficult to recover. There is no new coin from the hard fork, but a good chance to temporarily lose coins for staking wallets that did not update in time.

Read all about it here: https://blog.qtum.org/hard-fork-special-linux-raspberry-pi-40e60341923d

Qtum Telegram Channel: https://t.me/qtumofficial
Qtum Twitter: https://twitter.com/Qtum
Qtum Facebook: https://www.facebook.com/QtumOfficial
Qtum Reddit: https://www.reddit.com/r/Qtum

Frankrbruno

newbie

Activity: 27

Merit: 0

_

Quote from: readyUP on September 11, 2020, 09:40:45 AM

I have the wallet v.0.19.1 .. do I have to resynchronize or update the wallet ?!
where are these addresses to have the offline stake or the delegation of addresses?

A few questions...

Is this a new wallet?

If this is a new wallet with zero balance then you do not need to do anything except make sure that you have properly backed your wallet up. More details for of securing your wallet can be found here docs.qtum.org

If it is not a new wallet and you updated the wallet to v.0.19.1 after October 28th, then please read this article https://blog.qtum.org/you-missed-the-hard-fork-now-what-996bab6639de

Also, here is the link for the Qtum Stake-A-Thon https://stake-a-thon.qtum.org/en/pool-delegation

If you are just looking for a list of superstakers, you can look here https://stake-a-thon.qtum.org/en/super-staker/list

If you are looking for pool delegation list, you can look here https://stake-a-thon.qtum.org/en/pool-delegation

readyUP

newbie

Activity: 182

Merit: 0

sorry but for me as an Italian it is difficult to understand !!
I have the wallet v.0.19.1 .. do I have to resynchronize or update the wallet ?!
where are these addresses to have the offline stake or the delegation of addresses?
please do something more user friendly

Qtum

sr. member

Activity: 722

Merit: 259

Hard Fork Special: Mac

In this blog, we look at the Qtum mainnet hard fork at block 680,000 on August 28, 2020. This hard fork added protocol and consensus changes to activate offline staking and was a mandatory update for the Qtum Core wallets Qtum-Qt (the GUI desktop wallet) and qtumd (the command-line server wallet). There were no updates required for other types of wallets (mobile wallets, hardware wallets, etc.) and no new coins were created.

The hard fork for Qtum version 0.19.1 added offline staking capability, allowing address delegation and super stakers. The Qtum Core wallet can now be operated as a super staker to receive address delegations from others and stake their UTXOs. The hard fork happened at block 680,000 on August 28, 2020, at 7:11 pm GMT and only applied to the Qtum Core wallets Qtum-Qt and qtumd, no other wallets. While updated wallets made the hard fork automatically, users that don’t update in time saw their wallets disconnected from the main network, are not be able to make transactions, and (for staking wallets) may see their coins staked on a split chain, where they are difficult to recover. There is no new coin from the hard fork, but a good chance to temporarily lose coins for staking wallets that did not update in time.

Read all about it here: https://blog.qtum.org/hard-fork-special-mac-462e11a879d1

Qtum Telegram Channel: https://t.me/qtumofficial
Qtum Twitter: https://twitter.com/Qtum
Qtum Facebook: https://www.facebook.com/QtumOfficial
Qtum Reddit: https://www.reddit.com/r/Qtum

Qtum

sr. member

Activity: 722

Merit: 259

Development Updates (August 11 - 17)

See the weekly development updates: https://qtum.org/en/post/development-updates-september-01-07

Qtum Telegram Channel: https://t.me/qtumofficial
Qtum Twitter: https://twitter.com/Qtum
Qtum Facebook: https://www.facebook.com/QtumOfficial
Qtum Reddit: https://www.reddit.com/r/Qtum

JB395

newbie

Activity: 21

Merit: 0

Quote from: efemtekem on September 06, 2020, 03:32:13 PM

I have a question, friends say, delete the local copy of the blockchain, after installing the new version ..... Are they talking about deleting the Blocks "," stateQtum "," database "folders and" banlist.dat "files in the AppData / Roaming / Qtum file, or another step I was unable to update before the hard fork. Due to this incident I am trying to upload my wallet.dat file before the hard Fork to the Qtum wallet version 0.19.1 so I wanted to get some ideas to avoid doing anything wrong.

My last question is I can't see the "deleteblockchaindata -delete the local copy ......" tab in the Restore Wallet option. What can I do so that I can see that option.

Please see this blog for more details https://blog.qtum.org/hard-fork-special-windows-2c8febdbcd43

Qtum

sr. member

Activity: 722

Merit: 259

You Missed the Hard Fork – Now What?

Qtum mainnet hard forked on August 28 to launch offline staking protocol. Qtum Core wallet version 0.19.1 was a mandatory update for protocol and consensus changes and implemented a hard fork at block 680,000, which means older version wallets are incompatible and were automatically disconnected from mainnet.

If your wallet missed the hard fork it would be disconnected from mainnet, but still able to peer with other wallets that missed the hard fork, making up a smaller dying “split chain”. There are two fundamental reasons to not be on the split chain: missing transactions and lost block rewards.

Read more: https://blog.qtum.org/you-missed-the-hard-fork-now-what-996bab6639de

Qtum Telegram Channel: https://t.me/qtumofficial
Qtum Twitter: https://twitter.com/Qtum
Qtum Facebook: https://www.facebook.com/QtumOfficial
Qtum Reddit: https://www.reddit.com/r/Qtum

efemtekem

newbie

Activity: 9

Merit: 0

I have a question, friends say, delete the local copy of the blockchain, after installing the new version ..... Are they talking about deleting the Blocks "," stateQtum "," database "folders and" banlist.dat "files in the AppData / Roaming / Qtum file, or another step I was unable to update before the hard fork. Due to this incident I am trying to upload my wallet.dat file before the hard Fork to the Qtum wallet version 0.19.1 so I wanted to get some ideas to avoid doing anything wrong.

My last question is I can't see the "deleteblockchaindata -delete the local copy ......" tab in the Restore Wallet option. What can I do so that I can see that option.

Qtum

sr. member

Activity: 722

Merit: 259

August Recap: Offline Staking & More

https://blog.qtum.org/august-recap-offline-staking-more-42d1a5418d67

A lot has happened with Qtum in the month of August! Offline staking protocol hard fork took effect, the testnet Stake-A-Thon winded down, the mainnet Stake-A-Thon just got started, and the huge DeFi grant program went live, making this past August one the hottest months on record.

August started out with the continuation of the Qtum Testnet Stake-A-Thon which completed on August 24th paying out a total of 820 QTUM! We would like to say thank you to everyone who participated and congratulate all winners (as a special thank you, 5 lucky participants will receive an additional 100 QTUM prize)!

Read more https://blog.qtum.org/august-recap-offline-staking-more-42d1a5418d67

Qtum Telegram Channel: https://t.me/qtumofficial
Qtum Twitter: https://twitter.com/Qtum
Qtum Facebook: https://www.facebook.com/QtumOfficial
Qtum Reddit: https://www.reddit.com/r/Qtum

efemtekem

newbie

Activity: 9

Merit: 0

Quote from: JB395 on September 05, 2020, 03:29:40 PM

Quote from: efemtekem on September 05, 2020, 01:31:25 PM

If my wallet lock is the password entered when sending stakes or coins, I enter the password for a single stake or when sending coins, is there another step to activate it? before doing dummprivkey

An encrypted Qtum Core wallet has a single passphrase that can be used to fully unlock the wallet, or unlock the wallet for staking only. To send coins or dump the private key the wallet must be fully unlocked.

To fully unlock the Qtum-Qt GUI wallet go to Settings - Unlock wallet and "untick" the little box "For staking only." Then enter the passphrase and click OK.

To fully unlock the qtumd daemon wallet using qtum-cli enter the command as appropriate for your operating system:

Code:

qtum-cli walletpassphrase "your_passphrase" 600

Here the wallet would be fully unlocked for 600 seconds.

Thank you very much for JB395 information.

JB395

newbie

Activity: 21

Merit: 0

Quote from: efemtekem on September 05, 2020, 01:31:25 PM

If my wallet lock is the password entered when sending stakes or coins, I enter the password for a single stake or when sending coins, is there another step to activate it? before doing dummprivkey

An encrypted Qtum Core wallet has a single passphrase that can be used to fully unlock the wallet, or unlock the wallet for staking only. To send coins or dump the private key the wallet must be fully unlocked.

To fully unlock the Qtum-Qt GUI wallet go to Settings - Unlock wallet and "untick" the little box "For staking only." Then enter the passphrase and click OK.

To fully unlock the qtumd daemon wallet using qtum-cli enter the command as appropriate for your operating system:

Code:

qtum-cli walletpassphrase "your_passphrase" 600

Here the wallet would be fully unlocked for 600 seconds.

efemtekem

newbie

Activity: 9

Merit: 0

Quote from: JB395 on September 05, 2020, 01:11:47 PM

Quote from: efemtekem on September 05, 2020, 03:34:24 AM

When I type my wallet address after I enter the dumpprivkey command in the console Error: Please enter the wallet passphrase with walletpassphrase first. (code -13) error.

You need to unlock the wallet before dumping the private keys.

The wallet.dat file can be used on any computer running the Qtum Core
wallet. The private key can be used with any Qtum wallet that imports private keys.

If my wallet lock is the password entered when sending stakes or coins, I enter the password for a single stake or when sending coins, is there another step to activate it? before doing dummprivkey

JB395

newbie

Activity: 21

Merit: 0

Quote from: efemtekem on September 05, 2020, 03:34:24 AM

When I type my wallet address after I enter the dumpprivkey command in the console Error: Please enter the wallet passphrase with walletpassphrase first. (code -13) error.

You need to unlock the wallet before dumping the private keys.

The wallet.dat file can be used on any computer running the Qtum Core wallet. The private key can be used with any Qtum wallet that imports private keys.

efemtekem

newbie

Activity: 9

Merit: 0

Quote from: TomThumb on September 04, 2020, 03:04:36 PM

Quote from: efemtekem on September 03, 2020, 01:38:36 AM

Currently, my coins are showing in my wallet, but I cannot actively send them to the stock exchange or to another wallet. The reason is because of the hard fork. I had previously restored my wallet for adverse situations. But after the update, I cannot transfer to another place in my wallet. After that, I reloaded the wallet on the 64 processor computer and when I do the restore wallet in the new wallet, only transactions are coming. My coin is 0 on the 64 bit processor, but there are amounts on the 32 bit processor, which is my old computer. I cannot find a way to transfer these coins to the stock market or elsewhere. As I said, my wallet has a .dat file.

Why are you not able to use a 32-bit computer or, say, Windows 7 32-bit? In future, I recommend this wallet:

https://exodus.io

That said, the ".dat" file should be in a format that's CPU agnostic. It's bad design if it isn't! Are you sure you're not doing something else wrong?

I'd like to use it, but after the hard fork I can't send it from my wallet to the exchange or any other wallet as I don't think it's doing something wrong. As I read on the forums, these problems occur when we do not update or transfer to another location before the hard fork. Now, my only thought is to transfer my wallet from my 32 bit computer to an exchange or another wallet. I believe in Qtum technology, I hope it will be very good in the future.

efemtekem

newbie

Activity: 9

Merit: 0

Quote from: JB395 on September 04, 2020, 07:15:00 AM

Quote from: efemtekem on September 03, 2020, 03:37:56 PM

But if I think the situation is a little different;
The computer I use is a 32-bit processor computer and I cannot convert my computer to a 64-bit processor. My qtum wallet on my computer is mainnet-ignition-v0.18.3 (32-bit). After the hard fork update on August 28, 2020, I cannot update my wallet to mainnet-ignition-v0.19.1. I just have the wallet.dat file and password. If I load the mainnet-ignition-v0.19.1 wallet on another 64 bit processor computer, the coins do not come when I say restore wallet. I do not know what path to follow. You mentioned 2) delete the local blockchain and resync the whole thing 3) run the zapwallettxes = 2 command on startup. there is no option to choose boxes.
The boxes that I have
1 Restore File
2 Rebuild blockhain index
3 Recover transactions without metadata
4 Delete the local copy of the block chain. There is no image in the picture that appears called restore wallet you provided in your blog link. I wonder if I am the only one experiencing this trouble.

Sorry I wasn't focused on the 32-bitness of your computer. Bitcoin discontinued 32-bit versions a few updates ago, as did Qtum. There are a few things to try.

For "Restore Wallet" with a version 0.19.1 installed, the full name for the 3rd option is "zapwallettxes=2 recover transactions without metadata" so that is the option to chose (with a v0.19.1 wallet installed on a 64-bit machine and a new blockchain fully synced).

If you are missing images maybe try another browser.

Another approach to recovering the wallet is using the private keys. On your 32-bit older version wallet, find the Console to check the active addresses with the "listaddressgroupings" command. For every address with a balance (may be only one) dump the private key using this command

Code:

dumpprivkey "address"

Copy each private key (but be careful because private keys provide unencrypted access to your funds) and use to restore the wallet on Qtum Electrum (runs on 32-bit machines) or the Qtum Web Wallet (https://qtumeco.io/wallet). On the Web wallet this option is called "Restore from WIF".

When I type my wallet address after I enter the dumpprivkey command in the console Error: Please enter the wallet passphrase with walletpassphrase first. (code -13) error.

TomThumb

member

Activity: 189

Merit: 12

Quote from: efemtekem on September 03, 2020, 01:38:36 AM

Currently, my coins are showing in my wallet, but I cannot actively send them to the stock exchange or to another wallet. The reason is because of the hard fork. I had previously restored my wallet for adverse situations. But after the update, I cannot transfer to another place in my wallet. After that, I reloaded the wallet on the 64 processor computer and when I do the restore wallet in the new wallet, only transactions are coming. My coin is 0 on the 64 bit processor, but there are amounts on the 32 bit processor, which is my old computer. I cannot find a way to transfer these coins to the stock market or elsewhere. As I said, my wallet has a .dat file.

Why are you not able to use a 32-bit computer or, say, Windows 7 32-bit? In future, I recommend this wallet:

https://exodus.io

That said, the ".dat" file should be in a format that's CPU agnostic. It's bad design if it isn't! Are you sure you're not doing something else wrong?

JB395

newbie

Activity: 21

Merit: 0

Quote from: efemtekem on September 03, 2020, 03:37:56 PM

But if I think the situation is a little different;
The computer I use is a 32-bit processor computer and I cannot convert my computer to a 64-bit processor. My qtum wallet on my computer is mainnet-ignition-v0.18.3 (32-bit). After the hard fork update on August 28, 2020, I cannot update my wallet to mainnet-ignition-v0.19.1. I just have the wallet.dat file and password. If I load the mainnet-ignition-v0.19.1 wallet on another 64 bit processor computer, the coins do not come when I say restore wallet. I do not know what path to follow. You mentioned 2) delete the local blockchain and resync the whole thing 3) run the zapwallettxes = 2 command on startup. there is no option to choose boxes.
The boxes that I have
1 Restore File
2 Rebuild blockhain index
3 Recover transactions without metadata
4 Delete the local copy of the block chain. There is no image in the picture that appears called restore wallet you provided in your blog link. I wonder if I am the only one experiencing this trouble.

Sorry I wasn't focused on the 32-bitness of your computer. Bitcoin discontinued 32-bit versions a few updates ago, as did Qtum. There are a few things to try.

For "Restore Wallet" with a version 0.19.1 installed, the full name for the 3rd option is "zapwallettxes=2 recover transactions without metadata" so that is the option to chose (with a v0.19.1 wallet installed on a 64-bit machine and a new blockchain fully synced).

If you are missing images maybe try another browser.

Another approach to recovering the wallet is using the private keys. On your 32-bit older version wallet, find the Console to check the active addresses with the "listaddressgroupings" command. For every address with a balance (may be only one) dump the private key using this command

Code:

dumpprivkey "address"

Copy each private key (but be careful because private keys provide unencrypted access to your funds) and use to restore the wallet on Qtum Electrum (runs on 32-bit machines) or the Qtum Web Wallet (https://qtumeco.io/wallet). On the Web wallet this option is called "Restore from WIF".

efemtekem

newbie

Activity: 9

Merit: 0

Quote from: JB395 on September 03, 2020, 01:02:29 PM

Quote from: efemtekem on September 02, 2020, 07:35:17 AM

Currently, my coins are showing in my wallet, but I cannot actively send them to the stock exchange or to another wallet. The reason is because of the hard fork. I had previously restored my wallet for adverse situations. But after the update, I cannot transfer to another place in my wallet. After that, I reloaded the wallet on the 64 processor computer and when I do the restore wallet in the new wallet, only transactions are coming. My coin is 0 on the 64 bit processor, but there are amounts on the 32 bit processor, which is my old computer. I cannot find a way to transfer these coins to the stock market or elsewhere. As I said, my wallet has a .dat file.

Qtum had a manditory hard fork to Qtum Core wallet version 0.19.1 on August 28. This hard fork added offline staking protocol to mainnet.

Wallets that were not updated to version 0.19.1 by block 680,000 would show missing transactions, block reward problems, etc.

The recovery is basically 1) Update to version 0.19.1, 2) delete the local blockchain and resync the whole thing 3) run the zapwallettxes=2 command on startup. This blog gives more details for Windows wallets https://blog.qtum.org/hard-fork-special-windows-2c8febdbcd43

But if I think the situation is a little different;
The computer I use is a 32-bit processor computer and I cannot convert my computer to a 64-bit processor. My qtum wallet on my computer is mainnet-ignition-v0.18.3 (32-bit). After the hard fork update on August 28, 2020, I cannot update my wallet to mainnet-ignition-v0.19.1. I just have the wallet.dat file and password. If I load the mainnet-ignition-v0.19.1 wallet on another 64 bit processor computer, the coins do not come when I say restore wallet. I do not know what path to follow. You mentioned 2) delete the local blockchain and resync the whole thing 3) run the zapwallettxes = 2 command on startup. there is no option to choose boxes.
The boxes that I have
1 Restore File
2 Rebuild blockhain index
3 Recover transactions without metadata
4 Delete the local copy of the block chain. There is no image in the picture that appears called restore wallet you provided in your blog link. I wonder if I am the only one experiencing this trouble.

Qtum

sr. member

Activity: 722

Merit: 259

Qtum Now Has Over 2 Million Addresses That Have Been Created!

Qtum Telegram Channel: https://t.me/qtumofficial
Qtum Twitter: https://twitter.com/Qtum
Qtum Facebook: https://www.facebook.com/QtumOfficial
Qtum Reddit: https://www.reddit.com/r/Qtum

JB395

newbie

Activity: 21

Merit: 0

Quote from: efemtekem on September 02, 2020, 07:35:17 AM

Currently, my coins are showing in my wallet, but I cannot actively send them to the stock exchange or to another wallet. The reason is because of the hard fork. I had previously restored my wallet for adverse situations. But after the update, I cannot transfer to another place in my wallet. After that, I reloaded the wallet on the 64 processor computer and when I do the restore wallet in the new wallet, only transactions are coming. My coin is 0 on the 64 bit processor, but there are amounts on the 32 bit processor, which is my old computer. I cannot find a way to transfer these coins to the stock market or elsewhere. As I said, my wallet has a .dat file.

Qtum had a manditory hard fork to Qtum Core wallet version 0.19.1 on August 28. This hard fork added offline staking protocol to mainnet.

Wallets that were not updated to version 0.19.1 by block 680,000 would show missing transactions, block reward problems, etc.

The recovery is basically 1) Update to version 0.19.1, 2) delete the local blockchain and resync the whole thing 3) run the zapwallettxes=2 command on startup. This blog gives more details for Windows wallets https://blog.qtum.org/hard-fork-special-windows-2c8febdbcd43

Topic: [ANN] (QTUM) - A Scalable Smart Contract Platform w/ Proof of Stake - page 8. (Read 525257 times)