Re: BITCREDIT | UPDATE NOW 26/08/15 | BID ON THE BLOCKCHAIN | ESCROW
As for upping the BN portion... I am not averse to the idea but we need to
1) Fully justify it and
2) Choose a reasonable number
1) Fully justify it and
2) Choose a reasonable number
I was not envisioning a large increase, as this would diminish the amount of BCR being bid for and thus decrease backing, but a token extra, maybe 18 -> 20 for example. It's not a big deal to me, and believe me I do appreciate there are more urgent matters, just thought it was worth airing the notion.
This of course will have to be implemented in the next update, i already have 6 of my work horse machines trying to solo some blocks so we get past the current fork. Unless we delay the update until Monday (allows me time to also consider some of the changes i have in mind)
Just so you know, i am struggling with the logic behind service messaging, my problem is as follows and i would like some input:-
Should i attach messages to transactions and store them on the blockchain or maintain a side channel? Should they be in the clear or encrypted? Should i reduce the length the the exact max for msg formatting or allow messages and small pieces of data to be added to the chain (one click fashion) ? Should i mandate a cost for sending messages thereby monetizing Base nodes that only offer tx and message relay service?
To soothe the nerves of some of our users , the next update may have to be a UI only update.
Also I am thinking we should go closed source after this for a while.... anyone object? What would be the best software license to use? Should I craft a new one ?
Just so you know, i am struggling with the logic behind service messaging, my problem is as follows and i would like some input:-
Should i attach messages to transactions and store them on the blockchain or maintain a side channel? Should they be in the clear or encrypted? Should i reduce the length the the exact max for msg formatting or allow messages and small pieces of data to be added to the chain (one click fashion) ? Should i mandate a cost for sending messages thereby monetizing Base nodes that only offer tx and message relay service?
To soothe the nerves of some of our users , the next update may have to be a UI only update.
Also I am thinking we should go closed source after this for a while.... anyone object? What would be the best software license to use? Should I craft a new one ?
There are different messaging categories, I think the currency-wide stuff should be verifiable at least. I have no issues with going closed source* as long as the blockchain and associated machinery remains transparent where it needs to be, but I can obviously see uses for private comms capability. I think the messaging can be subject to ongoing review, but I like the idea of a tx-like fee (going to The Great BCR Barbarous Relic Stash of course) if it's adding bytes to the chain and infrastructure costs.
Block reward halvings...i removed those in favour of the new distribution method..... do you think i should re-instate them? Or should we cme up with something more customized to suit our new distribution model?
System as it stands is fine by me, I'm just tinkering with asset backing projections.
*I could go on about this but the tl;dr version is, "NOBODY CARES, except cryptognats, and this is the cunning bunch running supposedly privacy-centric apps on proprietary OSes while blathering about how decentralised their pool-mined currency is."
eg. DASH:
Blockchain security right there
- and it's been this bad for well over a year, with 3 pools owning 90% of the hash.