Row 4947

Row ID: 4947 | Dataset Entry | Axioma AXP Content Repository

Content Data

This page contains data entry 4947 from the Axioma AXP content repository. The structured data below represents the complete record for this entry.

Dear all,

I hope this finds you well. Besides privacy and usage-security reasons, it is also said that an address derived from a seed that is not used at all with other addresses is way harder to hack - for instance with an advanced quantum computer. The reason is that from the moment one address derived from a specific seed is used to sign a transaction or message, more information is revealed that can help to find the seed or specific private key. What I struggle to understand is the following: From the moment you create a complete new seed only and only for generating one address (called B) to send funds to and not use it at all, the public key is already known as funds are transferred from an address A to this new address B. This information can be seen on the blockchain and a possible hacker can use the public key in order to hack the seed or specific private key.

So why is it said that using this procedure makes it way harder to hack compared to the case where at least one transaction or message going out of address B? Is it because the signature reveals more relevant information that, in combination with the public key, makes it stocastically relative easier to hack? Please feel free to also use technical terms and sources on an academic level.

Thanks a lot!

FieldValue
text Dear all, I hope this finds you well. Besides privacy and usage-security reasons, it is also said that an address derived from a seed that is not used at all with other addresses is way harder to hack - for instance with an advanced quantum computer. The reason is that from the moment one address derived from a specific seed is used to sign a transaction or message, more information is revealed that can help to find the seed or specific private key. What I struggle to understand is the followin…
label r/ethereum
dataType post
communityName r/ethereum
datetime 2024-04-24
username_encoded Z0FBQUFBQm5LakwyLWxiN0JlWWNidXZQNnF4ZmhwOHMtVmxSa2p0UERrMEZMU2F4ekZaNFA0aVJCTEdkQkhiR2dYNDlmSWhYTlZIcUl2UElRdEJPSGFld19hNEc4VFRxVVE9PQ==
url_encoded Z0FBQUFBQm5Lak9GSFRuS1lHaDRtM0o3TXVKYTFPcXZIaUVPWGt5WnFEU01fbVp5WExNWEFRMmRzdzNQUDgyU3BqZVBNQjU2T2xDLWRYOHU4aWw4RkF6QW5KckEtQU1icl91TVdkQUt1X3NwR2Y2X3Y4SHRxRTd1cExORzRoeUhNazBUZHFLTEJjaFNVYUc5SWdfUlpkWjJaR3hIcGtuTE1IVk5kTlNidVJlb0swS1RSemllQ18tazl2S3NJOWMwN1pDal9mQzhDRDdy

Raw Record

{
  "text": "Dear all,\n\nI hope this finds you well. Besides privacy and usage-security reasons, it is also said that an address derived from a seed that is not used at all with other addresses is way harder to hack - for instance with an advanced quantum computer. The reason is that from the moment one address derived from a specific seed is used to sign a transaction or message, more information is revealed that can help to find the seed or specific private key. What I struggle to understand is the following: From the moment you create a complete new seed only and only for generating one address (called B) to send funds to and not use it at all, the public key is already known as funds are transferred from an address A to this new address B. This information can be seen on the blockchain and a possible hacker can use the public key in order to hack the seed or specific private key. \n\nSo why is it said that using this procedure makes it way harder to hack compared to the case where at least one transaction or message going out of address B? Is it because the signature reveals more relevant information that, in combination with the public key, makes it stocastically relative easier to hack? Please feel free to also use technical terms and sources on an academic level.\n\nThanks a lot!",
  "label": "r/ethereum",
  "dataType": "post",
  "communityName": "r/ethereum",
  "datetime": "2024-04-24",
  "username_encoded": "Z0FBQUFBQm5LakwyLWxiN0JlWWNidXZQNnF4ZmhwOHMtVmxSa2p0UERrMEZMU2F4ekZaNFA0aVJCTEdkQkhiR2dYNDlmSWhYTlZIcUl2UElRdEJPSGFld19hNEc4VFRxVVE9PQ==",
  "url_encoded": "Z0FBQUFBQm5Lak9GSFRuS1lHaDRtM0o3TXVKYTFPcXZIaUVPWGt5WnFEU01fbVp5WExNWEFRMmRzdzNQUDgyU3BqZVBNQjU2T2xDLWRYOHU4aWw4RkF6QW5KckEtQU1icl91TVdkQUt1X3NwR2Y2X3Y4SHRxRTd1cExORzRoeUhNazBUZHFLTEJjaFNVYUc5SWdfUlpkWjJaR3hIcGtuTE1IVk5kTlNidVJlb0swS1RSemllQ18tazl2S3NJOWMwN1pDal9mQzhDRDdy"
}
Explore Dataset Explore Row

Entry Information