Description

Various tests are failing or resulting in panic after cryptopq is added

Impact if not addressed

Tests needs to pass for stability of the system

Priority

On a scale of 1 to 5 (1 being most important)
2

Rationale

Enable block rewards halvening as per https://dogeprotocol.org/whitepapers/Doge-Protocol-Blockchain-Allocation-Whitepaper.pdf

Multi-fork can come in later.

Why should this feature exist?
What are the use-cases?

Implementation

Do you have ideas regarding the implementation of this feature?
Are you willing to implement this feature?

What is the priority?

(On a scale of 1 to 5, with 1 being highest priority)

Rationale

Currently, NTRU HRSS is used to secure inter-node communication. As with digital signature schemes, post quantum KEMs haven't been battle tested over time. Like SIKE, it's possible lattice based cryptography might get broken.

Why should this feature exist?
What are the use-cases?

As a mitigation till Kyber/NTRU HRSS or other KEMs are battle tested over time, the RLPX transport layer should switch to hybrid scheme using elliptic curve scheme plus post-quantum scheme (Kyber).

Implementation

Do you have ideas regarding the implementation of this feature?
Are you willing to implement this feature?

Rationale

Using proof-of-stake consensus, a votable system is required for gas limits, block time etc.

Why should this feature exist?
What are the use-cases?

This will allow a governance model for the blockchain, instead of hard-coded parameters and also make it easier to make changes at runtime instead of a hard-fork or requiring client update.

However, post any new voted change, the system should allow a period of at-least 30 days, to give time for validators to update their hardware and network to keep up with gas limit changes.

Implementation

Do you have ideas regarding the implementation of this feature?
Are you willing to implement this feature?

What is the priority?

(On a scale of 1 to 5, with 1 being highest priority)

Rationale

Complete part 2 of proof-of-stake consensus. The part 1 that was released with Testnet T2 is pretty rudimentary and does not handle slashing, proper block winner selection and so on. Automated staking contracts creation is required, it is manual for T2.

Why should this feature exist?
What are the use-cases?

Implementation

Do you have ideas regarding the implementation of this feature?
Are you willing to implement this feature?

What is the priority?

(On a scale of 1 to 5, with 1 being highest priority)

Rationale

Falcon and other PQ crypto hasn't been time tested. Just like SIKE that got broken in a classical computer, it's possible newer vulnerabilities may be found in lattice and other PQ crypto schemes.

Why should this feature exist?
As a mitigation for short term till PQ crypto proves their resilience to classical computers over a period of time, it's advisable to yse hybrid cryptography, such as requiring ECDSA+Falcon (classical+post-quantum) for signatures.

Implementation

Do you have ideas regarding the implementation of this feature?
Are you willing to implement this feature?

Rationale

Currently, the base fee for gas is hardcoded.

Why should this feature exist?
What are the use-cases?

A governance model can better help build the platform by allowing gas fee to be voted. The gas fee can be dynamically determined by allowing anyone to specify a smart contract that returns the gas fee and PoS stakes to vote and accept or reject this smart contract.

Implementation

Do you have ideas regarding the implementation of this feature?
Are you willing to implement this feature?

What is the priority?

(On a scale of 1 to 5, with 1 being highest priority)

Description

Currently, there is no end to end test system that launches a new testnet, executes various transactions etc. and reports failures.

Impact if not addressed

Without a test system, testnet creation for sake of testing is heavily manual and can take weeks to just setup an environment for each major change.

There needs to be a cloud based system that launches machines, configured ports, firewall rules etc., sets up a private testnet and executes all sorts of transactions and reports. This should preferably be nightly and triggerable from builds.

Priority

On a scale of 1 to 5 (1 being most important)

Rationale

Currently, as of T2, the block winner selection is a naive model. Something like RANDAO is required to select a winner as per the stake.

Why should this feature exist?
What are the use-cases?

Implementation

Do you have ideas regarding the implementation of this feature?
Are you willing to implement this feature?

What is the priority?

(On a scale of 1 to 5, with 1 being highest priority)

Description

The transaction metadata contains values names 'v', 'r', 's'; these are specific to ECDSA, a carry-over from the Ethereum codebase. These values can be used for public key recovery from the transaction metadata in Ethereum. These variables will be removed in forthcoming testnets because the cryptography scheme used in Doge Protocol is Falcon (for quantum resistance).

Impact if not addressed

Smart Contract tests are broken and contracts might not work as expected

Priority

On a scale of 1 to 5 (1 being most important)
2