BIP20160109 -implemneting decentralized masternodes in bitcoin to auto-blocksize

[prgiorgio]

prgiorgio BIP 20160109   :

soft proposals:
- complete the pruning so that a full pruning node can
a) use the wallet    
b) start validating transaction not from the begninning but
from other full pruning nodes downloading only UTXOs and actual minimal (last 288) blocks

- find a way to remunerate full nodes so that they will grow in number to secure the full node network,
actually not growing

- find a way miners can only operate in a p2pool mode (lik no centralization also in the worst scenario of 1 super pool)

- implement auto scaling block size every 14 days like difficulty, based on last three months size+25% WITH ALSO a hard maximum block size limit calculated so that 5 minutes is the maximum time that the 10% percentile of the slowlest nodes takes to verify and relay a block (anonymous statistics decentalized by the masternode distributed network).


optional
- implement masternode instant transactions (like dash masternodes) to lock from double spend even without a green address but in decentralized way
- implement node remuneration (example like dash masternode coinjoin mixing) to remunerate masternodes

[prgiorgio]

Interessante, soprattutto creare una remunerazione per i full node... con magari un minimo di BTC sopra...

"Interesting, creating a remuneration for full nodes, with a minimum of BTC on them".

YEs, that's what Dash guys alredy did and implemented (Dash is an alt currency),
that could be evolved and ported into btc (that will be an hard fork anyway).
May be a minimum of 100 units to operate the masternode in btc?

[Libertario]

Up!
Very interesting!
We want reward (remuneration for our node and full node), we want more decentralization!!!

[prgiorgio]

eheh,
some one asked me via chat:
'how to do the things you wuold like to be implemented'?

the answer is:
with a masternode-dash-like structure (dash is an altcoin),
that takes care of making distributed statistics on slowest nodes,
so that the block size limit can be auto adapted to the internet worlwide network speed.

- implement auto scaling block size every 14 days like difficulty, based on last three months size+25% WITH ALSO a hard maximum block size limit calculated so that 5 minutes is the maximum time that the 10% percentile of the slowlest nodes takes to verify and relay a block (anonymous statistics decentalized by the masternode distributed network).

:- )

[indstove]

Well, is this similar kind of thing with the recent RBF discussions going on.