HTTPS support for downloading receiver files - Bounty: 10M DVC

[Traxo7]

Does daemon try to reach receiver files via https, or http? As one of the custodians is successfully listed as an IP address instead of a domain, I presumed issuing an SSL is not required (as SSL is probably not even allowed to be issued to IP addresses in the first place, or at least it might be a struggle to set up?).
In other words, should receiver file be reachable via https://... in addition to http://... ?

[develCuy]

There is support for https but the source code support is very outdated so it is not able to download anything from https. For that reason, we only list http hosts. We need to updated the source code with the most recent ssl libraries so that https can work. Also, this will allow us to host receiver files in many free public mirrors (i.e: github, gitlab, bitbacket, etc.), along the existing custodians, for ensuring resilience.

[develCuy]

UPDATE
Bounty reduced to 10M DVC see: #77 (comment)

ORIGINAL

Bounty
Since it is critical to have a reliable set of receiver files mirrors, I set a bounty of 50 million DVC from the DevFund to be distributed among all the people that work to fix this issue. The tester assigned is Qtera, which should certify the fix.

[develCuy]

Block 396000 (round 99) was found on 2019-10-26 11:07:49 and this is the record of custodians reporting sync:
(all dates are UTC)

2019-10-22 03:51:08 Custodian 1
2019-10-22 06:21:38 Custodian 2
2019-10-23 13:21:37 Custodian 3
2019-10-23 17:04:45 Custodian 4
2019-10-26 09:07:47 Custodian 5

Also Custodian 6 didn't report back, but http://devcoin.darkgamex.ch reports file creation date:

2019-10-22 05:49 Custodian 6

Custodian 7 never synced and now is offline.

I checked each mirror as custodians reported. Custodian 3 was working by then, it was not working for me on Oct 27th. If we discard Custodian 3 for not being reliable we still had 4 mirrors ready when Custodian 4 synced on 2019-10-23 17:04:45.

In conclusion, we had the custodians well setup 2 days and 18 hours in advance to round 99. Yet, we should define a safe deadline for syncing custodians.

[develCuy]

sawa reported a syncing issue with receiver 99 on https://bitcointalk.org/index.php?topic=233997.msg52886290#msg52886290

After starting the daemon, this message is displayed in the console:

Number of pages in getCommonOutputByText: 7
Insufficient identical pages in getCommonOutputByText.
Warning, writeFileText in receiver.h won't write the file:
/home/user/.devcoin/receiver/receiver_99.csv
because the text is blank.

[develCuy]

If you are willing to help, please analyze https://github.com/devcoin/core/blob/master/src/receiver.h#L160 and https://github.com/devcoin/core/blob/master/src/main.cpp

[develCuy]

I figured out the fix faster than expected, so we don't need a big reward. Still, we have to test the fix extensively and release a new version of Devcoin! For that reason I change the bounty to 10M DVC from the DevFund to be distributed among all the people that work on fixing this issue. The tester assigned is @cpsilent, which should certify the fix.

[develCuy]

@cpsilent we are going to use the testnet for this. You have to start devcoin with the -testnet param or just add "testnet=1" to your devcoin.conf file

[cpsilent]

It seems opening the wallet with the testnet parameter was unable to sync the blockchain.

I used this guide to compile it: https://steemit.com/busy/@cpol/how-to-compile-your-very-own-devcoin-wallet-in-ubuntu-18-04

First, I downloaded the current source code from git using the command: git clone https://github.com/devcoin/core.git

The resulting compiled code version was this:

• Client version: v0.8.6.0-g25a7d46-beta
• Using OpenSSL version: OpenSSL 1.1.1 11 Sep 2018
• Build date: 2019-11-05 11:00:48 -0500
• Number of connections: 0
• On testnet: checked
• Current number of blocks, Estimated total blocks and last block time: N/A

As you can see in this first image, it began acquiring the blockchain at 8:21 but by 9:11 it kept stuck on 432 weeks

Then, I added my personal wallet and started it again at 9:17 but by 9:47 it remained stuck

I checked the previous compiled version (v0.8.5.1-g25a7d46-beta, 31st Oct 2019) without the testnet param and it synced properly. I waited around an hour and initiated the v0.8.6.0-g25a7d46-beta version without the testnet param and this time it synced properly. I tried also the v0.8.5.1-g25a7d46-beta version with the testnet param enabled with no blockchain syncing.

