dogecoin VS libdohj

imho you need to know the tx size and then calculate it: https://github.com/dogecoin/dogecoin/blob/master/doc/fee-recommendation.md

This effects us right now see https://github.com/dogecoin/dogecoin/discussions/2264 where the dogecoin devs are proposing 1.21 as a softfork upgrade. Not only do softforks in general have the risks I just mentioned, but the devs are intending to introduce segwit either in 1.21 or subsequently. Segwit can and will be gamed just like taproot has been. IMO we need to set dogecoin on a straightforward path of casting aside segwit and lightning and pursuing transaction throughput by reducing blocktime and increasing blocksize. Let the devs know how you feel about segwit and following bitcoin's (risky) development path in general, in the github link above.

Probably this depends on what you want to do. It is my understanding that the devs use regtest to check all functions after changing some of the core wallet's code (all local). This will create a new blockchain where you can do all the test from (https://github.com/dogecoin/dogecoin/tree/master/src/test). But I am also not sure about this (;

Absolutely, because what we're doing is trying to catch up on 4 years of very intensive Bitcoin development. Recent Bitcoin Core versions (such as the base we use for 1.21) are really good software and per the small discussion we had on GitHub, we would ideally wish this to become a stable base for Dogecoin to build further upon in the future. This is good because once that is done, contributors will no longer see all their work deleted with every major release.

Anyway, to give a recent and practical example: when I was re-testing Victor's wallet compatibility fix that we merged last week, I found that the regtest network in 1.21 was much more incompatible with 1.14 than I expected based on comments made in previous PRs and we cannot automatically test for regressions cross-version until it is fixed.

Unfortunately I hadn't thought this through when we worked on 1.10 back in 2015 (I too am a dumb) so now we're having it custom for dogecoin... Many wallets however are suspected to NOT implement Dogecoin's prefixes and just use Bitcoin prefixes, which should work fine.

I think the last time I saw Comic Sans used in any software as a main font was when I compiled dogecoin[1]. Can't remember any before that.

[1] https://github.com/dogecoin/dogecoin

After that - anything. I promised before that as we get closer to a release, I will re-propose a softfork plan and I intend to keep that. It will NOT be the same plan that I posted 16 months ago because reality has changed quite a lot since then, but I will try to make it a good and open plan, that - in the tradition of the plans I've been putting out since a year or so now - furthers decentralization and operator freedom.

#2758 that removes a potential spam problem in the p2p protocol needs testing with libdohj to make sure that we don’t accidentally exclude wallets built upon that library from the network.

The technical problem to solve is to have a means to translate implicit on-chain transaction events to webhook calls (tx received, tx confirmed, # confirmations, tx got reorg'd). For my pilot, I used block.io because /u/kindoge has made a very reliable webhook mechanism so I didn't have to code that from scratch. If you need a full sovereign solution, I think that besides doing it on Dogecoin Core, something can be built into dogecoin-spv-node (js) or create a custom thing with libdohj (java) (perhaps until /u/xanimo-net is further along with libdogecoin and gives you a php sdk 😁).

Pruning works well, you don't need any patches for that and can just use 1.14.5. You can also use dogecoin-node-spv or build something with libdohj for an spv client.

Multidoge is depreciated though, someone should build a new light wallet based on https://github.com/dogecoin/libdohj - that's a nice starter project because that offers a lot of the harder crypto already solved.

Libdohj the backbone for many Java implementations of Dogecoin wallets, based from this. Shows not only work but a full pushed update less than two weeks ago.