📅 Original date posted:2013-11-25
📝 Original message:Hi Christian,
Cool - thanks for posting - agree, that it would be nice to normalize
the results with block size - so divide by size and:
1. see if there is a correlation (we all presume there still is)
2. plot the delay graph as e.g. normalized to the averaged blocksize or
lets define a "standard block size" of 200kb or what ever so we can
compare the plot btw days.
Also, does the correlation of propagation times hold for transaction
sizes as well (would be ice to find the logical t0 and the constant - I
guess the interesting measure is not kb but signatures, so number of
inputs - some correlation with size though).
Best,
Michael
On 24/11/13, 17:37 , Christian Decker wrote:
> Sure thing, I'm looking for a good way to publish these measurements,
> but I haven't found a good option yet. They are rather large in size,
> so I'd rather not serve them along with the website as it hasn't got
> the capacity. Any suggestions? If the demand is not huge I could
> provide them on a per user basis.
> --
> Christian Decker
>
>
> On Sun, Nov 24, 2013 at 5:26 PM, Gregory Maxwell <gmaxwell at gmail.com> wrote:
>> On Sun, Nov 24, 2013 at 8:20 AM, Christian Decker
>> <decker.christian at gmail.com> wrote:
>>> Since this came up again during the discussion of the Cornell paper I
>>> thought I'd dig up my measurement code from the Information
>>> Propagation paper and automate it as much as possible.
>>
>> Could you publish the block ids and timestamp sets for each block?
>>
>> It would be useful in correlating propagation information against
>> block characteristics.
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
Michael Gronager [ARCHIVE] /
npub1nc…gw452
2023-06-07 15:09:58
in reply to nevent1q…gkfh
Author Public Key
npub1nc78dlt7hp3v5dl32qu3m678h2j0ss374glcjnz8df75xcx7ngpq4gw452Published at
2023-06-07 15:09:58Event JSON
{
"id": "0fb982772de5e979fdc1c549679360d63898ba64c2f9878f48c6359a08f20a2d",
"pubkey": "9e3c76fd7eb862ca37f150391debc7baa4f8423eaa3f894c476a7d4360de9a02",
"created_at": 1686150598,
"kind": 1,
"tags": [
[
"e",
"7fa6a2e0efa14d8aeeb1a4dbc09cbf6ae754b6c189c2763219e92dbd654934bb",
"",
"root"
],
[
"e",
"9627d33243e6a12c82f626c840d9111eae17421b3a26af7fa1333c3041a206d8",
"",
"reply"
],
[
"p",
"72cd40332ec782dd0a7f63acb03e3b6fdafa6d91bd1b6125cd8b7117a1bb8057"
]
],
"content": "📅 Original date posted:2013-11-25\n📝 Original message:Hi Christian,\n\nCool - thanks for posting - agree, that it would be nice to normalize\nthe results with block size - so divide by size and:\n1. see if there is a correlation (we all presume there still is)\n2. plot the delay graph as e.g. normalized to the averaged blocksize or\nlets define a \"standard block size\" of 200kb or what ever so we can\ncompare the plot btw days.\n\nAlso, does the correlation of propagation times hold for transaction\nsizes as well (would be ice to find the logical t0 and the constant - I\nguess the interesting measure is not kb but signatures, so number of\ninputs - some correlation with size though).\n\nBest,\n\nMichael\n\nOn 24/11/13, 17:37 , Christian Decker wrote:\n\u003e Sure thing, I'm looking for a good way to publish these measurements,\n\u003e but I haven't found a good option yet. They are rather large in size,\n\u003e so I'd rather not serve them along with the website as it hasn't got\n\u003e the capacity. Any suggestions? If the demand is not huge I could\n\u003e provide them on a per user basis.\n\u003e --\n\u003e Christian Decker\n\u003e \n\u003e \n\u003e On Sun, Nov 24, 2013 at 5:26 PM, Gregory Maxwell \u003cgmaxwell at gmail.com\u003e wrote:\n\u003e\u003e On Sun, Nov 24, 2013 at 8:20 AM, Christian Decker\n\u003e\u003e \u003cdecker.christian at gmail.com\u003e wrote:\n\u003e\u003e\u003e Since this came up again during the discussion of the Cornell paper I\n\u003e\u003e\u003e thought I'd dig up my measurement code from the Information\n\u003e\u003e\u003e Propagation paper and automate it as much as possible.\n\u003e\u003e\n\u003e\u003e Could you publish the block ids and timestamp sets for each block?\n\u003e\u003e\n\u003e\u003e It would be useful in correlating propagation information against\n\u003e\u003e block characteristics.\n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e Shape the Mobile Experience: Free Subscription\n\u003e Software experts and developers: Be at the forefront of tech innovation.\n\u003e Intel(R) Software Adrenaline delivers strategic insight and game-changing \n\u003e conversations that shape the rapidly evolving mobile landscape. Sign up now. \n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=63431311\u0026iu=/4140/ostg.clktrk\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e",
"sig": "9bb3476b9f335d620511bbe4562183f7d07be68650df42a82535894d6ecf79ea44d2cffa75df7dd6bf817b5ecd163b3750f9c65e7c96023ab9147d42ba690e89"
}