Testing Windows builds (64-bit)

[develCuy]

This issue is exclusively for reporting issues when running the binaries (a.k.a runtime bugs).

The main issue regarding Windows is #80

IMPORTANT! 32bit support for windows is deprecated #90

[develCuy]

@cpsilent please write a guide for testing the binaries build from #80, we should warn people about making a backup of their Devcoin wallet prior to using the new untested builds. Make sure to put the warning at the very top of the document, with an eye hurting format.

[cpsilent]

@cpsilent please write a guide for testing the binaries build from #80, we should warn people about making a backup of their Devcoin wallet prior to using the new untested builds. Make sure to put the warning at the very top of the document, with an eye hurting format.

Got it! I will begin as soon as possible. I'm reading the building instructions right now!

[develCuy]

@cpsilent this issue is for reporting issues when running the binaries. Please report your issues at #80

[cpsilent]

@cpsilent this issue is for reporting issues when running the binaries. Please report your issues at #80

Done! Moved to #80

[develCuy]

Great @cpsilent! I'll help you with a patch for the 64bit build in #80 ;)

[Satoshi0x]

Everything working wonderfully. First time I've had a client report I was 3 hours behind sync only to check our (only) block explorer to see the entire chain was stuck for the past three hours at the same block. When the block explorer (https://block.d.evco.in/chain/Devcoin) began moving forward again with blocks, my wallet showed it was "synced" again. Also I dig the orange sync bar over the green from 0.8.5.1-beta 32-bit build I was using since 2018 from the devcoin.org windows downloads. No screen shot from when it happened but the sync bar said I was 3 hours behind and the top right over the txns said (out of sync). It was just waiting maybe for a new block? At the time I had 5 connections.

[Satoshi0x]

I have successfully sent transactions between my original devcoin wallet and addresses I've been using since the 32bit 0.8.5.1 beta build from devcoin.org I started using in 2018 by a process that @develCuy instructed me to do on discord. I sent a transaction to an address I created from running a clean start of the new beta 64 bit version 0.8.7.0 for Windows that develCuy linked via discord in the #general channel went working with @iroking. I then changed file names as instructed by @develCuy after I sent from my original wallet.dat using the new build to the wallet address generated in the clean build. After one confirmation I shut down the old wallet containing build "devcoin" folder in roaming and changed the name of the folder to "devcoin-bkp" - after previously running the clean build and changing the name from devcoin to "devcoin-beta" I did the opposite and then ran my clean start wallet which was renamed "devcoin" once again and the funds I sent to its native address were received that I sent from my main wallet which I had renamed "devcoin-bkp" so it wouldn't be disturbed while I was running the different wallet.dat and different chainstate from the clean start. Anyway I was able to send the funds back from the clean start wallet I received from the wallet.dat I used on multiple versions since 2018 and did so by doing this all in reverse at develCuy's request. When I went back to my regular wallet.dat with my DVC in it from all versions the funds from the clean start address built from the start clean with solely the new 0.8.7.0 beta software - safely in my original wallet.dat, and on the current 0.8.7.0 beta wallet software. Cool magic. I've attached logs from the here is the transaction I sent out from my original wallet.dat to "zero-eth" labeled p2pk DVC address generated from the clean sync I made to get that address to send to. The other is the receiving of funds back from that wallet to my main wallet.dat while running 0.8.7.0 with my original wallet.dat. I sent it to my shares address for marketing since I know that's also on github. Just to hopefully have the best chance at getting these funds back.

"Confirmed","Date","Type","Label","Address","Amount","ID" "true","2020-12-02T14:25:31.000","Received with","Marketing team","16AJsk7oiNapaUx8Mnjs5sgQWWC8zd2Vy6","149999.00","753349023ce951b41e1fa7efa76b1cc0a9de8a8c4ac5d51c812b8413bd6baad6-000" "true","2020-12-02T00:34:35.000","Sent to","zero-eth","19EHx5U9zo8CPBFHxY4VKMTirE7SR7SpiB","-150001.00","9570ef5925ee1bc632c4aa32c6c506b28e7ea20c7e63111c2897f7f75e998ef0-000"

The folders as they are named after all of that now are devcoin for my main wallet contents and the clean build is preserved as devcoin-beta, both in windows AppData >> Roaming folder path.

Both transactions are on our Devcoin explorer powered by Abe:

https://block.d.evco.in/tx/9570ef5925ee1bc632c4aa32c6c506b28e7ea20c7e63111c2897f7f75e998ef0
My payments all came from my Marketing admin address anyhow.

https://block.d.evco.in/tx/753349023ce951b41e1fa7efa76b1cc0a9de8a8c4ac5d51c812b8413bd6baad6
My payment back came from my only address generated from the clean start of the new version labeled "zero-eth"

[develCuy]

@cpsilent, based on @Satoshi0x's report #85 (comment), can you perform your own test? The idea is to send funds to a new wallet you create with the new build, then send those coins back to an existing wallet. This test validates that the new build works well with old and new wallets

[cpsilent]

I tested sending some DVC from the old wallet to a new one using the wallet's version 0.8.7.0-g25a7d46-beta. I followed an analogue route with @Satoshi0x having two directories: devold with the old wallet and devnew with the new wallet. To switch back and forth from the different wallets, I renamed the directories accordingly to devcoin, located under AppData > Roaming in Windows 10.

I sent 777 DVC plus 1 DVC transaction fee to the New Wallet address: 1JjjBKRj1gRDE2vpj1GfYQHFczxnrJs2JH

Fig. 1: Old Wallet Sent

Fig. 2: New Wallet Received

You can see such transaction in the Devcoin explorer in https://block.d.evco.in/address/1JjjBKRj1gRDE2vpj1GfYQHFczxnrJs2JH

Once received, I sent them back to the old wallet using the 1341YgXKaRCsmj4u954xr3yRkDUkXizDEF address. In this case I sent 776 DVC plus 1 DVC transaction fee back.

Fig. 3: New Wallet Sent

Fig. 4: Old Wallet Received

That transaction can be seen in https://block.d.evco.in/address/1341YgXKaRCsmj4u954xr3yRkDUkXizDEF

In conclusion, I think it was a success!

[develCuy]

We now have many users reporting the new 64bit wallet is working well. For example the following via keybase's devcoins team:

[Satoshi0x]

We now have many users reporting the new 64bit wallet is working well. For example the following via keybase's devcoins team:

Can confirm v 0.8.7.0 is working great (64 bit, on Windows 10 OS)

[develCuy]

Thanks for the heads up @Satoshi0x. We can now consider Devcoin v0.8.7.0 build an stable release. Let's see how it goes with v0.8.8.0

[Satoshi0x]

Should I try to compile binaries myself for 0.8.8.0? Can I even? No windows executable for that one, prob need real devs to run that version lol. I will look into it a bit. I'm interested in making the most up to date build run on Windows 10 (64-bit).

If you don't want me to try let me know, I can wait and run v0.8.7.0 for now.

[develCuy]

@Satoshi0x, don't worry, @cpsilent and I will do our dev stuff, I'll let you know when we have the new build ready for test

[cpsilent]

By the way the Linux wallet for 0.8.8 works amazingly! I only removed the old chain and synced my wallet from 0 and it's done!

Question: Why won't we jump directly to the most recent BTC wallet version? I was wondering about that. Thank you!

[Satoshi0x]

that's cool @cpsilent very good news too it works great

[develCuy]

@cpsilent I guess that we can merge commits from Syscoin, they closely follow latest Bitcoin development, yet I need to double check with them.