Andreas Schildbach [ARCHIVE] on Nostr: 📅 Original date posted:2015-03-12 📝 Original message:On 03/12/2015 07:27 PM, ...
📅 Original date posted:2015-03-12
📝 Original message:On 03/12/2015 07:27 PM, Natanael wrote:
>
> Den 12 mar 2015 17:48 skrev "Mike Hearn" <mike at plan99.net
> <mailto:mike at plan99.net>>:
>>>
>>> b) "Creation date" is just a short-term hack.
>>
>>
>> I agree, but we need things to be easy in the short term as well as
> the long term :)
>>
>> The long term solution is clearly to have the 12 word seed be an
> encryption key for a wallet backup with all associated metadata. We're
> heading in that direction one step at a time. Unfortunately it will take
> time for wallets to start working this way, and all the pieces to fall
> into place. Restoring from the block chain will be a semi regular
> operation for users until then.
>
> This have been mentioned a few times before, and what I think is
> necessary is to create a common file format that can be interpreted by a
> library which all wallets can use. I see it as similar as the work to
> create libconsensus for parsing the blockchain.
I'm afraid this will never fly. Wallets are just too different and
that's a good thing! For example, by design choice Bitcoin Wallet and
bitcoinj doesn't support multiple accounts. How would it ever import
wallets from MultiBit or Mycelium?
Bitcoinj-based wallets could probably share the bitcoinj protobuf wallet
format (or whatever format we will be at the time of the "merge" – we
already have tons of requirements piling up!). This would mean bitcoinj
is the "consensus library equivalent" you were mentioning.
Published at
2023-06-07 15:31:33Event JSON
{
"id": "99b1d7b2caf1e30885f35611aae59e54f9583c3e5bfc7b9a9a60151b0b54e889",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686151893,
"kind": 1,
"tags": [
[
"e",
"bf192ab1459041905386f8a0c7782f07de04af2932326a4e49fe0d6ce14ed93c",
"",
"root"
],
[
"e",
"45c4775e14727f89271f8441c7e2af9e07601c1da3a40c4c9383c418885cf1f4",
"",
"reply"
],
[
"p",
"f14f3c71a4e63a12c842e4a50471263ada4b6cfde093fcb6588693a726b9b018"
]
],
"content": "📅 Original date posted:2015-03-12\n📝 Original message:On 03/12/2015 07:27 PM, Natanael wrote:\n\u003e \n\u003e Den 12 mar 2015 17:48 skrev \"Mike Hearn\" \u003cmike at plan99.net\n\u003e \u003cmailto:mike at plan99.net\u003e\u003e:\n\u003e\u003e\u003e\n\u003e\u003e\u003e b) \"Creation date\" is just a short-term hack.\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e I agree, but we need things to be easy in the short term as well as\n\u003e the long term :) \n\u003e\u003e\n\u003e\u003e The long term solution is clearly to have the 12 word seed be an\n\u003e encryption key for a wallet backup with all associated metadata. We're\n\u003e heading in that direction one step at a time. Unfortunately it will take\n\u003e time for wallets to start working this way, and all the pieces to fall\n\u003e into place. Restoring from the block chain will be a semi regular\n\u003e operation for users until then.\n\u003e \n\u003e This have been mentioned a few times before, and what I think is\n\u003e necessary is to create a common file format that can be interpreted by a\n\u003e library which all wallets can use. I see it as similar as the work to\n\u003e create libconsensus for parsing the blockchain.\n\n\nI'm afraid this will never fly. Wallets are just too different and\nthat's a good thing! For example, by design choice Bitcoin Wallet and\nbitcoinj doesn't support multiple accounts. How would it ever import\nwallets from MultiBit or Mycelium?\n\nBitcoinj-based wallets could probably share the bitcoinj protobuf wallet\nformat (or whatever format we will be at the time of the \"merge\" – we\nalready have tons of requirements piling up!). This would mean bitcoinj\nis the \"consensus library equivalent\" you were mentioning.",
"sig": "324503083d724ceb8548358d7729bf0bd0f6c6f859fc7881d857eade33456255775d14df8c1d868e85ef871b377d5820247238963a413148ddbdfe20fb0c184d"
}