Quote from: Cryptopotato021 on December 05, 2018, 03:17:52 AM

Please let me know if i'm correct.
I don't know if what i'm saying makes sense. This is what i've been trying to build from the past week

I afraid not. as HeRetik said above, you are going to centralize everything.

When we talk about AI, this means we are talking about a Decision Support System (DSS), not Decision System. don't go back to the idea of giving the whole consensus responsibility to the AI - this is just another kind of centralization and doesn't work.

and if you are going to work with some artificially-living nodes in your laboratory for studying something about Well-Known Algorithms, after training an entity you should let them work and never stop them in run time by any means - otherwise, you just kill your study. you need to see how many times of how much traitors could break down the consensus model and what would be their achievements. if you kill them, you will never understand your answers..

==========

BUT, instead of that, you try to use AI in enhancing the consensus protocol in run time. for example:

1- WHICH nodes would be better for my FULL/SPV node to connect? parameters: ping time, up time, etc..
2- WHAT difficulty target would fit better for the next block? parameters: distribution of hash power among pools, a disaster close to one major pool, maintenance in pools, changing regulation policies regarding to cryptocurrencies in one country, etc..
3- HOW we could arrange a format in nonce values that protect the network from selfish miners? statistically analysis of nonce values in
history of blockchains.. [I use this one in introducing BOUNCE value instead of classic nonce]
4- even WHEN will be the deadline of planning a hard fork for the network? parameters: number of nodes that follow the network, number of miners, volume of trades, destination of payments, etc..

these are living-problems that you could use DSS to better identify them..