The "making 1.21-dev great again" plan about dogecoin HOT 6 OPEN

Not in that exact form (we have Bitcoin script, not EVM) but you can probably hack together optimistic rollups today (but I wouldn't recommend it, it will be very hard to do securely.) However, if the Dogecoin network wants to adopt taproot at some point, things like TapRet and BitVM will become possible, permissionlessly. And people have only just started to look at the potential application of rollups using taproot - it's an interesting space to watch right now.

from dogecoin.

Additional finding from #3260 that I forgot to mention: contrib/devtools/security-check.py does not support arm64-darwin at this time, so we will incur some tech debt until we port in fixes from bitcoin/bitcoin. I'll add "updating devtools checks to support arm64" as an additional item under 4.

from dogecoin.

Hey Pat,
thanks for the contribution.
I am just wondering is possible dogecoin could have the same feature EIP-4844 (sharding) as TPS enhancement in the future plan?

from dogecoin.

Not in that exact form (we have Bitcoin script, not EVM) but you can probably hack together optimistic rollups today (but I wouldn't recommend it, it will be very hard to do securely.) However, if the Dogecoin network wants to adopt taproot at some point, things like TapRet and BitVM will become possible, permissionlessly. And people have only just started to look at the potential application of rollups using taproot - it's an interesting space to watch right now.

BitVM is an interesting topic and dogecoin networks would explode if that being implement.
I am not sure what X is doing right now, ppl discuss a lot X will onboard doge later.
In your opinion, how does dogecoin network react later?

from dogecoin.

What are the main goals of 1.21? Are we going to have SegWit addresses and CSV op code? I guess no taproot yet.

from dogecoin.

What are the main goals of 1.21?

The goal is updating the codebase safely to a point where we can propose protocol improvements without being scared of unforeseen consequences, like happened with 1.14's CLTV softfork. Basically, creating a baseline from which we can work linearly from there on out.

Are we going to have SegWit addresses and CSV op code?

1.21.0 should prepare for at least CSV and hopefully segwit in a slightly modified/optimized form, but do note that in earlier discussions, devs agreed that actually proposing activation for these should be done in a follow-up release, making sure that we have a 1-on-1 compatibility with the current protocol first, as the 1.21 code has significantly evolved vs 1.14. I also think today that doing this is the way to go, but am happy to discuss if anyone has a different opinion.

from dogecoin.