I saw that the testnet version made its own directory (testnet3) and it recreated all the files as you can see in the pictures, but it can't sync their blockchain at all. t seems there's something wrong with my testnet. I can try to compile it with docker instead but I think this has to do with something else but I'm not sure what could it be.

[develCuy]

OK, our testnet is officially broken then. Please report the issue, I'll set a 1M DVC bounty for it

[cpsilent]

Done @develCuy!

[develCuy]

Quick update, according to https://chainz.cryptoid.info/dvc/#!network we still have few nodes able to support https (version 0.8.6 and up), so we should keep waiting to mark this issue resolved:

[develCuy]

Good news! HTTPS support available in the majority of Devcoin Blockchain network:

Time to switch custodians to https

[develCuy]

Status:

• Custodians ready ... check
• New Binaries available ... check
• People updating their wallets ... in progress

[Satoshi0x]

I'm up to date and the 0.8.9.0 version -beta runs GREAT on Windows 11 for me :) Much appreciated - saw the copyrights updated to 2009-2021 Bitcoin and Devcoin Developers. We are now just one version under the March 2014 rebrand of Bitcoin-Qt to Bitcoin Core and their core dev slashing of OP_RETURN byes to 40 max. But dammit I like Counterparty. The XCP protocol is hard to get into Idon't buy BTC and I didn't see much XCP offered when it was dead since 2018. But Dogeparty reboot sure is a blast. XDP is running wild. The native protocol and anti spam ever deflationary currency of DogePartyXDP 2.0 - Fun and I would love to see us get rich on a Rare Doge collectible in honor the the crypto OGs they're finally writing about since Namecoin of all chains got its early NFT into Emblem Vault and onto Open Sea. Collectors are coming back to good old merge mined, 11 year running, SECURE, hardened, and collectible antiquities projects. Viva la Devcoin! Plus I like the old Bitcoin code base and our mods. I think Namecoin Devcoin, and for other reasons (always need side chains) IXC and I0C are gonna have the last laugh. Hard, immutable, fairly distributed, totally open source. Whenever Meta Platforms wants to take our GM currencies and metagame in to save itself leaguelly and provide Markm his users and the VR 3-D endgame tech - We can actually get on to the we told you so part of our lives! I'm optimistic!

…

On Thu, Dec 9, 2021 at 12:08 PM Fernando Paredes García < ***@***.***> wrote: Status: - Custodians ready ... check - New Binaries available ... check - People updating their wallets ... in progress — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#77 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALUVVT7GRAAFESLEXJNHIO3UQDWDNANCNFSM4JFZUAUA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[develCuy]

Full HTTPS support is finally working!

@cpsilent can you confirm that latest release is syncing beyond block 500000?

[cpsilent]

Full HTTPS support is finally working!

@cpsilent can you confirm that latest release is syncing beyond block 500000?

I opened the wallet and synced perfectly. Below there's a screen capture showing the receiver_125.csv. Can I run it differently to show you a more scientific prove? I synced the wallet before doing the screen capture, unfortunately. Maybe with a debug command or something? From my end it looks pretty fine!

[develCuy]

Thanks for reporting @cpsilent, can you confirm your DVC address for bounty payment?

[cpsilent]

Thanks for reporting @cpsilent, can you confirm your DVC address for bounty payment?

Sure thing, my DVC address is 14BL4enKz7LVbgVPQPQ3PUvETm58SA3Q8g Thank you!

[develCuy]

This is how the reward has been distributed among contributors:

Developer: 90% * 10M DVC => 9,000,000.00 DVC paid to @develCuy's address 1DogCa5wiVZJWFnFDezuw5XssoWWabijnE 3b300a84a7a01a23f0ad736e3d045f3248dfae5ca721df0447c7ac62d1ac0d6c
Tester 1: 10% * 10M DVC => 1,000,000.00 DVC paid to @cpsilent's address 14BL4enKz7LVbgVPQPQ3PUvETm58SA3Q8g 6fd7228089c6a2a6e445ba3155802c1406be43a755b34171eca49d504f66d80e