ð
Original date posted:2018-02-19
ð Original message:Real quick (I've received some off-list replies and do plan to respond to those), want to be clear: this thread is not meant to be interpreted as a proposal to modify Bitcoin (it is not a BIP), it is just, exactly as the subject says, some thoughts I had that I hadn't seen expressed elsewhere, that I felt like sharing, in case they are at all useful/interesting to anyone.
Cheers,
Greg
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
> On Feb 19, 2018, at 12:10 AM, Ryan J Martin <rjmarti2 at millersville.edu <mailto:rjmarti2 at millersville.edu>> wrote:
>
> To be frank, this kind of thing would be better off attempted as a fork to a new coin. Changing the max number of coins, the block reward, the difficulty algo, mining policy and protocol is going to be a non-starter. Also, what are the proposed quantifiavle benefits from removing timestamps? How would this be done at the protocol level? Are these other changes related to removing timestamps/rationale for other supply changes?
>
> Regards,
> Ryan J. Martin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180219/e9eb9acd/attachment.html>;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180219/e9eb9acd/attachment.sig>;
Tao Effect [ARCHIVE] /
npub1r0âŠvdpg3
2023-06-07 18:10:57
in reply to nevent1qâŠ97qh
Author Public Key
npub1r0g954grld59fuphzsypmuuhpdunq67f729afmp44h2mxvth2hts4vdpg3Published at
2023-06-07 18:10:57Event JSON
{
"id": "83dd1805328a9f8b16784dddc2d7fc8326e28a48d9785b712188459bd3197c21",
"pubkey": "1bd05a5503fb6854f03714081df3970b79306bc9f28bd4ec35add5b3317755d7",
"created_at": 1686161457,
"kind": 1,
"tags": [
[
"e",
"33426837e4385de326988d65d4b12c529d51e1b81c10e509c6e1e5a5e31e15ce",
"",
"root"
],
[
"e",
"72897b8b9722b7bf7051298d2f5d8bd5434611e0ed652676ba9026bd2fc1a081",
"",
"reply"
],
[
"p",
"fc8485cced5687dc244c3a18a80e5e7ea37064be96e1ab7c4862d782b8fbc9aa"
]
],
"content": "ð
Original date posted:2018-02-19\nð Original message:Real quick (I've received some off-list replies and do plan to respond to those), want to be clear: this thread is not meant to be interpreted as a proposal to modify Bitcoin (it is not a BIP), it is just, exactly as the subject says, some thoughts I had that I hadn't seen expressed elsewhere, that I felt like sharing, in case they are at all useful/interesting to anyone.\n\nCheers,\nGreg\n\n--\nPlease do not email me anything that you are not comfortable also sharing with the NSA.\n\n\u003e On Feb 19, 2018, at 12:10 AM, Ryan J Martin \u003crjmarti2 at millersville.edu \u003cmailto:rjmarti2 at millersville.edu\u003e\u003e wrote:\n\u003e \n\u003e To be frank, this kind of thing would be better off attempted as a fork to a new coin. Changing the max number of coins, the block reward, the difficulty algo, mining policy and protocol is going to be a non-starter. Also, what are the proposed quantifiavle benefits from removing timestamps? How would this be done at the protocol level? Are these other changes related to removing timestamps/rationale for other supply changes?\n\u003e \n\u003e Regards,\n\u003e Ryan J. Martin\n\u003e \n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180219/e9eb9acd/attachment.html\u003e\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: Message signed with OpenPGP\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180219/e9eb9acd/attachment.sig\u003e",
"sig": "61b671ecc31d75ad11cf0ef9b3eb297bf433aa47fb4abc75b1cfbadc13df55319d5c8e7e71d75be90ed74d422e39e1d6862695e1f3fe9fc106d17bbab6c6fa51"
}