NextGen Blockchain Features Proposals.

[CaptainDero]

This github issue is created to record suggestions of new features and improvements.

Please use this thread for NextGen Blockchain Features Proposals.
Feel free to include P2P, privacy, mining etc. anything related to requirement/mass-adoption/usage of futuristic blockchain like where common man and IOT devices are utilizing blockchain in day to day life with full privacy and without any hype.

Take this thread as beyond DERO, it is about futuristic blockchain.

DERO-HE is having following features right now.

DERO HE Current Features:

1. Homomorphic account based model [First privacy chain to have this.](Check blockchain/transaction_execute.go line 82-95).
2. Instant account balances[ Need to get 66 bytes of data only from the blockchain].
3. No more chain scanning or wallet scanning to detect funds, no key images etc.
4. Truly light weight and efficient wallets.
5. Fixed per account cost of 66 bytes in blockchain[Immense scalability].
6. Perfectly anonymous transactions with many-out-of-many proofs [bulletproofs and sigma protocol]
7. Deniability
8. Fixed transaction size say ~2.5KB (ring size 8) or ~3.4 KB (ring size 16) etc based on chosen anonymity group size[ logarithmic growth]
9. Anonymity group can be chosen in powers of 2.
10. Allows homomorphic assets ( programmable SCs with fixed overhead per asset ), with open Smart Contract but encrypted data [Internal testing/implementation not on this current testnet branch].
11. Allows open assets ( programmable SCs with fixed overhead per asset ) [Internal testing/implementation not on this current testnet branch]
12. Allows chain pruning on daemons to control growth of data on daemons.
13. Transaction generation takes less than 25 ms.
14. Transaction verification takes even less than 25ms time.
15. No trusted setup, no hidden parameters.
16. Pruning chain/history for immense scalability[while still secured using merkle proofs].
17. Example disk requirements of 1 billion accounts ( Assuming it does not want to keep history of transactions, but keeps proofs to prove that the node is in sync with all other nodes)

    Requirement of 1 account = 66 bytes
    Assuming storage overhead per account of 128 bytes ( constant )
    Total requirements = (66 + 128)GB ~ 200GB
    Assuming we are off by factor of 4 = 800GB

18. Note that, Even after 1 trillion transactions, 1 billion accounts will consume 800GB only, If history is not maintained, and everything still will be in proved state using merkle roots. And so, Even Raspberry Pi can host the entire chain.
19. Senders can prove to receiver what amount they have send (without revealing themselves).
20. Entire chain is rsyncable while in operation.

[Azylem]

On chain 2fa capability, to restrict transactions from a registered account(not wallet client level) would be amazing, if possible at all. If not, in the event someone's seeds were compromised, a layer to prevent a complete loss would be a huge safety perk for average users.

[Notoriousjoshyb]

1. Encrypted communications via wallet (Text messages)
2. Human readable DERO Addresses - When registering DERO address with option 4 give option to chose username (e.g send 10 DERO to joshy in stead of DERO address

[mastercyb]

Currently reliability and stability is more important for Dero than features. Successful web3 protocol requires several implementations (at least 3): python (more like testspec) and rust for performance cases.

Apart from that there were good issues rised at forum