Skip to content

Merge with Coinzen-Devcoin 0.9.2 and Bitcoin 22.0.0 (Bounty: 100M DVC) #73

Open

Description

@DevElCuy

There is a more up to date version of Devcoin that was contributed by @sidhujag

https://github.com/coinzen/devcoin0.9.2MM/blob/master/src/clientversion.h

The reported version of current official devcoin is 0.8.5

https://github.com/devcoin/core/blob/master/src/clientversion.h

So we are still very far

Activity

  1. changed the title [-]Merge with Coinzen-Devcoin 0.9.2[/-] [+]Merge with Coinzen-Devcoin 0.9.2 and Bitcoin 0.18.1 (Bounty: 100M DVC)[/+] on Oct 30, 2019
  2. DevElCuy commented on Dec 13, 2021

    @DevElCuy
    ContributorAuthor

    Devcoin 0.9.2 is older than OpenSSL 1.1.x, it means that a lot of fixes we already figured out would need rework. For example:

    https://github.com/devcoin/core/pull/45/commits

    Also, there are many old branches left by @belovachap and @sidhujag. Branch belovachap_devcoin0.9.2 was merged into devcoin0.9.2, yet it has one extra commit worth to rescue: 17d3bb3. Branches belovachap_1.0.0dev and 1.0.0dev are experimental versions of devcoin0.9.2, we can safely ignore them.

    Additionally, commits at devcoin0.9.2MM are very important, because they show the steps to convert bitcoin into devcoin, we can learn a lot from @sidhujag's work.

    Last but not least, from BIP 173 (Bitcoin 0.16.0) wallets have bech32 address format set by default, it should be set back P2PKH format for Devcoin.

  3. DevElCuy commented on Jan 15, 2022

    @DevElCuy
    ContributorAuthor

    For the record, Devcoin Core 22.0.0 is being worked into branch 22.x, so we need to rename this issue

  4. changed the title [-]Merge with Coinzen-Devcoin 0.9.2 and Bitcoin 0.18.1 (Bounty: 100M DVC)[/-] [+]Merge with Coinzen-Devcoin 0.9.2 and Bitcoin 22.0.0 (Bounty: 100M DVC)[/+] on Jan 15, 2022
  5. added 8 commits that reference this issue on Jan 19, 2022
  6. 44 remaining items

  7. added a commit that references this issue on Mar 11, 2022
  8. DevElCuy commented on Mar 11, 2022

    @DevElCuy
    ContributorAuthor

    @cpsilent, @Traxo7, I just pushed new code with VERY important changes, please clone a fresh copy and perform the build again

  9. Satoshi0x commented on Mar 31, 2022

    @Satoshi0x

    Ok I tried and got so close. SO CLOSE. But somehow fudged the ending. Will attempt again tomorrow on my pathetic tech brain with a lil college try :)

  10. Satoshi0x commented on Apr 2, 2022

    @Satoshi0x

    my first 22.x Devcoin Core address: 1Kq7cdCaazPc6da5J2xktoiPZjxFMio6Wb
    image

  11. cpsilent commented on Apr 9, 2022

    @cpsilent

    @cpsilent, I did try to send 1 Devcoin to your address, it worked after a second try:

    Status: 1/unconfirmed Date: 24 Feb 2022 02:25 To: 15j7DZWayaieBxkfoDpMRrKgAA7GMpqiWj Debit: -1.00000000 DVC Transaction fee: -1.28500000 DVC Net amount: -2.28500000 DVC Transaction ID: aeb86b90db3c956fd4f9cdaa759d2a40a61885dd2923b34dafda01a661f38a03 Transaction total size: 257 bytes Transaction virtual size: 257 bytes Output index: 0

    You can try to resend your transactions the following way, open port 52333 in your VM, run the old devcoind (0.8.x) on your VM, wait for it to sync, then start your 22.x wallet with a command like this:

    $ devcoind-qt -connect=IP #IP is your VM's IP address, make sure your host has access to your VM's port 52333
    

    Then on your QT wallet, open the console an run:

    sendrawtransaction 01000000019da6d652c132aac486bc00b35479c1d9cfb0f09b0fc4f6d88c06033eabc15c50000000008a473044022030c74a7c193fa89fb9e4f95766b06f3fa7d4319957d87a79210ca86b527e2efb022058d89cc7bd562173c848bcf91a4fd75a0c058b1b176ff66bfdd9aa926ebf51f10141048cf44c288cf896b58fdc817400f0bd3cc34528d18202087e99ee1e71361ddabce5336167489aa0ff9dc7a545689704da2d5bd027696da350c06ce370c64f1b57feffffff0280077184000000001976a91433d729b0c8fa33701e18ef33b22039e23b402a3288ac603f3885110000001976a91407ae9392174665492256b360fb8ed3533c6f102088aca6b50700
    

    sendrawtransaction will manually broadcast the given transaction to the remote nodes. In this case, your wallet is connecting exclusively to the IP you provided via -connect. If you get any error from sendrawtransaction, please report here

    Sorry for the long delay. I successfully pushed the transaction using your method above described. However, to take it out of the VM wallet, I had to do the same, this time connecting to the old client coexisting in the VM. So, I can confirm the wallets aren't connecting to the nodes by themselves, only using the old client.

    Here is the obligatory caption
    Screenshot_20220409_162339

    @cpsilent, @Traxo7, I just pushed new code with VERY important changes, please clone a fresh copy and perform the build again

    I did compile the new version, but the result was the same. Is it in another branch? I used the command git clone --branch 22.x https://github.com/devcoin/core.git to retrieve the new code. I feel we are closer now!!! Again, I'm so sorry for the delay!

  12. DevElCuy commented on Apr 10, 2022

    @DevElCuy
    ContributorAuthor

    @cpsilent, great news! Let me answer point by point:

    1. The actual bug is outgoing transactions not being included in new blocks, I don't know exactly why
    2. What we know is that the new wallet is able to connect to existing 0.8.x and 22.x nodes, and to sync with the blockchain
    3. Sometimes outgoing transactions work, sometimes doesn't. It might be due to some miners rejecting transactions generated from 22.x wallets, if so that miner should be running a very old version of Devcoin

    If my hypothesis is correct, things should improve once we have at least one miner supporting 22.x. In the mean time we can't officially release the new wallet.

  13. cpsilent commented on Apr 10, 2022

    @cpsilent

    @cpsilent, I did try to send 1 Devcoin to your address, it worked after a second try:

    Status: 1/unconfirmed Date: 24 Feb 2022 02:25 To: 15j7DZWayaieBxkfoDpMRrKgAA7GMpqiWj Debit: -1.00000000 DVC Transaction fee: -1.28500000 DVC Net amount: -2.28500000 DVC Transaction ID: aeb86b90db3c956fd4f9cdaa759d2a40a61885dd2923b34dafda01a661f38a03 Transaction total size: 257 bytes Transaction virtual size: 257 bytes Output index: 0

    You can try to resend your transactions the following way, open port 52333 in your VM, run the old devcoind (0.8.x) on your VM, wait for it to sync, then start your 22.x wallet with a command like this:

    $ devcoind-qt -connect=IP #IP is your VM's IP address, make sure your host has access to your VM's port 52333
    

    Then on your QT wallet, open the console an run:

    sendrawtransaction 01000000019da6d652c132aac486bc00b35479c1d9cfb0f09b0fc4f6d88c06033eabc15c50000000008a473044022030c74a7c193fa89fb9e4f95766b06f3fa7d4319957d87a79210ca86b527e2efb022058d89cc7bd562173c848bcf91a4fd75a0c058b1b176ff66bfdd9aa926ebf51f10141048cf44c288cf896b58fdc817400f0bd3cc34528d18202087e99ee1e71361ddabce5336167489aa0ff9dc7a545689704da2d5bd027696da350c06ce370c64f1b57feffffff0280077184000000001976a91433d729b0c8fa33701e18ef33b22039e23b402a3288ac603f3885110000001976a91407ae9392174665492256b360fb8ed3533c6f102088aca6b50700
    

    sendrawtransaction will manually broadcast the given transaction to the remote nodes. In this case, your wallet is connecting exclusively to the IP you provided via -connect. If you get any error from sendrawtransaction, please report here

    Sorry for the long delay. I successfully pushed the transaction using your method above described. However, to take it out of the VM wallet, I had to do the same, this time connecting to the old client coexisting in the VM. So, I can confirm the wallets aren't connecting to the nodes by themselves, only using the old client.

    Here is the obligatory caption
    Screenshot_20220409_162339

    @cpsilent, @Traxo7, I just pushed new code with VERY important changes, please clone a fresh copy and perform the build again

    I did compile the new version, but the result was the same. Is it in another branch? I used the command git clone --branch 22.x https://github.com/devcoin/core.git to retrieve the new code. I feel we are closer now!!! Again, I'm so sorry for the delay!

    @cpsilent, great news! Let me answers point by point:

    1. The actual bug is outgoing transactions not being included in new blocks, I don't know exactly why
    
    2. What we know is that the new wallet is able to connect to existing 0.8.x and 22.x nodes, and to sync with the blockchain
    
    3. Sometimes outgoing transactions work, sometimes doesn't. It _might be_ due to some miners rejecting transactions generated from 22.x wallets, if so that miner should be running a very old version of Devcoin
    

    If my hypothesis is correct, things should improve once we have at least one miner supporting 22.x. In the mean time we can't officially release the new wallet.

    Well in that case, I think is great news, then! I thought it has something to do with the wallet itself, bu let's hope your hypothesis is correct and miners begin supporting the new wallet very soon! I hope next time I won't be so distracted to help you with this much faster! Cheers!

  14. Satoshi0x commented on Apr 17, 2022

    @Satoshi0x

    I was able to receive 1 DVC on Devcoin Core from my Devcoin-Qt 0.8.9.0 beta version on April 2, 2022 and I tested a payment to myself out of curiosity from Devcoin Core 22.x running on another computer April 16, 2022 so the outgoing txn had no problem confirming quickly from my Devcoin Core 22.x build. Wondering if you want us sending anything back from 22.x to Devcoin-Qt 0.8.9.0? Not sure if that would accomplish anything so I'm not messing around just yet but I guess it would be a way to send coins out from 22.x to an older version and not just to myself?

  15. DevElCuy commented on Apr 17, 2022

    @DevElCuy
    ContributorAuthor

    @Satoshi0x, yes, we are testing transfers from the 22.x wallet. Also, worth to note that coins are transferred only if mining nodes accept a given transaction. Somehow transactions from 22.x wallets seem to be ignored by miners. It is not happening always but frequently enough to look for a fix. In the mean time 22.x is still beta

  16. Satoshi0x commented on Apr 26, 2022

    @Satoshi0x

    Just sent another from 0.8.9.x to 22.x. No problem. :P

  17. added 2 commits that reference this issue on May 19, 2022
  18. added 2 commits that reference this issue on Dec 29, 2022
  19. added a commit that references this issue on May 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions