Row 29130

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

Content Data

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

> I don't hear Tom saying that there is only one way to build a wallet.

As I explained two here, you are correct ;-)

> I personally think that it's 100% unacceptable to say "well some apps got built so that they assume there's always a full blockchain history laying around."

I mean, its practically all (non trivial) apps and wallets that do this, so hyperboling doesn't help build understanding.

If you come up with a different way of doing things, build it and make it better than the ones you're intending to break, then obviously the problem goes away.

To me the question of why it is and will stay scalable is not to answered by the idea of throwing away history. Sorry, I see that as a premature optimization at best.

The solution lies in today's tech already:

* user-wallets only ever need to scan the blockchain once. Ever. And then only a part of it. So if they start a wallet in 2015, they can ignore all data before that point. * Wallets store state up until a certain date. this is why they only need to check for newer blocks. * Wallet state can be backed up.

And last:

* starting a new wallet and moving funds from an old wallet to a new wallet makes one able to ignore all blocks before the new wallet was created.

There is no big secret here, no big technical thing we haven't implemented yet. This all works today, it works well and it scales.

FieldValue
text > I don't hear Tom saying that there is only one way to build a wallet. As I explained two here, you are correct ;-) > I personally think that it's 100% unacceptable to say "well some apps got built so that they assume there's always a full blockchain history laying around." I mean, its practically all (non trivial) apps and wallets that do this, so hyperboling doesn't help build understanding. If you come up with a different way of doing things, build it and make it better than the ones you…
label r/btc
dataType comment
communityName r/btc
datetime 2024-05-21
username_encoded Z0FBQUFBQm5Lak1GcEpNb1BsUmRQZEZtZndmMTVaWmVPYy1nOWpuVzNiLS1HdGdHUDdNS3JGb0ZBR21ETk5BM2N2YU4tLVlqU0JCV3ctWWlhS2dPY1UtczNwZmFTQUJLdnc9PQ==
url_encoded Z0FBQUFBQm5Lak9VNUlDUldUdngzN0sxLXRHalpVTXJXMmRqUzV1VVdmRFljTnotaGNLajU3U0hocVl2SGdFV2pXeHo1R1Z4QTA3alZTS0xrbE1rU0NZcE0tcXdjQVFYUVZtczBDTVFKdTdBS2RCN1U3dTAwYjR0LVFuajBsV3hEU0ltYnp2cXFGcHNnRmg3RlJxV25uMFhld1NFZ0FnbVVNamJJVUdzVjBnZHpIMGd3eFlYbkRaRTdyVEJvQXZQVGJrY0Zqdk1pTVI5YTNFVHI4YnJQd1JKb1FWTnliUTlEQT09

Raw Record

{
  "text": "> I don't hear Tom saying that there is only one way to build a wallet.\n\nAs I explained two here, you are correct ;-)\n\n> I personally think that it's 100% unacceptable to say \"well some apps got built so that they assume there's always a full blockchain history laying around.\"\n\nI mean, its practically all (non trivial) apps and wallets that do this, so hyperboling doesn't help build understanding.\n\nIf you come up with a different way of doing things, build it and make it better than the ones you're intending to break, then obviously the problem goes away.\n\nTo me the question of why it is and will stay scalable is not to answered by the idea of throwing away history. Sorry, I see that as a premature optimization at best.\n\nThe solution lies in today's tech already:\n\n* user-wallets only ever need to scan the blockchain once. Ever. And then only a part of it. So if they start a wallet in 2015, they can ignore all data before that point.\n* Wallets store state up until a certain date.  \nthis is why they only need to check for newer blocks.\n* Wallet state can be backed up.\n\nAnd last:\n\n* starting a new wallet and moving funds from an old wallet to a new wallet makes one able to ignore all blocks before the new wallet was created.\n\nThere is no big secret here, no big technical thing we haven't implemented yet. This all works today, it works well and it scales.",
  "label": "r/btc",
  "dataType": "comment",
  "communityName": "r/btc",
  "datetime": "2024-05-21",
  "username_encoded": "Z0FBQUFBQm5Lak1GcEpNb1BsUmRQZEZtZndmMTVaWmVPYy1nOWpuVzNiLS1HdGdHUDdNS3JGb0ZBR21ETk5BM2N2YU4tLVlqU0JCV3ctWWlhS2dPY1UtczNwZmFTQUJLdnc9PQ==",
  "url_encoded": "Z0FBQUFBQm5Lak9VNUlDUldUdngzN0sxLXRHalpVTXJXMmRqUzV1VVdmRFljTnotaGNLajU3U0hocVl2SGdFV2pXeHo1R1Z4QTA3alZTS0xrbE1rU0NZcE0tcXdjQVFYUVZtczBDTVFKdTdBS2RCN1U3dTAwYjR0LVFuajBsV3hEU0ltYnp2cXFGcHNnRmg3RlJxV25uMFhld1NFZ0FnbVVNamJJVUdzVjBnZHpIMGd3eFlYbkRaRTdyVEJvQXZQVGJrY0Zqdk1pTVI5YTNFVHI4YnJQd1JKb1FWTnliUTlEQT09"
}
Explore Dataset Explore Row

Entry Information