This seems unnecessarily complicated ("don't use cannon to kill mosquito"
kind of thing). If the community were interested in a realtime hashrate
rebalancing proposal one could simply adjust difficulty at each new block
using the current method.
If faster relaxation in case of adversity is require
I accidentally replied to Luke off-list, and this was his reply to my last
message:
"But wouldn't the server be a trusted third-party in this case?
I'm thinking it's very close to being possible for an untrusted server to do
this..."
If you are okay with anyone being able to view your PaymentRequ
Our BIP just defines protocol definitions, and doesn't really dictate how
people use them (we're coming up with a new title for the BIP, by the way,
to more accurately convey that). Using our definitions as building blocks,
someone could definitely accomplish what you described. For example, Joe
Mo
Is there a way for Joe Mobile Wallet User to upload a set of N PaymentRequests
authenticated by his key to an untrusted server, which encrypts and passes
them on in response to InvoiceRequests? Or does this necessarily require the
recipient to be online?
On Tuesday, March 01, 2016 6:58:16 PM Ju
Dave Hudson via bitcoin-dev [bitcoin-dev@lists.linuxfoundation.org] wrote:
> I think the biggest question here would be how would the difficulty
> retargeting be changed? Without seeing the algorithm proposal it's difficult
> to assess the impact that it would have, but my intuition is that this i
It has been about 1 month since BIP 2 finished receiving comments, so I
believe it is an appropriate time to begin the process of moving it to Final
Status. Toward this end, I have opened a pull request:
https://github.com/bitcoin/bips/pull/350
The current requirement for this is that "the
On Tuesday, March 08, 2016 2:35:21 AM G. Andrew Stone via bitcoin-dev wrote:
> Not an unreasonable request, however while I personally respect the many
> great accomplishments of individual engineers loosely affiliated with
> "Core", Bitcoin Unlimited has our own process for documentation and
> dis
