Cryptoconditions is only compatible with transparent transactions and hence is not compatible with HUSH nor DRAGONX. Because the code technically supports it, it slows down compiling and syncing and increases memory usage of HUSH+DRAGONX. It also is likely related to a build system bug where parallel builds sometimes fail due to a race condition.
It would still be usable by HAC's with optional privacy but is unmaintained and untested and has no GUI. Since our main focus is full privacy blockchains, it will be deleted.
A lot of CCs have already been deleted, this issue is to track completely removing it from our codebase.
Cryptoconditions is only compatible with transparent transactions and hence is not compatible with HUSH nor DRAGONX. Because the code technically supports it, it slows down compiling and syncing and increases memory usage of HUSH+DRAGONX. It also is likely related to a build system bug where parallel builds sometimes fail due to a race condition.
It would still be usable by HAC's with optional privacy but is unmaintained and untested and has no GUI. Since our main focus is full privacy blockchains, it will be deleted.
A lot of CCs have already been deleted, this issue is to track completely removing it from our codebase.
I have run into some issues where some dpow code and also opreturn_burn RPC rely on some code in the src/cc/ directory so things will be "interesting" to fully remove.
I have run into some issues where some dpow code and also opreturn_burn RPC rely on some code in the src/cc/ directory so things will be "interesting" to fully remove.
This is close to being complete. There are a few CC files left but the code inside of them is actually used by non-CC code.
The main goal was to remove the dependency on libcryptoconditions, which is done in the duke branch. Currently the duke branch has 137K lines deleted compared to the dev branch 😅
This is close to being complete. There are a few CC files left but the code inside of them is actually used by non-CC code.
The main goal was to remove the dependency on libcryptoconditions, which is done in the `duke` branch. Currently the `duke` branch has 137K lines deleted compared to the `dev` branch :sweat_smile:
duke
Cryptoconditions is only compatible with transparent transactions and hence is not compatible with HUSH nor DRAGONX. Because the code technically supports it, it slows down compiling and syncing and increases memory usage of HUSH+DRAGONX. It also is likely related to a build system bug where parallel builds sometimes fail due to a race condition.
It would still be usable by HAC's with optional privacy but is unmaintained and untested and has no GUI. Since our main focus is full privacy blockchains, it will be deleted.
A lot of CCs have already been deleted, this issue is to track completely removing it from our codebase.
I have run into some issues where some dpow code and also opreturn_burn RPC rely on some code in the src/cc/ directory so things will be "interesting" to fully remove.
This is close to being complete. There are a few CC files left but the code inside of them is actually used by non-CC code.
The main goal was to remove the dependency on libcryptoconditions, which is done in the
dukebranch. Currently thedukebranch has 137K lines deleted compared to thedevbranch 😅dukebranch is merged todev, calling this done