<<  >> (p.2)
    Author Topic: The economics of generalized bitcoin  (Read 8168 times)
    appamatto
    Jr. Member
    *
    Offline Offline

    Activity: 36
    Merit: 17


    View Profile
    December 09, 2010, 03:50:36 PM
     #21

    Thanks for the backup. :p

    Yes, I think that the different bit-apps should be as orthogonal as possible, both to each other and to the "uber-chain" of BitX.

    Honestly, bitcoin may not be the killer app for the block chain platform.  If this is the case then we run the risk of a more popular app leaving bitcoin in the dust, and then having someone incorporate a currency platform into that app, thereby dwarfing the bitcoin block history and popping the bubble.

    That's why I think it's essential to "bind the fates" of the various bit-apps together in a single BitX "uber-chain" that can provide mutual protection for bit-apps like bitDNS and bitcoin as well as easily foster new apps.

    you seem to be suggesting that somehow there would be a general "bitx" chain, which all the different apps use, and thus there's no fragmentation of cpu power. sounds theoretically nifty... but how would you achieve that? the point of bitcoin is that it makes it expensive, and verifiable, to insert data into the chain. if you have a separate chain that doesn't actually have any data in it... then how do you tie the 'apps' into it? it seems that you have not offered even an inkling of an approach that would make it possible? or am i wrong and i missed something in the upstream post?

    This was touched upon in the original mega-thread for BitX, but it's worth restating here simply.

    Basically a BitX block looks something like this:

    <hash of previous block (BitX backlink)>
    <hash of bit-foo name> <hash of bit-foo block> <bit-foo backlink>
    <hash of bit-bar name> <hash of bit-bar block> <bit-bar backlink>
     ... and so on for each bit-app ...
    <timestamp>
    <nonce>

    Notice that no app-data is present in the actual BitX block.  The app blocks are separate although probably are distributed in the same way as the BitX blocks.

    So I need to answer for you: where are the multiple chains, and how are blocks in each accepted/refuted?

    The BitX chain is straight-forward although a key observation here is that BitX blocks should never be rejected for bit-app reasons, i.e. a client should be able to accept/reject a BitX block without ever downloading app blocks.  This is how bitcoin for example operates without ever needing to know about bitDNS data, other than a couple hundred bytes of metadata.  BitX blocks can be rejected only if they have a bad timestamp, fail to meet difficulty criteria or have some other formatting problem.  Oh, and there is an additional restriction that only one new app be created per block, to prevent spam in the chain.

    The bit-app chains aren't really the domain of concern for BitX.  BitX simply provides three fields that can be used by apps to do bit-app-like things.  The (current) suggestion is that the bit-foo backlink be a hash of the BitX block which contains the head of the last valid bit-foo app chain.  An alternative is for this field to simply be an integer which is the offset in the chain from the current BitX block, indicating the same thing.  In any case this allows bit-apps to form their own linked lists with their own accept/reject rules.  Rejection for a bit-foo means pointing further back in the BitX chain to the last sane bit-foo entry.  Rejection for a bit-app does not entail rejecting the current BitX head itself.

    Conceptually you have a single BitX chain with several bit-app chains weaving in and out of it.  Generating a BitX block will then allow you to generate a bitcoin block, a bitDNS block, a bit-foo block, etc.

    That's the protocol.  In terms of the likely market behavior of this system, I think the most powerful incentive is toward participation in meaningful bit-apps; It costs almost nothing to generate bitDNS names while you are generating bitcoin, with a large possible payoff.  The earlier you are in adopting new bit-apps, the more you stand to gain as a miner.

    The principle behind BitX is to provide the smallest possible block chain kernel to support decentralized but mutually-beneficial bit-app development.  This, in my opinion, is the only way to ensure success given that none of us may have already thought of the killer bit-app yet; it may be neither bitDNS nor bitcoin.
Page 1
Viewing Page: 2