Topic: discussion - multiple variable blockchains managed by single client. (Read 997 times)

i posted this in the Project Development forum, but moved it here because it makes more sense.
follows an idea i've been considering for a couple of weeks. it sprung from consideration of data transmission and how it could be handled.


MALLEABLE BLOCK CHAINS AND MULTIPLE BLOCK CHAIN CLIENT

There are uses where a large block chain is un-necessary. entries may not even need to last 24 hours.
example.
data, send data. when received the data nor information no longer needs to stay in chain.

There are uses where currency aspects are un-necessary. the "coin" may be best shared rather than sent, or the notion of sending value is not appropriate.
example.
file sharing. maybe acheived in one way by importing an address rather than sending a coin.
or when considering torrenting, the network exists independent of currency.

There are uses where it maybe appropriate to single use a blockchain, then abandon it.
example.
private data share. using a private network all information is dependent on the network existent, once it is no longer used it can be deleted.

----

HOW

imagine a light mother block chain, it's general purpose is to carry private and broadcast public information regarding children blockchains.

the client communicates with extra blockchains through creation/destruction addition/removal. it may even be useful to create neutered clients that can only interact with one such chain.

upon creation, children blockchains can be given various parameter settings. these children can then be added to other clients upon request.

example.
private data share.
Client1 adds/creates blockchainB to required settings. Sends information via mother chain to Client2.
Client2 uses information (ip and passcode) to add blockchainB from Client1, and becomes part of child network using blockchainB.
repeat for any other Clients.

alternatively, the existence of blockchainB could be broadcast publicly and may be seen through any client. consider something similar to chat rooms where the rooms maybe publicly broadcast.

. . .

OTHER POINTS

NODES

must be creatable automatically upon creation of child network. clients will add themselves as nodes to appropriate networks.





--
an earlier version with some different aspects i posted here
http://forum.qrk.cc/thread/1870/idea-appreciate-feedback