Search content
Sort by

Showing 3 of 3 results by erroltsau
Post
Topic
Board Development & Technical Discussion
Re: What do you think about BIP 177
by
erroltsau
on 30/05/2025, 08:47:31 UTC
I oppose BIP-177 due to its potential for confusion, high implementation costs, and cultural impact. I believe this change introduces significant risks without clear benefits. Using "satoshi" as the default unit in software is a simpler, more practical solution that respects Bitcoin’s heritage and meets user needs.

1. Potential for Confusion: The proposed "bitcoin" unit is too similar to the existing "Bitcoin (BTC)", which could confuse users, especially newcomers. Most wallets, exchanges, and users already use "Bitcoin (BTC)" or "sat" consistently. Changing the terminology may lead to errors in transactions or misunderstandings across platforms.

2. Compatibility and Cost: Redefining the unit requires updates to wallets, exchanges, and other infrastructure, which could be costly and disrupt existing systems. This seems unnecessary when user interfaces can already address small transactions by displaying "satoshi (sat)" as the default unit.

3. Cultural Significance: The satoshi unit honors Bitcoin’s creator, Satoshi Nakamoto, and has become a valued part of Bitcoin’s culture. Redefining it as "bitcoin" risks diminishing this tradition, which holds symbolic importance for the community.

4. Alternative Solution: I recommend promoting satoshi as the default display unit in user interfaces instead of altering the protocol. Many wallets (e.g., Phoenix, Wallet of Satoshi) already use "satoshi" as the default unit for small transactions, particularly in Lightning Network contexts. This approach is effective, requires no protocol changes, and avoids compatibility issues.
Post
Topic
Board Bitcoin Technical Support
Re: Is a newly migrated Wallet contain the same private key for re-funding ?
by
erroltsau
on 19/03/2024, 22:04:56 UTC
Yes, it is functional, but it is a complex solution that requires a deep understanding of the wallet. It is best suited for advanced users.

Thanks for your solution, I need to learn more.
Post
Topic
Board Bitcoin Technical Support
Re: Is a newly migrated Wallet contain the same private key for re-funding ?
by
erroltsau
on 19/03/2024, 14:54:40 UTC
You can use
Code:
migratewallet
to migrate your legacy wallet (BDB) to HD wallet.

1. Bitcoin Core Wallet should NOT be in prune mode. Per my test, it will crash if the wallet is in a prune mode.
2. Open Bitcoin Core Wallet and import your data
3. run command
Code:
migratewallet {legacy_wallet_name} {the wallet's password}

Wait for a few minutes, it's done.

If you have some private keys to import, my idea is to import them to a legacy wallet with a lower version Bitcoin Core Wallet, e.g. V24, then migrate the legacy wallet in V26.


I read this Subject from OP digital_mine: https://bitcointalk.org/index.php?topic=5475186.0

And now I am running Bitcoin Core V26 with a wallet created on V22. Let's call it OutletWallet.
Everytime I open OutletWallet I get a warning message:
Code:
the legacy wallet type is being deprecated...migrate...
So, I proceeded with Migrate Wallet so that I can function with an uptodate Wallet on V26.

I still have my Paper Wallet with Public/Private key and QR code printed way back when I printed that sheet.

Will the new migrated OutletWallet still receive funds when I will utilize my QR code paper wallet to fund again ?

If I want a new paper document to backup my new OutletWallet, what informations should be printed so that I can retreive my funds in case of possible problems with computer or else ?  Is there a function in the Console that I can utilize to show such information ?
Thanks